Thanks to those that responded.
>On Thu, Nov 04, 2010 Victor Duchovni wrote:
>> Is there a way to tell postfix to log a more informational message
>> when smtpd_recipient_limit is exceeded? If it just logged the
>> same message it is sending to the client ("452 4.5.3 Error: too
>> many recipients") that would be helpful.
>Given ESMTP pipelining, this is not a good idea. The client will deliver
>the accepted recipients, and make a second connection (or more) connection
>to send the rest.
Hi Victor,
I don't quite understand what the problem would be with this. It's just
writing an additional bit of text to the maillog, preferably at the same
time, in the same line, it writes "sender non-delivery notification" to
the log. Could you please expand on why it is "not a good idea"? Thanks.
Also, our customer is unable to determine which, if any, of his emails
were actually sent. He just sees the "non-delivery notification" email
which lists a part of his attempts with the line "too many recipients"
after each failed email address. Since he doesn't see all the emails
he tried to send, and can't tell which (if any) succeeded, his tendency
is to resend them all, which is not good for anyone.
>On Thu, Nov 04, 2010 Will Fong wrote:
>> I have a client trying to send to more than the allowed number of
>> recipients (smtpd_recipient_limit =3D 100). On the server side the
>> only indication I see in the maillog is a "sender non-delivery
>> notification" with no explanation. This makes debugging the
>> client's problem more difficult when you are handling 20-30 million
>> SMTP requests per day.
>
>What are you trying to, debug? I thought the problem was obvious?
Hi Will,
Perhaps "debug" was the wrong term. We have customers who don't pay any
attention to the error returned. We need a way to quickly determine
their sending problem so we can explain it to them. While it's true
that postfix doesn't think of this as a problem, the customer does.
>Also, if someone was sending to that many recipients, it may be worth =
>while to use some sort of mailing list software. Would be able to track =
>bounces and such a bit better. It's a bit of a concern for you as it may =
>harm your IP reputation for delivery.
Yes, we have such available, but not all clients want the trouble (and
additional expense) of setting up a true mailing list, especially if
the sending is a one-time event.
Regarding our IP reputation, yes I would rather they use a list, but
since we are handling 20-30 million smtp requests every day, a few
hundred don't make much of a difference, so we don't insist.
Thank you both for your responses, I hope I clarified the "problem".
I would appreciate any additional thoughts or suggestions.
- Richard
