DomainKeys is in sort of a state of flux at the moment. Depending on the version of qmail-toaster you're running, YMMV.
In earlier versions with qmail-dk, disabling with David's method is recommended. It was pretty badly broken. Alexey did some great work on it, and his modifications were introduced in v1.3.9. This improved things tremendously, but there are still a few bugs in there. In the latest version(s), DKVERIFY="" should safely disable incoming checking. To disable things entirely though, you can still use the earlier method. What I don't understand regarding your problem is that qmail-dk is apparently trying to *sign* (as in outgoing process) these messages. I'm not sure how it knows when to sign and when to check, other than the DKSIGN and DKVERIFY environment variables. Unless you really want/need it for some reason, the simplest solution would be to disable it entirely. FWIW, DomainKeys is being superceded by DKIM, so DomainKeys will go away eventually. David Ferreira wrote: > I think that adding DKVERIFY="" in the tcp.smtp won't work. > Just use this to totaly disable domain keys: > > rm -f /var/qmail/bin/qmail-queue; ln -s /var/qmail/bin/qmail-queue.orig > /var/qmail/bin/qmail-queue > > If the problem is related which domain keys would be solved :) > > Best regards, > David > > > Bill Kwok escribió: >> Hi Terry, >> >> When gmail / yahoo sent email out, they will sign the email by their >> own domain keys. But when these emails are forwarded from your ISP, >> the header has been modified and the signature became invalid. I >> guess that's the reason why your server rejects them. Try adding >> DKVERIFY="" to the line of your ISP in tcp.smtp and rebuild the cdb to >> disable incoming checking. >> >> Hope it helps you and good luck. >> >> Best regards, >> Bill >> >> On 3/1/07, *T Rigby* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote: >> >> Hello all, first time poster here. Ive been using QT for some >> time now and I've just updated to one of the more recent versions >> and since its worked so well out of the box in the past for me I >> guess I have a lot of holes in my ability to administate my mail >> system. >> >> I currently use fetchmail to grab my emails from my ISP and >> forward it to an email address I have on my own server here at >> home, for example fetchmail grabs mail from my ISP " >> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>" and then sends it off >> to "[EMAIL PROTECTED] >> <mailto:[EMAIL PROTECTED]>". Somewhere along the line I run >> into the issue of mail getting rejected due to this. I am >> guessing its fetchmail causing the issue or rather the fact that >> the mail is to " myisp.com <http://myisp.com>" yet its being >> delivered to "myhomeserver.com <http://myhomeserver.com>". I >> really do lack the knowledge to really know whats going on to fix >> it properly. >> >> My /var/log/qmail/smtp/current shows a bunch of errors like the >> following.... >> qmail-smtpd: qq hard reject (qmail-dk: Cannot sign message due to >> invalid message syntax. (#5.3.0)): MAILFROM:< [EMAIL PROTECTED] >> <mailto:[EMAIL PROTECTED]>> RCPTTO:[EMAIL PROTECTED] >> <mailto:RCPTTO:[EMAIL PROTECTED]> >> >> The odd thing is, most emails get through to me, its mostly emails >> from yahoo and gmail that dont get through. I've tried adding >> rules to tcp.smtp and rebuilding the rules but that only makes it >> so that the IP's that are whitelisted arent hard rejected but soft >> rejected. So fetchmail leaves them on my ISP's mail server >> instead of rejecting and deleting them. Also, there are multiple >> IP addresses for gmail and yahoo mail servers which makes it >> harder to whitelist them. >> >> In order to try and figure out what is casing the mail to be >> rejected I've edited my tcp.smtp quite a bit.. it is currently as >> follows... >> >> >> 127.0.0.1:allow,RELAYCLIENT="",QMAILQUEUE="/var/qmail/bin/simscan",CHKUSER_RCPTLIMIT="50",CHKUSER_WRONGRCPTLIMIT="10" >> >> >> 24.71.223.:allow,RBLSMTPD="",QMAILQUEUE="/var/qmail/bin/simscan" >> 66.135.192.:allow,RBLSMTPD="",QMAILQUEUE="/var/qmail/bin/simscan" >> 66.94.234.:allow,RBLSMTPD="",QMAILQUEUE="/var/qmail/bin/simscan" >> 216.109.112.:allow,RBLSMTPD="",QMAILQUEUE="/var/qmail/bin/simscan" >> 209.191.69.:allow,RBLSMTPD="",QMAILQUEUE="/var/qmail/bin/simscan" >> >> :allow,BADMIMETYPE="",BADLOADERTYPE="M",CHKUSER_RCPTLIMIT="50",CHKUSER_WRONGRCPTLIMIT="10",QMAILQUEUE="/var/qmail/bin/simscan" >> >> >> >> I probably have it pretty messed up here but before I g editing it >> anymore I wanted to post to this list to get some ideas on how to >> resolve this situation. I also have to mention that I dont have >> issues with email being send directly to [EMAIL PROTECTED] >> <mailto:[EMAIL PROTECTED]>, it is only when emails are >> grabbed with fetchmail. >> >> Can anyone here suggest what I might do to fix this problem other >> than stop using fetchmail :) Thank you in advance for your time. >> >> Terry Rigby >> -- -Eric 'shubes' --------------------------------------------------------------------- QmailToaster hosted by: VR Hosted <http://www.vr.org> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
