On 10/22/00 5:43 AM -0700, SRE wrote:
>I'm not sure what other packages do, so I'm consulting the oracle to
>see what you all suggest. Are you using X*Loop as an error trap? Do you
>have subscribers who send human-originated email with X*Loop headers?
>
>Opinions and experiences requested!
>
>Below is the response from this subscriber's tech support person:
>
>>Thank you for contacting technical support. I apologize for all the
>>inconvenience this issue may have caused you. Our mail system puts this
>>comment, X*Loop*Detect: 1, in the subject line to track looping mail
>>
>>According to RFCs, you can put a user-defined field that starts with ëX-ë
>>and we use this to track looping mail through our mail servers. If any mail
>>server isnít accepting mail because of this, please contact the
>>administrators of that mail server and request them to setup their mail
>>server according to RFCs.
>>
>>If you have any other question or feel that this issue has not been resolved
>>to your satisfaction, please feel free to contact us again.
A: that ISP needs a lesson in what it means to follow the RFCs. :)
Majordomo's following them just fine.
B: Seems to me that instead of putting "X*Loop*Detect: 1" in the header and
filtering on the presence of that header, it would make better sense to put
in "X*Loop*Detect: majordomo@yourhost.com" and filter based on the content
of that header matching.
(replace * with - where necessary)
Or, since X-headers can be anything you want, maybe even
X-Majordomo-Loop-Detect: yourhost.com
Dave Miller Technical Lead / Database Support
A2Central.com: Your total source for Apple II computing news
http://www.a2central.com/ justdave@a2central.com
References:
|
|
