Hello DZ-Jay, > Plus, the RFC requires transport servers in transit to include all "X" > headers untouched.
So this also means if I add a X-Loop header that another server leave it untouched and add also his own X-Loop header (so there could be more of them)? --- Rgds, Wilfried [TeamICS] http://www.overbyte.be/eng/overbyte/teamics.html http://www.mestdagh.biz Sunday, April 20, 2008, 16:03, DZ-Jay wrote: > On Apr 20, 2008, at 04:31, Wilfried Mestdagh wrote: >> Can someone advice on how the best way to detect a circular mail? >> >> I have smtp server and the mailboxes are all GSM. Sms are sent to >> another smtp server who deliver it for email reader (pop3 or imap). >> When >> users send email the other smtp server delivers it to mine who send it >> then to the GSM's. >> >> But there could be circumstances (wrong settings by IT manager) that I >> deliver a mail the the other server who send it back and so on. The way >> around is also possible. For example by filling in a wrong domain or an >> IT manager email at wrong domain or so. > The common way is for the SMTP server (or Mail Delivery Agent) to add > an additional header with the sender's address, then ignore any > messages where the recipient is the same as the value in that header. > This is how most (properly configured) MDAs handle it. MailMan uses > "X-BeenThere" and Procmail uses "X-Loop". You may want to use your own > convention. > This is a lot more effective and efficient than having to scan the > entire "Received:" header stack. Plus, the RFC requires transport > servers in transit to include all "X" headers untouched. > dZ. > -- > DZ-Jay [TeamICS] > http://www.overbyte.be/eng/overbyte/teamics.html -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
