Jump to content

[Resolved] Spamcop certified?


moltar

Recommended Posts

I was just talking to the tech support at mail service [at]canada.com and the guy told me that my mail server is not certified with SpamCop. What the hell does that mean? How can I certify with SpamCop? I've been a paying customer for the email service at spamcop for 3 years. I've listed my servers in mailhosts in the CP. What else do I need to do?

Link to comment
Share on other sites

Hi, moltar,

...AFAIK, you need to do nothing as far as SpamCop is concerned. I don't know what the tech support person meant, either. Perhaps you can get her/him to clarify?

...Just to satisfy my curiosity, what is "the CP" where you've listed your servers?

Link to comment
Share on other sites

I was just talking to the tech support at mail service [at]canada.com and the guy told me that my mail server is not certified with SpamCop. What the hell does that mean? How can I certify with SpamCop? I've been a paying customer for the email service at spamcop for 3 years. I've listed my servers in mailhosts in the CP. What else do I need to do?

37276[/snapback]

Please explain what you were trying to do that got you into the conversation.

I'm thinking you were trying to send an email to their site, got some kind of rejection and called. That could be related to spamcop being on some blacklists itself, or because they do not use SPF records, but I'm just guessing here.

Link to comment
Share on other sites

Please explain what you were trying to do that got you into the conversation. 

I'm thinking you were trying to send an email to their site, got some kind of rejection and called.  That could be related to spamcop being on some blacklists itself, or because they do not use SPF records, but I'm just guessing here.

37280[/snapback]

Man, you are psychic!

Here is the story:

I own a dedicated server. One of my clients has an email accounts at his domain that simply forward to the [at]canada.com mailbox. He wants it that way, because he doesn't want to check multiple mailboxes.

So whenever someone sends an email to his domain address, they all bounce back (bounce comes from my qmail) to the sender with the following error:

<*USER*[at]canada.com>:

216.xxx.xxx.xxx does not like recipient.

Remote host said: 550 Command RCPT User <*USER*[at]canada.com> not OK

Giving up on 216.xxx.xxx.xxx.

Tech's initial guess was that it's something related to SpamCop, because they use it for filtering, and he asked me whether my server was "certified" with SpamCop.

After I read the error message to him, he said that in fact the error is on their side and has nothing to do with SpamCop. But I am still curious as whether I need to get my server "certified".

Link to comment
Share on other sites

Man, you are psychic!

But I am still curious as whether I need to get my server "certified".

37281[/snapback]

I'll add that to my resume ;)

No, there is not certified as far as spamcop is concerned. The IP address is either currently sending spam (as reported by it's users) or it not.

Mailhosts only function is to help avoid reporting your own mail providers during the reporting process.

Link to comment
Share on other sites

To my knowledge, no one certifies servers with SpamCop. Definitely ask for clarification. If the tech pushes the issue, ask to see proof that his admins/management certified their servers with SpamCop. :)

Link to comment
Share on other sites

To my knowledge, no one certifies servers with SpamCop.  Definitely ask for clarification.  If the tech pushes the issue, ask to see proof that his admins/management certified their servers with SpamCop.  :)

37283[/snapback]

I'll definetely do that when I call them back tomorrow to follow up on the issue. I'll let you know here what they said.

Link to comment
Share on other sites

<*USER*[at]canada.com>:

216.xxx.xxx.xxx does not like recipient.

Remote host said: 550 Command RCPT User <*USER*[at]canada.com> not OK

Giving up on 216.xxx.xxx.xxx.

I am unable to make any sense out of this statement, but do have one suggestion you may want to followup on.

Is your mail server and domain properly configuered?

Correct MX records?

Correct rDNS records?

Abuse address?

etc

Incorrect or missing records have been known to cause mail rejection by some servers.

Link to comment
Share on other sites

Correct rDNS records?

Abuse address?

37291[/snapback]

I did DNS report (www.dnsreport.com) and got a few warnings and one error, I am not sure, but I didn't think they were that important...

WARNING: Your SOA serial number is: 1133877169

WARNING: One or more of your mailservers is claiming to be a host other than what it really is (the SMTP greeting should be a 3-digit code, followed by a space or a dash, then the host name). This probably won't cause any harm, but is a technical violation of RFC821 4.3 (and RFC2821 4.3.1). Note that the hostname given in the SMTP greeting should have an A record pointing back to the same server.

mail.CLIENT_DOMAIN.ca claims to be host HOST_DOMAIN.ca [but that host is at xx.xx.xx.175, not xx.xx.xx.230].

ERROR: One or more of your mailservers does not accept mail to postmaster[at]CLIENT_DOMAIN.ca. Mailservers are required (RFC822 6.3, RFC1123 5.2.7, and RFC2821 4.5.1) to accept mail to postmaster.

