SMTP and incomming mail -- PROBLEMS??
I have some questions about mail configuration. I have a new SuSE 9.1 Pro system. There is yet no firewall setup. I choose to set up the mail routing before I configure the firewall. Because I am new to SuSE I choose to set up mail routing and then set up the firewall after that is working. The machine is only on the internet when I am working on the configuration. Background ... The internet is configured. DNS is configured. All browsers and network services appear to be working. telnet, ftp, etc., etc. all work fine The machine has 20 user accounts. What works ... Sending mail from user account to user account. Sending mail out from the machine to any valid email account. Problems ... I can not get mail into the machine, or, if it does come in it is rejected. I do not know which. I know postfix is working as I can do ... libros:~ # telnet localhost 25 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 libros.andante.mn.org ESMTP Postfix Can someone point me to the correct issue? I am not wishing for a complete answer just a pointer to the correct documentation. Certainly if someone has the complete answer I would be very grateful:-) Is this all a postfix configuration issue? The final configuration I wish to achieve is that mail coming in for someuser@SuSEbox.mydomain OR someuser@mydomain will be delivered to someuser on the SuSE 9.1 system while mail for someuser@someothermachine.mydomain will be sent to one of the other computers on the LAN for delivery on that machine. If this is entirely in the realm of postfix configuration I can work with it as I have a good set of postfix docs. I am more concerned about missing something with respect to having the SMTP port open or not configured correctly to receive incoming mail. Thanks you all very much for reading this. Peace john ------------------------------------ John N. Alegre o Andante Systems o eCommerce Consulting o Custom Web Development <*{{{{}>< ------------------------------------
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday 21 May 2004 17:19, John N. Alegre wrote:
I have some questions about mail configuration.
I have a new SuSE 9.1 Pro system. There is yet no firewall setup. I choose to set up the mail routing before I configure the firewall. Because I am new to SuSE I choose to set up mail routing and then set up the firewall after that is working. The machine is only on the internet when I am working on the configuration.
Background ...
The internet is configured. DNS is configured. All browsers and network services appear to be working. telnet, ftp, etc., etc. all work fine The machine has 20 user accounts.
What works ...
Sending mail from user account to user account. Sending mail out from the machine to any valid email account.
Problems ...
I can not get mail into the machine, or, if it does come in it is rejected. I do not know which. I know postfix is working as I can do ...
libros:~ # telnet localhost 25 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 libros.andante.mn.org ESMTP Postfix
Can someone point me to the correct issue? I am not wishing for a complete answer just a pointer to the correct documentation. Certainly if someone has the complete answer I would be very grateful:-) Is this all a postfix configuration issue? The final configuration I wish to achieve is that mail coming in for someuser@SuSEbox.mydomain OR someuser@mydomain will be delivered to someuser on the SuSE 9.1 system while mail for someuser@someothermachine.mydomain will be sent to one of the other computers on the LAN for delivery on that machine. If this is entirely in the realm of postfix configuration I can work with it as I have a good set of postfix docs. I am more concerned about missing something with respect to having the SMTP port open or not configured correctly to receive incoming mail.
this sound related to my problem 'postfix and kmail' What is in /etc/HOSTNAME and /etc/hosts? - -- Collector of vintage computers http://www.ncf.ca/~ba600 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFArqmnLPrIaE/xBZARAv9pAJ9LxCZtZHLrWtODA+3zGG9sFNfXZwCggv8+ Ganj01/XP3P55FFcQ23lfHE= =HQMH -----END PGP SIGNATURE-----
Mike, On 22-May-04 Mike Kenzie wrote:
this sound related to my problem 'postfix and kmail'
What is in /etc/HOSTNAME and /etc/hosts?
I am far from an expert on this but I don't think either of these files have anything to do with receiving or delivering mail on a smtp port via postfix. I will post them on the off chance that I am wrong. Names changed to protect the innocent;-) :::::::::::::: HOSTNAME :::::::::::::: somemachine.mydomain :::::::::::::: hosts :::::::::::::: # Lots of comments deleted 127.0.0.1 localhost # special IPv6 addresses ::1 localhost ipv6-localhost ipv6-loopback fe00::0 ipv6-localnet ff00::0 ipv6-mcastprefix ff02::1 ipv6-allnodes ff02::2 ipv6-allrouters ff02::3 ipv6-allhosts # Local domain info XXX.XXX.XXX.48 SuSEbox.mydomain SuSEbox XXX.XXX.XXX.50 someothermachine1.mydomain someothermachine1 XXX.XXX.XXX.51 someothermachine2.mydomain someothermachine2 XXX.XXX.XXX.52 someothermachine3.mydomain someothermachine3 XXX.XXX.XXX.53 someothermachine4.mydomain someothermachine4 XXX.XXX.XXX.54 someothermachine5.mydomain someothermachine5 XXX.XXX.XXX.47 router.mydomain router Does anyone else have any comments on the original question that might be helpful? Original question ################################################################### I have some questions about mail configuration. I have a new SuSE 9.1 Pro system. There is yet no firewall setup. I choose to set up the mail routing before I configure the firewall. Because I am new to SuSE I choose to set up mail routing and then set up the firewall after that is working. The machine is only on the internet when I am working on the configuration. Background ... The internet is configured. DNS is configured. All browsers and network services appear to be working. telnet, ftp, etc., etc. all work fine The machine has 20 user accounts. What works ... Sending mail from user account to user account. Sending mail out from the machine to any valid email account. Problems ... I can not get mail into the machine, or, if it does come in it is rejected. I do not know which. I know postfix is working as I can do ... libros:~ # telnet localhost 25 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 libros.andante.mn.org ESMTP Postfix Can someone point me to the correct issue? I am not wishing for a complete answer just a pointer to the correct documentation. Certainly if someone has the complete answer I would be very grateful:-) Is this all a postfix configuration issue? The final configuration I wish to achieve is that mail coming in for someuser@SuSEbox.mydomain OR someuser@mydomain will be delivered to someuser on the SuSE 9.1 system while mail for someuser@someothermachine.mydomain will be sent to one of the other computers on the LAN for delivery on that machine. If this is entirely in the realm of postfix configuration I can work with it as I have a good set of postfix docs. I am more concerned about missing something with respect to having the SMTP port open or not configured correctly to receive incoming mail. Thanks you all very much for reading this. ################################################################### Peace john ------------------------------------ John N. Alegre o Andante Systems o eCommerce Consulting o Custom Web Development <*{{{{}>< ------------------------------------
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday 22 May 2004 15:30, John N. Alegre wrote:
Mike,
On 22-May-04 Mike Kenzie wrote:
this sound related to my problem 'postfix and kmail'
What is in /etc/HOSTNAME and /etc/hosts?
I am far from an expert on this but I don't think either of these files have anything to do with receiving or delivering mail on a smtp port via postfix. I will post them on the off chance that I am wrong. Names changed to protect the innocent;-)
HOSTNAME
somemachine.mydomain
I have linux.local
hosts
# Lots of comments deleted 127.0.0.1 localhost
I also have a 127.0.0.2 linux.local I'm not sure where this comes form but it rejects mail with that name
Does anyone else have any comments on the original question that might be helpful?
look in yast for Network services/ Mail Transfer Agent/ outgoing mail / masquerading I think you need to list the domains there.
Problems ...
I can not get mail into the machine, or, if it does come in it is rejected. I do not know which. I know postfix is working as I can do ...
what is in the mail logs? mail.info mail.warn - -- Collector of vintage computers http://www.ncf.ca/~ba600 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFAr8TuLPrIaE/xBZARAn98AJ4h8602Dg2Q4JbEXXUdR/t+B1rUygCdEsGu exhVBS3uB4FzCGlQyYFsrEc= =MYvU -----END PGP SIGNATURE-----
Thanks for your continued comments Mike, Hosts is only used as a DNS replacement. It is not used at all on incomming packets. What you suggest should have no effect on incomming smtp. All outgoing mail works fine. As far as HOSTNAME, I think, someone correct me if I am wrong, that since I have a static IP on the net 24/7 via DSL that the entry in HOSTNAME for machine.domainname is correct. john On 22-May-04 Mike Kenzie wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Saturday 22 May 2004 15:30, John N. Alegre wrote:
Mike,
On 22-May-04 Mike Kenzie wrote:
this sound related to my problem 'postfix and kmail'
What is in /etc/HOSTNAME and /etc/hosts?
I am far from an expert on this but I don't think either of these files have anything to do with receiving or delivering mail on a smtp port via postfix. I will post them on the off chance that I am wrong. Names changed to protect the innocent;-)
HOSTNAME
somemachine.mydomain
I have linux.local
hosts
# Lots of comments deleted 127.0.0.1 localhost
I also have a 127.0.0.2 linux.local
I'm not sure where this comes form but it rejects mail with that name
Does anyone else have any comments on the original question that might be helpful?
look in yast for Network services/ Mail Transfer Agent/ outgoing mail / masquerading I think you need to list the domains there.
Problems ...
I can not get mail into the machine, or, if it does come in it is rejected. I do not know which. I know postfix is working as I can do ...
what is in the mail logs? mail.info mail.warn
- -- Collector of vintage computers http://www.ncf.ca/~ba600 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQFAr8TuLPrIaE/xBZARAn98AJ4h8602Dg2Q4JbEXXUdR/t+B1rUygCdEsGu exhVBS3uB4FzCGlQyYFsrEc= =MYvU -----END PGP SIGNATURE-----
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
------------------------------------ John N. Alegre o Andante Systems o eCommerce Consulting o Custom Web Development <*{{{{}>< ------------------------------------
The Saturday 2004-05-22 at 17:13 -0500, John N. Alegre wrote:
As far as HOSTNAME, I think, someone correct me if I am wrong, that since I have a static IP on the net 24/7 via DSL that the entry in HOSTNAME for machine.domainname is correct.
Notice that for email (SMTP) to work, the DNS server (the one used by the "senders" side) must have a "MX" entry form your domaain name. Your "hosts" file is not involved. As a side note, working without firewall, even for a moment, is dangerous. -- Cheers, Carlos Robinson
Carlos, On 23-May-04 Carlos E. R. wrote:
Notice that for email (SMTP) to work, the DNS server (the one used by the "senders" side) must have a "MX" entry form your domaain name. Your "hosts" file is not involved.
Thanks for your reply. This is the case. Right now I have a Red Hat 6.0 box which is accepting this and all email with the same machinename.domainname that I am trying to get working on the SuSE box. I bring that machine down when I am trying to configure the new SuSE box and back up again in a few hours. Mail is flowing fine to that system. My IP provider has a "MX" entry for machinename.domainname with the correct IP. As I said both the SuSE box and the working Red Hat 6.0 system are the same in that respect. This is why I questioned the former statement that I needed a FQDN in my HOSTNAME and /etc/hosts file unless there is something different about SuSE. I am currently thinking this is an entry of the domain name in some postfix config file. That is assuming the port is set up correctly (see original question in thread). Can anyone help me here? john ------------------------------------ John N. Alegre o Andante Systems o eCommerce Consulting o Custom Web Development <*{{{{}>< ------------------------------------
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday 22 May 2004 21:53, John N. Alegre wrote:
Carlos,
On 23-May-04 Carlos E. R. wrote:
Notice that for email (SMTP) to work, the DNS server (the one used by the "senders" side) must have a "MX" entry form your domaain name. Your "hosts" file is not involved.
Thanks for your reply.
This is the case. Right now I have a Red Hat 6.0 box which is accepting this and all email with the same machinename.domainname that I am trying to get working on the SuSE box. I bring that machine down when I am trying to configure the new SuSE box and back up again in a few hours. Mail is flowing fine to that system. My IP provider has a "MX" entry for machinename.domainname with the correct IP. As I said both the SuSE box and the working Red Hat 6.0 system are the same in that respect. This is why I questioned the former statement that I needed a FQDN in my HOSTNAME and /etc/hosts file unless there is something different about SuSE.
I am currently thinking this is an entry of the domain name in some postfix config file. That is assuming the port is set up correctly (see original question in thread). Can anyone help me here?
the mydestination value is set to myhostname in my case this no longer matches the value in HOSTNAME and think this is causing rejects. Adding the extra domains to that field I think will fix your trouble. postconf -n will show you the current settings - -- Collector of vintage computers http://www.ncf.ca/~ba600 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFAsBHvLPrIaE/xBZARAqfVAJ403ef2pUJFjaLHBiY2KoZlYyJjSgCgmYez Ii2VpzKj+iDDBe97TqakZRg= =Krim -----END PGP SIGNATURE-----
(For some reason this message of yours hasn't made to the list :-? ) El 2004-05-22 a las 20:53 -0500, John N. Alegre escribió:
Date: Sat, 22 May 2004 20:53:12 -0500 (CDT) From: John N. Alegre To: Carlos E. R. Cc: suse-linux-e
Carlos,
On 23-May-04 Carlos E. R. wrote:
Notice that for email (SMTP) to work, the DNS server (the one used by the "senders" side) must have a "MX" entry form your domaain name. Your "hosts" file is not involved.
Thanks for your reply.
This is the case. Right now I have a Red Hat 6.0 box which is accepting this and all email with the same machinename.domainname that I am trying to get working on the SuSE box. I bring that machine down when I am trying to configure the new SuSE box and back up again in a few hours. Mail is flowing fine to that system. My IP provider has a "MX" entry for machinename.domainname with the correct IP. As I said both the SuSE box and the working Red Hat 6.0 system are the same in that respect. This is why I questioned the former statement that I needed a FQDN in my HOSTNAME and /etc/hosts file unless there is something different about SuSE.
Then it is not a dns problem, and it shouldn't be a hosts file either.
I am currently thinking this is an entry of the domain name in some postfix config file. That is assuming the port is set up correctly (see original question in thread). Can anyone help me here?
Instead of:
libros:~ # telnet localhost 25 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 libros.andante.mn.org ESMTP Postfix
Try to do it giving the same domain name you use for email - then it should try to connect using the eth0 ip address instead of the 127... one. Even better, try from some other machine. You should have a look at these entries in "/etc/sysconfig/postfix" ## Type: string ## Default: "" # # Comma separated list of host-/domainnames for which postfix # should accept mail for. # localhost and the own hostname is appended automatically # POSTFIX_LOCALDOMAINS="" and then run suseconfig. There is also a setting you can use for increased verbosity when debuging: POSTFIX_ADD_debug_peer_list="someserver.somedomain" where that "someserver" would be the one email is coming from. -- Saludos Carlos Robinson
On Saturday 22 May 2004 17:08, Carlos E. R. wrote:
As a side note, working without firewall, even for a moment, is dangerous.
Nonsense. If you don't have a ton of un-needed services running (e.g. ports open) there is really very little risk. After all, most hardware firewalls are nothing but unix/linux burned into a chipset. This isn't Windows Xp, its Linux. Its what firewalls are made of. -- _____________________________________ John Andersen
The Monday 2004-05-24 at 17:49 -0800, John Andersen wrote:
Nonsense.
If you don't have a ton of un-needed services running (e.g. ports open) there is really very little risk. After all, most hardware firewalls are nothing but unix/linux burned into a chipset.
This isn't Windows Xp, its Linux. Its what firewalls are made of.
I have to disagree. Running SuSE Linux with service "susefirewall" stopped while connected to the Internet, is not wise; specially a newly installed machine, still with the configuration not finished, as is the case in point of this thread. I'm not talking of independent hardware firewalls. -- Cheers, Carlos Robinson
On Tuesday 25 May 2004 15:20, Carlos E. R. wrote:
The Monday 2004-05-24 at 17:49 -0800, John Andersen wrote:
Nonsense.
If you don't have a ton of un-needed services running (e.g. ports open) there is really very little risk. After all, most hardware firewalls are nothing but unix/linux burned into a chipset.
This isn't Windows Xp, its Linux. Its what firewalls are made of.
I have to disagree. Running SuSE Linux with service "susefirewall" stopped while connected to the Internet, is not wise; specially a newly installed machine, still with the configuration not finished, as is the case in point of this thread.
SuSE, unlike RedHat, installs pretty securely. You have to specifically turn on those ports/services you want open, rather than run around and close them. Even the Xserver does not listen remote any more. Case in point: I just installed 9.1 taking all the defaults and "netstat -anp" shows only port 22 and 25 as listening, and the only reason 25 is listening is because I told it to. If a port is not open (listening) there is nothing much that can be done to it. I never run susefirewall, I alsways run shorewall when I want build a firewall. The both just set up iptables, but closed ports present no target for attackers.
I'm not talking of independent hardware firewalls.
But I was, and I was pointing out that many of them are nothing but linux. -- _____________________________________ John Andersen
The Tuesday 2004-05-25 at 17:19 -0800, John Andersen wrote:
I'm not talking of independent hardware firewalls.
But I was, and I was pointing out that many of them are nothing but linux.
But the original poster was not using an external firewall; we were talking about the suse provided firewall being dissabled or not configured. -- Cheers, Carlos Robinson
On Friday 21 May 2004 13:19, John N. Alegre wrote:
Problems ...
I can not get mail into the machine, or, if it does come in it is rejected. I do not know which. I know postfix is working as I can do ...
libros:~ # telnet localhost 25 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 libros.andante.mn.org ESMTP Postfix
Can someone point me to the correct issue?
Have you looked at Yast2 / Network services / Mail transfer agent (step thru the NEXT button till you get to "Incoming Mail") and check the box "Accept Remote SMTP Connections" Or to check this without yast look in /etc/sysconfig/mail and make sure SMTP_LISTEN_REMOTE="yes" -- _____________________________________ John Andersen
* John Andersen <xx@xx.xx> [05-24-04 20:55]:
On Friday 21 May 2004 13:19, John N. Alegre wrote:
Problems ...
I can not get mail into the machine, or, if it does come in it is rejected. I do not know which. I know postfix is working as I can do ...
libros:~ # telnet localhost 25 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 libros.andante.mn.org ESMTP Postfix
Can someone point me to the correct issue?
Have you looked at Yast2 / Network services / Mail transfer agent (step thru the NEXT button till you get to "Incoming Mail") and check the box "Accept Remote SMTP Connections"
Or to check this without yast look in /etc/sysconfig/mail and make sure SMTP_LISTEN_REMOTE="yes"
make that SMTPD_LISTEN_REMOTE="yes" -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711
participants (5)
-
Carlos E. R. -
John Andersen -
John N. Alegre -
Mike Kenzie -
Patrick Shanahan