On Wed April 22 2009 17:36:56 Harsh Jain wrote:
> I am choosing the following settings to be on the safe side, so as
> to not get blocked by any ISP for being aggressive.
I would suggest, rather, that you simply not send any unsolicited bulk
email. Use industry standards for confirmation of Web or email opt-in:
exactly ONE confirmation message sent per subscription request. If you
do it all correctly (and maintain records of all confirmations), you're
not the one to blame for delivery problems; it would be the fault of
the inexperienced or incompetent or overaggressive (in filtering) site
who blocks you.
Of course, it's any site's prerogative to do so at any time, with or
without what you might consider a valid reason. You can ask to be
unblocked, but understand that it might not happen.
> - We expect to deliver around 50K mails per day.
That's fine, if as above, the list is clean. If it's dirty, it's
probably well below what a typical spammer pumps out.
> - We do not want to reattempt delivery of bounced or failed
> deliveries.
So your valued, confirmed opt-in subscribers are going to miss your
important messages, when their MX host happens to be temporarily down
or unreachable for some reason? I doubt they're going to like that, if
they were, in fact, confirmed.
> Please let me know if this won't affect us otherwise or any other
> advice.
If this doesn't hurt you, it should!
> # Be Nice
> default_destination_concurrency_limit = 1
> maximal_queue_lifetime = 0
> bounce_queue_lifetime = 0
> default_destination_rate_delay = 2s
> default_destination_recipient_limit = 1
> default_recipient_limit = 100
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
