ERROR WITH SPAMCOP MTA

[slootsky]

Starting around 9pm EST, the following type of errors started being generated...

----- The following addresses had permanent fatal errors -----

<user[at]spamcop.net>

(reason: 553 sorry, that domain isn't allowed to be relayed thru this MTA (#5.7.1))

----- Transcript of session follows -----

... while talking to mx2.cesmail.net.:

>>> DATA

<<< 553 sorry, that domain isn't allowed to be relayed thru this MTA (#5.7.1)

550 5.1.1 <user[at]spamcop.net>... User unknown

<<< 503 RCPT first (#5.5.1)

[Wazoo]

At this point in time, I'd suggest you shut down your system, clean caches, etc. and try it again in a bit. Your time frame places the failure over an hour ago, and if this was a system failure, the newsgroups would be smoking and I'm sure many more posts here in these Forums. Thus far, you're alone in noting the problem. Maybe in a while more folks will notice that they can't send their e-mail, but .... fir now, it looks like the failure is closer to home.

[jonsimon@spamcop.net]

I notified support[at]spamcop.net of this problem late this afternoon. I have been receiving these emails all day.

The original message was received at Wed, 26 May 2004 18:49:21 -0600 from root[at]localhost

----- The following addresses had permanent fatal errors ----- jonsimon[at]spamcop.net

(reason: 553 sorry, that domain isn't allowed to be relayed thru this MTA (#5.7.1))

----- Transcript of session follows -----

... while talking to mx2.cesmail.net.:

>>> DATA

<<< 553 sorry, that domain isn't allowed to be relayed thru this MTA (#5.7.1) 550 5.1.1 jonsimon[at]spamcop.net... User unknown <<< 503 RCPT first (#5.5.1)

[Wazoo]

OK, that makes two people. Thanks for adding to the data, but still have to state that it's pretty quiet for a "systemis-down" scenario .... not sure what to ask to ascertain oif there's something in common between the two of you outside the obvious ... location, OS, platform, etc ...

[Eönwë]

OK, that makes two people.  Thanks for adding to the data, but still have to state that it's pretty quiet for a "systemis-down" scenario ....  not sure what to ask to ascertain oif there's something in common between the two of you outside the obvious ...  location, OS, platform, etc ...

Three, since some time between 06:30 and 08:30 EDT Thursday 27 May. Stop brushing it off; there's a problem. I don't know how many MTAs there are, but if only one of them is h0rked, I'd not expect to see a lot of complaints. All the complaints I've seen say that it's MX2.CESMAIL.NET; that's the one that's h0rked for me as well. It's got to be fixed - now, before there are a lot of people ranting about it - or it's got to be pulled offline entirely until it can be fixed. Thirty-two bounces while trying to forward spam for reporting is NOT something that can be brushed off.

I'm using Forté Agent as my mailer, which doesn't cache lookups, so let's dispense with that issue immediately.

[Eönwë]

OK, this has just gotten a whole lot worse - it just bounced a user-directed report, which has now disabled my ability to report spam at all.

THIS MUST BE FIXED IMMEDIATELY. How do I get into priority contact with whoever is responsible for the crapped-out MTA?

:angry:

[turetzsr]

OK, this has just gotten a whole lot worse - it just bounced a user-directed report, which has now disabled my ability to report spam at all.

THIS MUST BE FIXED IMMEDIATELY.  How do I get into priority contact with whoever is responsible for the crapped-out MTA?

:angry:

...You can't. Only a Moderator or SpamCop employee can do that. Fortunately, by posting here you have done exactly the right thing to get a Moderator and/ or SpamCop employee to see it.

[hoffphil]

If I send email from my work exchange 2000 server to my spamcop address , I get this error message.

"The following message to <xxxxx> was undeliverable. The reason for the problem: 5.1.0 - Unknown address error 551-'This is not a relay host - mail must be to or from host domain.'"

However, if I send email from my hotmail account to my spamcop address it goes OK. I can also send email from my work exchange 2000 server to my hotmail account OK. What is it about spamcop that rejects my work exchange 2000 server email?

Thanks,

Phil

ps. here is the options view from the returned email

Microsoft Mail Internet Headers Version 2.0

Received: from nyntmail02.fxall.com ([208.251.159.49]) by nycluster01.fxall.com with Microsoft SMTPSVC(5.0.2195.6713);

Tue, 25 May 2004 13:27:47 -0400

Received: from nyspam01.fxall.com ([208.251.159.60]) by nyntmail02.fxall.com with Microsoft SMTPSVC(5.0.2195.6713);

Tue, 25 May 2004 13:27:47 -0400

Received: from c60.cesmail.net [216.154.195.49] by nyspam01.fxall.com - SurfControl E-mail Filter (4.7); Tue, 25 May 2004 13:27:46 -0400

Received: from unknown (0.0.0.0)

by c60.cesmail.net with ; 25 May 2004 13:27:47 -0400

From: Mail Delivery System <MAILER-DAEMON[at]c60.cesmail.net>

To: phil.hoff[at]FXALL.com

Date: 25 May 2004 13:27:47 -0400

Subject: Delivery Status Notification (Failure)

MIME-Version: 1.0

Content-Type: multipart/report; report-type=delivery-status; boundary="--=_NextPart_ST_13_27_46_Tuesday_May_25_2004_29390"

Return-Path: <>

Message-ID: <NYNTMAIL02YILoygXLs00000c77[at]nyntmail02.fxall.com>

X-OriginalArrivalTime: 25 May 2004 17:27:47.0072 (UTC) FILETIME=[9889A800:01C4427D]

----=_NextPart_ST_13_27_46_Tuesday_May_25_2004_29390

Content-Type: text/plain

----=_NextPart_ST_13_27_46_Tuesday_May_25_2004_29390

Content-Type: message/delivery-status

----=_NextPart_ST_13_27_46_Tuesday_May_25_2004_29390

Content-Type: message/rfc822

Received: (qmail 2338 invoked by uid 1010); 25 May 2004 17:27:45 -0000

Delivered-To: spamcop-net-phoff2824[at]spamcop.net

Received: (qmail 2320 invoked from network); 25 May 2004 17:27:45 -0000

Received: from unknown (192.168.1.101)

by blade1.cesmail.net with QMQP; 25 May 2004 17:27:45 -0000

Received: from host3.fxall.com (HELO nycluster01.fxall.com) (208.251.159.3)

by mailgate.cesmail.net with SMTP; 25 May 2004 17:27:45 -0000

X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0

content-class: urn:content-classes:message

MIME-Version: 1.0

Content-Type: multipart/alternative;

boundary="----_=_NextPart_001_01C4427D.96BB4918"

Subject: fxall

Date: Tue, 25 May 2004 13:27:44 -0400

Message-ID: <204AB30D250D5945B495E9BC153366FB0173BDAA[at]NYCLUSTER01.fxall.com>

X-MS-Has-Attach:

X-MS-TNEF-Correlator:

Thread-Topic: fxall

Thread-Index: AcRCfZa8K7vn4uLLRwmSR06vNik09g==

From: "Phil Hoff" <phil.hoff[at]FXALL.com>

To: <phoff2824[at]spamcop.net>

X-spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on blade1

X-spam-Level: *

X-spam-Status: hits=1.2 tests=HTML_MESSAGE,MIME_HTML_MOSTLY version=2.63

X-SpamCop-Checked: 192.168.1.101 208.251.159.3

------_=_NextPart_001_01C4427D.96BB4918

Content-Type: text/plain;

charset="us-ascii"

Content-Transfer-Encoding: quoted-printable

------_=_NextPart_001_01C4427D.96BB4918

Content-Type: text/html;

charset="us-ascii"

Content-Transfer-Encoding: quoted-printable

------_=_NextPart_001_01C4427D.96BB4918--

----=_Next

[StevenUnderwood]

This very topic is being discussed in the Email forum right now:

http://forum.spamcop.net/forums/index.php?showtopic=1591

Hopefully a moderator will move or merge this comment over there.

The Email Setup forum is for configuring spamcop to work with any particular users setup.

[Wazoo]

OK, this makes 4. I did see the post over in the newsgroups. I don't think I was "minimizing" at all, just pointing out the lack of an outcry. But yes, JT notified. hoffphil also PM'd to advise of the movement of his/her post.

[Merlyn]

Justin posted in .email:

"I was able to contact JT and he has corrected the issue."

[Wazoo]

Justin posted in .email:

"I was able to contact JT and he has corrected the issue."

I just did a reset on the newsgroups .. I only see spamcop.mail .. but thought that that group had been dropped a while back .. interesting.

[Merlyn]

Justin posted in .email:

"I was able to contact JT and he has corrected the issue."

I just did a reset on the newsgroups .. I only see spamcop.mail .. but thought that that group had been dropped a while back .. interesting.

None of the groups have actually been dropped. Many frequent the groups. Actually I prefer the groups instead of this type of interface.

[Merlyn]

Justin posted in .email:

"I was able to contact JT and he has corrected the issue."

Quoting myself

I meant .mail not .email

<AOL>Fingers to fast, brain to slow</AOL>

[Wazoo]

None of the groups have actually been dropped. Many frequent the groups. Actually I prefer the groups instead of this type of interface.

Though you quoted me, I know you're not talking to me <g>

I was going that though it's a few more clicks to find the NNTP links to most of the newsgroups, the .mail links were dropped way back when. Not using the e-mail stuff myself, was never subscribed, but that no "new" user is goin gto stumble in there is why I was going with "it's dead" ...

[Merlyn]

None of the groups have actually been dropped. Many frequent the groups. Actually I prefer the groups instead of this type of interface.

Though you quoted me, I know you're not talking to me <g>

I was going that though it's a few more clicks to find the NNTP links to most of the newsgroups, the .mail links were dropped way back when. Not using the e-mail stuff myself, was never subscribed, but that no "new" user is goin gto stumble in there is why I was going with "it's dead" ...

Actually when you point your newsreader at news.spamcop.net you get a list of all the groups available.

[Wazoo]

Agreed, I did mention that I did a "reset" just to make sure that what I was seeing was more than just a ghost of what was (and to try to pull up your 'new' group <g>) ... but again, I'm referring to the newbies that if found, they'd only get to the page showing NNTP/WebTV links ...

[Wazoo]

> http://forum.spamcop.net/forums/index.php?showtopic=3D1591

> One user complained, suggested a possible issue at his end.

> Only complaint in the newsgroup at this time is a posting

> by the another user that I was minimizing the issue in the

> Forums. Well, there's now a total of four people that

> may be talking about the same issue.

Yeah, sorry about that. There was a problem, now fixed.

Jeff

Yet another confirmation that the problem is fixed.