If you look closely at the headers, you'll see that the first 'Received:' header is tagged as using HTTP (not SMTP) protocol.
Received: from localhost (webmail2-maint.its.uiowa.edu [128.255.56.154])
by day.its.uiowa.edu (8.12.9/8.12.9/ns-mx-1.14) with ESMTP id h6H21naK015350;
Wed, 16 Jul 2003 21:01:49 -0500
Received: from AC826956.ipt.aol.com (AC826956.ipt.aol.com [172.130.105.86])
by webmail2.its.uiowa.edu (IMP) with HTTP
for <[EMAIL PROTECTED]>; Wed, 16 Jul 2003 21:01:49 -0500
I realize that this is a rather unusual kind of header to find in a mail transaction, but it is a correct usage of the protocol.
It's not that unusual actually, we use Squirrelmail for webmail, and it does the same thing (HTTP header) for example:
Received: from webmail.igrin.co.nz (mail.igrin.co.nz [202.49.244.12])
by mail.igrin.co.nz (8.11.6p2/8.11.6) with SMTP id h6HNRQQ09080
for <[EMAIL PROTECTED]>; Fri, 18 Jul 2003 11:27:26 +1200
Received: from 202.49.244.7 (proxying for 202.49.247.225)
(SquirrelMail authenticated user simon)
by webmail.igrin.co.nz with HTTP;
Fri, 18 Jul 2003 11:27:26 +1200 (NZST)So hopefully this kind of thing is handled properly when SpamAssassin parses the headers....
Regards, Simon
------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here: http://www.vmware.com/wl/offer/345/0 _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
