Changes to exim.conf

jbb

Verified User
Joined
Jan 30, 2005
Messages
16
Location
Oregon, US
Looking at the stock exim.conf, if you choose to use RBL's there are references to example.com in the deny_message on line 500 and line 510,

I think this line should be changed to something like "deny message = $sender_host_address is listed at $dnslist_domain"

This is understandable and does not require a special webpage.

On line 484, the deny_messag is "deny message = $sender_host_address is listed at $dnslist_domain"

I suggest a change to "denied by local blacklist"
 
jbb said:
Looking at the stock exim.conf, if you choose to use RBL's there are references to example.com in the deny_message on line 500 and line 510,

I think this line should be changed to something like "deny message = $sender_host_address is listed at $dnslist_domain"
You can certainly change it if you wish.

When I first wrote and tested the exim.conf file I thought of doing it that way.

I changed my mind because a focus group of ordinary Internet users had problems with it; not one of them could understand what they had to do to get unblocked.

The system I use works (see http://www.spamblocked.net/) because it explains to people exactly what they need to do. And since spammers don't get the messages (their servers are set to ignore blocked address replies), spammers don't ask to be put on the whitelist.
This is understandable and does not require a special webpage.
It's understandable by you and I. But not by ordinary Internet users, who seem to have a lot of problems with it. I strongly suggest using the special webpage; it's what makes your hosting company user-friendly.
On line 484, the deny_messag is "deny message = $sender_host_address is listed at $dnslist_domain"
Actually, on the standard installed exim.conf file (you can find it here) the line says:

You may think you're legal but you're still an unwanted spammer

Because when I first implemented the local blocklist it was for just that, folk who follow all the rules but still get through to my server. I agree that it needs to be changed, and it will be in the next released version of the file.
I suggest a change to "denied by local blacklist"
You can change it to anything you want. The less intuitive you make it the more your users will ask to have their domains whitelisted from blocklists completely.

Jeff
 
I realize I can change it to anything I want. You can keep on using whatever you want also. I'm suggesting changes to the default exim.conf distributed by DA.

The default install should work with as little special configuration as possible.

If you don't like my message thats fine but I think the current default needs to be changed because it requires an admin to edit exim.conf for each installation.

Most RBL service return a link in the txt record that could be included.
 
We tried including the link during our beta testing. The problem is that most MUAs (email programs) only report the first line of multi-line messages.

I wrote the exim.conf file. You haven't convinced me, though I understand that the lack of documentation is a problem.

You could try convincing the folk at JBMC, who write DirectAdmin, that they should make the change. This isn't the right subforum for that.

If they're convinced, then they can certainly decide to change the copy they distribute.

The history of the SpamBlocked exim.conf file is simple: I wrote it for my own clients. My selling feature to my clients is that we won't subject any false positives to the same kind of complex procedures as other blocklist solutions do.

When the staff at JBMC said they'd like to use my exim.conf file, I said "Of course".

You may want to post your suggestions in the "Feedback & Feature Requests" forum.

And in the meantime, just make the change east time you provision a DA server. Once it's installed, DA won't change it.

Jeff
 
Back
Top