I have installed Postfix, Dovecot, and Squirrelmail on a CentOS 5.5
machine. In Squirrelmail a user can send mail, but he is not receiving
replies. There is nothing relevant in the maillog other than the
user's (successful) login attempts. I am at loss, I have been
following tutorials such as the Perfect Server [1] series and other
Google results, but I cannot get this thing to receive mail. What
should I be checking?

Thanks!


[1] http://www.howtoforge.com/perfect-server-centos-5.5-x86_64-ispconfig-2

--
Dotan Cohen

http://gibberish.co.il
http://what-is-what.com
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

On Sun, Oct 17, 2010 at 6:39 PM, Dotan Cohen <dotancohen@gmail.com> wrote:
> I have installed Postfix, Dovecot, and Squirrelmail on a CentOS 5.5
> machine. In Squirrelmail a user can send mail, but he is not receiving
> replies. There is nothing relevant in the maillog other than the
> user's (successful) login attempts. I am at *loss, I have been
> following tutorials such as the Perfect Server [1] series and other
> Google results, but I cannot get this thing to receive mail. What
> should I be checking?
>
> Thanks!
>
>
> [1] http://www.howtoforge.com/perfect-server-centos-5.5-x86_64-ispconfig-2
>
> --
> Dotan Cohen
>

You will want to check your DNS and try to telnet to the server. If
your server is behind NAT or you run split-dns it would be advisable
to try it from another connection.

dig mx yourdomain.com
telnet smtp.yourdomain.com 25

Of course if your mx record points to something other than
smtp.yourdomain.com you will want to use that instead.

Ryan
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

On Mon, Oct 18, 2010 at 01:46, Ryan Wagoner <rswagoner@gmail.com> wrote:
> You will want to check your DNS and try to telnet to the server. If
> your server is behind NAT or you run split-dns it would be advisable
> to try it from another connection.
>
> dig mx yourdomain.com
> telnet smtp.yourdomain.com 25
>
> Of course if your mx record points to something other than
> smtp.yourdomain.com you will want to use that instead.
>

Thanks, Ryan. The MX record looks fine, but telnet won't connect:

✈dcl:~$ dig mx sharingcenter.eu

; <<>> DiG 9.7.1-P2 <<>> mx sharingcenter.eu
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22263
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 1

;; QUESTION SECTION:
;sharingcenter.eu. IN MX

;; ANSWER SECTION:
sharingcenter.eu. 86400 IN MX 10 mail.sharingcenter.eu.

;; AUTHORITY SECTION:
sharingcenter.eu. 86400 IN NS ns2.sharingcenter.eu.
sharingcenter.eu. 86400 IN NS ns1.sharingcenter.eu.

;; ADDITIONAL SECTION:
mail.sharingcenter.eu. 86400 IN A 178.63.65.136

;; Query time: 88 msec
;; SERVER: 212.150.49.10#53(212.150.49.10)
;; WHEN: Mon Oct 18 21:52:25 2010
;; MSG SIZE rcvd: 107

✈dcl:~$ telnet sharingcenter.eu 25
Trying 178.63.65.188...
^C
✈dcl:~$ telnet mail.sharingcenter.eu 25
Trying 178.63.65.136...
telnet: Unable to connect to remote host: No route to host
✈dcl:~$



On the server, it looks like everything is running as it should:
[root@mercury ~]# service postfix status
master (pid 31800) is running...
[root@mercury ~]# service dovecot status
dovecot (pid 29751) is running...
[root@mercury ~]# netstat -anp --tcp --udp | grep LISTEN | grep 25
tcp 0 0 127.0.0.1:25 0.0.0.0:*
LISTEN 31800/master
[root@mercury ~]#


What could I be missing? The logs are clean.

--
Dotan Cohen

http://gibberish.co.il
http://what-is-what.com
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Am 18.10.2010 22:02, schrieb Dotan Cohen:
> On the server, it looks like everything is running as it should:
> [root@mercury ~]# service postfix status
> master (pid 31800) is running...
> [root@mercury ~]# service dovecot status
> dovecot (pid 29751) is running...
> [root@mercury ~]# netstat -anp --tcp --udp | grep LISTEN | grep 25
> tcp 0 0 127.0.0.1:25 0.0.0.0:*
> LISTEN 31800/master
> [root@mercury ~]#

The daemon is bound to localhost only.

> What could I be missing? The logs are clean.

postconf -e 'inet_interfaces = all'

service postfix restart

Alexander
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

On Mon, Oct 18, 2010 at 22:06, Alexander Dalloz <ad+lists@uni-x.org> wrote:
> The daemon is bound to localhost only.
>

Yes, that would be a problem!

>> What could I be missing? The logs are clean.
>
> postconf -e 'inet_interfaces = all'
>
> service postfix restart
>

Thanks! However, even after the change and confirming that postfix is
listening properly:
[root@mercury ~]# postconf -e 'inet_interfaces = all'
[root@mercury ~]# service postfix restart
Shutting down postfix: [ OK ]
Starting postfix: [ OK ]
[root@mercury ~]# netstat -anp --tcp --udp | grep LISTEN | grep 25
tcp 0 0 0.0.0.0:25 0.0.0.0:*
LISTEN 7816/master
[root@mercury ~]#


I still cannot cannot connect with telnet:

