Jump to content
Sign in to follow this  
eric

[Resolved] qq internal bug

Recommended Posts

[also posted on spamcop.mail newsgroup]

No mail is being accepted for filtering at the Spamcop mx:

[deleted][at]spamcop.net... Connecting to mx.spamcop.net. via esmtp...
220 mxin1.cesmail.net ESMTP
>>> EHLO mail.[deleted].com
250-mxin1.cesmail.net
250-PIPELINING
250-8BITMIME
250 SIZE 0
>>> MAIL From:<[deleted]> SIZE=4578
250 ok
>>> RCPT To:<[deleted]>
>>> DATA
250 ok
354 go ahead
>>> .
451 qq internal bug (#4.3.0)
[deleted]... Connecting to mx2.spamcop.net. via esmtp...
220 mx70.cesmail.net ESMTP
>>> EHLO mail.[deleted].com
250-mx70.cesmail.net
250-PIPELINING
250-8BITMIME
250 SIZE 0
>>> MAIL From:<[deleted]> SIZE=4578
250 ok
>>> RCPT To:<[deleted]>
>>> DATA
250 ok
354 go ahead
>>> .
451 qq internal bug (#4.3.0)
[deleted][at]spamcop.net... Deferred: 451 qq internal bug (#4.3.0)

This seemed to start today at about 13:51 PST, and is still happening as of 15:29 PST.

It appears to be an error at both cesmail MX hosts. As far as I can tell, this error is generated by qmail under some circumstances when it can't process an incoming SMTP transaction. No clue from the outside what the problem might be that started causing this just seconds after a successful SMTP message handoff.

Share this post


Link to post
Share on other sites
[also posted on spamcop.mail newsgroup]

No mail is being accepted for filtering at the Spamcop mx:

This seemed to start today at about 13:51 PST, and is still happening as of 15:29 PST.

It appears to be an error at both cesmail MX hosts. As far as I can tell, this error is generated by qmail under some circumstances when it can't process an incoming SMTP transaction. No clue from the outside what the problem might be that started causing this just seconds after a successful SMTP message handoff.

Is there any indication that this problem is being addressed? It is still continuing for me.

Greg

Share this post


Link to post
Share on other sites

server seems to be acceping mail now (1300 hrs AEST - GMT +11)

Is there any indication that this problem is being addressed? It is still continuing for me.

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  

×