Jump to content

Jeff G.

Membersph
  • Content Count

    3,727
  • Joined

  • Last visited

Everything posted by Jeff G.

  1. No, but that's been preventing notifications to you and/or your admins of problems. OK, here's one: stop sending UUBE.
  2. In my case (using OE6), it is recording the machine name, which I understand OE6 typically uses in its HELO greeting. And I couldn't get OE6's SSL to work with it. Other than that, it works just great!
  3. Jeff G.

    No Information Email

    BTW, please be aware of the info on http://www.enom.com/domains/whois.asp?Doma...amp;submit.y=13 and http://www.whitepages.com/10866/search/Rev...hone=7704320779 .
  4. As soon as you change something and click the "Modify" Button bringing you to https://webmail.spamcop.net/horde/imp/spamc....php?modified=1 or http://webmail.spamcop.net/horde/imp/spamc....php?modified=1, the SpamCop Email System should start POPping your email, or throwing an Error. It should take no more than 15 minutes. You did configure your Gmail account to allow you to POP from it, right?
  5. Jeff G.

    No Information Email

    That's great, but please make sure that you still implement all of the aliases required of you by RFC2142.
  6. Unfortunately, it looks like you might not be getting any email whatsoever because server mail.macupgrades.co.uk.macupgrades.co.uk doesn't exist - see the following for details:
  7. Jeff G.

    Individual Email Blocked

    mail.internode.on.net (203.16.214.182) has the following recent Report History (it shouldn't be sending bounces entitled "Returned mail: see transcript for details"): Submitted: Sunday 2006/10/08 11:34:59 -0400: Returned mail: see transcript for details 1957171426 ( 203.16.214.182 ) ( UUBE ) To: uube[at]devnull.spamcop.net --------------------------------------------- Submitted: Friday 2006/10/06 18:31:31 -0400: Returned mail: see transcript for details 1954684771 ( 203.16.214.182 ) ( UUBE ) To: uube[at]devnull.spamcop.net --------------------------------------------- Submitted: Friday 2006/10/06 05:11:51 -0400: =?windows-1251?B?w+7r7uLt7uzzIOHz9ePg6/Ll8PM=?= 1953683393 ( 203.16.214.182 ) To: aunic[at]internode.com.au 1953683387 ( 150.101.155.102 ) To: spamcop[at]imaphost.com 1953683377 ( 150.101.155.102 ) To: abuse[at]internode.on.net --------------------------------------------- Submitted: Friday 2006/10/06 01:27:56 -0400: Returned mail: see transcript for details 1953425241 ( 203.16.214.182 ) ( UUBE ) To: uube[at]devnull.spamcop.net ------------------------------------------------- Submitted: Thursday 2006/10/05 18:36:32 -0400: Returned mail: see transcript for details 1953020993 ( 203.16.214.182 ) ( UUBE ) To: uube[at]devnull.spamcop.net ----------------------------------------------- Submitted: Monday 2006/10/02 02:05:54 -0400: Returned mail: see transcript for details 1947192429 ( 203.16.214.182 ) ( UUBE ) To: uube[at]devnull.spamcop.net ------------------------------------------------ Submitted: Tuesday 2006/09/26 23:20:32 -0400: Returned mail: see transcript for details 1939973887 ( 203.16.214.182 ) ( UUBE ) To: uube[at]devnull.spamcop.net ------------------------------------------------ Submitted: Tuesday 2006/09/26 09:55:05 -0400: =?iso-8859-1?B?oVKturOhpUjDuKW7pOKqa7rrpN/DuLtzqrq1tK3brk2u0SAsumHA8rdz?= =?i... 1939122998 ( 203.16.214.182 ) To: aunic[at]internode.com.au 1939122951 ( 203.122.240.116 ) To: spamcop[at]imaphost.com 1939122892 ( 203.122.240.116 ) To: abuse[at]internode.on.net --------------------------------------------- Submitted: Friday 2006/09/22 02:22:36 -0400: Returned mail: see transcript for details 1932973466 ( 203.16.214.182 ) ( UUBE ) To: uube[at]devnull.spamcop.net ---------------------------------------------------- Submitted: Wednesday 2006/09/20 15:49:39 -0400: Returned mail: see transcript for details 1930617626 ( 203.16.214.182 ) ( UUBE ) To: uube[at]devnull.spamcop.net
  8. Jeff G.

    Why is my mail server being blocked?

    More Report History follows (each of the 13964 domains controlled by MCI/UUNet/Worldcom per http://www.senderbase.org/?searchBy=ipaddr...ng=142.77.1.111 needs to be checked for bouncing ("Undeliverable mail:") and for delayed mail warnings ("WARNING. Mail Delayed:")): Submitted: Saturday 2006/10/07 23:29:46 -0400: WARNING. Mail Delayed: High-quality medications here. 1956418024 ( 142.77.1.111 ) ( UUBE ) To: uube[at]devnull.spamcop.net ------------------------------------------------- Submitted: Saturday 2006/10/07 04:28:31 -0400: WARNING. Mail Delayed: vvatch this st-0ck Trade 1955242165 ( 142.77.1.111 ) ( UUBE ) To: uube[at]devnull.spamcop.net --------------------------------------------- Submitted: Friday 2006/10/06 07:28:23 -0400: WARNING. Mail Delayed: Re: Home Loan - APPROVED. - 12Thu, 05 Oct 2006 21:56:0... 1953831594 ( 142.77.1.111 ) ( UUBE ) To: uube[at]devnull.spamcop.net ------------------------------------------------- Submitted: Thursday 2006/10/05 09:28:30 -0400: Undeliverable mail: this is how I got thin 1952353510 ( 142.77.1.111 ) ( UUBE ) To: uube[at]devnull.spamcop.net ----------------------------------------------- Submitted: Monday 2006/10/02 09:28:25 -0400: WARNING. Mail Delayed: Solid Loans with options. 1947636416 ( 142.77.1.111 ) ( UUBE ) To: uube[at]devnull.spamcop.net ----------------------------------------------- Submitted: Sunday 2006/10/01 16:28:59 -0400: WARNING. Mail Delayed: this is how I got thin 1946704317 ( 142.77.1.111 ) ( UUBE ) To: uube[at]devnull.spamcop.net
  9. Jeff G.

    Spamcop requires the full Message

    Please keep in mind that the limits of 50,000 bytes per Submitted spam and 100,000 bytes per Submission Email are still in effect.
  10. Jeff G.

    Parser Stuck (?) When Quick Reporting

    Sorry, that doesn't work any more for regular Reports, and I'm not sure if it ever did for Quick Reports. Please see my most recent Post on the subject of "Personal copies of outgoing reports".
  11. Jeff G.

    Quick reporting data Reports

    Certainly, old SpamCop Email System Customers have been permitted to use Quick Reporting without Mailhosts, until circumstances forced them to implement Mailhosts.
  12. Jeff G.

    Mailhosts Typical Questions

    That last bit should be: contact the deputies via deputies[at]spamcop.net and include "Mailhosts" in the Subject.
  13. More recent Report History follows (you should be accepting and acting on UUBE Reports, rather than opting not to receive them): Submitted: Saturday 2006/10/07 18:58:23 -0400: Mail delivery failed : returning message to sender 1956179132 ( 216.254.136.21 ) ( UUBE ) To: uube[at]devnull.spamcop.net ------------------------------------------------ Submitted: Saturday 2006/10/07 18:57:18 -0400: Mail delivery failed : returning message to sender 1956177981 ( 216.254.136.21 ) ( UUBE ) To: uube[at]devnull.spamcop.net ------------------------------------------------ Submitted: Saturday 2006/10/07 04:56:21 -0400: Mail delivery failed : returning message to sender 1955272751 ( 216.254.136.21 ) ( UUBE ) To: uube[at]devnull.spamcop.net ------------------------------------------------ Submitted: Saturday 2006/10/07 02:02:14 -0400: Mail delivery failed : returning message to sender 1955090106 ( 216.254.136.21 ) ( UUBE ) To: uube[at]devnull.spamcop.net --------------------------------------------- Submitted: Friday 2006/10/06 22:17:21 -0400: Mail delivery failed : returning message to sender 1954881195 ( 216.254.136.21 ) ( UUBE ) To: uube[at]devnull.spamcop.net --------------------------------------------- Submitted: Friday 2006/10/06 21:29:03 -0400: Mail delivery failed : returning message to sender 1954837468 ( 216.254.136.21 ) ( UUBE ) To: uube[at]devnull.spamcop.net --------------------------------------------- Submitted: Friday 2006/10/06 18:47:49 -0400: Mail delivery failed : returning message to sender 1954696702 ( 216.254.136.21 ) ( UUBE ) To: uube[at]devnull.spamcop.net --------------------------------------------- Submitted: Friday 2006/10/06 15:03:08 -0400: REQUEST TO BE OUR COMPANY'S PAYMENT AGENT IN YOUR REGION 1954459122 ( 216.254.136.21 ) To: aupviolations[at]primus.ca --------------------------------------------- Submitted: Friday 2006/10/06 12:13:41 -0400: Mail delivery failed : returning message to sender 1954233714 ( 216.254.136.21 ) ( UUBE ) To: uube[at]devnull.spamcop.net ------------------------------------------------ Submitted: Thursday 2006/10/05 21:52:53 -0400: spam: =?ISO-8859-1?Q?ATTN: YOU WON =A31.5M (CLAIM IT NOW).?= 1954456583 ( 216.254.136.21 ) To: spamcop[at]imaphost.com 1954456574 ( 216.254.136.21 ) To: aupviolations[at]primus.ca --------------------------------------------- Submitted: Friday 2006/10/06 09:02:03 -0400: Mail delivery failed : returning message to sender 1953960092 ( 216.254.136.21 ) ( UUBE ) To: uube[at]devnull.spamcop.net --------------------------------------------- Submitted: Friday 2006/10/06 08:37:16 -0400: MYSTERY SHOPPER WANTED EARN NO LESS THAN $ 500.00 1953925654 ( 216.254.136.21 ) To: aupviolations[at]primus.ca --------------------------------------------- Submitted: Friday 2006/10/06 07:49:41 -0400: Mail delivery failed : returning message to sender 1953862577 ( 216.254.136.21 ) ( UUBE ) To: uube[at]devnull.spamcop.net --------------------------------------------- Submitted: Friday 2006/10/06 00:55:52 -0400: Mail delivery failed : returning message to sender 1953393459 ( 216.254.136.21 ) ( UUBE ) To: uube[at]devnull.spamcop.net ------------------------------------------------- Submitted: Thursday 2006/10/05 17:46:15 -0400: Mail delivery failed : returning message to sender 1952968721 ( 216.254.136.21 ) ( UUBE ) To: uube[at]devnull.spamcop.net ------------------------------------------------- Submitted: Thursday 2006/10/05 16:26:44 -0400: Mail delivery failed : returning message to sender 1952881542 ( 216.254.136.21 ) ( UUBE ) To: uube[at]devnull.spamcop.net --------------------------------------------------- Submitted: Wednesday 2006/10/04 23:29:04 -0400: Mail delivery failed : returning message to sender 1951737240 ( 216.254.136.21 ) ( UUBE ) To: uube[at]devnull.spamcop.net --------------------------------------------------- Submitted: Wednesday 2006/10/04 16:24:05 -0400: Mail delivery failed : returning message to sender 1951332937 ( 216.254.136.21 ) ( UUBE ) To: uube[at]devnull.spamcop.net --------------------------------------------------- Submitted: Wednesday 2006/10/04 07:34:17 -0400: Mail delivery failed : returning message to sender 1950600067 ( 216.254.136.21 ) ( UUBE ) To: uube[at]devnull.spamcop.net --------------------------------------------------- Submitted: Wednesday 2006/10/04 03:05:59 -0400: Mail delivery failed : returning message to sender 1950309905 ( 216.254.136.21 ) To: aupviolations[at]primus.ca --------------------------------------------------- Submitted: Wednesday 2006/10/04 00:39:22 -0400: Mail delivery failed : returning message to sender 1950149440 ( 216.254.136.21 ) ( UUBE ) To: uube[at]devnull.spamcop.net ------------------------------------------------ Submitted: Tuesday 2006/10/03 20:54:58 -0400: Mail delivery failed : returning message to sender 1949945431 ( 216.254.136.21 ) ( UUBE ) To: uube[at]devnull.spamcop.net ------------------------------------------------ Submitted: Tuesday 2006/10/03 07:14:31 -0400: NOTIFICA DEL PREMIO:CONGRATULAZIONI!!! 1948963158 ( 216.254.136.21 ) To: spamcop[at]imaphost.com 1948963153 ( 216.254.136.21 ) To: aupviolations[at]primus.ca ------------------------------------------------ Submitted: Tuesday 2006/10/03 07:04:11 -0400: Mail delivery failed : returning message to sender 1948949337 ( 216.254.136.21 ) ( UUBE ) To: uube[at]devnull.spamcop.net
  14. Jeff G.

    Usage of bcc hidden or not ?

    Yes, a spammer can easily use bcc. Most do, and you'll maybe get a "bcc: undisclosed-recipients" if you're lucky. OTOH, some spam programs will just send "to:" a whole lot of recipients (and some badly-configured programs will send "bcc:" a whole lot of recipients, defeating the "blind" in "blind carbon copy"), in which case by default most email client programs will only show a limited number of those recipients by virtue of their design (need to save room on the screen for the other display elements).
  15. Yes, you should definitely start using Mailhosts, if you haven't already, or you may end up Reporting Gmail rather than the actual perpetrator. Here follows a snippet from an email from SpamCop Admin on the subject:
  16. Quick Reporting allows the reporting of only spam sources, very quickly. Please see the WARNING: below about the danger of such speed. Note: for those that would rather read a simpler, less detailed description of Quick Reporting see the following entry in the Wiki: QuickReporting The following is a detailed description of Quick Reporting and its Dangers: Emphasis: ONLY the spam source Nothing in the body of the spam is even looked at by the parsing engine. Further explanatory notes found at Is quick-reporting still BETA? Some procedural issues are addressed by Julian at Mailhosts and Quick Reporting Email-based Quick Reporting is a feature of the SpamCop Parsing and Reporting System which may be allowed on a case-by-case basis by a SpamCop Admin. Please see To Quick Report via email (Linear Post #2 below) for details on using it. Web-based Quick Reporting is an exclusive feature of the SpamCop Parsing and Reporting System which only SpamCop Email System Customers may access, and which can currently be used from both Systems' websites. On the SpamCop Parsing and Reporting System, that feature is part of what is variously known as VER (Very Easy Reporting), Held Email, Held Mail Log, held log, and heldlog, and in all cases resides at http://mailsc.spamcop.net/reportheld?action=heldlog. It can accessed via the "HeldMail" Button/Link in the menu bar of the SpamCop Parsing and Reporting System http://mailsc.spamcop.net/ (which can be accessed via the "Report spam" Button/Link in Webmail) and has six Actions as follows:  VER Action                Webmail Capability  ~~~~~~~~~~                ~~~~~~~~~~~~~~~~~~  Quick - report immediately and trash   "Report as spam"  Queue for reporting (and move to trash)  In Progress  Queue for reporting (do not trash)    In Progress  Forward (and whitelist sender)      "Release and Whitelist"  Forward (do not whitelist sender)     Release (or Move or Open and Redirect)  Delete                  Delete To "Queue for reporting" from Webmail, forward (from the message list interface only, not when viewing any particular message) to your confidential submit.16charANcodeNMBR[at]spam.spamcop.net address (your Confidential Submit Address). However Quick Reporting happens, it will produce one or more "SpamCop Quick reporting data" email messages similar to the following: Return-Path: <user.mkWcYgeVzP7tz6z6[at]bounces.spamcop.net> Delivered-To: x[at]spamcop.net Received: (qmail 15696 invoked from network); 28 Sep 2005 21:05:34 -0000 Received: from unknown (192.168.1.103) by blade3.cesmail.net with QMQP; 28 Sep 2005 21:05:34 -0000 Received: from vmx1.spamcop.net (204.15.82.27) by mx53.cesmail.net with SMTP; 28 Sep 2005 21:03:08 -0000 Received: from sc-app5.ironport.com (HELO spamcop.net) (204.15.82.24) by vmx1.spamcop.net with SMTP; 28 Sep 2005 14:03:02 -0700 Wrom: GPKYLEJGDGVCJVTLBXFGGMEPYOQKEDOTWFAOBUZX To: x <x[at]spamcop.net> Subject: SpamCop Quick reporting data Precedence: list Message-ID: <qr433b0506g7533[at]msgid.spamcop.net> Date: Wed, 28 Sep 2005 21:03:02 GMT X-Mailer: [url="http://www.spamcop.net/"]http://www.spamcop.net/[/url] v1.493 X-spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on blade3.cesmail.net X-spam-Level: X-spam-Status: hits=-98.1 tests=AWL,FORGED_RCVD_HELO,J_CHICKENPOX_63, J_CHICKENPOX_73,J_CHICKENPOX_75,USER_IN_WHITELIST version=3.0.2 X-SpamCop-Checked: 192.168.1.103 204.15.82.27 204.15.82.24 ... SpamCop.net Here are the results of your submission: Processing spam: Wrom: UWLSZLKBRNVWWCUFPEGAUTFJMVRESK Subject: ATTN: BENEFICIAL PREPOSITION Received: (qmail 32070 invoked from network); 28 Sep 2005 15:55:23 -0000 warning:Ignored Received: from unknown (192.168.1.101) by blade2.cesmail.net with QMQP; 28 Sep 2005 15:55:23 -0000 192.168.1.101 found host 192.168.1.101 (getting name) no name host 192.168.1.101 = ip192-168-1-101.z1-168-192.customer.algx.net (old cache) warning:192.168.1.101 discarded Received: from mail-kr.bigfoot.com (211.115.216.226) by mailgate.cesmail.net with SMTP; 28 Sep 2005 15:55:23 -0000 211.115.216.226 found host 211.115.216.226 = mail-kr.bigfoot.com (cached) mail-kr.bigfoot.com is 211.115.216.226 Possible spammer: 211.115.216.226 Received line accepted Relay trusted (211.115.216.226) Received: from hotmail.com ([65.54.185.21]) by BFLITEMAIL-KR3.bigfoot.com (LiteMail v3.03 (BFLITEMAIL-KR3)) with SMTP id 0509281145_BFLITEMAIL-KR3_464317_53569328; Wed, 28 Sep 2005 11:51:06 -0400 EST 65.54.185.21 found host 65.54.185.21 = bay15-f21.bay15.hotmail.com (cached) bay15-f21.bay15.hotmail.com is 65.54.185.21 Possible spammer: 65.54.185.21 Possible relay: 211.115.216.226 211.115.216.226 not listed in relays.ordb.org. 211.115.216.226 has already been sent to relay testers Received line accepted Relay trusted (hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 28 Sep 2005 08:50:58 -0700 warning:Ignored Received: from 63.215.198.21 by by15fd.bay15.hotmail.msn.com with HTTP; Wed, 28 Sep 2005 15:50:58 GMT 63.215.198.21 found host 63.215.198.21 = unknown.Level3.net (cached) Possible spammer: 63.215.198.21 Possible relay: 65.54.185.21 65.54.185.21 not listed in relays.ordb.org. 65.54.185.21 has already been sent to relay testers Received line accepted Sender relay: 63.215.198.21 De-referencing level3.net[at]abuse.net abuse net level3.net = abuse[at]level3.net, spamtool[at]level3.net Report routing for 63.215.198.21: abuse[at]level3.net, spamtool[at]level3.net abuse[at]level3.net redirects to level3[at]admin.spamcop.net spamtool[at]level3.net redirects to level3[at]admin.spamcop.net Tracking message source:80.88.135.149: Report routing for 80.88.135.149: emperion.net[at]devnull.spamcop.net Message is 5 hours old 80.88.135.149 not listed in dnsbl.njabl.org 80.88.135.149 not listed in dnsbl.njabl.org 80.88.135.149 not listed in cbl.abuseat.org 80.88.135.149 not listed in dnsbl.sorbs.net 80.88.135.149 not listed in relays.ordb.org. /dev/null'ing report for emperion.net[at]devnull.spamcop.net May be saved for future reference: [url="http://www.spamcop.net/sc?id=z810205604z2434444f7217f4c47d6e96388a8c07c6z"]http://www.spamcop.net/sc?id=z810205604z24...6e96388a8c07c6z[/url] Processing spam: From: ycorditej[at]mailpride.com...[/CODEBOX] [color=red]WARNING:[/color] Like its counterpart of normal Reporting, Quick Reporting also allows the reporting of you to your ISP or of your ISP to your ISP's ISP (both Very Bad Things), but in a more dangerous manner because it is faster and there is no verification step. Your ISP probably has various "solutions" in its arsenal to stop you from Quick Reporting yourself or it, including friendly advice, warning, suspension, deactivation, termination, fines, and even lawsuits for breach of contract, defamation, and/or interference with a contractual relationship. PLEASE make sure that your normal Reporting is working well for an extended period (never offering to report you to your ISP or your ISP to your ISP's ISP) before venturing into Quick Reporting. PLEASE also review your "SpamCop Quick reporting data" email messages to ensure that your Reports are not going to the wrong places. Please see FAQ Entry: What is VER (Very Easy Reporting)? for details on VER (Very Easy Reporting). Please see http://mail.spamcop.net/individuals.php for details on signing up for the SpamCop Email System. For addiltional official uptodate comments by SpamCop Admin see the following post http://forum.spamcop.net/forums/index.php?...ost&p=37352 posted on December 7, 2005 2004/03/22 [Wazoo] Updated to reflect new "Release" Links and "Queue for reporting" workaround. Edit: 2005/09/19 08:40 EDT -0400 Jeff G. updated with more info on email-based Quick Reporting (including reference to the Post below) and clarified some other language. Edit: 2005/09/28 00:04 EDT -0400 Jeff G. added access hints for VER, a caution for quick reporting via email, and a link to the new "FAQ Entry: What is VER (Very Easy Reporting)?". Edit: 2005/09/28 10:06 EDT -0400 Jeff G. added the [color=red]WARNING[/color] (thanks to Steve T for bringing it up). Edit: 2005/09/28 17:54 EDT -0400 Jeff G. added info about the the "SpamCop Quick reporting data" email messages to the body and the [color=red]WARNING[/color] (thanks to Steven Underwood and again to Steve T for bringing it up). Edit: 2005/12/06 11:05 PST -0800 dbiel added link to Don's December 7th post on the topic of Quick Reporting Edit: 2006/09/03 - [Wazoo] shortend up the long Received: Lines in the [ code box ] section to resolve a user complaint of having to scroll horizintally to read this Topic/Discussion .... Edit: 2006/12/14 - [Dbiel] added link to Wiki entry near the beginning of this post
  17. Jeff G.

    Lack of SMTP Service

    As discussed in I am shocked, no smtp?, please add "SMTP Service is not provided", "Email may only be sent from Webmail", or similar verbiage on the SpamCop Home Page http://spamcop.net and http://www.spamcop.net, as well as anywhere else the SpamCop Email System and Accounts on it are promoted. Thanks!
  18. You can always click on "Track this topic" above.
  19. Should we keep the link in the Welcome Topic?
  20. Jeff G.

    Why BlackList a Gateway?

    If you and your browsing provider customers have NTP synchronization and real-time access to your and their verbose NAT/firewall logs and your SpamCop Reports, you should be able to work together to track specific HTTP POST commands back through your and their NAT/firewall to the real culprits, and then if you have stringent TOS/AUP, you should be able to nail the real culprits to the wall. This may require some additional disk space for the logs and processing power for generating and searching the logs.
  21. Jeff G.

    BL test wanted

    Don't worry about it. I didn't remember the details, either.
  22. Jeff G.

    Yahoo! Mailservers Blocklisted

    What "SpamCop client software"? You must be referring to spamcop.com or spamcop.org client software, because AFAIK there is no working "SpamCop client software" distributed by this domain spamcop.net. Also, I am merging your Topic "All Yahoo mails blocked by default?" with the existing Topic Yahoo! Mailservers Blocklisted. Please read from the first post - you might learn something.
  23. Jeff G.

    Concerned about potential false blacklist

    I get hundreds of misdirected bounces, challenges, and auto-responses a day, and use the SpamCop Parsing and Reporting System to Report them. If you have time, you can use the SpamCop Parsing and Reporting System's Parser to help you compose a Manual Report to the ISP of the system that sent the original spam email messages.
  24. Please post proof of that allegation. Thanks!
  25. Jeff G.

    why am i blocked?

    No, you can try resending until your email goes through, you can try complaining to Yahoo!, and/or you can try resending through a more responsible provider. Please don't blame SpamCop - the problem is ineffective Yahoo! administration and oversight, and the spammers they let abuse their systems.
×