How do I remove IP from sorbs.net blacklist?
It would seem that SORBS is having a database problem right now, and is blocking a lot more than it usually does. This may be a transient issue: http://isc.sans.edu/diary.html?storyid=9685
It would seem that SORBS is having a database problem right now, and is blocking a lot more than it usually does. This may be a transient issue: http://isc.sans.edu/diary.html?storyid=9685
Do yourself a favor and set them up with a gateway anti-spam service such as Postini. For a few dollars per mailbox per month, there’s absolutely no reason not to and you’ll not only eliminate 99% of your spam, you’ll also enjoy having access to their spool service (handy for scheduled or unscheduled downtime), not … Read more
This is spam at the least – at worst, it’s a scam. Do not agree to send a read receipt. Do not download unnecessary content. Do not click links. Do not reply. Do not pass Go… etc. As others have mentioned, protecting your contact details in whois information may help eliminate these emails; I’d also … Read more
Here is my list and why I use them: zen.spamhaus.org – Comprehensive RBL, catches a ton of spam sources, updated regularly. They have a long history and decent reputation in the spam filtering community. I have heard some negative things about them from time to time, but those are generally without real merit. Downside is … Read more
Short Answer: You can’t. For more info, this gives a basic explaination as to why. This shows how easy it is to do. It’s just the nature of SMTP, it’s insecure! Just because an email appears to come from somebody, it doesn’t mean it did.
Both libspf2 (C) and Mail::SPF::Query (perl, used in sendmail-spf-milter) implement a limit of 10 DNS-causing mechanisms, but the latter does not (AFAICT) apply the MX or PTR limits. libspf2 limits each of mx and ptr to 10 also. Mail::SPF (perl) has a limit of 10 DNS-causing mechanisms, and a limit of 10 lookups per mechanism, … Read more
These are bots trying to send you spam, or worse, trying to exploit your contact form to send spam to others. For example, there are several well-known exploits for the PHP mail() command commonly used by contact forms that can cause the TO address you put in your code to be overwritten by POSTed data, … Read more
Since it hasn’t been explicitly stated yet, I’ll state it. No one’s using your domain to send spam. They’re using spoofed sender data to generate an email that looks like it’s from your domain. It’s about as easy as putting a fake return address on a piece of postal mail, so no, there’s really no … Read more