Jump to content

ddi

Members
  • Content Count

    2
  • Joined

  • Last visited

Community Reputation

0 Neutral

About ddi

  • Rank
    Newbie
  1. ddi

    Why are we blocked?

    A long forgotten test machine in a long forgotten test segment (which unfortunately was specifically allowed to send mail on the outgoing relay).. It has been disabled, which seems to have stopped the honeypot counter. If you come across any more from .100 or .101, don't hesitate to contact me. Thank you very much for the information, it's been a big time-saver in finding the culprit :-).
  2. Our mail relay 130.227.153.100 is blocked by SpamCop. It has never been an open relay (at least not for the last couple of years). There's no information of interest to be found at http://www.spamcop.net/w3m?action=checkblo...130.227.153.100. Full Quote: ================= 130.227.153.100 listed in bl.spamcop.net (127.0.0.2) Since SpamCop started counting, this system has been reported about 400 times by less than 10 users. It has been listed for 40 hours. In the past week, this system has: Been detected sending mail to spam traps ================= We have a very tight mail server setup, and I can't imagine anyone here ever having sent anything remotely like spam. I could imagine that the problem may stem from a non-delivery report or so unintentionally bouncing back and forth between a spamtrap and our system - but with the little information above, it's hard to tell. Is there any way to get more information on what SpamCop sees? Is it possible that someone is faking us as a sender address and that SpamCop wrongly accepts this information? Update: We have disabled all NDR's etc. (all system messages), and the honeypot counter on spamcop.net is still happily counting upwards.
×