|
Home > Archive > Debian Developers > April 2004 > Re: exim4-config: doesn't support smarthost with local mail and rewriting
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Re: exim4-config: doesn't support smarthost with local mail and rewriting
|
|
| Andreas Metzler 2004-04-07, 10:50 am |
| On Wed, Apr 07, 2004 at 03:52:12AM -0500, Chris Cheney wrote:
[...]
> Also the question for /etc/mailname isn't clear I think it should be the
> hostname of the box they are configuring, right? If you set it to the
> domain name of your mail provider then exim thinks all users are local.
> If you set it to your hostname then it doesn't do rewriting!
[...]
Marc Haber, Chris Cheney, Adam Conrad and me had a rather extensive
discussion about that on IRC. The real culprit seems indeed to be
/etc/mailname. Policy and mailname(5) both define mailname as the
visible domain part of outgoing mail. Exim[1] has used it both for that
purpose and as part of the list of domains that are local, i.e. that
should be delivered locally.
The fix I intend to implement is to stop to *always* include
/etc/mailname in local_domains and instead only to add it as default
for "dc_other_hostnames" in debconf. This should fix this bug *and*
not break any upgrades of existing installations.
cu andreas
PS: I know this too short but I lack the energy currently for writing
an exhaustive essay. ;-)
[1] eximv3, eximv4 and postfix
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Andreas Metzler 2004-04-07, 12:35 pm |
| On Wed, Apr 07, 2004 at 02:44:38PM +0200, Andreas Metzler wrote:
> Policy and mailname(5) both define mailname as the
> visible domain part of outgoing mail. Exim[1] has used it both for that
> purpose and as part of the list of domains that are local, i.e. that
> should be delivered locally.
>
> The fix I intend to implement is to stop to *always* include
> /etc/mailname in local_domains and instead only to add it as default
> for "dc_other_hostnames" in debconf. This should fix this bug *and*
> not break any upgrades of existing installations.
[...]
I have invested a little time in this, starting implementation and
stumbled over these Gotchas:
* Should mailname be used to qualify only senders or also recipient
addresses?
* There is a reason why /etc/mailname is local: It is used to qualify
both sender _and_ recipient and you do not want root to be qualified
as root@hotmail.com.
* How using mailname to qualify senders and hostname -f or "localhost"
for qualifying recipients?
* Policy is unclear or wrong in this respect.
* What's up with "satellite" ("mail sent by smarthost; no local
mail")? It currently expects you to use hostname -f in /etc/mailname
and later hides it with rewriting and uses the value given at "Domain
name for local users:". The only clean solution would be to abolish
this rewriting and use /etc/mailname as the "visible name". But
afaict this cannot be done without breaking upgrades from exim4 and
exim3.
cu and- just questions, no answers. -reas
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
|
|
|
|
|