Jump to content

lisati

Memberp
  • Content Count

    475
  • Joined

  • Last visited

Everything posted by lisati

  1. I know exactly what you mean. I have several Yahoo email addresses, and my ISP uses Yahoo as their provider. Sometimes when I've looked at headers of email sent and received via Yahoo, there has been evidence in the Received headers of what could be multiple servers at Yahoo's end being involved.
  2. That reads to me as if some kind of filter, possibly outsourced, is operating on one of your provider's outgoing servers kicked in before the message got anywhere near Spamcop.
  3. I'm wondering if there's been a change in your server or hosting provider's setup that would require you to re-do your mailhosts setup.
  4. lisati

    BT Mail 'Upgrade'

    I thought that BT had dumped Yahoo.....
  5. I, too, don't use the email service. My focus when coming here is on dealing with spam and other unwanted email. My sense is that the reporting service is still working reasonably well, and as long as this is the case, I'm not too worried about a "missing" logo.
  6. Sometimes people responding to reports make mistakes, or even tell lies. There could even be a massive pile of messages queued somewhere, waiting to be delivered, even though the underlying issue has been addressed. I'd still submit the report(s): spam is still spam, even when someone who plays a part in its transmission says otherwise. As turetzsr has said, it helps keep IP addresses on the list.
  7. I hear you. It had occured to me that the missing logo could be a symptom or side effect of something untoward going on. The only issue I've noticed is largely cosmetic (I don't use the mail service). The gurus who deal with such things probably have more important things to worry about at the moment.
  8. True: as long as the reporting system works OK, I'm not going to worry too much.
  9. I noticed on the www.spamcop.net web page when reporting. Until recently there was a "spamcop.net" logo similar to the one showing in the forum headers to the left of the stats graph. Reporting seems to be unaffected by the "missing" logo. Edit: A reference to it is still in evidence in the page source, and occasionally when I load the page there's a brief flash of an outline where I was expecting the graphic.
  10. I'd noticed too, but had pencilled it in to a possible rendering issue in my browser and hadn't bothered looking into it.
  11. lisati

    False spam Trap

    If the suspect email address is one that was previously a valid email address but has now reverted to a honeypot role, it's possible that at one point emails to the address in question were bouncing or rejected. This should have been picked up and flagged by your mailing list's bounce processing.
  12. lisati

    UCE from 184.22.119.205 not resolved

    True about the botnet bit. What I'd spotted was the reference to Postfix in the message headers, which is fairly easily configured to prevent unauthorised access from outside sources that might want to relay spam. When I was running my own email server, I was using Postfix as the MTA, the spam mentioned in the tracking link you provided would have either been caught by the cbl listing, or possibly rejected with a "relaying not allowed" message.
  13. lisati

    UCE from 184.22.119.205 not resolved

    Definitely looks like the folks who administer 1.82.191.88 need to tighten up who they accept mail from. Open relay? Maybe, maybe not.
  14. lisati

    Mail Server Blacklisted?

    If I've ever received a NDR or bounce that cited an APEWS listing, it was long enough ago for me to have forgotten. From what I've read here on the Spamcop forum and elsewhere, a listing there can usually be ignored.
  15. lisati

    blocked email

    If I have understood Andres' post correctly, it is someone who has sent Andres an email that didn't getting through. At the moment now, there seems to be a listing for 209.17.115.40 on Spamcop's list, even though Spamcop isn't specifically mentioned on the NDR.
  16. lisati

    All outgoing mail tagged as spam

    I'm inclined to agree that the tagging of email subjects looks like something that tools such as SpamAssassin can do. I believe that SpamAssassin can be configured to check the "Received" headers against DNSBLs such as SpamCop: perhaps a copy of SpamAssassin somewhere has done this and identified a possible problem. My next step would be to try to identify whether a copy of SpamAssassin at your email providers end or at the recipient's end is tagging the emails.
  17. lisati

    RFC2142 email addresses not honored

    I like the idea of such a site, and was sad to learn of the demise of the rfc-ignorant website. At the time of its being shut down, I did learn of another site which was going to take up the challenge of maintaining similar lists, but it seems to have shut down too.
  18. lisati

    [Resolved] spam volume graphs

    I believe the OP is referring to the graphs accessible here: http://www.spamcop.net/spamstats.shtml They look stuck from my end too.
  19. lisati

    Mail Server Blacklisted?

    As near as I can tell, the IP address isn't currently listed on Spamcop's list. Sadly, the lookup tools I normally use (e.g. MX Toolbox) didn't provide me with much in the way of clues as to why Spamcop might be mentioned. Perhaps someone else with a bit more time to research things might be able to provide some insight. One thing I did notice is that some email servers might have an issue with its reverse DNS resembling a generic rDNS.
  20. lisati

    Mail Server Blacklisted?

    If a mail server is being blocked because of a listing on SpamCop, it will be based on the IP address, not by the server name or email addresses. Often the sender of the emails that were blocked will have access to a link to the Spamcop lookup page in the bounce message, assuming that there was at one point a real lising, but unfortunately not all mail providers play nice by providing such a link. Having such a link can be useful when troubleshooting deliverability problems. It's possible that when the message was sent, there was a listing but the IP address was subsequently removed. Another possibility is that the recipient's provider used a stale cache of lookup results or they were too lazy provide anything more than a generic message. edit: Oh, perhaps I misread the question. The info was from the recipient's IT people?
  21. lisati

    Alternatives to Spamcop

    GMX aren't in my good books at the moment, cancelling an account I've had there for several years without warning and not being particularly helpful when asked why.
  22. lisati

    Strange little messages don't parse

    Spammers are stupid! On a side note, I had an interesting one coming in to an email address I'd set up as a spam-catcher account for my fictious friend "Hugh" (as in short for "huge <insert-name-of-body-part>"). It claimed to be from Mr Donald Duck. A great opporunity for having a bit of fun. Sadly, I never heard back from them after letting them know I'd consulted with other Disney characters.
  23. lisati

    spam.spamcop.net DNS issues?

    Hmmm...../me scratches head. Isn't "mutt" an email client? Edit: has there been an update to mutt on your system that changed configuration settings?
  24. lisati

    remove the blacklist

    I agree. A good first port of call for a request for removal from any blacklist is the list's lookup page. A link to that page is commonly (but not always) provided in non-delivery reports, and will normally provide useful information about what needs to happen before removal from the list occurs.
  25. Say what? Please read the post just before yours.
×