Re: Sendmail Smart Relay Configuring

Am Mi, den 15.02.2006 schrieb Lovell Mcilwain um 1:08:

So after your help with getting me started initially. I found another
FAQ (http://www.cri.ch/linux/docs/sk0009.html) that gave me a step by
step of how to set up smtp relay for sendmail.

The additional steps I took were as follows:

Added the following to the sendmail.mc file:
|* define(`SMART_HOST', `your-smtp-server')
FEATURE(authinfo)dnl*
*define(`RELAY_MAILER_ARGS', `TCP $h 587')
define(`ESMTP_MAILER_ARGS', `TCP $h 587')*

I would modify just 1 mailer and then define smart_host more specific.
Given you redefine the relay mailer to use port 587 outgoing then set

define(`SMART_HOST', `relay:your-smtp-server')dnl

Be aware that you need to put the smart host address into squared
brackets if the host has an MX record, which would cause the mail going
to a different, not intended host.

Updated the sendmail.cf file
||* m4 /etc/mail/sendmail.mc > /etc/mail/sendmail.cf*

Defined my account info in the AuthInfo file:
||* AuthInfo:<your-smtp-server> "U:<your-smtp-user>"
"P:<your-smtp-password>" "M:DIGEST-MD5"*
Im not sure if the "M:" is correct since the server that I would be
logging into would be over TLS port 587 and usually just does a login
challenge and nothing more. I don't know if I just need to specify login..

telnet <your smart host> 25
< greet message from smart host
ehlo your.local.hostname

Now watch out which MECHs the server offers. You can't use DIGEST-MD5 if
the other server does not handle it.

Updated the authinfo.db file
|||*| makemap hash /etc/mail/authinfo < /etc/mail/authinfo|*
|

Here I personally would use masquerading, maybe generics feature with it
in combination.

http://www.sendmail.org/m4/userdb.html

Created a userdb for header rewriting
|*|user:mailname foo@xxxxxxx|*
Created the userdb.db file
*| makemap btree /etc/mail/userdb.db < /etc/mail/userdb|*

Sendmail, Tested, and got the following output:
*[root@FC4FW mail]# /usr/sbin/sendmail -bv root@localhost
root@xxxxxxxxxxxx deliverable: mailer local, user root

[root@FC4FW mail]# /usr/sbin/sendmail -bv lovell.mcilwain@xxxxxxxxx
lovell.mcilwain@xxxxxxxxxxxx deliverable: mailer relay, host
foo.barr.com, user user@xxxxxxx
*
This would leave me to belive that this was successful from what I see
in the output. But then I take a look at /var/log/maillog and find the
following:
*
*Feb 14 18:37:04 localhost sendmail[12272]: k1EEWlrh009414:
to=<lovell.mcilwain@xxxxxxxxx>, *ctladdr=<root@xxxxxxxxxxxxxxxxxxxxx>*
(0/0), delay=09:04:17, xdelay=00:00:01, mailer=relay, pri=945174,
relay=foo.bar.com [11.222.333.444], dsn=5.0.0, *stat=Service unavailabl*e
Feb 14 18:37:04 localhost sendmail[12272]: k1EEWlrh009414:
k1ENb3vE012272: *sender notify: Service unavailable

In your sendmail.mc you find a line

dnl define(`confLOG_LEVEL', `15')dnl

Remove the leading `dnl' and restart the sendmail service. Logging will
be more verbose then.
I suspect that the smart host you defined does not handle DIGEST-MD5
password challenges.

*I thought the tutorial has gotten me closer to where I wanted to be but
can anyone else tell me what else Im missing to get this to work
properly? The things I noticed off the top of my head were:

1.The authentication method is wrong but I can't see any documentation
that states that the entry "M:login" will work.

If you call the smart host with an EHLO it will tell you what mechanism
it accepts (given it is properly configured it will handle it then).
Hope the remote server does STARTTLS sessions for LOGIN and PLAIN auth.

2. It still looks like the return mail is showing as
root@xxxxxxxxxxxxxxxxxxxxx when I thought the usersdb.db file was
supposed to take care of this. Did I need to restart sendmail or re run
the m4 command to update that there is now a usersdb.db in existance?

Do not test as root. root user has a special role: it is by default
defined as an exposed user. Always test as a mortal user.

3. Could this be an issue of not specifying the port number correctly
for sendmail to talk with the relay server properly?

I don't think so. If you think you made a mistake there you could sniff
the communication by running `tcpdump'.

I know this mail was a bit lengthy but any help is appreciated :)

Much better you provide detailed information than a statement like "it
does not work" ;)

Alexander


--
Alexander Dalloz | Enger, Germany | GPG http://pgp.mit.edu 0xB366A773
legal statement: http://www.uni-x.org/legal.html
Fedora Core 2 GNU/Linux on Athlon with kernel 2.6.11-1.35_FC2smp
Serendipity 03:03:29 up 4 days, 11:54, load average: 0.04, 0.10, 0.14

Attachment: signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Relevant Pages

  • Re: virtual domain relaying question
    ... The relay host running sendmail is then set up as ... an MX for example.not (the "front" end server). ... configuration happens on the front end relay server. ... ldap_routing *without* LDAP. ...
    (comp.mail.sendmail)
  • Re: Beaten to Death: Open Relay
    ... You can update sendmail manually. ... "The simplest approach is to list the domains you are willing to relay ... relaying, good or bad. ... people in my office send mail through the server is to include the IP ...
    (comp.mail.sendmail)
  • Re: using an smtp connector instead of smart relay setting
    ... >You can configure an SMTP connector with a Smart Host ... >> routing group as the first server, ... >> server is set to use a smart relay (we have a spam ...
    (microsoft.public.exchange.connectivity)
  • Exchange 2003 reporting Relaying Denied error for User Unknown
    ... We have an Exchange 2003 server that forwards outbound e-mail to a sendmail ... in the sendmail logs on the relay. ...
    (microsoft.public.exchange.connectivity)
  • Re: can I customize multiple relay host ? by recipient ?
    ... I have some of my clients domains MX records point to my server so that I can spam filter for them. ... I then have my Sendmail configured to relay for these domains and corresponding Mailertable entries to tell Sendmail to relay email for these domains to the real mail server, not the onelisted in MX records. ... Or, if the host name listed in the Mailertable resolves to multiple servers, Sendmail will use them. ...
    (comp.mail.sendmail)