Re: receiving mail

2009-01-14 Thread Chuck Swiger

On Jan 13, 2009, at 11:51 PM, Pieter Donche wrote:

on host1:
$ host -t MX macos.cmi.ua.ac.be
returns no answer


It is recommended to configure MX records for the domains in DNS, but  
mail will fall back to using A records if no MX records exist.



But, when I try from host1
$ telnet host2.domain.topdom 25

Trying 143.129.75.1...
telnet: Unable to connect to remote host: Connection refused

Op host2.domain.topdom I see sendmail is running:
host2: $ ps -jaxw | grep sendm
smmsp   816 1   816   8160 Is??0:00.02 sendmail:  
Queue run...@00:30:00 for /var/spool/clientmqueue (sendmail)
root812 1   812   8120 Ss??0:00.01 sendmail:  
accepting connections (sendmail)


What's wrong? Why does this not work out of the box ??



Given the security history of sendmail, it's not prudent to enable  
sendmail by default.  Those two processes are the client mqueue runner  
and probably a daemon listening only on localhost rather than on all  
interfaces.


There is a minimum level of effort required to set up mail properly;  
at the least, read /etc/mail/README and set:


  sendmail_enable=YES

...in /etc/rc.conf.  I expect to deal with sendmail for as long as I  
administer Unix boxes, but alternatives like Postfix in particular  
would be my preference from a number of standpoints.


Regards,
--
-Chuck

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: receiving mail

2009-01-14 Thread Jeffrey Goldberg

On Jan 14, 2009, at 1:02 PM, Chuck Swiger wrote:


On Jan 13, 2009, at 11:51 PM, Pieter Donche wrote:





What's wrong? Why does this not work out of the box ??


Given the security history of sendmail, it's not prudent to enable  
sendmail by default.


It's not just that, but people who don't understand how mail transport  
works, shouldn't be running mail servers.


I expect to deal with sendmail for as long as I administer Unix  
boxes, but alternatives like Postfix in particular would be my  
preference from a number of standpoints.


I'm in the same position.  I starting running alternatives to sendmail  
in the late 90s on systems that I knew I was always going to maintain,  
but for systems that would be passed to others to maintain, I stuck  
with installing sendmail because there was much more expertise.  Now a- 
days, I'm happy to set up Postfix on such systems (but will still use  
exim for myself).


Cheers,

-j

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: receiving mail

2009-01-13 Thread Mel
On Tuesday 13 January 2009 13:20:33 Pieter Donche wrote:

 'Returned mail: see transcript for details:

 - The following addresses had permanent fatal errors -
 u...@host2.domain.topdom

 - Transcript of session follows -
 550 5.1.2 u...@host2.domain.topdom... Host unknown (Name server:
 mailhost.domain.topdom: host not found)
 -

 host1 and host2 are both behind a firewall, but they are in the same
 zone (so firewall rules do not apply), both are even connected to same
 switch and their IPs are in the same subnet.
 Both have fixed IP address (not DHCP)

 mailhost.domain.topdom does not exist in DNS, but host1 can send
 mail to other mailservers all over the world.

MX record for host2.domain.topdom resolves to an unknown 
mailhost.domain.topdom.
See: host -t MX host2.domain.topdom on host1.domain.topdom.

-- 
Mel

Problem with today's modular software: they start with the modules
and never get to the software part.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: receiving mail

2009-01-13 Thread Sahil Tandon
On Tue, 13 Jan 2009, Pieter Donche wrote:

 Between host1 (non-freebsd) and host2 (freebsd 7), sending a mail from  
 host1 to host2 (both in domain  .domain.topdom) results in message  
 'Returned mail: see transcript for details:

- The following addresses had permanent fatal errors -
 u...@host2.domain.topdom

- Transcript of session follows -
 550 5.1.2 u...@host2.domain.topdom... Host unknown (Name server:
 mailhost.domain.topdom: host not found)
 -

The MX for host2.domain.topdom is mailhost.domain.topdom; the latter is
unreachable by host1, hence the permanent failure.

 mailhost.domain.topdom does not exist in DNS, but host1 can send
 mail to other mailservers all over the world.

The fact that host1 can send mail anywhere else is irrelevant; fix the MX
entry or make mailhost.domain.topdom real/reachable from host1.  Or remove
or adjust the MX entry for host2.domain.topdom so host1 sends mail to
host2.domain.topdom instead of its mailhost.domain.topdom.

-- 
Sahil Tandon sa...@tandon.net
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: receiving mail

2009-01-13 Thread Pieter Donche

on host1:
$ host -t MX macos.cmi.ua.ac.be
returns no answer

This is the same as with another host on the same subnet, also in the
same zone and on the same switch...  and which does receive a sent mail

---

But, when I try from host1
$ telnet host2.domain.topdom 25

Trying 143.129.75.1...
telnet: Unable to connect to remote host: Connection refused

Op host2.domain.topdom I see sendmail is running:
host2: $ ps -jaxw | grep sendm
smmsp   816 1   816   8160 Is??0:00.02 sendmail: Queue 
run...@00:30:00 for /var/spool/clientmqueue (sendmail)
root812 1   812   8120 Ss??0:00.01 sendmail: accepting 
connections (sendmail)


What's wrong? Why does this not work out of the box ??


On Tue, 13 Jan 2009, Mel wrote:


On Tuesday 13 January 2009 13:20:33 Pieter Donche wrote:


'Returned mail: see transcript for details:

- The following addresses had permanent fatal errors -
u...@host2.domain.topdom

- Transcript of session follows -
550 5.1.2 u...@host2.domain.topdom... Host unknown (Name server:
mailhost.domain.topdom: host not found)
-

host1 and host2 are both behind a firewall, but they are in the same
zone (so firewall rules do not apply), both are even connected to same
switch and their IPs are in the same subnet.
Both have fixed IP address (not DHCP)

mailhost.domain.topdom does not exist in DNS, but host1 can send
mail to other mailservers all over the world.


MX record for host2.domain.topdom resolves to an unknown
mailhost.domain.topdom.
See: host -t MX host2.domain.topdom on host1.domain.topdom.

--
Mel

Problem with today's modular software: they start with the modules
   and never get to the software part.


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org