nobaloney
NoBaloney Internet Svcs - In Memoriam †
SpamBlocker 3.2.4-RC is now ready for testing.
We've reworked the code to block backscatter spam, and we'd like some testing. Don't forget to check all the EDIT locations in the file to make sure it works in your environment.
We've found some issues that I can't resolve with help from the DirectAdmin staff, unless YOU know of a workaround.
We use the domain names in in /etc/virtual/domains to determine if a domain sends mail from the server. The problem is that DirectAdmin uses the same file to determine if a domain receives mail on the server.
The problem is that when you change MX to a different server DirectAdmin removes the domain name from this file.
This has two effects, one which has always occurred since my first SpamBlocker technology exim.conf file; it simply makes spamblocking less effective:
Presuming you use /etc/virtual/use_rbl_domains as a link to /etc/virtual/domains, then spamblocking simply doesn't occur when senders ignore MX records and send email to your server because it hosts the A record for a domain. Some spammers do that, and I'd love to have a separate file of all domains on the server to use.
The problem in the latest file, 3.2.4-RC, is in addition to the above problem, which still remains.
If your server sends mail for a domain (for example, example.com) for which you've changed the MX server, then if some of that outgoing email from your server is to bad addresses, and Mailer-Daemon sends back a message, the sender will never get it, because the domain name isn't listed in the /etc/virtual/domains file.
The problem with that is that if you're using a list server of some kind, or even a form, to send email, and you're getting undeliverable replies from Mailer-Daemon, you need to get them, so you can take action.
To fix this, DirectAdmin would have to maintain for us a file with all domains on the server, whether or not they receive email.
Hopefully the DirectAdmin staff can help us with this, or suggest something else.
Yet another issue:
It's been brought to my attention that the code we use to check for legal Helo FQDNs is no longer accurate on today's Internet and will block mail to domains with numbers in their names, as well as mail to anyone using IDNs (International Domain Names).
Unless someone can provide us with code we can use, I'll probably remove the current code by the final release.
This is also something we'd like some testing on.
Your input is appreciated.
The new file may be found here.
Please try it and let me know your experiences.
Thanks.
Jeff
We've reworked the code to block backscatter spam, and we'd like some testing. Don't forget to check all the EDIT locations in the file to make sure it works in your environment.
We've found some issues that I can't resolve with help from the DirectAdmin staff, unless YOU know of a workaround.
We use the domain names in in /etc/virtual/domains to determine if a domain sends mail from the server. The problem is that DirectAdmin uses the same file to determine if a domain receives mail on the server.
The problem is that when you change MX to a different server DirectAdmin removes the domain name from this file.
This has two effects, one which has always occurred since my first SpamBlocker technology exim.conf file; it simply makes spamblocking less effective:
Presuming you use /etc/virtual/use_rbl_domains as a link to /etc/virtual/domains, then spamblocking simply doesn't occur when senders ignore MX records and send email to your server because it hosts the A record for a domain. Some spammers do that, and I'd love to have a separate file of all domains on the server to use.
The problem in the latest file, 3.2.4-RC, is in addition to the above problem, which still remains.
If your server sends mail for a domain (for example, example.com) for which you've changed the MX server, then if some of that outgoing email from your server is to bad addresses, and Mailer-Daemon sends back a message, the sender will never get it, because the domain name isn't listed in the /etc/virtual/domains file.
The problem with that is that if you're using a list server of some kind, or even a form, to send email, and you're getting undeliverable replies from Mailer-Daemon, you need to get them, so you can take action.
To fix this, DirectAdmin would have to maintain for us a file with all domains on the server, whether or not they receive email.
Hopefully the DirectAdmin staff can help us with this, or suggest something else.
Yet another issue:
It's been brought to my attention that the code we use to check for legal Helo FQDNs is no longer accurate on today's Internet and will block mail to domains with numbers in their names, as well as mail to anyone using IDNs (International Domain Names).
Unless someone can provide us with code we can use, I'll probably remove the current code by the final release.
This is also something we'd like some testing on.
Your input is appreciated.
The new file may be found here.
Please try it and let me know your experiences.
Thanks.
Jeff