3 messages in net.sourceforge.lists.courier-usersRe: [courier-users] "Smart" relay to ...
FromSent OnAttachments
Randall ShawAug 1, 2002 11:49 am 
Randall ShawAug 1, 2002 4:58 pm 
Randall ShawAug 1, 2002 5:08 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] "Smart" relay to courier email server machineActions...
From:Randall Shaw (me@randallshaw.com)
Date:Aug 1, 2002 5:08:40 pm
List:net.sourceforge.lists.courier-users

AYYYYEEEEEEEEEEE!!!!!!!!!!

Ok... I think I stumbled across a fix for that problem I was having.

After I put the tab in place, and then started to notice a TON of deferred notices on all sorts of email address (from clients using their esmtp compliant clients)... I decided "hmm, lets comment out this IP address of allow,RELAYCLIENT. The IP address I commented out was the IP of the courier-mta machine itself. I had that in there, in addition to the 127.0.0.1 allow,RELAYCLIENT entry, just to be sure it would relay for itself.

Well... for some unknown, odd reason, by having that line in there, made it FREAK OUT!

So, just a warning to yall, don't put this in your smtpaccess file: 127.0.0.1 allow,RELAYCLIENT ip.of.same.machine allow,RELAYCLIENT

heh! it blows up on relay for anything. Commenting it out fixed it for me. Goofy. Ok, so that problem is solved... onto the next one ;-)

-Randall Shaw