normally not a problem for someone using my server for smtp, but it means my clients couldn't send me email from their home account. so i took sorbs off my rbl list for a week and sent the ISPs tech support and admin addresses a note about getting de-listed.
now i appreciate sorbs even more than before. my personal account, with a normally low spam load, got slammed for a week. i have a half dozen other rbls in my list, and they're doing their part, but sorbs seems to be blocking the lion's share.
after the week, sorbs still had the netblock listed, so i put it into my "client host addresses" list. yay, they can send me mail again.
but, doesn't this also mean that anybody in that netblock can use my server to relay? according to sorbs, the only offense these guys are guilty of (so far) is sending to a spamtrap somewhere - no open relays, zombies, etc. but the last thing i want to do is get *my* server listed because someone discovers this hole and starts spewing indiscriminately. normally, i think i'd list only the IPs from the MX records of the ISP, but none of the email i've gotten from these guys has come directly from the MX, but from some other ips in the same netblock.
any suggestions on how to lock this down better?
charles mangin | Alpha Geek and Chief Mental Hygienist
[EMAIL PROTECTED] | What's that watermelon doing there?
http://niftee-tron.com | http://mentalhygiene.com
############################################################# This message is sent to you because you are subscribed to the mailing list <[EMAIL PROTECTED]>. To unsubscribe, E-mail to: <[EMAIL PROTECTED]> To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]> To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]> Send administrative queries to <[EMAIL PROTECTED]>
