Autoresponder Fails - 550

BigWil

Verified User
Joined
Aug 5, 2004
Messages
296
All of my autoresponders are failing with a 550 Authentication Required. We do use an outside relay service but all other mail is working great. The only thing that doesn't are the autoresponders. Even the vacation messages work fine.

Before anyone asks DA 1.23.4 and Exim 4.44

Here are my customizations to the standard exim.conf file. I will snip where appropriate. Everything besides that below is standard and updated today. Before you ask DA

--begin_exim.conf_mods--
daemon_smtp_port = 25 : 26
acl_smtp_rcpt = check_recipient
acl_smtp_data = check_message

--snip--
hostlist relay_hosts = net-lsearch;/etc/virtual/my_whitelist : 127.0.0.1
hostlist auth_relay_hosts = *

--snip--
# Deny stuff from insecure hosts & spammers. No exceptions for known users.
# but do bypass all checking for whitelisted host names
deny message = to unblock $sender_host_name see http://www.example.com/
# only for domains that do want to be tested against RBLs
domains = +use_rbl_domains
# only smtp.dnsbl.sorbs.net = 127.0.0.5
dnslists = sbl.spamhaus.org : \
relays.ordb.org : \
dnsbl.sorbs.net=127.0.0.5

# Next deny stuff from more "fuzzy" blacklists
# but do bypass all checking for whitelisted host names
deny message = to unblock $sender_host_name see http://www.example.com/
hosts = !+relay_hosts
domains =+use_rbl_domains
!authenticated = *
# dnslists not including spam.dnsbl.sorbs.net
dnslists = dnsbl.njabl.org : \
sbl-xbl.spamhaus.org : \
relays.ordb.org : \
dnsbl.sorbs.net!=127.0.0.6

--end_exim.conf_mods--

Additionally:

ls -al /etc/virtual
-rw-r--r-- 1 mail mail 0 Feb 19 21:28 blacklist_domains
drwxr-xr-x 3 mail mail 512 Feb 22 18:02 customerdomain.com
drwxr-xr-x 2 mail mail 512 Dec 10 15:01 mach1.mymachines.net
-rw-r--r-- 1 mail mail 58 Feb 19 17:07 domainowners
-rw-r--r-- 1 mail mail 54 Feb 22 18:39 domains
-rwxr-xr-x 1 mail mail 14 Feb 17 18:36 limit
drwxr-x--x 5 majordomo daemon 512 Dec 10 15:04 majordomo
-rwxr-xr-x 1 mail mail 1817 Feb 22 18:35 my_whitelist
-rwxr-xr-x 1 mail mail 15 Feb 22 21:54 pophosts
drw-rw---- 2 mail mail 512 Feb 22 16:12 usage
lrwxr-xr-x 1 root mail 9 Jan 12 17:47 use_rbl_domains -> ./domains
-rwxr-xr-x 1 mail mail 0 Dec 11 12:03 use_rbl_domains.old
-rw-r--r-- 1 mail mail 1 Feb 22 21:07 whitelist_from


As you can see from the above I have the popb4smtp turned off.

I require all domains be scanned by the rbl servers.

And I have a list of IPs in my_whitelist that are allowed to smtp to the server without interference from RBL or 550 errors. And if I am mistaken someone please correct me.

Again I can send and receive emails to and from the machine from anything from another machine, from yahoo.com, from hotmail, from mars, but as soon as I try to use the autoresponders BANG 550 Authentication Required. Nearly exact errors follow:


The bounce:
Hi. This is the qmail-send program at front.mymachines.net.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<[email protected]>:
64.18.5.10 does not like recipient.
Remote host said: 550
Giving up on 64.18.5.10.


The Exim_RejectLog:
2005-02-22 21:07:14 H=exprod6mx126.outsiderelay.com (osrelay.com) [64.18.1.33] F=<[email protected]> rejected RCPT <[email protected]>:

I have checked on all of my DA machines and they all do the same thing. Remarkably I haven't heard from a complaining customer until today.

Any help anyone can provide would be most appreciated.


Big Wil
 
You should check to see why your relay (the qmail-send program at front.mymachines.net) is getting email that should be sent to the autoresponder. Unless I'm completely misunderstanding what you're trying to do, mail being sent to the autoresponder shouldn't ever leave your server.

Please post the latency times you're getting between you and your server on Mars; I'm having some very slow latency times to Mars and may want to switch providers there.

Thanks.

Jeff
 
Jeff,

First change to Galactic Internet. Their great. :p

Front isn't the relay service. Front.mymachines.net is the email server that the originating email came from. i.e. the one my personal box lives on. Because it is a different machine on the network it still goes through the relay service.


Front -> Relay -> Customer Machine |
-----------------------------------| autoreponder
Front <- Relay <- Customer Machine |

But right now all I get is this:

Front -> Relay -> Customer Machine |
-----------------------------------| autoreponder


As useless as the one legged horse that I got when I signed up for my Galactic account. They gave me the option of upgrading to the two legged but I would have had to pay the shipping.

Big Wil
 
Last edited:
So is there a replacement out there for the stock autoresponder program? I have tried everything and apparently they have never worked since going to Direct Admin and away from my old Autoresponder2 and Qmail. I need something that will work please.

I don't think it can be my relay setup because the Vacation email functions the same way and works fine.

Big Wil
 
I'm not sure where I'm going with this...

but...

is autoresponder@ the real name in the error?

if so, then the problem is that autoresponder isn't able to receive email.

Jeff
 
[email protected] isn't the real email address no. It is fictional but still represents a real autoresponder address.

Problem has been identified. Apparently because of the 'unseen' bit in the configuration of the autoresponder the email was receiving a 550 and wasn't going through. This is because there was no catchall, was no email box with the same name, and the unseen bit was set.

By commenting out the unseen bit the autoresponder responds successfully.

userautoreply:
driver = accept
condition = ${lookup{$local_part} lsearch {/etc/virtual/${domain}/autoresponder.conf}{yes}{no}}
require_files = /etc/virtual/${domain}/reply/${local_part}.msg
transport = userautoreply
#unseen

But now the question arises... does this pose any kind of a breach or open up any holes a spammer can get through. Lets hope not.

Special thanks to the DA crew for helping me by figuring this one out.

Big Wil
 
Back
Top