(off-topic) Outlook 2003 msgids causing odd email problems
I'm raising this here in case anyone else has either seen this problem and has any thoughts, or alternatively has experienced the fallout and is wondering why. Over the last few weeks I've had complaints that email messages are going astray. This has happened in Cyrus imapd on delivery, and in Mailman, where archiving of posts is sometimes broken. After much scratching of head and tearing of hair, I have finally found two provable instances - one in Cyrus and one in Mailman - of replies to messages being sent using Microsoft Outlook Service Pack 2, where Outlook has given the reply the same message-id as the message it is replying to - in flat violation of RFC{2}822. (In one case the original message, the read-receipt automatically generated by Outlook, the reply, and the forward of the reply sent when the reply didn't arrive, all had the same msg-id). As far as I can tell this behaviour was introduced by SP2; the Web says Outlook 2003 before that didn't add message-ids at all. I've now set duplicatesuppression no in imapd.conf which seems to be addressing the problem of lmtpd discarding the ``duplicate'' messages. Mailman is another issue. I haven't seen any discussion of this problem on the Web: has anyone else encountered it? Better yet, does anyone have a fix (on the Microsoft side)? Jonathan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: (off-topic) Outlook 2003 msgids causing odd email problems
Replying to myself, On Tuesday 11 September 2007 12:20, Jonathan McKeown wrote: After much scratching of head and tearing of hair, I have finally found two provable instances - one in Cyrus and one in Mailman - of replies to messages being sent using Microsoft Outlook Service Pack 2, where Outlook has given the reply the same message-id as the message it is replying to - in flat violation of RFC{2}822. (In one case the original message, the read-receipt automatically generated by Outlook, the reply, and the forward of the reply sent when the reply didn't arrive, all had the same msg-id). After further investigation, it appears that the message-id generated by Outlook 2003 has the originating host name on the RHS (after the @), unless the sending machine is a member of a Server 2003 AD domain in which case the domain name is used which increases the risk of a collision (especially if the LHS is copied!). Jonathan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: (off-topic) Outlook 2003 msgids causing odd email problems
Yeah Outlook Express did that when it forwarded messages I forgot the version - it screwed up spamassassin, I filed a bug, bug finally got a workaround added. File a bug with mailman and cyrus dev. teams, maybe they can work around it. At least get it documented. And call Microsoft tech support and complain. Microsoft does not charge for tech support incidents where a bug is reported. Ted -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Jonathan McKeown Sent: Tuesday, September 11, 2007 3:20 AM To: freebsd-questions@freebsd.org Subject: (off-topic) Outlook 2003 msgids causing odd email problems I'm raising this here in case anyone else has either seen this problem and has any thoughts, or alternatively has experienced the fallout and is wondering why. Over the last few weeks I've had complaints that email messages are going astray. This has happened in Cyrus imapd on delivery, and in Mailman, where archiving of posts is sometimes broken. After much scratching of head and tearing of hair, I have finally found two provable instances - one in Cyrus and one in Mailman - of replies to messages being sent using Microsoft Outlook Service Pack 2, where Outlook has given the reply the same message-id as the message it is replying to - in flat violation of RFC{2}822. (In one case the original message, the read-receipt automatically generated by Outlook, the reply, and the forward of the reply sent when the reply didn't arrive, all had the same msg-id). As far as I can tell this behaviour was introduced by SP2; the Web says Outlook 2003 before that didn't add message-ids at all. I've now set duplicatesuppression no in imapd.conf which seems to be addressing the problem of lmtpd discarding the ``duplicate'' messages. Mailman is another issue. I haven't seen any discussion of this problem on the Web: has anyone else encountered it? Better yet, does anyone have a fix (on the Microsoft side)? Jonathan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]