✈dcl:~$ telnet sharingcenter.eu 25
Trying 178.63.65.188...
Trying 178.63.65.136...
telnet: Unable to connect to remote host: Connection timed out
✈dcl:~$ telnet mail.sharingcenter.eu 25
Trying 178.63.65.136...
telnet: Unable to connect to remote host: No route to host
✈dcl:~$ ping sharingcenter.eu
PING sharingcenter.eu (178.63.65.188) 56(84) bytes of data.
64 bytes from static.188.65.63.178.clients.your-server.de
(178.63.65.188): icmp_req=1 ttl=50 time=85.0 ms
64 bytes from static.188.65.63.178.clients.your-server.de
(178.63.65.188): icmp_req=2 ttl=50 time=189 ms
64 bytes from static.188.65.63.178.clients.your-server.de
(178.63.65.188): icmp_req=3 ttl=50 time=92.0 ms
^C
--- sharingcenter.eu ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 85.069/122.275/189.675/47.745 ms
✈dcl:~$


Why might that be?

--
Dotan Cohen

http://gibberish.co.il
http://what-is-what.com
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Dotan Cohen wrote:
> On Mon, Oct 18, 2010 at 22:06, Alexander Dalloz <ad+lists@uni-x.org>
> wrote:
<snip>
> Thanks! However, even after the change and confirming that postfix is
> listening properly:
<snip>
> I still cannot cannot connect with telnet:
>
> â??dcl:~$ telnet sharingcenter.eu 25
> Trying 178.63.65.188...
> Trying 178.63.65.136...
> telnet: Unable to connect to remote host: Connection timed out
> â??dcl:~$ telnet mail.sharingcenter.eu 25
> Trying 178.63.65.136...
> telnet: Unable to connect to remote host: No route to host
<snip>
Coming in late, and sorry if this has been suggested, but could it be a
firewall rule blocking it?

mark

_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

On 10/18/2010 04:18 PM, Dotan Cohen wrote:

On Mon, Oct 18, 2010 at 22:06, Alexander Dalloz <ad+lists@uni-x.org> wrote:


The daemon is bound to localhost only.




Yes, that would be a problem!




What could I be missing? The logs are clean.



postconf -e 'inet_interfaces = all'

service postfix restart




Thanks! However, even after the change and confirming that postfix is
listening properly:
[root@mercury ~]# postconf -e 'inet_interfaces = all'
[root@mercury ~]# service postfix restart
Shutting down postfix: [ OK ]
Starting postfix: [ OK ]
[root@mercury ~]# netstat -anp --tcp --udp | grep LISTEN | grep 25
tcp 0 0 0.0.0.0:25 0.0.0.0:*
LISTEN 7816/master
[root@mercury ~]#


I still cannot cannot connect with telnet:

✈dcl:~$ telnet sharingcenter.eu 25
Trying 178.63.65.188...
Trying 178.63.65.136...
telnet: Unable to connect to remote host: Connection timed out
✈dcl:~$ telnet mail.sharingcenter.eu 25
Trying 178.63.65.136...
telnet: Unable to connect to remote host: No route to host
✈dcl:~$ ping sharingcenter.eu
PING sharingcenter.eu (178.63.65.188) 56(84) bytes of data.
64 bytes from static.188.65.63.178.clients.your-server.de
(178.63.65.188): icmp_req=1 ttl=50 time=85.0 ms
64 bytes from static.188.65.63.178.clients.your-server.de
(178.63.65.188): icmp_req=2 ttl=50 time=189 ms
64 bytes from static.188.65.63.178.clients.your-server.de
(178.63.65.188): icmp_req=3 ttl=50 time=92.0 ms
^C
--- sharingcenter.eu ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 85.069/122.275/189.675/47.745 ms
✈dcl:~$


Why might that be?



Firewall?



--

StephenÂ*Clark

NetWolves

Sr.Â*SoftwareÂ*EngineerÂ*III

Phone:Â*813-579-3200

Fax:Â*813-882-0209

Email:Â*steve.clark@netwolves.com

http://www.netwolves.com




_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

No, I should have mentioned that the firewall is open:

[root@mercury public_html]# iptables -L -n -v
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source
destination

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source
destination

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source
destination
[root@mercury public_html]#

--
Dotan Cohen

http://gibberish.co.il
http://what-is-what.com
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

On Mon, Oct 18, 2010 at 22:34, Steve Clark <sclark@netwolves.com> wrote:
> Hmm... I am not having any problem connecting from the U.S.
>
> ping 178.63.65.136
> PING 178.63.65.136 (178.63.65.136) 56(84) bytes of data.
> 64 bytes from 178.63.65.136: icmp_seq=1 ttl=49 time=140 ms
> 64 bytes from 178.63.65.136: icmp_seq=2 ttl=49 time=142 ms
> 64 bytes from 178.63.65.136: icmp_seq=3 ttl=49 time=138 ms
>
> telnet 178.63.65.136 25
> Trying 178.63.65.136...
> Connected to 178.63.65.136.
> Escape character is '^]'.
> ^]
> telnet> close
> Connection closed.
>

Exactly the problem! It pings fine (so I know that connections can be
established over the physical wires) and on the IP address telnet
answers. However, telnet to port 25 (smtp) with the domain name fails.
Why could that be?

--
Dotan Cohen

http://gibberish.co.il
http://what-is-what.com
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Dotan Cohen wrote:
> On Mon, Oct 18, 2010 at 22:34, Steve Clark <sclark@netwolves.com> wrote:
>> Hmm... I am not having any problem connecting from the U.S.
<snip>>
>> telnet 178.63.65.136 25
>> Trying 178.63.65.136...
>> Connected to 178.63.65.136.
>> Escape character is '^]'.
>> ^]
>> telnet> close
>> Connection closed.
>
> Exactly the problem! It pings fine (so I know that connections can be
> established over the physical wires) and on the IP address telnet
> answers. However, telnet to port 25 (smtp) with the domain name fails.
> Why could that be?

Bingo! DNS.

mark

_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos