Jump to content
Sign in to follow this  
Nisse

SpamCop rejecting report

Recommended Posts

There's a misconfigured BT Connect mailserver out there that keeps trying to send us an email, despite the fact that we keep rejecting it with a 550.

SpamCop refuses to accept a report for this, because instead of looking at the date we receive the mail, it's looking at the date the mail was originally sent, and saying it's too old to report.

Can anything be done about this?

Share this post


Link to post
Share on other sites

Much confusion here. Use of a 5xx code would normally suggest that the incoming e-mail was rejected. Yet, you suggest that you're trying to 'report' one of these e-mails. Something missing in the story, specifically just how you are generating the 5xx rejection notice, when you are sending it, how you are still actually receiving the e-mail in question, etc....

In general, the SpamCop parser makes it's decision on the 'date' based on the top-most valid Received: line, which is normally "your" server. No data provided to look at from this side of the screen.

Your query/picture doesn't actually state that the specific e-mail in question "is" spam .... but also based on the picture you paint, there is a possible question about the mis-use of the SpamCop parsing and reporting tool .. again, no data to look at ...

If the issue is "just this one BT Connect mailserver, have you tracked down ownership of that server and contacted those folks directly? If you are actually running your own mailserver, why not put a block on that incoming IP? Again, not sure what you are really asking for, based on that you provided no specific data to work with and part of the story just doesn't "sound" right.

Share this post


Link to post
Share on other sites
There's a misconfigured BT Connect mailserver out there that keeps trying to send us an email, despite the fact that we keep rejecting it with a 550.

SpamCop refuses to accept a report for this, because instead of looking at the date we receive the mail, it's looking at the date the mail was originally sent, and saying it's too old to report.

Can anything be done about this?

29478[/snapback]

We need to see the Tracking URL to get any useful information back to you but the date SHOULD be the date from the earliest trusted source. If the message first hit their server too long ago, that would be accurate.

It is also possible that this is not the same email message but many of the same type messages, all sent seperately.

Question: Since you are rejecting them with a 550, that usually indicates that you are NOT downloading the entire message.

If I were you, I would contact the support people at BT and ask them to stop trying to resend this message. It is questionable whether this would legally be reportable through spamcop.

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  

×