|
Mime-Version: |
1.0 |
Sender: |
|
Subject: |
|
From: |
|
Date: |
Tue, 26 Oct 2004 22:36:56 -0400 |
In-Reply-To: |
<Pine.GSO.4.44.0410262038010.22566-100000@infinity> |
Content-Type: |
text/plain; charset="us-ascii"; format=flowed |
Reply-To: |
|
At 10/26/2004 21:41 Tuesday, Winship wrote:
>The old manual I have says the RFC822 header option, which should not be
>used as a regular option, can be used for debugging specific problems.
>What specific problems, or sort of problems? Is it of use to listowners,
>or only site maintainers?
If you're referring to one such SHORT822, it is when the "foreign" MTA
bounces a mail (usually distributed via LISTSERV with a generic TO: and
BCC: to intended subscriberS) and it does NOT ID the offending mailbox
(though sometimes it can be found in the RECEIVED line headers). By
having LISTSERV generate a "real" subscriber in the TO: field (using the
SHORT822 options for subscribers in the target domain), you stand a
better chance of IDing the "bad" mailbox, at the expense ("overhead") of
increased Internet and mail server traffic.
/Pete
|
|
|