`dnsdomainname` is an interesting default; of course its not guaranteed to work (for me its just my local host name). Probably you already have something on your system saying "use this to send mail" (a "smarthost"). Otherwise, none of these would have worked. Another option would be to do a dnslookup on 'smtp-server', which seems to get used sometimes. Justin On Mon, Aug 09, 2004 at 01:48:37PM +0200, Tore Anderson wrote: > Anyway, to see if you or I am the odd man out here :-) , I tested the > packages that are providing mail-transport-agent to see if they worked > with only their default configuration. My Debconf priority is set > to "high" - and the packages was installed by just hitting enter whenever > I was asked something, and finally send an email to a remote address > and see if it arrived. > > Results: > > postfix, courier-mta: Worked without requiring any interaction. > > exim (v3): Worked fine, but insisted on me entering the account > rootmail should be forwarded to. > > sendmail: Worked fine, but I had explicitly say that I wanted to > configure it. > > smail: Insisted on me specifying smarthost (I entered "none") and > an alias for rootmail just like exim. After that, it sent mail > just fine. > > xmail: Didn't provide /usr/lib/sendmail (policy violation?), but > mail sent via 'nc localhost smtp' arrived to the remote > destination as expected. > > emtp-run: Did not work, probably due to its nature - it requires > a mail relay to function as far as I understand. > > nullmailer, ssmtp: Worked, though that was probably just luck - > they seem to require an smtp relay just like esmtp-run, but > guessed mail.`dnsdomainname` in the default configuration which > happens to work here.
Attachment:
signature.asc
Description: Digital signature