Re: [qmailtoaster] Re: DK problem
Dear friends, I am facing the same problem with DK. Says all messages from my servers are permanently deferred. (see the copy of the bounce). What surprises me is why this problem is arising suddenly - my server is up for the past 3 years or more. This happens to the mails sent to yahoomail at present that too for the past 4-5 days. I have even disabled DK as per the advise given by Eric Shubert. It is not working. What can be done? Pl. advise. The bounce message: ** Hi. This is the qmail-send program at geophy.ngri.res.in. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. grsg...@yahoo.com: Connected to 66.94.238.147 but greeting failed. Remote host said: 421 4.7.1 [TS03] All messages from 203.153.42.81 will be permanently deferred; Retrying will NOT succeed. See http://postmaster.yahoo.com/421-ts03.html I'm not going to try again; this message has been in the queue too long. --- Below this line is a copy of the message. Return-Path: grsg...@ngri.res.in Received: (qmail 10679 invoked by uid 89); 15 Oct 2012 08:26:31 - Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=private; d=ngri.res.in; b=k2GRc7rechwTUy3452VnNHxJj0/tXM8E79DEmmCAWMKvTRhz5WLomQLqJsPGBPBB; Received: from unknown (HELO ngri.res.in) (127.0.0.1) by geophy.ngri.res.in with SMTP; 15 Oct 2012 08:26:31 - * Mails to gmail are going fine. ---seshagiri - Original Message - From: Eric Shubert e...@shubes.net To: qmailtoaster-list@qmailtoaster.com Cc: Sent: Thursday, October 11, 2012 1:43 AM Subject: [qmailtoaster] Re: DK problem On 10/10/2012 12:43 PM, Aleksander Podsiadły wrote: Sometimes there is the problem with domainkeys on this mailing list: 8-- Subject: failure notice Hi. This is the qmail-send program at mail.qmailtoaster.com. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. a...@mniow.pl: User and password not set, continuing without authentication. a...@mniow.pl 194.181.132.129 failed after I sent the message. Remote host said: 554 DomainKeys verify status: bad key (#5.3.0) [...] Here are the message numbers: 13393 --- Enclosed is a copy of the bounce message I received. 8-- EOT DK is (and has been for some time) disabled on mail.qmailtoaster.com. QMT hosts with DK enabled occasionally have a problem sending to other QMT hosts, the symptom of which I've seen in the past as an error signing rejection when the host is receiving (not supposed to be signing) a message. I haven't seen the bad key error before in this situation, but it appears to be the opposite, where it should be signing and is checking instead. I consider DK on QMT to be presently broken, and disable it on my QMT hosts. Hopefully one day we'll get DKIM integrated into the stock QMT. To disable DK: # cd /var/qmail/bin # ln -sf qmail-queue.orig qmail-queue -- -Eric 'shubes' - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Re: DK problem
Sounds like this has more to do with the volume and or content of messages hitting the yahoo servers than with DK. If you read the link (http://help.yahoo.com/kb/index?page=contenty=PROD_MAIL_MLlocale=en_USid=SLN3436impressions=true) they are recommending that you inspect you mail outflow to see if someone is spamming from one of your accounts. Perhaps someone has had an account compromised? I'd look at your logs to see if one particular user is sending an inordinate amount of mail. Dear friends, I am facing the same problem with DK. Says all messages from my servers are permanently deferred. (see the copy of the bounce). What surprises me is why this problem is arising suddenly - my server is up for the past 3 years or more. This happens to the mails sent to yahoomail at present that too for the past 4-5 days. I have even disabled DK as per the advise given by Eric Shubert. It is not working. What can be done? Pl. advise. The bounce message: **  Hi. This is the qmail-send program at geophy.ngri.res.in. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. grsg...@yahoo.com: Connected to 66.94.238.147 but greeting failed. Remote host said: 421 4.7.1 [TS03] All messages from 203.153.42.81 will be permanently deferred; Retrying will NOT succeed. See http://postmaster.yahoo.com/421-ts03.html I'm not going to try again; this message has been in the queue too long. --- Below this line is a copy of the message. Return-Path: grsg...@ngri.res.in Received: (qmail 10679 invoked by uid 89); 15 Oct 2012 08:26:31 - Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=private; d=ngri.res.in; b=k2GRc7rechwTUy3452VnNHxJj0/tXM8E79DEmmCAWMKvTRhz5WLomQLqJsPGBPBB; Received: from unknown (HELO ngri.res.in) (127.0.0.1) by geophy.ngri.res.in with SMTP; 15 Oct 2012 08:26:31 - * Mails to gmail are going fine. ---seshagiri - Original Message - From: Eric Shubert e...@shubes.net To: qmailtoaster-list@qmailtoaster.com Cc: Sent: Thursday, October 11, 2012 1:43 AM Subject: [qmailtoaster] Re: DK problem On 10/10/2012 12:43 PM, Aleksander PodsiadÅy wrote: Sometimes there is the problem with domainkeys on this mailing list: 8-- Subject: failure notice Hi. This is the qmail-send program at mail.qmailtoaster.com. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. a...@mniow.pl: User and password not set, continuing without authentication. a...@mniow.pl 194.181.132.129 failed after I sent the message. Remote host said: 554 DomainKeys verify status: bad key   (#5.3.0) [...] Here are the message numbers:   13393 --- Enclosed is a copy of the bounce message I received. 8-- EOT DK is (and has been for some time) disabled on mail.qmailtoaster.com. QMT hosts with DK enabled occasionally have a problem sending to other QMT hosts, the symptom of which I've seen in the past as an error signing rejection when the host is receiving (not supposed to be signing) a message. I haven't seen the bad key error before in this situation, but it appears to be the opposite, where it should be signing and is checking instead. I consider DK on QMT to be presently broken, and disable it on my QMT hosts. Hopefully one day we'll get DKIM integrated into the stock QMT. To disable DK: # cd /var/qmail/bin # ln -sf qmail-queue.orig qmail-queue -- -Eric 'shubes' - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] Re: DK problem
On 10/10/2012 12:43 PM, Aleksander Podsiadły wrote: Sometimes there is the problem with domainkeys on this mailing list: 8-- Subject: failure notice Hi. This is the qmail-send program at mail.qmailtoaster.com. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. a...@mniow.pl: User and password not set, continuing without authentication. a...@mniow.pl 194.181.132.129 failed after I sent the message. Remote host said: 554 DomainKeys verify status: bad key (#5.3.0) [...] Here are the message numbers: 13393 --- Enclosed is a copy of the bounce message I received. 8-- EOT DK is (and has been for some time) disabled on mail.qmailtoaster.com. QMT hosts with DK enabled occasionally have a problem sending to other QMT hosts, the symptom of which I've seen in the past as an error signing rejection when the host is receiving (not supposed to be signing) a message. I haven't seen the bad key error before in this situation, but it appears to be the opposite, where it should be signing and is checking instead. I consider DK on QMT to be presently broken, and disable it on my QMT hosts. Hopefully one day we'll get DKIM integrated into the stock QMT. To disable DK: # cd /var/qmail/bin # ln -sf qmail-queue.orig qmail-queue -- -Eric 'shubes' - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
