[
https://issues.apache.org/jira/browse/JAMES-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12643651#action_12643651
]
Danny Angus commented on JAMES-875:
-----------------------------------
@stefano. Difficult question...
In the wrapper makes james behave like an MTA by default but may confuse people
who are used to JavaMail.
If we could somehow set a flag or param to hint that a new id is required then
I'd definitely say it should be in the wrapper, because 99 times out of 100
James users will want to alter an existing message, not effectively create a
new one.
(This issue also causes problems for MUA's that use ID's and In-reply-to id's
to organise threads)
> Message-ID changed by mailets (MSGID_FROM_MTA_HEADER changed)
> -------------------------------------------------------------
>
> Key: JAMES-875
> URL: https://issues.apache.org/jira/browse/JAMES-875
> Project: JAMES Server
> Issue Type: Bug
> Components: SMTPServer
> Affects Versions: 2.3.1, Trunk
> Environment: Linux (Fedora Core 8)
> Reporter: Marc SCHNEIDER
> Fix For: 2.3.2, Trunk
>
> Attachments: config-james.xml
>
>
> I noticed that emails sent using my James Server have this header when they
> are delivered :
> X-Spam-Status: No, score=0.1 required=5.0 tests=AWL,MSGID_FROM_MTA_HEADER
>
> This is added by SpamAssassin telling that the Message-Id was generated by a
> relay, rather than by the user agent.
> If I use the same mailing software but not James to send an email, I don't
> have this problem.
> I looked in the configuration files of James and couldn't find anything about
> this msgid. Why is James changing that ?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
