On 11/13/2010 07:16 AM, Tonix (Antonio Nati) wrote:
Il 13/11/2010 15:04, Martin Waschbuesch ha scritto:
Hi all,
I wonder about this one... First of all, I agree with Jake that MX
verification is rather important.
However, the problem at hand is also a nuisance: Why should one bad
address out of 15 in the list cause all mails to not be delivered?
Is this problem related to clients or to emails coming from servers?
This is a key question, as they should be treated differently. Incoming
messages need MX verification so that bounces have a better probability
of being deliverable. Submissions, on the other hand, are rejected
directly during the smtp session to the user's client, so there is no
bounce (as far as QMT is concerned) and thus no need for MX verification.
Double check with clients, because a lot of them stop sending as receive
the first error back, while servers continue sending remaining recipients.
For my authenticated senders I've completely disabled chkuser, using a
dedicated ip only for this purpose (relaying).
If you cannot have a dedicated IP you can always use submission port,
and setup a dedicated qmail-smtpd for this usage.
I like this solution. I've said before that I think that port 25
(incoming smtp) and port 587 (submission) should have separate tcp.smtp
files. Such configuration facilitates turning off chkuser on port 587,
which I like as a solution for this.
Thanks for chiming in on this, Tonino.
--
-Eric 'shubes'
---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group
(www.vickersconsulting.com)
Vickers Consulting Group offers Qmailtoaster support and installations.
If you need professional help with your setup, contact them today!
---------------------------------------------------------------------------------
Please visit qmailtoaster.com for the latest news, updates, and packages.
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
