smtpd_delay_reject = yes & Reject Logging
in [Postfix]
|
From: Ralf Hildebrandt on 10 Aug 2010 16:46 * JunkYardMail1(a)Verizon.net <JunkYardMail1(a)Verizon.net>: > Yes it does cause a problem. > It does not indicate the stage the rejection is associated with > (CONNECT, HELO, FROM, RCPT, etc.). The rejection always happens at the RCPT TO stage in those cases. Thus it's called "smtpd_delay_reject". Back in the dawn of Postfix I had this problem that a mailserver would not accept a arejection at a prior stage. Thus it came back over and over again. To be rejected over and over again. Thus smtpd_delay_reject had been introduced, delaying the reject to the RCPT TO: stage NOT MATTER what would have caused the rejection at an earlier stage. -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | http://www.charite.de
From: Michael Orlitzky on 10 Aug 2010 17:02 On 08/10/2010 04:46 PM, Ralf Hildebrandt wrote: > * JunkYardMail1(a)Verizon.net<JunkYardMail1(a)Verizon.net>: >> Yes it does cause a problem. >> It does not indicate the stage the rejection is associated with >> (CONNECT, HELO, FROM, RCPT, etc.). > > The rejection always happens at the RCPT TO stage in those cases. > Thus it's called "smtpd_delay_reject". > > Back in the dawn of Postfix I had this problem that a mailserver would > not accept a arejection at a prior stage. Thus it came back over and > over again. To be rejected over and over again. > Thus smtpd_delay_reject had been introduced, delaying the reject to > the RCPT TO: stage NOT MATTER what would have caused the rejection at > an earlier stage. > I think he just wants to know which smtpd restrictions list contains the rule that caused the rejection. An almost-answer: each reject_foo rule has a certain log format which, once learned, will give you a pretty good idea about the rule that caused the rejection. You still have to look up which restrictions list contains that rule, though.
From: Ralf Hildebrandt on 10 Aug 2010 17:06 * Michael Orlitzky <michael(a)orlitzky.com>: > I think he just wants to know which smtpd restrictions list contains > the rule that caused the rejection. Could be. > An almost-answer: each reject_foo rule has a certain log format > which, once learned, will give you a pretty good idea about the rule > that caused the rejection. Yes indeed. > You still have to look up which restrictions list contains that rule, > though. Yes, there could be different check_sender_access rules - even without smtpd_delay_reject it would be hard to see WHICH ONE fired. They way I do this is to look at the log and play through the restrictions in my head (does it come from mynetwork? no! Next restriction etc.) -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | http://www.charite.de
From: Wolfgang Zeikat on 10 Aug 2010 17:40 In an older episode, on 2010-08-10 23:06, Ralf Hildebrandt wrote: >> You still have to look up which restrictions list contains that rule, >> though. > > Yes, there could be different check_sender_access rules - even without > smtpd_delay_reject it would be hard to see WHICH ONE fired. > > They way I do this is to look at the log and play through the > restrictions in my head (does it come from mynetwork? no! Next > restriction etc.) > postmap -q can also be quite helpful ...
From: JunkYardMail1 on 10 Aug 2010 17:41 "I think he just wants to know which smtpd restrictions list contains the rule that caused the rejection." Correct. -------------------------------------------------- From: "Michael Orlitzky" <michael(a)orlitzky.com> Sent: Tuesday, August 10, 2010 2:02 PM To: <postfix-users(a)postfix.org> Subject: Re: smtpd_delay_reject = yes & Reject Logging > On 08/10/2010 04:46 PM, Ralf Hildebrandt wrote: >> * JunkYardMail1(a)Verizon.net<JunkYardMail1(a)Verizon.net>: >>> Yes it does cause a problem. >>> It does not indicate the stage the rejection is associated with >>> (CONNECT, HELO, FROM, RCPT, etc.). >> >> The rejection always happens at the RCPT TO stage in those cases. >> Thus it's called "smtpd_delay_reject". >> >> Back in the dawn of Postfix I had this problem that a mailserver would >> not accept a arejection at a prior stage. Thus it came back over and >> over again. To be rejected over and over again. >> Thus smtpd_delay_reject had been introduced, delaying the reject to >> the RCPT TO: stage NOT MATTER what would have caused the rejection at >> an earlier stage. >> > > I think he just wants to know which smtpd restrictions list contains the > rule that caused the rejection. > > An almost-answer: each reject_foo rule has a certain log format which, > once learned, will give you a pretty good idea about the rule that > caused the rejection. You still have to look up which restrictions list > contains that rule, though. >
First
|
Prev
|
Next
|
Last
Pages: 1 2 3 4 5 Prev: Simple hack to get $3000 to your home Next: compile Postfix in static linking |