>
> Yeah, what Mark said is totally correct, the message is almost the same to
> the two million recipients, but each delivery has one recipient and
> different links to track clicks, let him/her u_n_s_u_b_s_c_r_i_b_e (my reply
> before this got bounced because it have these word so they thought I want to
> get off the list) and all those things. In each server we have a daemon that
> get all the data from database, generate each message and queue it through
> local smtp.
>
> Thank you Jeroen, the idea of changing the *minimal_backoff_time* is
> great, we should have thought about that before. Also thanks for the doc
> I'll give a look right now.
>
>
> Pedro Axelrud
> http://mailee.me
> http://softa.com.br
> http://flavors.me/pedroaxl
>
>
> On Thu, Nov 11, 2010 at 13:11, Mark Goodge <[email protected]> wrote:
>
>> On 11/11/2010 14:56, Jeroen Geilman wrote:
>>
>>> On 11/11/2010 03:14 PM, Pedro Axelrud wrote:
>>>
>>>> Hello guys,
>>>>
>>>> We have a startup with an email marketing web app, we are very rigid
>>>> with our clients to not allow spammers.
>>>> One of our client's wants to send a message to two million contacts
>>>>
>>>
>>> HOW will they be sending these messages ?
>>> That's the most important factor.
>>> If they try to maildrop 2M messages (or 2000 messages with 1000
>>> recipients each) into your postfix server, without consultation with
>>> you, things will get hairy.
>>> If they wish to send a bulk mail to 2M recipients, you probably want to
>>> tell them to implement a steady delivery mechanism on their end.
>>>
>>> There's several ways that can go; you could require that they spread out
>>> destinations over multiple messages, to spread the concurrency load.
>>> Or the exact opposite: require them to group recipients by domain into
>>> separate messages, so you can take advantage of the fact that postfix
>>> will also deliver them as one message.
>>>
>>> The right solution will probably be somewhere in the middle; but it
>>> won't require you to process and queue 2 million messages.
>>> It should be perfectly doable with about 20000 messages or so, each with
>>> 100 recipients.
>>>
>>
>> If they're running a legitimate and properly managed opt-in mailing list
>> then every message will have one, and only one, recipient, as it will
>> contain both individual unsubscribe details for that subscriber and header
>> tracking to ensure that they can identify any subscriber who mistakenly
>> reports it as spam to their ISP or where any message bounces.
>>
>> So yes, they're going to have to send 2 million messages. There's no
>> practical way round that. And if they're not following best practice for
>> opt-in mailing lists (including bounce tracking and individual opt-out
>> links), then the OP shouldn't be letting them use his mail servers as
>> otherwise, he's going to be the one getting the spam complaints.
>>
>> Mark
>> --
>> http://mark.goodge.co.uk
>>
>
>
