setting HELO name per MTA

I am using DAEMON_OPTIONS to configure mail to be sent on different
IPs. For example:
DAEMON_OPTIONS(`Port=smtp, Name=MTA, Addr=xx.xx.xx.xx, M=bh')

Although the b switch works, and it sends the email on the same
interface that it receives it on, the h switch doesn't seem to work.
The server identifies itself by the main hostname of the server. Is
there a way to set this on each individual MTA definition?

I have googled and saw a few people asking the same question, but with
no responses.

Re: setting HELO name per MTA

In article <1193690346.661356.118070@y42g2000hsy.googlegroups.com> Russ
writes:
>I am using DAEMON_OPTIONS to configure mail to be sent on different
>IPs. For example:
>DAEMON_OPTIONS(`Port=smtp, Name=MTA, Addr=xx.xx.xx.xx, M=bh')
>
>Although the b switch works, and it sends the email on the same
>interface that it receives it on, the h switch doesn't seem to work.
>The server identifies itself by the main hostname of the server. Is
>there a way to set this on each individual MTA definition?

Sure, but it's not the server that sends HELO, it's the client - i.e.
the h modifier goes in CLIENT_OPTIONS() (look for DaemonPortOptions and
ClientPortOptions in doc/op/op.*).

--Per Hedeland
per@hedeland.org

Re: setting HELO name per MTA

"Russ" wrote in message
news:1193690346.661356.118070@y42g2000hsy.googlegroups.com.. .
> I am using DAEMON_OPTIONS to configure mail to be sent on different
> IPs. For example:
> DAEMON_OPTIONS(`Port=smtp, Name=MTA, Addr=xx.xx.xx.xx, M=bh')
>
> Although the b switch works, and it sends the email on the same
> interface that it receives it on, the h switch doesn't seem to work.
> The server identifies itself by the main hostname of the server. Is
> there a way to set this on each individual MTA definition?
>
> I have googled and saw a few people asking the same question, but with
> no responses.

I use this:
define(`confSMTP_LOGIN_MSG',`$?{if_name}${if_name}$|$j$. Sendmail $v; $b
(spammers executed here)')dnl

It picks up the name from the PTR record for the interface's IP address -
which DAEMON_OPTIONS( ... Modifier=b ) locks in.

There's still a problem with the "b" modifier: If one locks in an IPv6
address and needs to forward/relay the message out, if the next destination
doesn't have IPv6, the message gets stuck in the queue. The bug is still
there.

Re: setting HELO name per MTA

Per Hedeland wrote:
> In article <1193690346.661356.118070@y42g2000hsy.googlegroups.com> Russ
> writes:
> >I am using DAEMON_OPTIONS to configure mail to be sent on different
> >IPs. For example:
> >DAEMON_OPTIONS(`Port=smtp, Name=MTA, Addr=xx.xx.xx.xx, M=bh')
> >
> >Although the b switch works, and it sends the email on the same
> >interface that it receives it on, the h switch doesn't seem to work.
> >The server identifies itself by the main hostname of the server. Is
> >there a way to set this on each individual MTA definition?
>
> Sure, but it's not the server that sends HELO, it's the client - i.e.
> the h modifier goes in CLIENT_OPTIONS() (look for DaemonPortOptions and
> ClientPortOptions in doc/op/op.*).
>
> --Per Hedeland
> per@hedeland.org

I'm not quite sure whether this is working or not. How do I test what
name the server uses during the HELO?

Also it seems when i telnet to the server on port 25, it still
identifies itself as the main hostname. Is there a way to change this
on a per ip basis?

Re: setting HELO name per MTA

In article <1193698549.965336.152000@v3g2000hsg.googlegroups.com> Russ
writes:
>
>Per Hedeland wrote:
>> In article <1193690346.661356.118070@y42g2000hsy.googlegroups.com> Russ
>> writes:
>> >I am using DAEMON_OPTIONS to configure mail to be sent on different
>> >IPs. For example:
>> >DAEMON_OPTIONS(`Port=smtp, Name=MTA, Addr=xx.xx.xx.xx, M=bh')
>> >
>> >Although the b switch works, and it sends the email on the same
>> >interface that it receives it on, the h switch doesn't seem to work.
>> >The server identifies itself by the main hostname of the server. Is
>> >there a way to set this on each individual MTA definition?
>>
>> Sure, but it's not the server that sends HELO, it's the client - i.e.
>> the h modifier goes in CLIENT_OPTIONS() (look for DaemonPortOptions and
>> ClientPortOptions in doc/op/op.*).

>I'm not quite sure whether this is working or not. How do I test what
>name the server uses during the HELO?

Hm, so apparently that wasn't what you were asking about. Anyway that's
what 'h' *does*, and the simplest way to test it may be to look at the
Received: headers of a message that has gone this route - the one
generated by the next-hop should show the HELO argument (at least it
does if it's sendmail, and IIRC the RFC requires it). Or you can
probably get it logged if you bump up the LogLevel high enough, see
doc/op/op.*.

>Also it seems when i telnet to the server on port 25, it still
>identifies itself as the main hostname. Is there a way to change this
>on a per ip basis?

See "D. Stussy"'s followup - or doc/op/op.*.

--Per Hedeland
per@hedeland.org