Jump to content

trevorb

Retired SpamCop Staff
  • Posts

    63
  • Joined

  • Last visited

Everything posted by trevorb

  1. The server that generates the graphs (alpha) lost power during all the events and failed to reboot. It is stored remotely and is low priority (it provides no mail services), so we didn't go out there immediately. It is back up now. -Trevor
  2. Two servers that handle routing of POP, IMAP, and HTTP encountered problems simultaneously, so those services were unreliable for the last 45 minutes. Everything should be back up and running smoothly now. -Trevor
  3. The 'popgate' functionality is provided by third-party software that attempts to add features to sites like Yahoo that do not support POP. Unfortunately, since it depends on "screen scraping" it is impossible to reach 100% reliability and even the slightest changes on Yahoo's side can break popgate until an update is released. Since 'popgate' will *always* be an experimental feature, if you depend on mail from an account that does not provide POP we recommend you use a different provider or pay extra for POP access. The current status is that hundreds of users are receiving their Yahoo e-mail perfectly, but some users are only getting partial or no success. The Yahoo! webmail settings seem to be important, and many users have found that switching from the "New" to the "Classic" interface or vice versa solves their popgate problems. I installed a big update to popgate2 this morning and it included changes to the Yahoo code. If you have been having trouble with Yahoo, now is a good time to try again. Make sure you open the POP server configuration page in SpamCop Webmail and click the "modify" button to reset any errors and start checking your accounts again. Please let us know if this fixes any issues or introduces any new ones. EDIT: One more note: 'popgate2' can get hung up on an individual e-mail, so if it was working and suddenly stopped working try deleting or moving the top-most message via Yahoo's webmail interface. -Trevor
  4. Support for '%' notation is actually back now. It isn't supported by our mail server software by default and creating custom patches to support it was making it more difficult for us to do security upgrades. However, we found a way to support it without patching the mail servers so it will keep working for the few users who still need it. -Trevor
  5. Also posted on the news page: The percent sign alternative was originally used because buggy old e-mail clients did not support "[at]" in the username field. Modern clients do not have that problem.
  6. Recently spammers have been gaining access to SpamCop e-mail accounts and thousands of messages out through Webmail. These spam runs have caused ISPs to temporarily block and delay messages from us, as many of you have noticed. To limit the influence of these spam runs, yesterday we added a 30 recipient limit to e-mails sent via Webmail -- that is, no one message can be addressed to more than 30 people. If you need to send to more than 30 addresses and cannot break the list into batches of 30, please use a stand-alone e-mail client instead of Webmail. Our inbound (IMAP/POP) server address is 'mail.spamcop.net' and our outbound (SMTP) server address is 'smtp.cesmail.net'. Both servers require authentication. Your username is your full SpamCop e-mail address, including the '[at]spamcop.net' domain. We recommend Thunderbird as a stand-alone client. You will most likely find that it is easier to manage mailing lists offline, and your will have better control over backing up your contact list. Webmail should not be considered a safe storage medium for large contact lists. We are also looking into alternative ways to restrict spammers so we can eventually raise this per-message limit. -Trevor
  7. All of my missing messages eventually showed up in my test Hotmail account, and messages appear to be delivering instantly now. They were apparently just queuing our messages for an unreasonably long time. We are subscribed to their SNDS service, but it clearly doesn't help. We are currently working on changes to the backend that will limit the impact of these spam runs.
  8. JT and I are aware of this problem with Hotmail. Some spammers managed to send a few thousand messages out of a SpamCop account yesterday, and Hotmail over-reacted with how long they put us on their blacklists for. It is a temporary problem that will clear itself up, but we have no input from Hotmail as to how long it will take. Generally it takes 24-48 hours. -Trevor
  9. This looks like a greylisting bug. Do you both have greylisting enabled? The plus-address extension isn't being removed before adding entries to the greylist. Now that one message has come through can you send a message (from the same server) to the same address and get it immediately? We'll try to get this fixed soon. Thanks for reporting it! -Trevor
  10. Javier is right, held messages are automatically deleted when they are more than two weeks old. You are certainly not required to empty your own Held Mail if you don't want to. -Trevor
  11. For every other blacklist we check all IPs. It's only for the PBL that the last IP is skipped. It is *not* skipped if it is the only IP, so direct-to-MX should be caught. I fixed the duplicate IP bug today, so each IP address should only be checked once. There is nothing we can do about the spam that gets by even though the first IP is in the PBL, since the first IP is usually in the PBL whether it is spam or not. -Trevor
  12. DavidT, For the e-mail you linked to that we didn't block even though it had an IP in the PBL, that is actually correct behavior. The Barracuda doesn't reject messages that are in blocklists like we do, it just scores them higher. Since we outright block them, we have to be more careful about what IP addresses we consider. The very first hop of the e-mail chain does not get checked against the PBL list. The first address is usually the IP address of the computer you are sending from, which is very likely to be your own dynamic IP assigned from your ISP. Since the PBL includes IP blocks that ISPs designate as their dynamic IP range, there is a very high chance that the first source IP in an e-mail will be on the PBL list even though the message is valid. We check every IP except the first hop (which is actually the last one listed in the 'Received' headers) against the PBL. -Trevor
  13. Yep, PBL has been turned on and should be working. -Trevor
  14. Actually, we have had a change of plans. We can't mirror "Zen" directly since it is really an aggregation of Spamhaus' three blacklists, so we are just going to add the PBL and you can choose whatever combination of the three you want (SBL+XBL+PBL = Zen). PBL is disabled for now until we get the local mirror up. -Trevor
  15. The Zen blacklist is an available option now, if you want to try it out. We are going to wait a few days before making an announcement on the news page to make sure all the kinks are worked out. For now you can still subscribe to the other two Spamhaus blacklists, but if you enable Zen you should disable the others since they are included. We will remove the older ones and move everyone over to Zen prior to making a formal announcement. Keep us updated on whether or not you are seeing good results. I ran a test on a batch of 1,000 spam messages. With SBL+XBL 174 messages made it to the Inbox, with Zen only 80 made it by. -Trevor
  16. It's been on the list of stuff to do for a long time, but that particular list works differently from all of the others and isn't compatible with our software. Since there has been so much interest in it, though, I started the code modifications today. No exact time frame, but probably a couple of days until it is up. We're going to replace the two existing Spamhaus entries with one Zen entry, and move everyone over to that one. -Trevor
  17. The triplet is saved for 36 days after the last time a message from that triplet was received. Allowing an entry will allow the e-mail to pass through the next time it is sent, but the message will not be immediately available, for the reason explained after the next question: The messages are blocked at the SMTP server. We don't store them at all. That depends on how the spammer treats bounces. It is likely that some spammers will remove you from their list if they get a greylist bounce. -Trevor
  18. We do not limit the size of incoming e-mails, so the limit is just whatever the servers can handle. The message limit listed in Webmail's compose screen relates *only* to sending e-mails from the Webmail interface, and does not affect the rest of the system. E-mail is not designed for large attachments, and you really shouldn't expect an e-mail over 1 meg to get to its destination no matter where you send it from or to. Every system does have a limit, including ours, but it is hard to measure and impossible to guarantee. Additionally, your message passes through different servers and software depending on how you sent it (webmail vs SMTP server vs forwarding), each one of which could have different limits. It can hop through a bunch of different ISPs and mail hosts on its way to its destination, all of which also have their own limits and attachment policies and virus scanners that could mangle or drop your message without warning. -Trevor
  19. What number are you talking about? Do you mean the "#" column in the Webmail mailbox view? That number is how the IMAP server numbers each message internally and the new IMAP servers use the number in a slightly different way than the old ones did. We re-indexed all of the mailboxes a couple of days ago, but the new servers didn't actually go live until today. Because of that, the "newest" # for you rolled back to whatever it was back when we re-indexed, and you had received ~100 messages since then so the number jumped a bit. -Trevor
  20. I ran a batch rebuild on everyone's account. Most of the IMAP errors and missing folder problems that were reported are fixed now. So, once again, if you have any troubles with IMAP access after now (3:20pm EDT), send another e-mail off to support[at]spamcop.net. Problem reports sent earlier today will not get a response since there were so many. -Trevor
  21. For IMAP errors, send an e-mail to support[at]spamcop.net and be sure to specify your username. -Trevor
  22. IMAP and POP are very related, actually. Despite the news message from yesterday, the new IMAP servers didn't go live until today. The POP authentication server failed in the process, but it's back up now. POP should be functioning properly, and all IMAP access (both external and Webmail) is going through the new, faster servers. There will be a forum and news post about it in a minute. Send us an e-mail if there are any problems accessing your mailbox. -Trevor
  23. You probably want to e-mail this to deputies[at]admin.spamcop.net. They handle issues related to spam reporting. -Trevor
  24. "Release & Whitelist" is not currently working, but we are working on making it compatible with the new system. If you receive any messages about IMAP failures while using webmail (especially when deleting messages), send an e-mail with the action you attempted, the error message, and your username to trevorb[at]cesmail.net and we'll get it fixed. We had to convert all users over to a new file format, but a few users had special cases and need to be done by hand. *** UPDATE *** "Release" and "Release & Whitelist" should both work again. Let us know if there are any more issues. -Trevor
×
×
  • Create New...