[jira] Updated: (JAMES-360) Support for Additional "received for" headers: e.g. X-Envelope-To

["Stefano Bagnara (JIRA)" <se...@james.apache.org>]

     [ http://issues.apache.org/jira/browse/JAMES-360?page=all ]

Stefano Bagnara updated JAMES-360:
----------------------------------

    Attachment: fetchmail-patch-against-mergebranch-20050504.tgz

Here is an updated patch against current (20050504) svn branch trunk-merged.
It supports the use of a custom header to recognize the recipient (Delivered-To, X-Envelope-To, Apparently-To, etc).

> Support for Additional "received for" headers: e.g. X-Envelope-To
> -----------------------------------------------------------------
>
>          Key: JAMES-360
>          URL: http://issues.apache.org/jira/browse/JAMES-360
>      Project: James
>         Type: Improvement
>   Components: FetchMail
>     Versions: 2.2.0
>     Reporter: Stefano Bagnara
>     Priority: Minor
>  Attachments: fetchmail-patch-against-mergebranch-20050504.tgz, fetchmail.tar.gz
>
> I added support for a further parameter to the <account /> tag: customrcpt-header.
> There are many MDA that will not add the "for" statement in the received header but they will add an header "X-Envelope-To" or "Received-For" or something similar with the content of the RCPT for that message.
> using:
> <account user="<USER>" password="<PASS>" recipient="<RECIPIENT>" ignorercpt-header="false" customrcpt-header="X-Envelope-To" />
> will use the content of X-Envelope-To instead of the received for to get the intended recipient.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org