Jump to content

drez

Members
  • Content Count

    3
  • Joined

  • Last visited

Community Reputation

0 Neutral

About drez

  • Rank
    Newbie
  1. Was just about to post about this happening again. Sorbs started blacklisting 204.15.82.113 again. ec 24 11:11:12 phuct postfix/smtpd[26591]: NOQUEUE: reject: RCPT from sc-smtp12-inbound.soma.ironport.com[204.15.82.113]: 554 5.7.1 Service unavailable; Client host [204.15.82.113] blocked using dnsbl.sorbs.net; Currently Sending spam See: http://www.sorbs.net/lookup.shtml?204.15.82.113; from=<spamid.5205215538[at]bounces.spamcop.net> to=<xxx[at]yyyzzz.net> proto=ESMTP helo=<sc-smtp12-inbound.soma.ironport.com>
  2. drez

    sorbs blocking spamcop?

    Awesome, thank you very much!
  3. So for the past few days I have had to reset my bounce flag on spamcop quite a bit. I checked my postfix log and I keep seeing sorbs blocking 204.15.82.126 Nov 10 10:06:16 phuct postfix/smtpd[20847]: NOQUEUE: reject: RCPT from sc-smtp4-bulkmx.soma.ironport.com[204.15.82.126]: 554 5.7.1 Service unavailable; Client host [204.15.82.126] blocked using dnsbl.sorbs.net; Currently Sending spam See: http://www.sorbs.net/lookup.shtml?204.15.82.126; Aside from removing sorbs as a rbl, is there anything that can be done to remedy this?
×