Spamcop and SORBS blacklist Gmail.com

It appears that both SpamCop and SORBS are blacklisting part or all of Gmail's outgoing SMTP servers for sending mail to spam traps. This means that effectively gmail users will be deprived of the chance to send their e-mails to our servers, and possibly very large portions of the internet too.

I've done some lookups based on hits on my mailservers and it's pretty bad, feel free to complain to Gmail and spamcop and SORBS about this, as the automated spamtraps from those two groups do not distinguish between traps and lured trap hits - and this is looking very suspicious to me. Someone is trying to screw with gmail.

Lookups:
http://www.us.sorbs.net/lookup.shtml?72.14.204.200,
http://www.spamcop.net/w3m?action=blcheck&ip=72.14.204.206.

Sep 24 02:02:22 espresso lard[4919]: executing command: "/usr/sbin/block-ip-from 'Sep 24 02:02:22
espresso postfix/smtpd[11751]: NOQUEUE: reject: RCPT from qproxy.gmail.com[72.14.204.205]: 554
Service unavailable; Client host [72.14.204.205] blocked using bl.spamcop.net; Blocked - see
http://www.spamcop.net/bl.shtml?72.14.204.205; from= to=
proto=ESMTP helo='"
Sep 24 02:20:19 espresso lard[4919]: executing command: "/usr/sbin/block-ip-from 'Sep 24 02:20:19
espresso postfix/smtpd[12524]: NOQUEUE: reject: RCPT from qproxy.gmail.com[72.14.204.203]: 554
Service unavailable; Client host [72.14.204.203] blocked using bl.spamcop.net; Blocked - see
http://www.spamcop.net/bl.shtml?72.14.204.203; from= to=
proto=ESMTP helo='"
Sep 24 02:25:07 espresso lard[4919]: executing command: "/usr/sbin/block-ip-from 'Sep 24 02:25:07
espresso postfix/smtpd[12833]: NOQUEUE: reject: RCPT from xproxy.gmail.com[66.249.82.194]: 554
Service unavailable; Client host [66.249.82.194] blocked using bl.spamcop.net; Blocked - see
http://www.spamcop.net/bl.shtml?66.249.82.194; from= to=
proto=ESMTP helo='"
Sep 24 02:32:20 espresso lard[4919]: executing command: "/usr/sbin/block-ip-from 'Sep 24 02:32:20
espresso postfix/smtpd[13396]: NOQUEUE: reject: RCPT from xproxy.gmail.com[66.249.82.192]: 554
Service unavailable; Client host [66.249.82.192] blocked using bl.spamcop.net; Blocked - see
http://www.spamcop.net/bl.shtml?66.249.82.192; from= to=
proto=ESMTP helo='"

Message back from SpamCop


Hi -- we have had discussions with gmail about this. They refuse to include
any IP in the headers indicating the injecting user and only have their own
IP. All the other large free mailers include the injecting user IP which we
recognize as the source of the spam.

Ellen
SpamCop

That's pretty bad, I never looked at it this way. Perhaps I should add SpamCop back to our list again - even hotmail and yahoo do this and google should not play the web censor itself IMHO. No reply from sorbs, although I didn't ask for one.

Message back from SORBS


Google is being used by 419 spammers, and we are playing whack -a-mole with them at the moment.

We are hoping that Google will start inmpllementing some of the controls that ISPs have been forced to.

Until then they'll go in and out of SORBS regularly.

Regards,

Mat

Good to know... I'm considering putting both blacklists back into work - they catch 95% of spam or more on espresso.

If you want to help - complain to google.