You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Duane Hill <d....@yournetplus.com> on 2005/10/30 14:48:22 UTC
unparsable relay
Hello All,
Did some searching but couldn't really come up with much. Is there
anything that can be done to correct unparsable relays? I see then
in the SA header markup every once in a while. It is causing a small
issue with some Spam getting through.
If this has been covered before, just tell me to go search more :)
--
"This message is made of 100% recycled electrons."
Re: unparsable relay
Posted by Duane Hill <d....@yournetplus.com>.
On Sunday, October 30, 2005 at 11:31:29 PM, usebsd@free.fr confabulated:
> Duane Hill a écrit :
>>Received: from support@yournetplus.com
>> by admin.mwci.net (CommuniGate Pro GROUP 4.2.8)
>> with GROUP id 166248333; Sun, 30 Oct 2005 20:03:56 +0000
>>
>>
> GROUP is not a known method and support@foo is not a known from. the
> communigate guys should really put these between parens. the with
> methods must be registered at IANA, uless communigate developpers want
> us to consider all mail relayed through their bugware as spam.
> now, should SA ignore unknown methods?
Your guidance is much appreciated! I will address this with them and
see what is said.
--
"This message is made of 100% recycled electrons."
Re: unparsable relay
Posted by mouss <us...@free.fr>.
Duane Hill a écrit :
>Received: from support@yournetplus.com
> by admin.mwci.net (CommuniGate Pro GROUP 4.2.8)
> with GROUP id 166248333; Sun, 30 Oct 2005 20:03:56 +0000
>
>
GROUP is not a known method and support@foo is not a known from. the
communigate guys should really put these between parens. the with
methods must be registered at IANA, uless communigate developpers want
us to consider all mail relayed through their bugware as spam.
now, should SA ignore unknown methods?
Re: unparsable relay
Posted by Duane Hill <d....@yournetplus.com>.
On Sunday, October 30, 2005 at 4:33:48 PM, usebsd@free.fr confabulated:
> Duane Hill a écrit :
>>Hello All,
>>
>> Did some searching but couldn't really come up with much. Is there
>> anything that can be done to correct unparsable relays? I see then
>> in the SA header markup every once in a while. It is causing a small
>> issue with some Spam getting through.
>>
>> If this has been covered before, just tell me to go search more :)
>>
> can you post samples?
This particular one happens to be a legit message.
Return-Path: <mc...@lists.mci.com>
Received: by admin.mwci.net (CommuniGate Pro PIPE 4.2.8)
with PIPE id 166248378; Sun, 30 Oct 2005 20:03:58 +0000
X-Spam-Flag: NO
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on cgppri.ndunet.com
X-Spam-Level:
X-Spam-Status: Hits:-2.3 Bayes:0.0000 Bayes-Lrnd:ham Tests:BAYES_00,
UNPARSEABLE_RELAY
Received: from support@yournetplus.com
by admin.mwci.net (CommuniGate Pro GROUP 4.2.8)
with GROUP id 166248333; Sun, 30 Oct 2005 20:03:56 +0000
X-Autogenerated: group
Received: from pmesmtp01.mci.com ([199.249.20.1] verified)
by admin.mwci.net (CommuniGate Pro SMTP 4.2.8)
with ESMTP id 166248315 for support@yournetplus.com; Sun, 30 Oct 2005 20:03:56 +0000
Received: from dgismtp01.wcomnet.com ([166.38.58.141])
by firewall.mci.com (Iplanet MTA 5.2)
with ESMTP id <0I...@firewall.mci.com> for support@yournetplus.com;
Sun, 30 Oct 2005 20:03:30 +0000 (GMT)
Received: from dgismtp01.wcomnet.com by dgismtp01.mcilink.com
(iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003))
with SMTP id <0I...@dgismtp01.mcilink.com>; Sun,
30 Oct 2005 20:03:28 +0000 (GMT)
Received: from pmmlists1.mcilink.com ([166.38.62.106])
by dgismtp01.mcilink.com (iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar
18 2003)) with ESMTP id <0I...@dgismtp01.mcilink.com>; Sun,
30 Oct 2005 20:03:27 +0000 (GMT)
Received: from dgismtp04.wcomnet.com ([166.38.58.144])
by pmmlists1.mcilink.com (Post.Office MTA v3.5.3 release 223 ID#
0-72210U28000L34000S0V35)
with ESMTP id com for <mc...@lists.mci.com>; Sun,
30 Oct 2005 20:03:25 +0000
Received: from CONVERSION-DAEMON.dgismtp04.mcilink.com by dgismtp04.mcilink.com
(iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003))
id <0I...@dgismtp04.mcilink.com> for mci_irsc_maints@lists.mci.com;
Sun, 30 Oct 2005 20:03:24 +0000 (GMT)
Received: from dgismtp04.wcomnet.com by dgismtp04.mcilink.com
(iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003))
with SMTP id <0I...@dgismtp04.mcilink.com> for
mci_irsc_maints@lists.mci.com; Sun, 30 Oct 2005 20:03:24 +0000 (GMT)
Received: from imr0.ash.ops.us.uu.net ([153.39.43.11])
by dgismtp04.mcilink.com (iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar
18 2003)) with ESMTP id <0I...@dgismtp04.mcilink.com>; Sun,
30 Oct 2005 20:03:24 +0000 (GMT)
Received: from noclogin2.sfld.ops.us.uu.net by imr0.ash.ops.us.uu.net with
ESMTP (peer crosschecked as: noclogin2.sfld.ops.us.uu.net [147.225.16.31])
id j9UK3NWN004278; Sun, 30 Oct 2005 20:03:23 +0000 (GMT)
Received: from localhost by noclogin2.sfld.ops.us.uu.net with SMTP
(peer crosschecked as: kat@localhost) id j9UK3MxE008759; Sun,
30 Oct 2005 20:03:22 +0000 (GMT)
Date: Sun, 30 Oct 2005 20:03:22 +0000 (GMT)
From: MCI Reseller Support Center <rs...@mci.com>
Subject: Urgent Maintenance Announcements for Thursday, November 3, 2005
X-Sender: kat@noclogin2.sfld.ops.us.uu.net
To: Undisclosed.Recipients@mci.com
Message-id:
<Pi...@noclogin2.sfld.ops.us.uu.net>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
--
"This message is made of 100% recycled electrons."
Re: unparsable relay
Posted by mouss <us...@free.fr>.
Duane Hill a écrit :
>Hello All,
>
> Did some searching but couldn't really come up with much. Is there
> anything that can be done to correct unparsable relays? I see then
> in the SA header markup every once in a while. It is causing a small
> issue with some Spam getting through.
>
> If this has been covered before, just tell me to go search more :)
>
>--
>
>"This message is made of 100% recycled electrons."
>
>
>
>
can you post samples?