Jump to content
Sign in to follow this  
gw1500se

[Resolved] spam with no originating IP

Recommended Posts

I keep getting spam that I cannot report because it results in the error:

Unable to process message. IPv6 addresses are not supported.

No source IP address found, cannot proceed.

I may have asked this question before but I don't think I was able to produce the headers at the time so it was really never resolved. This time I have posted the full headers below. I can see the X-Originating-IP header but I don't understand why this cannot be processed. Can someone shed any light on this and suggest what I might do? TIA.

X-Account-Key: account1

X-Mozilla-Keys:

X-Apparently-To: x via 98.138.213.185; Fri, 16 Dec 2011 04:55:43 -0800

Received-SPF: none (domain of frederickcountymd.gov does not designate permitted sender hosts)

X-YMailISG: QxBAIiYWLDsTRb0vX4H3O8YESsj39aUyP0BORMk7tItHihyn

jZlOpcwDIV7ioPjYQZ6RcUvQufWVeqbRYXV4eDjmviAITmlKUMmHx7RhO3Fo

Edq_Fu9NSlCKA4IAPGdegq5cLIriR8Xyw3tbTpckW5eY3R.wvShWJWpZGwHd

asp6qLrEvwzko9FWFUsBP4Scj4JXGYMm.7eeMIZwka.n5gcrcXh47VS9x5rk

Mpn9e81wWEEYGW5jCMLU_izzJboNQv5AipZWslqoZlufrG2PdsWzfV6h

X-Originating-IP: [199.248.201.241]

Authentication-Results: mta1013.sbc.mail.sp1.yahoo.com from=FrederickCountyMD.gov; domainkeys=neutral (no sig); from=FrederickCountyMD.gov; dkim=neutral (no sig)

Received: from 204.127.217.78 (EHLO fgateway08.isp.att.net) (204.127.217.78)

by mta1013.sbc.mail.sp1.yahoo.com with SMTP; Fri, 16 Dec 2011 04:55:43 -0800

Received: from mailgw2.frederickcountymd.gov ([199.248.201.241])

by isp.att.net (frfwmxc08) with ESMTP

id <20111216125543M080041q79e>; Fri, 16 Dec 2011 12:55:43 +0000

X-ATT-UNSOLICITED: OK

Received: from mailgw2.frederickcountymd.gov ([199.248.201.241])

by isp.att.net (frfwmxc08) with ESMTP

id <20111216125543M080041q79e>; Fri, 16 Dec 2011 12:55:43 +0000

X-Originating-IP: [199.248.201.241]

Received: from mailgw2.frederickcountymd.gov (localhost.localdomain [127.0.0.1])

by mailgw2.frederickcountymd.gov (8.13.8/8.13.8) with SMTP id pBGCtglv003558

for <x>; Fri, 16 Dec 2011 07:55:42 -0500

Received: from NT1S21.nt1.local ([10.12.20.123] helo=NT1S21.nt1.local) with

IPv4:25 by mailgw2.frederickcountymd.gov; 16 Dec 2011 07:55:42 -0500

Received: from nt1s21.nt1.local ([::1]) by NT1S21.nt1.local ([::1]) with mapi;

Fri, 16 Dec 2011 07:55:42 -0500

From: "Coleman, Sherman" <SColeman[at]FrederickCountyMD.gov>

To: "x" <x>

Date: Fri, 16 Dec 2011 07:55:41 -0500

Subject: Fw:

Thread-Index: Acy750wZMu3TXA60RKyg4fRMjhDnwAACrfzm

Message-ID: <D828__________________________________0D98[at]NT1S21.nt1.local>

Accept-Language: en-US

Content-Language: en-US

X-MS-Has-Attach:

X-MS-TNEF-Correlator:

acceptlanguage: en-US

x-tm-as-product-ver: SMEX-10.2.0.1135-6.800.1017-18586.004

x-tm-as-result: No--46.194300-0.000000-31

x-tm-as-user-approved-sender: Yes

x-tm-as-user-blocked-sender: No

Content-Type: multipart/alternative;

boundary="_000_D828BBBC7AA3CF49B52C756F07A2A3EF0CFBF80D98NT1S21nt1loca_"

MIME-Version: 1.0

X-Assp-Version: 1.8.1.7(1.0.06 on mailgw2.frederickcountymd.gov

X-Assp-Passing: acceptAllMail

X-Assp-ID: mailgw2.frederickcountymd.gov 13240-50489

X-Assp-Intended-For: x

X-Assp-Envelope-From: scoleman[at]frederickcountymd.gov

Share this post


Link to post
Share on other sites

Received: from nt1s21.nt1.local ([::1]) by NT1S21.nt1.local ([::1]) with mapi

That is an IPv6 "Received" line.

SpamCop goes wonky when it sees that and processing aborts.

We should have new processing code ready in the first quarter of 2012.

- Don D'Minion - SpamCop Admin -

- service[at]admin.spamcop.net -

Share this post


Link to post
Share on other sites

Received: from nt1s21.nt1.local ([::1]) by NT1S21.nt1.local ([::1]) with mapi

That is an IPv6 "Received" line.

SpamCop goes wonky when it sees that and processing aborts.

We should have new processing code ready in the first quarter of 2012.

- Don D'Minion - SpamCop Admin -

- service[at]admin.spamcop.net -

Thanks.

Share this post


Link to post
Share on other sites

It's now nearly the end of the second quarter of 2012, and we still can't report spam from IPv6 addresses.

IPv6 support in reporting was first promised to be ready in 2011.

More and more of my spam is unreportable because of this.

When is it going to be fixed?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×