>-----Message d'origine----- >De : [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] la part de Edinilson - ATINET >Envoy=E9 : vendredi 25 mai 2007 16:02 >=C0 : xmail@xmailserver.org >Objet : [xmail] Re: Strange error after upgrade > > >OK, thanks Davide and Clement. > >I will catalog some logs (smtp and slog) and report if I found=20 >something=20 >"strange". > > >Edinilson >--------------------------------------------------------- >ATINET-Professional Web Hosting >Tel Voz: (0xx11) 4412-0876 >http://www.atinet.com.br > >
As the 'bad' server is not your Xmail, the xmail logs will only say to = you if the mail was 'routed' or not by your xmail and the 'bad' side = (before your xmail or minimum second hop after it). The NDR headers will give = you the last successfull hop. I really think that getting the complete NDR message (headers included) = is important as it will give you the name of the ndr sending server, so = the last server that successfully received the original mail. And if this server is not the last customer server/firwall/security appliance/... just before your xmail server, the problem is not your = xmail server (Davide allready proved it by the 'Relay denied' message 'case', = but it's more 'by chance' that the reason is different ...). PS : Remember that the 'relay' problem can be before your xmail server :) As an example : the sending customer send to an internal server, = chained or not with other internal servers, then routed to a security and control appliance server, a firewall, a proxy, ..., then finaly the last mail gateway in customer network send to your xmail for Internet delivery. = In this case, the only way to find the culprit is the complete NDR = message. 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]
