> >> FYI, People running Declude JunkMail can add the following to their
>config files to fix this:
> XINHEADER Return-Path: < % MAILFROM % > <<
>
>You posted this in the Imail list.
>
>However, isn't that redundant with:
>
> >> If you want to record the name of the sender (according to the SMTP
>Envelope) in the E-mail headers, you can use the XSENDER configuration
>option. To do this, add a line to the \IMail\Declude\global.cfg file that
>says "XSENDER ON". <<
No, it is not redundant. Well, actually, it IS, but not in the way you think.
If you use the "XSENDER ON" option, Declude adds a header of its own that
shows the true sender ("X-Declude-Sender: [EMAIL PROTECTED]
[192.168.100.12]"). That provides useful information, but it doesn't use
the same format that RFC2821 discusses ("Return-Path:
<[EMAIL PROTECTED]>"). So using the XSENDER option would not produce the
RFC-compliant Return-Path: header.
>Sounds like these two features/functions should be consolidated? Is
>"X-Sender" an "official" header, or is Return-Path the proper header to
>record the Envelope MAIL FROM. Please advise!
The header mentioned in the RFCs is "Return-Path:". The only advantage to
that versus the one that Declude adds with the XSENDER option is that the
receiving mail client might look for the Return-Path: header (although I
can't imagine why it would do so).
Note that the functionality of the XSENDER and XSPOOLNAME options can be
mimicked with the XINHEADER/XOUTHEADER options. The XSENDER/XSPOOLNAME
options were added before the XINHEADER/XOUTHEADER options, which is why
they were kept.
-Scott
---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail". You can E-mail
[EMAIL PROTECTED] for assistance. You can visit our web
site at http://www.declude.com .
