Search the Community
Showing results for tags 'gmail'.
Found 4 results
Sorry for the long post; I'm trying to be crystal clear. I sent this to the "service[at]admin.spamcop.net" address on June 5, 2018 but never heard back from anyone. If this is covered elsewhere, please point me to an appropriate thread. I've searched the forums and can't find a clear answer. Quick backstory: I've been using SpamCop since the early days. In fact, I swapped email and design ideas for the SpamCop logo with founder Julian Haight around 1998. The logo I designed and donated is still in use by SpamCop. I'm running the latest versions of MacOS (10.13.4) and Apple Mail. In addition to one "real" email address for my design studio's domain, I have one Gmail address. The Gmail account is set up to forward incoming mail to my Mac (with IMAP)... which means Gmail also forwards spam sent to the Gmail account. Grrrr. It used to be simple to report that spam... I revealed the raw source (full headers and body), copied, and pasted into the SpamCop reporting form. Worked like a charm for years until the new Mail-host system went in to effect. When attempting to report spam from my Gmail account the system now says: I've tried unsuccessfully to correct this. I even deleted the old Gmail host configuration and followed the instructions to make a new one. I received 5 test messages from the SpamCop bot and successfully submitted them via the online form at https://www.spamcop.net/mcgi?action=mhreturn A new Gmail host was created in the Mailhosts section of my SpamCop account. But it doesn't work. I'm getting the same "nothing to do" result when attempting to report spam. Can someone walk me through this? Please be kind: I'm not a programmer—just a designer. It's probably something simple, but the instructions are not clear to me. BTW, spam that slips through Mail filters to my "real" address inbox is easy to report and works fine on the SpamCop report page. I haven't tried forwarding spam directly to SpamCop in years. That never worked (it bounces). Sigh. Thanks in advance for any tips and help. I love reporting spam via SpamCop. Even if it's only symbolic and doesn't truly help stop the onslaught, it makes me feel a bit better.
This problem has recently (last 7-10 days) popped up. Every report I attempt to submit, ends up with this or similar: Parsing header: host 2002:a81:8705:0:0:0:0:0 (getting name) no name 0: Received: by 2002:a81:8705:0:0:0:0:0 with SMTP id x5-v6csp1438670ywf; Thu, 24 May 2018 07:42:11 -0700 (PDT) No unique hostname found for source: 2002:a81:8705:0:0:0:0:0 Possible forgery. Supposed receiving system not associated with any of your mailhosts Will not trust this Received line. Mailhost configuration problem, identified internal IP as source Mailhost: Please correct this situation - register every email address where you receive spam No source IP address found, cannot proceed. The email was sent to my GMAIL address, I then tried to reprocess my MAILHOSTs configuration for GMAIL. No help! Any ideas? Tracking URL is: https://www.spamcop.net/sc?id=z6466300524z8c4f8dd4c37bd064db31639836fe7077z
I may move my domain to a hosted service from a SaaS provider. One issue I'm trying to solve is how to report spam from Gmail to Spamcop. Now, I understand about display source and copy and paste, but not when I have 10's of messages to report, that's not going to happen. I'm wondering if there is some clever API mechanism that could be triggered (even remotely) when messages are stored in a certain folder. Anyone found a decent hack that will work reliably?
Hi all! Sorry if posting in wrong forum - but this one seemed most appropriate at first glance. Since at least few weeks I am experiencing problems with mail delivery. Mails send from GMail and Google Apps users to me (I'm using commercial hosting) are delayed or fail to deliver. Delays are random - from minutes to many hours. After many hours and days spend on tests and analyzing Received headers I found the cause - it turned out, that my hosting company is using SpamCop's blacklists and that some GMail IP addresses has been blacklisted. For example this IP: https://www.spamcop.net/w3m?action=checkblock&ip=188.8.131.52 - and many other from range 184.108.40.206 - 220.127.116.11 - which belong to Google and are used by GMail MTA servers. I think that those IPs should be whitelisted (whole: 18.104.22.168/17 range and probably some other ranges) - because those IPs are used also when normal users (not spammers) send mails using GMail (via both: web interface and SMTP server). If hosting company uses Spamcop's blacklist, mails send from GMail or Google Apps get delayed - even for hours, until Google retries sending them from different IP - one that is not blacklisted. If sender has no luck and Google retries sending message only through blacklisted IPs for more than 24h, then Mail Delivery Subsystem informs, that it failed to deliver mail. It took quite a lot of time for me to find the cause of those delays - since Google and my hosting company weren't very helpful. And now, Google support says it's not their problem, that somebody blacklisted them, while my hosting company insists, that Google and Spamcop should take care of it (but they probably even didn't inform you about the problem, reported by many of their clients). I also see that there are search results for gmail blacklisted by spamcop - some quite fresh, from last few weeks... I'm a little fed up with my hosting company, because I think that they should report (or resolve) such things - as they are users of SpamCop's blacklists - and I'm just their client, that should not care about it at all. At the moment they whitelisted some IPs (not whole range mentioned above) - and delays occur less frequently - but weren't fully eliminated. And they don't want to whitelist anything more - they are just waiting until Google and SpamCop fix the problem. I hope the problem can be solved - otherwise I will have to search for other hosting companies - ones that don't use spamcop's BLs - quite strange criterion... I am aware that according to RFC, mail protocol wasn't meant for instantaneous delivery - but such delays are difficult to accept these days. Regards, Mirek