WARNING: One or more of your mailservers does not accept mail to abuse[at]CLIENT_DOMAIN.ca. Mailservers are expected by RFC2142 to accept mail to abuse.

Your domain does not have an SPF record. This means that spammers can easily send out E-mail that looks like it came from your domain, which can make your domain look bad (if the recipient thinks you really sent it), and can cost you money (when people complain to you, rather than the spammer). You may want to add an SPF record ASAP, as 01 Oct 2004 was the target date for domains to have SPF records in place (Hotmail, for example, started checking SPF records on 01 Oct 2004).
Link to comment
Share on other sites

I just added two email accounts - postmaster and abuse, tried to send a test email - and still getting bounces. So it must be something on their side.

BTW I can't add SPF records, because the server is under Plesk, and Plesk doesn't allow that. I can edit the DNS records manually, but once I change something thru Plesk it will overwrite the file with it's own values.

Link to comment
Share on other sites

A 'real' server admin is reading this topic and may provide better information, but in my quick look up, that IP address is not on any blocklists at the moment.

IIWY, I would be very assertive to whomever is giving you a hard time. the scbl is entirely automatic; if an IP address is reported as sending spam, it is listed. When the spam stops, it is delisted. No certification.

Miss Betsy

Link to comment
Share on other sites

Seems A-OK with SCBL and a few others:

Parsing input: 69.64.32.230
host 69.64.32.230 = terrahost.ca (cached)
No recent reports, no history available

Statistics:
69.64.32.230 not listed in bl.spamcop.net
69.64.32.230 not listed in dnsbl.njabl.org
69.64.32.230 not listed in dnsbl.njabl.org
69.64.32.230 not listed in cbl.abuseat.org
69.64.32.230 not listed in dnsbl.sorbs.net
69.64.32.230 not listed in relays.ordb.org.

Link to comment
Share on other sites

it is actually blocked by one of the services - outblaze.com, but that happened just recently and I am trying to figure out why...

37314[/snapback]

Are you sure about that?

http://spamblock.outblaze.com/69.64.32.230

RBL Status

IP Entered Date Status Reason

   Not Found.

Explanatory Note :

Your IP is not currently blocked by us.

According to :http://spamblock.outblaze.com/spamchk.html

They use the following:

ORDB http://www.ordb.org Open Relays

SBL http://www.spamhaus.org spam Sources

XBL http://www.spamhaus.org Compromised Hosts

Sorbs DUHL http://www.sorbs.net Dynamic IPs

DSBL http://www.dsbl.org Insecure Servers

Which, as I posted above, you're not listed on.

Link to comment
Share on other sites

in my quick look up, that IP address is not on any blocklists at the moment.

37311[/snapback]

A longer look shows that it is listed by SORBSSPEWS-L1, SORBSSPEWS-L2, and DNSBLAUSPEWS (see http://spews.org/ask.cgi?S1267 or more specifically http://spews.org/html/S1267.html for details on that listing, which appears to be escalation for the nefarious activities of 69.64.32.59) per dr. jørgen mash's DNS database list checker drbcheck at http://moensted.dk/spam/?addr=69.64.32.230 , SenderBase doesn't see mail from it, and it has no history with SpamCop. Perhaps canada.com is blocking mail from servers listed by SPEWS rather than by the SCBL? In any case, Sascha Wintz <s.wintz[at]server4you.net> at Server4You Inc. already appeared to be taking a good long look at 69.64.32.59 per http://groups.google.com/groups?q=69.64.32.59 last year, but given Server4You's whois and postmaster problems, perhaps you should be seeking another provider.
Link to comment
Share on other sites

I guess they removed it because I complained. They told me that they won't remove me until i fix my problems. Which I was investigating, but just didn't see any way there could be spam from my server. I checked all the logs and everything and couldn't find anything. So good to know! :)

Link to comment
Share on other sites

http://www.dnsstuff.com/tools/ip4r.ch?ip=69.64.32.230 - SPEWS1 & 2

http://www.moensted.dk/spam/?addr=69.64.32.230&Submit=Submit - 3 SPEWS listings

http://www.senderbase.org/?searchBy=ipaddr...ng=69.64.32.230 - some very confusing data there ... are you sure about this IP address?

When I see "outblaze" I don't think of a 'service' .... I think of a world-renowned anti-spam abuse person ....

Link to comment
Share on other sites

Well damn, the SPEWs stuff is ridiculours. They listed 69.64.32.0/24, when there are only 2 IPs of mine that in that block.

Hosting company randomly allocates IPs all over the place. I have 5 IPs and they are from 3 different blocks.

[edit]typo[/edit]

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...