Using a large mallet, Duke Normandin whacked out:
> I take that by "mismatches" you mean an almost correct match on the RDNS.
> In this day-and-age, 'almost' _is not_ good enough. The suckers _had_
> better resolve. The implications of this whole thread for some Mutt users
Heck no. Have you ever considered the case of large ISPs and webhosts - and
especially virtual server setups?
forward dns resolves to my-cat-is-cute.com - but reverse will point to
server22.some-web-host.com
> local mail from more one MUA, he cannot run the server "end-to-end"
> because given his dyn. IP, his outbound mail will always be rejected
> because RDNS never resolves. Hence, the need to use the 'From' thing in
You need that as ISPs dont accept mail from unresolvable domains
> /etc/muttrc, AND to "relay" your outbound to your ISP. HELO had better be
> 'yourISP.whatever' for your outbound to get through -- mismatches don't
> count.
No. You _dont_ want to filter on HELO - IIRC there's an RFC against that
> up to you. Like I said though, increasingly, your outbound needs to
> resolve on RDNS --- sad, but a fact. So this second scenario _also_ has
> implications as to how Mutt is set up.
rDNS must exist. There is no requirement that it must match forward dns
--
Suresh Ramasubramanian + Lumber Cartel India - <tinlcI>
mallet @ cluestick.org + Wallopus Malletus Indigenensis
EMail Sturmbannfuhrer, Lower Middle Class Unix Sysadmin
