George Bonser <[EMAIL PROTECTED]> writes:
> This is also a correct method. By setting your HELO to the name your IP
> address resolves to, you are assured of delivery to most every site that
> accepts mail from ISP dialups.
Right. I get the same effect (though there's a minor bug because DNS
isn't always happy as soon as the IP address changes) from my dhcpcd
script with exim like this:
#!/bin/sh
source /etc/dhcpc/dhcpcd-eth1.info
logger echo "`date` dhcpcd-sv: IP address changed to $IPADDR"
RR_NAME=`host ${IPADDR} ${DNS} | grep Name | cut -b 7-`
# Tell exim what happened.
(cd /etc && \
perl -pi -e "s/^RR_HOSTNAME = (.*)/RR_HOSTNAME = ${RR_NAME}/o" exim.conf)
exit 0
And I just have this in my exim.conf file:
# This is who we want to be known as. It also affects the outgoing
# HELO messages, so you want it to match exim's outgoing IP
RR_HOSTNAME = cs2868-35.austin.rr.com
primary_hostname = RR_HOSTNAME
etc.
> Note that many mailhosts not only refuse mail from blocks of IP
> addresses that are known dialups but also reject mail from
> hostsnames including such patterns as "cust" or "dialup" or
> "dynamic"
Yep. I haven't really had a problem (that I know of) with this, but
it's a choice between two evils. If I do this, I risk being shut out
by people that block dynamic ip's, but if I use the RR smtp relay,
then I'm relying on RR to keep their server up and well maintained and
that doesn't give me a warm fuzzy feeling either...
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
