Thanks Steve. I just needed to update the mailertable correctly, like your example. Webmin apparently didn't do it the way I thought. (I probably did it incorrectly, but we won't go there... :-) ...)
Anyway, it's routing mail now. I just have to wait and see if it catches any spam. Thanks for your help. James On Tue, 2002-11-12 at 13:34, Cowles, Steve wrote: > > -----Original Message----- > > From: James Pifer > > Subject: RE: SMTP/AV/Spam Follow-Up > > > > > > Steve, > > > > Thanks. That fixed it. I appreciate the instructions. > > > > I do have a new problem you might be able to help me with. I seem to > > have a routing problem. Here's the situation. I'm attempting to test > > MailScanner using spam and antivirus. So I installed another Linux > > machine and have all of that working. So I want to redirect my > > incoming mail to this new server first, then forward it to my existing > > mail server after it's gone through the filters. > > > > My original mail server is 192.168.1.2 and the new one is 192.168.1.6. > > My MX record in DNS points to my external IP address. Mail from the > > outside is forwarded though a Linksys router to 192.168.1.6. > > > > On 192.168.1.6 I used webmin to configure it to deliver SMTP mail for > > the domain to 192.168.1.2 and ignore the MX record. I tried both SMTP > > and SMTP Relay settings. > > > > When a message comes in from the outside it gets to 192.168.1.6 but > > then fails saying there's a mail loop, possibly a problem with the > > MX record. Root ends up getting the error message in its mailbox. > > > > Any suggestions? > > James > > > > I'd really need to se the actual error message, but it sounds like the "Mail > loops back to myself" error. If so, then checkout the FAQ as > www.sendmail.org This particular error is in the top 5 list. > > Also, I have never used webmin to configure sendmail. So I have no idea how > its configuring sendmail to relay inbound e-mail for your domain. FWIW: I > add entries to /etc/mail/mailertable to override the MX record so that final > delivery is sent to our Exchange sever. i.e. > > If FQDN exchange.mydomain.com can be resolved through DNS... > mydomain.com esmtp:exchange.mydomain.com > > If exchange.mydomain.com cannot be resolved through DNS, but listed in > /etc/hosts > mydomain.com esmtp:[exchange.mydomain.com] > > If neither of the above... you can always use the ip address > mydomain.com esmtp:[192.168.1.2] > > Plus, I had to remove mydomain.com from /etc/mail/local-host-names to stop > local delivery. i.e. no procmail. This one change may cause you problems if > your using a procmail recipe to invoke your scanning software. For me, I had > to re-compile sendmail for milter support so that sendmail would call > spamassassin early on in the delivery cycle prior to final delivery > (mailertable). > > Steve Cowles > > > > -- > redhat-list mailing list > unsubscribe mailto:redhat-list-request@;redhat.com?subject=unsubscribe > https://listman.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:redhat-list-request@;redhat.com?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
