"no immediate delivery" vs. queuing
Yves Goergen <nospam.list <at> unclassified.de>
2014-04-21 10:33:41 GMT
Recently somebody misused one of the accounts on my mail server to send
out large amounts of spam. Reading the logs, it came all from a single
IP address, in a single SMTP connection.
I found the following log line:
no immediate delivery: more than 10 messages received in one connection
Do I understand it correctly that Exim decided to no longer try to
deliver e-mails on the same originating SMTP connection and report any
failures immediately, but instead blindly accept all incoming e-mails
and report each failure with a "Mail delivery failed" message in the
poor user's inbox?
That would be the exact opposite of what is recommended and good
behaviour. It leads to massive amounts of delivery error messages AFTER
the messages had been accepted for delivery. My idea was actually to not
take responsibility for any incoming message unless it is sure that it
can be delivered - which can only be known when the message has been
delivered. I don't want to sit on a queue of garbage and let the MTA
throw around error messages to who is almost always the wrong recipient.
The workaround seems to be to set the following configuration somewhere:
Where number is the maximum number of messages per connection to do
whatever with. What implications does it have? Can I set it to