Hello all. Spend some tome trying to figure out the cause of problem discussed in "Qmail Ver.1.3 yahoo/gmail (554 mail server permanently rejected message)" thread, and finally come to a decision to modify qmail-dk a bit to get some log feedback from it. In attachment there is first pre-alpha path that enables some very basic log messages from qmail-dk (goes to qmail-smtpd log) and some so-called "Custom SMTP repplies" in case of mail rejection.
WARNING: You should consider it to be very-very-early-alpha-path, as it was done using quick-n-dirty way. It took about two hour to read docs, dig into sources and come up with a final code which compile successfully on my CentOS 4.4 server box. Log feedback from this patch allowed me to figure out that the message rejection problem we were discussing in initial thread was caused by DK_STAT_SYNTAX status returned from dk_eom() call. According to libdomainkeys sources: DK_STAT_SYNTAX, /* Message is not valid syntax. Signature could not be created/checked */ I'm not sure but it looks like it means that message signature gets somehow corrupted during "check-spam-viri-forward-on" trip, that leads to a situation when libdomainkeys unable to check signature at all. ATM I've got a copy of a message that causes libdomainkeys to throw DK_STAT_SYNTAX when checking it, but I'm unsure how to check if this is a bad/garbled message problem, libdomainkeys fault of a bug in qmail-dk checking scheme. Does anybody know how to check one particular massage against libdomainkeys? Are there any standalone CLI utilities for it? P.S. I'm going to spend some more time over qmail-dk-log-patch on the next week, remastering code to be more readable/editable and providing more verbose logging with more info in it. Suggestions and beta-testers are welcome. -- С уважением, Alexey mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- QmailToaster hosted by: VR Hosted <http://www.vr.org> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
