[EMAIL PROTECTED] wrote:
From my read of this thread there appear to be two seperate problems.
Your diagnosis of Jake Vickers' note about a "similar message... that
is a little more descriptive" - the endpoint advertising TLS but not
having a certificate - makes sense.
The "554 qq permanent problem", although triggered from a similar
mailing list bounce scenario, appears to me to be a wholly separate
issue. While there are a handful of local, receiving-side
configuration problems that could manifest as 'qq permanent problem',
my best guess is that in this case the error is coming from qmail-dk
being overly picky about headers.
As I mentioned in the "ezmlm warning" thread, qmail-dk ought to either
not drop messages with headers it thinks are malformed, or it ought to
be a lot more verbose.
I don't think that modifying one's DKVERIFY, as roughly documented,
can be used to work around this problem. You either have to patch
qmail-dk, or you have to turn off DKVERIFY completely.
I have turned off DK on the machine that receives this mailing list and
have not had the problem (yet). It usually only happens once a week or
so, so I have a few more days until I'm sure this solved it.
---------------------------------------------------------------------
QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
