>-----Message d'origine----- >De : [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] la part de Hal Dell >Envoy=E9 : vendredi 15 juin 2007 05:56 >=C0 : [email protected] >Objet : [xmail] Re: eMail NOT automatically being requeued? > > >=20 >Dear David Lord- > >> Hal Dell wrote: >>=20 >> The problem is that I received the error code and message "451=20 >> Greylisted, please try again in 900 seconds". In the case of=20 >xMail it=20 >> did not retry to send the eMail. >>=20 >> According to RFC2505, 4xx are Transient Negative Completion reply=20 >> (Temporary >> Error) and should result in the mail transfer being put back=20 >on queue=20 >> again and a new attempt being made later. > >>> David Lord wrote: >>> >>> That doesn't seem right, as greylisting has been taken up by more >providers I've seen temporary >>> failure many times but xmail retries and either delivers or=20 >eventually >gives up and I get an unable >>> to deliver message. Only unable to deliver have been whilst=20 >testing and >not to real addresses. >>> Xmail default here was a notification after first temporary=20 >failure then >after complete failure which >>> might be 4 - 5 days later. I modified notification settings to = 1,6,9 >attempts but any that have hit >>> 6, all test emails, never get through at all. If I'm=20 >desperate I check >what is still in spool file that >>> xmail is still trying. One unlikely possibility is the=20 >greylisting accept >period is too short and after >>> jumping past it there is no possibility mail will get through.=20 > >Thanks for the input -- I've been using xMail for quite some time and >checked on your suggestions. > >I don't understand the "NotifyTryPattern" option -- is this in=20 >hours? None >of the docs I found describe >this in detail. > >The problem is that with the 451 returned error from the=20 >remote MTA -- xMail >seems to have >considered this an error because it immediately sent back an=20 >eMail to the >user with >the Subject "Error sending message...". It did NOT retry -- I=20 >double checked >this >by reviewing the log file. Here is what is in the LOG file=20 >(please note I >removed the >original from/to for privacy) : > >[PeekTime] 1181221418 : Thu, 7 Jun 2007 09:03:38 -0400 ><< >ErrCode =3D -77 >ErrString =3D [RCPT TO:] not permitted by remote SMTP server >ErrInfo =3D 451 Greylisted, please try again in 900 seconds >SMAIL SMTP-Send MX =3D "mail22.webcontrolcenter.com." >SMTP =3D "smtp-x1.phl1.mgfx.com" From =3D "<dest>" To =3D "<from>" = Failed ! >SMTP-Error =3D "451 Greylisted, please try again in 900 seconds" >SMTP-Server =3D "mail22.webcontrolcenter.com." >>> > >The error code -77 translates to ERR_SMTP_BAD_RCPT_TO" with >the string "[RCPT TO:] not permitted by remote SMTP server" as shown. >I don't think this is correct.... > >I am hoping that someone can read the source code better then I can to >help figure this out. I don't see any place in the Server.Tab=20 >to change this >behavior. For xMail to work with other MTAs it needs to follow the RFC >2505 and I think xMail should treat 451 as a soft error? > > >Thanks, >Hal Dell >Managing Partner >ePodWorks.net, Inc. >PO Box 22 >Willow Grove, PA 19090 >+1-215-830-0662 (phone) >+1-215-913-6894 (cell) >+1-866-549-4652 (fax) >Need Support send eMail to [EMAIL PROTECTED] ! >
Sure, 4xx error codes should allways be considered as they are, = "temporary errors", so the sending mta should retry according to it's own normal scheduling retry process. I noticed some other mta on the web changing some specific 4xx error to 'fatal' when received in particular places in the smtp session (after = some specific commands even if rfc says it's ok to send this 4xx error at = this place). Could it be the case for xmail when sending ? I didn't check the code too :) Francis - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
