[Pkg-exim4-users] two elementary questions

David Liontooth liontooth@cogweb.net
Mon, 16 May 2005 00:09:51 -0700


Hi Marc,

Marc Haber wrote:

>>>On Sun, May 15, 2005 at 08:15:04PM -0700, David Liontooth wrote:
>>>      
>>>
>>>>When I try to mail to a local user, I get "R=dnslookup T=remote_smtp
>>>>defer (111)"
>>>>        
>>>>
>>>So the system doesn't consider that mail local and tries to send to
>>>the smarthost.
>>>      
>>>
In brief, if I chose 'satelite', to get exim4 to consider any mail local
I need to manually add in this kind of thing:

dc_other_hostnames='chianti.cogweb.net'

Is that correct? So that means it's a local address?
That's really not self-explanatory. I added this,
borrowing from exim3 a more explicitly named variable:

dc_local_domains='localhost:chianti'

That seems to work, but I haven't tested if this line is what makes
the difference. Which one do I really need?

>>exim 3 has better text guiding naive users towards the "Internet"
>>choice, which is what I needed.
>>    
>>
>"Smarthost" should work for you as well, if configured correctly.
>
>Experience has shown that it is not a good idea to nudge people
>towards some choice, since there are always configurations in which
>the "default" choice won't work. This actually is something we have
>learned from exim3 nudging people towards the "internet" choice, which
>will fall in pieces in a firewalled setup where usage of a smarthost
>is absolutely mandated - for example in most corporate environments
>and on ISP networks employing port 25 blocking.
>  
>
The fact that there's no universal default configuration is
a given; it's still useful to suggest a commonly valid default.

>"This name will also be used by other programs; it should be the
>single, full domain name (FQDN) from which mail will appear to
>originate." "chianti" is not a fully qualified domain name. This is
>one of the first changes that will be done to the Debconf templates
>once the strings have been unfrozen after sarge's release.
>  
>
If I use the FQDN, will exim4 still understand this is to
be treated as the local machine? Where the mail appears
to originate isn't much of an issue for me; I'm not
receiving mail from the outside in any case.

>>I suspect
>>my problem was that I kept chosing 'satellite' at the start --
>>    
>>
>No, satellite is fine.
>  
>
Interesting -- but only after manually adding local machines,
right?

>Mail is - unfortunately - a little more complex than your average core
>package, and the debconf templates have been frozen for too long time.
>  
>
I see -- so this is pain inflicted by a delayed sarge?

Cheers,
Dave