Re: Can a more useful bounce message be provided - correction
Phil Stracchino wrote: On 11/13/20 1:22 PM, John Fawcett wrote: On 13/11/2020 07:38, li...@lazygranch.com wrote: My server bounced a message. Here is the server log (sanitized). - Nov 13 02:07:52 myserver postfix/smtpd[27706]: NOQUEUE: reject: RCPT from sonic302-23.consmr.mail.gq1.yahoo.com[98.137.68.149]: 554 5.7.1 Service unavailable; Client host [98.137.68.149] blocked using cbl.abuseat.org; Blocked - see http://www.abuseat.org/lookup.cgi?ip=98.137.68.149; from= to= proto=ESMTP helo= --- Here is what the sender received: From: mailer-dae...@yahoo.com Date: November 12, 2020 at 6:07:55 PM PST To: per...@sbcglobal.net Subject: Failure Notice Sorry, we were unable to deliver your message to the following address. : 554: 5.7.1 Service unavailable --- Below this line is a copy of the message. --- So did the Oath server swallow the useful link to abuseat.org? Can this be improved? missing NOT makes all the difference: Your server rejected that message, so your server was NOT responsible for generating the bounce message. That was generated by yahoo. I think what the OP is asking here is, can Yahoo/Oath be compelled to provide a more useful failure message relaying the informative response provided by OP's Postfix instance. And the answer to that, unfortunately, is no. The meta-question is whether there's any benefit to blocking mail from one of Yahoo!'s outgoing mail servers because it was listed in a DNSBL. DNSBLs are useful where the majority of mail coming from an IP is spam. The majority of mail received through that server is not spam.
Re: Can a more useful bounce message be provided - correction
On 15/11/2020 09:52, Nick Tait wrote: > On 14/11/20 7:30 am, Phil Stracchino wrote: >> I think what the OP is asking here is, can Yahoo/Oath be compelled to >> provide a more useful failure message relaying the informative response >> provided by OP's Postfix instance. >> >> And the answer to that, unfortunately, is no. > > But by the look of things the bounce notification generated by Yahoo > contains the first part of the original reject message - i.e. the bold > part of the red text below: > > Nov 13 02:07:52 myserver postfix/smtpd[27706]: NOQUEUE: reject: RCPT > from sonic302-23.consmr.mail.gq1.yahoo.com[98.137.68.149]: *554 5.7.1 Service > unavailable*; Client host [98.137.68.149] blocked > using cbl.abuseat.org; Blocked - see > http://www.abuseat.org/lookup.cgi?ip=98.137.68.149; > from= to= proto=ESMTP > helo= > > So presumably if you can somehow change the reject message and perhaps > remove the semicolons, then maybe Yahoo will provide the entire > message in the bounce notification? Which comes back to the original > question about whether this message can be customised? But I suspect > the answer to that question is still no? > > Nick. > The reject message used by smtpd when rejecting due to an rbl based restriction can be customized: http://www.postfix.org/postconf.5.html#default_rbl_reply That changes the default, so applies to any rbl based restriction. The message can be customized for only specific rbls with rbl_reply_maps. John
Re: Can a more useful bounce message be provided - correction
On 14/11/20 7:30 am, Phil Stracchino wrote: I think what the OP is asking here is, can Yahoo/Oath be compelled to provide a more useful failure message relaying the informative response provided by OP's Postfix instance. And the answer to that, unfortunately, is no. But by the look of things the bounce notification generated by Yahoo contains the first part of the original reject message - i.e. the bold part of the red text below: Nov 13 02:07:52 myserver postfix/smtpd[27706]: NOQUEUE: reject: RCPT from sonic302-23.consmr.mail.gq1.yahoo.com[98.137.68.149]:*554 5.7.1 Service unavailable*; Client host [98.137.68.149] blocked using cbl.abuseat.org; Blocked - see http://www.abuseat.org/lookup.cgi?ip=98.137.68.149; from= to= proto=ESMTP helo= So presumably if you can somehow change the reject message and perhaps remove the semicolons, then maybe Yahoo will provide the entire message in the bounce notification? Which comes back to the original question about whether this message can be customised? But I suspect the answer to that question is still no? Nick.
Re: Can a more useful bounce message be provided - correction
On 11/13/20 1:22 PM, John Fawcett wrote: > On 13/11/2020 07:38, li...@lazygranch.com wrote: >> My server bounced a message. Here is the server log (sanitized). >> - >> Nov 13 02:07:52 myserver postfix/smtpd[27706]: NOQUEUE: reject: RCPT >> from sonic302-23.consmr.mail.gq1.yahoo.com[98.137.68.149]: 554 5.7.1 >> Service unavailable; Client host [98.137.68.149] blocked using >> cbl.abuseat.org; Blocked - see >> http://www.abuseat.org/lookup.cgi?ip=98.137.68.149; >> from= to= proto=ESMTP >> helo= >> --- >> Here is what the sender received: >> >> >>> From: mailer-dae...@yahoo.com >>> Date: November 12, 2020 at 6:07:55 PM PST >>> To: per...@sbcglobal.net >>> Subject: Failure Notice >>> >>> Sorry, we were unable to deliver your message to the following address. >>> >>> : >>> 554: 5.7.1 Service unavailable >>> >>> --- Below this line is a copy of the message. >> --- >> >> So did the Oath server swallow the useful link to abuseat.org? Can this >> be improved? > missing NOT makes all the difference: > > > Your server rejected that message, so your server was NOT responsible for > > generating the bounce message. That was generated by yahoo. I think what the OP is asking here is, can Yahoo/Oath be compelled to provide a more useful failure message relaying the informative response provided by OP's Postfix instance. And the answer to that, unfortunately, is no. -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958
Re: Can a more useful bounce message be provided - correction
On 13/11/2020 07:38, li...@lazygranch.com wrote: > My server bounced a message. Here is the server log (sanitized). > - > Nov 13 02:07:52 myserver postfix/smtpd[27706]: NOQUEUE: reject: RCPT > from sonic302-23.consmr.mail.gq1.yahoo.com[98.137.68.149]: 554 5.7.1 > Service unavailable; Client host [98.137.68.149] blocked using > cbl.abuseat.org; Blocked - see > http://www.abuseat.org/lookup.cgi?ip=98.137.68.149; > from= to= proto=ESMTP > helo= > --- > Here is what the sender received: > > >> From: mailer-dae...@yahoo.com >> Date: November 12, 2020 at 6:07:55 PM PST >> To: per...@sbcglobal.net >> Subject: Failure Notice >> >> Sorry, we were unable to deliver your message to the following address. >> >> : >> 554: 5.7.1 Service unavailable >> >> --- Below this line is a copy of the message. > --- > > So did the Oath server swallow the useful link to abuseat.org? Can this > be improved? missing NOT makes all the difference: Your server rejected that message, so your server was NOT responsible for generating the bounce message. That was generated by yahoo. John
Re: Can a more useful bounce message be provided
On 13/11/2020 07:38, li...@lazygranch.com wrote: > My server bounced a message. Here is the server log (sanitized). > - > Nov 13 02:07:52 myserver postfix/smtpd[27706]: NOQUEUE: reject: RCPT > from sonic302-23.consmr.mail.gq1.yahoo.com[98.137.68.149]: 554 5.7.1 > Service unavailable; Client host [98.137.68.149] blocked using > cbl.abuseat.org; Blocked - see > http://www.abuseat.org/lookup.cgi?ip=98.137.68.149; > from= to= proto=ESMTP > helo= > --- > Here is what the sender received: > > >> From: mailer-dae...@yahoo.com >> Date: November 12, 2020 at 6:07:55 PM PST >> To: per...@sbcglobal.net >> Subject: Failure Notice >> >> Sorry, we were unable to deliver your message to the following address. >> >> : >> 554: 5.7.1 Service unavailable >> >> --- Below this line is a copy of the message. > --- > > So did the Oath server swallow the useful link to abuseat.org? Can this > be improved? Your server rejected that message, so your server was responsible for generating the bounce message. That was generated by yahoo. John
Can a more useful bounce message be provided
My server bounced a message. Here is the server log (sanitized). - Nov 13 02:07:52 myserver postfix/smtpd[27706]: NOQUEUE: reject: RCPT from sonic302-23.consmr.mail.gq1.yahoo.com[98.137.68.149]: 554 5.7.1 Service unavailable; Client host [98.137.68.149] blocked using cbl.abuseat.org; Blocked - see http://www.abuseat.org/lookup.cgi?ip=98.137.68.149; from= to= proto=ESMTP helo= --- Here is what the sender received: > From: mailer-dae...@yahoo.com > Date: November 12, 2020 at 6:07:55 PM PST > To: per...@sbcglobal.net > Subject: Failure Notice > > Sorry, we were unable to deliver your message to the following address. > > : > 554: 5.7.1 Service unavailable > > --- Below this line is a copy of the message. --- So did the Oath server swallow the useful link to abuseat.org? Can this be improved?
