Re: unparsable relay

2005-10-30 Thread Duane Hill
On Sunday, October 30, 2005 at 11:31:29 PM, [EMAIL PROTECTED] confabulated: > Duane Hill a écrit : >>Received: from [EMAIL PROTECTED] >> by admin.mwci.net (CommuniGate Pro GROUP 4.2.8) >> with GROUP id 166248333; Sun, 30 Oct 2005 20:03:56 + >> >> > GROUP is not a known method and [EMAIL

Re: unparsable relay

2005-10-30 Thread mouss
Duane Hill a écrit : Received: from [EMAIL PROTECTED] by admin.mwci.net (CommuniGate Pro GROUP 4.2.8) with GROUP id 166248333; Sun, 30 Oct 2005 20:03:56 + GROUP is not a known method and [EMAIL PROTECTED] is not a known from. the communigate guys should really put these between parens.

Re: unparsable relay

2005-10-30 Thread Duane Hill
On Sunday, October 30, 2005 at 4:33:48 PM, [EMAIL PROTECTED] 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 on

Re: unparsable relay

2005-10-30 Thread Justin Mason
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 mouss writes: > Duane Hill a écrit : > > 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

Re: unparsable relay

2005-10-30 Thread mouss
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