jesse hassett wrote:
> Always. Also along with SPF its best to make sure your RDNS is correct as many people overlook that.
> Though to my knowledge gmail does not offer any whitelisting and hotmail/msn uses a pay service that requires a volume of mail out of the scope of alpha and beta stages of many companies. Yahoo AOL and earthlink are pretty easy to work with as long as you are compliant. AOL offers their feedback loops which are helpful in maintaining a good status.
well, if it was easy to get whitelisted, you understand that they will
soon be inundated...
> Any thoughts on allowing a user to remove their address form a suppression list? I like to use confirmation key sent to the address but always wonder if this might be considered by some to be violating their wish to unsubscribe. Its kind of hard when there is no list persay.
what's a suppression list?
I see no problem verifiying that the user who wants to get removed is he
who claims. but propose a human contact for people who don't understand
what it's all about.
> I always try and keep these as plain as possible but insist on a standardized footer on all site mailings that includes the unsub link. Which makes them html. Making sure the correct Mime-types are set is good for spam filtering.
there is no need for html. most "basic users" use MUAs that will make
URLs clickable even in plain text.
> This is exactly why I am looking to track the response codes on the mails. After reaching a threshold supported by business needs accounts returning perpetual 400 errors or 550s can be marked as invalid and cut down on clogging up my and others mail servers. That and so I can display to our users the status of messages used to introduce their peers to our application. Typos are of course the most common problem and should be easy to remedy if the user knows.
> How would you implement this tracking and blocking within the mail system? If I could do this without the need to integrate into my application and wait on the developers to have time, as well as the security implications of having a mailing server with database access, I would be ecstatic.
by periodically parsing logs and adding addresses to a map called with
check_recipient_access (if sendmail is used, then transport_maps should
be used instead).
>> - and of course, don't use anybody else's list. This may be hard for
>> businesses, but business is not supposed to be easy. use your
>> imagination and creativity to find ways to attract your target
> Any advice on dealing with the need to allow users to send an invitation through our site to an account we have no relationship with?
Ask the user to provide the first and last name and use these in the To
field. This helps a bit because many filters will "be happy" if the
first and last name match the user address (unlike random first/last
names found in spam).
Use a reserved display and address for the From header. Don't forgte
that MUAs "collect" addresses and will use them for address completion.
An alternative is to use the "member" address in the From header, but
this may be risky (LinkedIn do that, but they are whitelisted in many
consider providing a mailto button for those who can use their mailer
(won't work for webmailers). Chances are they are whitelisted at the
PS. Be ready to get your share of Challenge/Response scatter...
> Our registered and confirmed users are the ones initiating the mail but it of course is sourced with us. (This has been a personal issue for me at many of my jobs as it borders on spamming. But thats part of "Social Networking") I ensure that the from headers and reply-to are always clear and do not impersonate the email address of my registered users as many sites seem to do. All mail coming out of my mail server is from my mail domain and is used solely for my applications.
I don't think it's at the border of spam. Fighting spam doesn't mean
Anyway, let's stop here to avoid annoying other members. if you need
more infos, contact me offlist.