A user on my system gets updates form FedEx and it seems the SpamFilter is comcatenating the From header when it passes it on to my mail server. The new From causes my mail server to reject tthe message probbaly because it looks like a single email address with two @ signs. Below is the original message header and clip from SpamFilter's activity log. I emailed FedEx to see if it was necessary to have two email addresses in the From field but they have not responded.

Here is the original header:

And this is the lines from the activity log. This is also how it is passed to my mail server.

05/25/03 06:02:32:234 -- (544) Sending email from mailto:sysdeliv@fn3a.prod.fedex.cominsightmail@fedex.com" CLASS="ASPForums" TITLE="WARNING: URL created by poster. - sysdeliv@fn3a.prod.fedex.cominsightmail@fedex.com to mailto:marinav@polytecpi.com" CLASS="ASPForums" TITLE="WARNING: URL created by poster. - marinav@polytecpi.com
05/25/03 06:02:34:106 -- (544) EMail from mailto:sysdeliv@fn3a.prod.fedex.cominsightmail@fedex.com" CLASS="ASPForums" TITLE="WARNING: URL created by poster. - sysdeliv@fn3a.prod.fedex.cominsightmail@fedex.com to mailto:marinav@polytecpi.com" CLASS="ASPForums" TITLE="WARNING: URL created by poster. - marinav@polytecpi.com   was forwarded to 127.0.0.1

We've seen that by FedEx... The problem is that they are sending emails out using TWO From addresses:

From: <sysdeliv@fn3a.prod.fedex.com>, FedEx <insightmail@fedex.com>

They can't do that... The From must be unique!

FedEx is aware of the problem, but decided not to fix it. Their solution was to have the mail server accept all emails ending in fedex.com...

We'll see if we can change our code to only consider the 1st address, but can't promise anything as that involves changing how SpamFilter interacts with the RFCs and can induce other bugs without knowing about it...

Roberto Franceschetti
LogSat Software

LogSat Software,

We've encountered the same problem.  So, even though the problem is initiated by FedEx or the sending party ... your software actually creates the invalid address by concatenating the two addresses. I'm not that familiar with the specifics of email but why can't the email be sent along untouched???  Better yet, is there a patch??? 

Mike

P.S. I've encountered this problem again but from a different customer.

Due to the increasing number of user experiencing difficulties with FedEx's non RFC compliant emails, we made major changes in how SpamFilter handles incoming and outgoing emails. These modifications should allow FedEx's emails to be delivered correctly.

The latest beta build 1.2.0.191 attempts to deliver emails with non-RFC compliant MAIL FROMs commands. Licensed users can find this build in the registered users area for download.

Please note that despite the relative simplicity of the problem, extensive changes have been made to handle it, and this build is a beta that has not been thoroughly tested.

Roberto
LogSat Software

Due to the increasing number of user experiencing difficulties with FedEx's non RFC compliant emails, we made major changes in how SpamFilter handles incoming and outgoing emails. These modifications should allow FedEx's emails to be delivered correctly.

The latest beta build 1.2.0.191 attempts to deliver emails with non-RFC compliant MAIL FROMs commands. Licensed users can find this build in the registered users area for download.

Please note that despite the relative simplicity of the problem, extensive changes have been made to handle it, and this build is a beta that has not been thoroughly tested.

Roberto
LogSat Software