Help Needed | Postfix won't send emails on my Lab Server

Discussion in 'Server Operation' started by Captain Gold, Nov 11, 2013.

  1. Captain Gold

    Captain Gold New Member

    Hello to all and thanks for reading :eek:
    I'm in dire need of help :(

    My situation:

    I'm the IT guy at my company. We have a Live server with a running site using Ubuntu server 12.04.3, wordpress (with a custom template of course), xampp, and postfix.

    I have recently installed a lab server in our office (on a MacMini1.1) using the same installation process as the Live server.

    I've fixed every issue along the way but one. Postfix refuses to send emails.

    For the explanation I'm going to use this example info:

    Website (set the same both on the Live & the Lab): www.mywebsite.co.il

    Live IP address: 6.111.222.77

    Lab IP address (in the LAN): 192.168.2.32

    Our support email address: [email protected]

    The Server User: moishe

    moishe's Password: mypass

    My "sudo dpkg-reconfigure postfix" configuration is:

    General type of mail configuration: Internet Site

    System mail name: mywebsite.co.il

    Root and postmaster mail recipient: [email protected]

    (I've also tried [email protected])

    Other destinations to accept mail for: mywebsite.co.il, localhost.co.il, localhost

    Force synchronous updates on mal queue? No

    Local networks: 127.0.0.0/8 [::ffff:127.0.0.0]/104 192.168.2.32/24

    (I've also tried: "127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128" as I remember it being the default. I realized through the hosts file that "::1" is the ipv6 localhost, and we use ipv4 so I assumed the proper one is the LAN address)

    Mailbox size limit: 0

    Local address extension character: +

    Internet protocol to use: ipv4

    I of course restarted the xampp ("sudo /opt/lampp/lampp restart") and even reloaded the postfix ("sudo /etc/init.d/postfix reload") after configuring the postfix.

    One issue I've already fixed was this error message:

    "WARNING: /etc/aliases exists, but does not have a root alias". I will gladly explain how I fixed it if it matters for the troubleshooting of my situation.

    The file "/var/log/mail.err1" on m y lab server contains the following:

    "Oct 31 12:41:30 mywebsite postfix[5377]: error: to submit mail, use the Postfix sendmail command Oct 31 12:41:30 mywebsite postfix[5377]: fatal: the postfix command is reserved for the superuser"

    Reverse DNSing shows the ip address of the live server.

    I have also made a few fixes to lampp before even installing postfix, but I assume they are not relevant here (if they are, I'm willing to share the info).

    I've looked around the internet and have spent 3 whole days on this already (10 hours per day which were mainly spent on this).

    I'm very confused as to "sendmail", as I've seen people say I shouldn't install it if I have postfix because it runs postfix over, and because postfix is a replacement to sendmail anyway… or something… ...very confused.

    I've tried real hard to understand the issue deeply enough to be able to solve this on my own, and concluded that I need the help of this community.

    I have tried several troubleshooting guides from several different sites. If needed, and if allowed in this forum, I will gladly supply links.

    Please help.

    How do I troubleshoot this? My head is steaming info through my ears already ^_^
     
  2. Croydon

    Croydon ISPConfig Developer ISPConfig Developer

    The question is, if you configured your lampp to use "postfix" for sending mails.
    Postfix should install a sendmail binary with it, that has to be used for sending mails.
     
  3. Captain Gold

    Captain Gold New Member

    Assume I'm a noob in dire need of help . . .

    Thanks for the help :)

    Hmm... I've been looking online for "how to configure xampp to use postfix for sending mails" and all I find is people asking how to do it and no one actually giving a straight answer relevant to my case.

    Out of the configurations I've done, the closest I think I did to what you seem to be describing is this:

    sudo vim /opt/lampp/etc/extra/httpd-xampp.conf

    I've replaced:
    <Directory "/opt/lampp/phpmyadmin">
    AllowOverride AuthConfig Limit
    Order allow,deny
    Allow from all
    </Directory>

    With:
    <Directory "/opt/lampp/phpmyadmin">
    AllowOverride AuthConfig Limit
    Order allow,deny
    Allow from all
    Require all granted
    </Directory>

    At the bottom of the file - I've also changed:
    <LocationMatch "^/(?i:(?:xampp|security|licenses|phpmyadmin|webalizer|server-status|server-info))">
    Order deny,allow
    Deny from all
    Allow from ::1 127.0.0.0/8 \
    fc00::/7 10.0.0.0/8 172.16.0.0/12 192.168.0.0/16 \
    fe80::/10 169.254.0.0/16
    ErrorDocument 403 /error/XAMPP_FORBIDDEN.html.var
    </LocationMatch>

    To:
    <LocationMatch "^/(?i:(?:xampp|security|licenses|phpmyadmin|webalizer|server-status|server-info))">
    Order deny,allow
    Allow from all
    </LocationMatch>


    Then I saved the file and used the following command:
    sudo chown moishe:moishe /opt/lampp/phpmyadmin/config.inc.php

    Then:
    sudo /opt/lampp/lampp security
    I answered "YES" to all and type the corresponding password.
    Then:
    sudo chown moishe:moishe /opt/lampp/phpmyadmin/config.inc.php
    sudo /opt/lampp/lampp restart


    Is that what you were referring to? Or am I missing something?
    I get the feeling I'm missing something.
    Or wait... Come to think about it though, that was all before I even installed postfix :\

    How would I go about configuring my lampp to use "postfix" for sending mails?
    What I did on the Lab Server seemed to work on the Live server... I don't understand why it wouldn't work here :confused:

    Please Help *performing a pantomime sketch of a drowning man*
     
  4. Croydon

    Croydon ISPConfig Developer ISPConfig Developer

    Ok, simpler question:
    How exactly do you try to send mails currently?
     
  5. Captain Gold

    Captain Gold New Member

    The ways I try to send e-mails to test my postfix

    There are three ways. One is by making a purchase on my Lab-Site. Which normally sends an e-mail to the customer with the electronic product. In my lab server-site - it doesn't at the moment.

    The other is this:
    echo "Test mail from postfix" | mail -s "Test Postfix" [email protected]
    (Taken from: http://rtcamp.com/tutorials/mail/postfix-debugging/)

    As that one failed, I've also tried:
    php -a
    mail ('[email protected]', "Test Postfix", "Test mail from postfix");
    exit ();

    (Taken from: http://rtcamp.com/tutorials/php/test-email-sending/)

    Failed as well. I assume it fails because I don't receive an e-mail on the gmail account.
     
  6. Croydon

    Croydon ISPConfig Developer ISPConfig Developer

    Did you try sending a mail with the "sendmail" command?
     
  7. Captain Gold

    Captain Gold New Member

    I think I did and it told me to install sendmail. which is where I got stuck.
    But just to make sure I'll try again when I get a chance to. It might only happen in the following days but if I'll try to make time for it today, as you've been kind enough to reply quickly :)
     
  8. Croydon

    Croydon ISPConfig Developer ISPConfig Developer

    If you have installed postfix there should be a binary sendmail installed with it.
    It is NOT the same as installing the program "sendmail" that is separate from postfix.
    Postfix sendmail should reside in /usr/sbin/sendmail
     
  9. Captain Gold

    Captain Gold New Member

    That's exactly what I thought and why I got stuck and turned to the forums. Because I didn't want to install sendmail as postfix should have it.

    To avoid any mistakes, let's make sure I know how:
    How do I send mail using sendmail itself? (the postfix sendmail)
     
  10. Croydon

    Croydon ISPConfig Developer ISPConfig Developer

    If your postfix sendmail behaves like mine you can test sending like this:

    Code:
    /usr/sbin/sendmail [email protected]
    Then it should wait for mail input (no prompt!)
    Enter:
    Code:
    Subject: Testmail
    This is the content to send as a test
    And this is a second line
    .
    
    Remind the trailing dot in a separate line that marks the email end.

    Have a look in the mail log what happens there.
     
  11. Captain Gold

    Captain Gold New Member

    Thank you :)
    I'll see if I remember how to look at the log (shouldn't be a problem) when I get the time to check this.
    I'll repost here this week.
     
  12. Captain Gold

    Captain Gold New Member

    My mail.log reads as follows:
    Code:
    [email protected]:~$ vim /var/log/mail.log
    Nov 19 18:03:56 mywebsite postfix/master[1383]: daemon started -- version 2.9.6, configuration /etc/postfix
    Nov 19 18:05:44 mywebsite postfix/master[1383]: reload -- version 2.9.6, configuration /etc/postfix
    Nov 19 18:06:26  postfix/master[1383]: last message repeated 2 times
    Nov 19 18:13:45 mywebsite postfix/pickup[1800]: E2EB640FEB: uid=1000 from=<moishe>
    Nov 19 18:13:45 mywebsite postfix/cleanup[1813]: E2EB640FEB: message-id=<[email protected]>
    Nov 19 18:13:45 mywebsite postfix/qmgr[1801]: E2EB640FEB: from=<[email protected]>, size=342, nrcpt=1 (queue active)
    Nov 19 18:14:16 mywebsite postfix/smtp[1815]: connect to gmail-smtp-in.l.google.com[173.194.70.26]:25: Connection timed out
    Nov 19 18:14:46 mywebsite postfix/smtp[1815]: connect to alt1.gmail-smtp-in.l.google.com[74.125.143.27]:25: Connection timed out
    Nov 19 18:15:16 mywebsite postfix/smtp[1815]: connect to alt2.gmail-smtp-in.l.google.com[173.194.79.26]:25: Connection timed out
    Nov 19 18:15:46 mywebsite postfix/smtp[1815]: connect to alt3.gmail-smtp-in.l.google.com[173.194.64.27]:25: Connection timed out
    Nov 19 18:16:16 mywebsite postfix/smtp[1815]: connect to alt4.gmail-smtp-in.l.google.com[74.125.142.27]:25: Connection timed out
    Nov 19 18:16:16 mywebsite postfix/smtp[1815]: E2EB640FEB: to=<[email protected]>, relay=none, delay=193, delays=43/0.03/150/0, dsn=4.4.1, status=deferred (connect to alt4.gmail-smtp-in.l.google.com[74.125.142.27]:25: Connection timed out)
    Nov 19 18:21:26 mywebsite postfix/qmgr[1801]: E2EB640FEB: from=<[email protected]>, size=342, nrcpt=1 (queue active)
    Nov 19 18:21:56 mywebsite postfix/smtp[1843]: connect to gmail-smtp-in.l.google.com[173.194.70.26]:25: Connection timed out
    Nov 19 18:22:26 mywebsite postfix/smtp[1843]: connect to alt1.gmail-smtp-in.l.google.com[74.125.143.26]:25: Connection timed out
    Nov 19 18:22:56 mywebsite postfix/smtp[1843]: connect to alt2.gmail-smtp-in.l.google.com[173.194.79.27]:25: Connection timed out
    Nov 19 18:23:26 mywebsite postfix/smtp[1843]: connect to alt3.gmail-smtp-in.l.google.com[173.194.64.26]:25: Connection timed out
    Nov 19 18:23:56 mywebsite postfix/smtp[1843]: connect to alt4.gmail-smtp-in.l.google.com[74.125.142.27]:25: Connection timed out
    Nov 19 18:23:56 mywebsite postfix/smtp[1843]: E2EB640FEB: to=<[email protected]>, relay=none, delay=654, delays=503/0.02/150/0, dsn=4.4.1, status=deferred (connect to alt4.gmail-smtp-in.l.google.com[74.125.142.27]:25: Connection timed out)
    
    (btw, how to I make the Code box bigger? hehe)

    Umm... So there seems to be an issue with the connectivity to google-smtp servers, right?
    Only I don't quite understand what the problem is exactly, nor how to solve it.

    Awaiting patiently & hopping for another step.
     
  13. Croydon

    Croydon ISPConfig Developer ISPConfig Developer

    Ok, back to basic ;)

    Post the output (anonymized) of:
    netstat -ntap

    iptables -L -n

    ping 74.125.143.27 (or the other ips of the google servers)
    if ping is failing then please

    traceroute 74.125.143.27

    Maybe this leads us to the solution.
     
  14. Captain Gold

    Captain Gold New Member

    Code:
    [email protected]:~$ netstat -ntap
    (No info could be read for "-p": geteuid()=1000 but you should be root.)
    Active Internet connections (servers and established)
    Proto Recv-Q Send-Q Local Address           Foreign Address         State                                                     PID/Program name
    tcp        0      0 0.0.0.0:3306            0.0.0.0:*               LISTEN                                                    -
    tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN                                                    -
    tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN                                                    -
    tcp        0      0 0.0.0.0:25              0.0.0.0:*               LISTEN                                                    -
    tcp        0      0 127.0.0.1:6010          0.0.0.0:*               LISTEN                                                    -
    tcp        0      0 0.0.0.0:443             0.0.0.0:*               LISTEN                                                    -
    tcp        0     64 192.168.2.32:22         192.168.2.11:53087      ESTABLISHED                                               -
    tcp6       0      0 :::21                   :::*                    LISTEN                                                    -
    tcp6       0      0 :::22                   :::*                    LISTEN                                                    -
    tcp6       0      0 ::1:6010                :::*                    LISTEN                                                    -
    [email protected]:~$ iptables -L -n
    FATAL: Error inserting ip_tables (/lib/modules/3.8.0-32-generic/kernel/net/ipv4/                                              netfilter/ip_tables.ko): Operation not permitted
    iptables v1.4.12: can't initialize iptables table `filter': Table does not exist                                               (do you need to insmod?)
    Perhaps iptables or your kernel needs to be upgraded.
    [email protected]:~$ ping 74.125.143.27
    PING 74.125.143.27 (74.125.143.27) 56(84) bytes of data.
    64 bytes from 74.125.143.27: icmp_req=1 ttl=43 time=114 ms
    64 bytes from 74.125.143.27: icmp_req=2 ttl=43 time=112 ms
    64 bytes from 74.125.143.27: icmp_req=3 ttl=43 time=109 ms
    64 bytes from 74.125.143.27: icmp_req=4 ttl=43 time=159 ms
    64 bytes from 74.125.143.27: icmp_req=5 ttl=43 time=125 ms
    64 bytes from 74.125.143.27: icmp_req=6 ttl=43 time=112 ms
    64 bytes from 74.125.143.27: icmp_req=7 ttl=43 time=131 ms
    64 bytes from 74.125.143.27: icmp_req=8 ttl=43 time=110 ms
    64 bytes from 74.125.143.27: icmp_req=9 ttl=43 time=117 ms
    64 bytes from 74.125.143.27: icmp_req=10 ttl=43 time=114 ms
    64 bytes from 74.125.143.27: icmp_req=11 ttl=43 time=122 ms
    64 bytes from 74.125.143.27: icmp_req=12 ttl=43 time=110 ms
    64 bytes from 74.125.143.27: icmp_req=13 ttl=43 time=110 ms
    64 bytes from 74.125.143.27: icmp_req=14 ttl=43 time=122 ms
    64 bytes from 74.125.143.27: icmp_req=15 ttl=43 time=114 ms
    64 bytes from 74.125.143.27: icmp_req=16 ttl=43 time=115 ms
    64 bytes from 74.125.143.27: icmp_req=17 ttl=43 time=120 ms
    64 bytes from 74.125.143.27: icmp_req=18 ttl=43 time=150 ms
    64 bytes from 74.125.143.27: icmp_req=19 ttl=43 time=122 ms
    64 bytes from 74.125.143.27: icmp_req=20 ttl=43 time=109 ms
    64 bytes from 74.125.143.27: icmp_req=21 ttl=43 time=178 ms
    64 bytes from 74.125.143.27: icmp_req=22 ttl=43 time=164 ms
    64 bytes from 74.125.143.27: icmp_req=23 ttl=43 time=196 ms
    64 bytes from 74.125.143.27: icmp_req=24 ttl=43 time=127 ms
    64 bytes from 74.125.143.27: icmp_req=25 ttl=43 time=127 ms
    64 bytes from 74.125.143.27: icmp_req=26 ttl=43 time=119 ms
    64 bytes from 74.125.143.27: icmp_req=27 ttl=43 time=118 ms
    64 bytes from 74.125.143.27: icmp_req=28 ttl=43 time=139 ms
    64 bytes from 74.125.143.27: icmp_req=29 ttl=43 time=194 ms
    64 bytes from 74.125.143.27: icmp_req=30 ttl=43 time=174 ms
    64 bytes from 74.125.143.27: icmp_req=31 ttl=43 time=233 ms
    64 bytes from 74.125.143.27: icmp_req=32 ttl=43 time=115 ms
    64 bytes from 74.125.143.27: icmp_req=33 ttl=43 time=112 ms
    64 bytes from 74.125.143.27: icmp_req=34 ttl=43 time=145 ms
    64 bytes from 74.125.143.27: icmp_req=35 ttl=43 time=151 ms
    64 bytes from 74.125.143.27: icmp_req=36 ttl=43 time=201 ms
    64 bytes from 74.125.143.27: icmp_req=37 ttl=43 time=167 ms
    64 bytes from 74.125.143.27: icmp_req=38 ttl=43 time=175 ms
    64 bytes from 74.125.143.27: icmp_req=39 ttl=43 time=209 ms
    64 bytes from 74.125.143.27: icmp_req=40 ttl=43 time=211 ms
    64 bytes from 74.125.143.27: icmp_req=41 ttl=43 time=112 ms
    64 bytes from 74.125.143.27: icmp_req=42 ttl=43 time=110 ms
    64 bytes from 74.125.143.27: icmp_req=43 ttl=43 time=112 ms
    64 bytes from 74.125.143.27: icmp_req=44 ttl=43 time=119 ms
    64 bytes from 74.125.143.27: icmp_req=45 ttl=43 time=112 ms
    64 bytes from 74.125.143.27: icmp_req=46 ttl=43 time=111 ms
    64 bytes from 74.125.143.27: icmp_req=47 ttl=43 time=118 ms
    ^C
    --- 74.125.143.27 ping statistics ---
    47 packets transmitted, 47 received, 0% packet loss, time 46065ms
    rtt min/avg/max/mdev = 109.333/137.590/233.623/33.354 ms
    [email protected]:~$ traceroute 74.125.143.27
    The program 'traceroute' can be found in the following packages:
     * inetutils-traceroute
     * traceroute
    Try: sudo apt-get install <selected package>
    
    The weird thing is... 192.168.2.11 is a non related computer in my LAN. I would've thought It'd try to connect through the router (192.168.2.1).

    The ping had a response so I saw no need to apt-get traceroute.

    I seem to only have time to continue this troubleshooting at the very end of my work-day, so sorry for the delayed replies. Also that makes it so I had to relog since yesterday's test (I'm SSHing this from within the LAN). I thought it's best to inform about that.

    I'm kind of loosing you here... what did we find out and how? :eek:
     
  15. Croydon

    Croydon ISPConfig Developer ISPConfig Developer

    Seens you are not root ;)
    So the correct commands would have been with sudo in front of them.
    Like "sudo iptables -L -n"
     
  16. Captain Gold

    Captain Gold New Member

    I thought that might be the case, as I'm aware that I'm not the direct root and I've been using sudo all the time during my installation & configuration processes ^_^
    I'll be right back with the sudo output ;)
     
  17. Captain Gold

    Captain Gold New Member

    Here it is

    Code:
    [email protected]:~$ sudo /usr/sbin/sendmail [email protected]
    Subject: Testmail
    This is the content to send as a test
    And this is a second line
    .
    [email protected]:~$ sudo vim /var/log/mail.log
    Nov 20 06:36:29 mywebsite postfix/qmgr[1801]: E2EB640FEB: from=<[email protected]>, size=342, nrcpt=1 (queue active)
    Nov 20 06:36:59 mywebsite postfix/smtp[2790]: connect to gmail-smtp-in.l.google.com[74.125.136.27]:25: Connection timed out
    Nov 20 06:37:29 mywebsite postfix/smtp[2790]: connect to alt1.gmail-smtp-in.l.google.com[74.125.143.27]:25: Connection timed out
    Nov 20 06:37:59 mywebsite postfix/smtp[2790]: connect to alt2.gmail-smtp-in.l.google.com[173.194.79.26]:25: Connection timed out
    Nov 20 06:38:29 mywebsite postfix/smtp[2790]: connect to alt3.gmail-smtp-in.l.google.com[173.194.64.26]:25: Connection timed out
    Nov 20 06:38:59 mywebsite postfix/smtp[2790]: connect to alt4.gmail-smtp-in.l.google.com[74.125.142.27]:25: Connection timed out
    Nov 20 06:38:59 mywebsite postfix/smtp[2790]: E2EB640FEB: to=<[email protected]>, relay=none, delay=44756, delays=44606/0.02/150/0, dsn=4.4.1, status=deferred (connect to alt4.gmail-smtp-in.l.google.com[74.125.142.27]:25: Connection timed out)
    Nov 20 07:46:29 mywebsite postfix/qmgr[1801]: E2EB640FEB: from=<[email protected]>, size=342, nrcpt=1 (queue active)
    Nov 20 07:46:59 mywebsite postfix/smtp[2865]: connect to gmail-smtp-in.l.google.com[74.125.136.26]:25: Connection timed out
    Nov 20 07:47:29 mywebsite postfix/smtp[2865]: connect to alt1.gmail-smtp-in.l.google.com[173.194.71.27]:25: Connection timed out
    Nov 20 07:47:59 mywebsite postfix/smtp[2865]: connect to alt2.gmail-smtp-in.l.google.com[173.194.79.26]:25: Connection timed out
    Nov 20 07:48:29 mywebsite postfix/smtp[2865]: connect to alt3.gmail-smtp-in.l.google.com[173.194.64.27]:25: Connection timed out
    Nov 20 07:48:59 mywebsite postfix/smtp[2865]: connect to alt4.gmail-smtp-in.l.google.com[74.125.142.26]:25: Connection timed out
    Nov 20 07:49:00 mywebsite postfix/smtp[2865]: E2EB640FEB: to=<[email protected]>, relay=none, delay=48957, delays=48806/0.02/150/0, dsn=4.4.1, status=deferred (connect to alt4.gmail-smtp-in.l.google.com[74.125.142.26]:25: Connection timed out)
    Nov 20 08:56:29 mywebsite postfix/qmgr[1801]: E2EB640FEB: from=<[email protected]>, size=342, nrcpt=1 (queue active)
    Nov 20 08:56:59 mywebsite postfix/smtp[2932]: connect to gmail-smtp-in.l.google.com[74.125.136.26]:25: Connection timed out
    Nov 20 08:57:29 mywebsite postfix/smtp[2932]: connect to alt1.gmail-smtp-in.l.google.com[173.194.71.27]:25: Connection timed out
    Nov 20 08:57:59 mywebsite postfix/smtp[2932]: connect to alt2.gmail-smtp-in.l.google.com[173.194.79.27]:25: Connection timed out
    Nov 20 08:58:29 mywebsite postfix/smtp[2932]: connect to alt3.gmail-smtp-in.l.google.com[173.194.64.26]:25: Connection timed out
    Nov 20 08:58:59 mywebsite postfix/smtp[2932]: connect to alt4.gmail-smtp-in.l.google.com[74.125.142.26]:25: Connection timed out
    Nov 20 08:59:00 mywebsite postfix/smtp[2932]: E2EB640FEB: to=<[email protected]>, relay=none, delay=53156, delays=53006/0.02/150/0, dsn=4.4.1, status=deferred (connect to alt4.gmail-smtp-in.l.google.com[74.125.142.26]:25: Connection timed out)
    Nov 20 10:06:29 mywebsite postfix/qmgr[1801]: E2EB640FEB: from=<[email protected]>, size=342, nrcpt=1 (queue active)
    Nov 20 10:06:59 mywebsite postfix/smtp[2989]: connect to gmail-smtp-in.l.google.com[74.125.136.27]:25: Connection timed out
    Nov 20 10:07:29 mywebsite postfix/smtp[2989]: connect to alt1.gmail-smtp-in.l.google.com[173.194.79.27]:25: Connection timed out
    Nov 20 10:07:59 mywebsite postfix/smtp[2989]: connect to alt2.gmail-smtp-in.l.google.com[173.194.64.27]:25: Connection timed out
    Nov 20 10:08:29 mywebsite postfix/smtp[2989]: connect to alt3.gmail-smtp-in.l.google.com[74.125.142.27]:25: Connection timed out
    Nov 20 10:08:59 mywebsite postfix/smtp[2989]: connect to alt4.gmail-smtp-in.l.google.com[74.125.137.26]:25: Connection timed out
    Nov 20 10:09:00 mywebsite postfix/smtp[2989]: E2EB640FEB: to=<[email protected]>, relay=none, delay=57357, delays=57206/0.02/150/0, dsn=4.4.1, status=deferred (connect to alt4.gmail-smtp-in.l.google.com[74.125.137.26]:25: Connection timed out)
    Nov 20 11:16:29 mywebsite postfix/qmgr[1801]: E2EB640FEB: from=<[email protected]>, size=342, nrcpt=1 (queue active)
    Nov 20 11:16:59 mywebsite postfix/smtp[3063]: connect to gmail-smtp-in.l.google.com[74.125.136.26]:25: Connection timed out
    Nov 20 11:17:29 mywebsite postfix/smtp[3063]: connect to alt1.gmail-smtp-in.l.google.com[173.194.79.27]:25: Connection timed out
    Nov 20 11:17:59 mywebsite postfix/smtp[3063]: connect to alt2.gmail-smtp-in.l.google.com[173.194.64.27]:25: Connection timed out
    Nov 20 11:18:29 mywebsite postfix/smtp[3063]: connect to alt3.gmail-smtp-in.l.google.com[74.125.142.26]:25: Connection timed out
    Nov 20 11:18:59 mywebsite postfix/smtp[3063]: connect to alt4.gmail-smtp-in.l.google.com[74.125.137.26]:25: Connection timed out
                                                                                                               1,1           Top
    :q!
    [email protected]:~$ sudo netstat -ntap
    Active Internet connections (servers and established)
    Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
    tcp        0      0 0.0.0.0:3306            0.0.0.0:*               LISTEN      1242/mysqld
    tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      867/httpd
    tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      716/sshd
    tcp        0      0 0.0.0.0:25              0.0.0.0:*               LISTEN      1383/master
    tcp        0      0 127.0.0.1:6010          0.0.0.0:*               LISTEN      4834/0
    tcp        0      0 0.0.0.0:443             0.0.0.0:*               LISTEN      867/httpd
    tcp        0    272 192.168.2.32:22         192.168.2.11:50711      ESTABLISHED 4815/sshd: moishe [pr
    tcp6       0      0 :::21                   :::*                    LISTEN      1279/proftpd: (acce
    tcp6       0      0 :::22                   :::*                    LISTEN      716/sshd
    tcp6       0      0 ::1:6010                :::*                    LISTEN      4834/0
    [email protected]:~$ sudo iptables -L -n
    Chain INPUT (policy ACCEPT)
    target     prot opt source               destination
    
    Chain FORWARD (policy ACCEPT)
    target     prot opt source               destination
    
    Chain OUTPUT (policy ACCEPT)
    target     prot opt source               destination
    [email protected]:~$ sudo ping 74.125.143.27
    PING 74.125.143.27 (74.125.143.27) 56(84) bytes of data.
    64 bytes from 74.125.143.27: icmp_req=1 ttl=43 time=127 ms
    64 bytes from 74.125.143.27: icmp_req=2 ttl=43 time=199 ms
    64 bytes from 74.125.143.27: icmp_req=3 ttl=43 time=164 ms
    64 bytes from 74.125.143.27: icmp_req=4 ttl=43 time=110 ms
    64 bytes from 74.125.143.27: icmp_req=5 ttl=43 time=123 ms
    64 bytes from 74.125.143.27: icmp_req=6 ttl=43 time=218 ms
    64 bytes from 74.125.143.27: icmp_req=7 ttl=43 time=113 ms
    64 bytes from 74.125.143.27: icmp_req=8 ttl=43 time=239 ms
    64 bytes from 74.125.143.27: icmp_req=9 ttl=43 time=197 ms
    64 bytes from 74.125.143.27: icmp_req=10 ttl=43 time=185 ms
    ^C
    --- 74.125.143.27 ping statistics ---
    10 packets transmitted, 10 received, 0% packet loss, time 9012ms
    rtt min/avg/max/mdev = 110.723/167.924/239.613/44.448 ms
    [email protected]:~$
    
    There. I've resent the email just in case, posted the log here, and usedd the sudo with those commands. Again, didn't see the need to install traceroute yet. If there's such a need - let me know.

    Awaiting your grace :D
    Did I say thank you yet?
    I just love it when people are helpful and patient ^_^
     
  18. Croydon

    Croydon ISPConfig Developer ISPConfig Developer

    Ok, thats odd...
    You can ping the google server but you can't connect.

    Ok, try this:
    Code:
    sudo telnet gmail-smtp-in.l.google.com 25
    If you get a timeout it seems either your server or the google servers or your server hoster blocks port 25.

    What about
    Code:
    sudo iptables -L -n
     
  19. Captain Gold

    Captain Gold New Member

    It took me a while.
    So:
    Code:
    [email protected]:~$ sudo telnet gmail-smtp-in.l.google.com 25
    [sudo] password for moishe:
    Trying 74.125.136.26...
    Trying 2a00:1450:4008:c01::1b...
    telnet: Unable to connect to remote host: Network is unreachable
    
    The cmd line on windows on another computer in my LAN can access it with no issues by the way:
    Code:
    C:\Users\Moishale>ping gmail-smtp-in.l.google.com
    Reply from 74.125.136.26: bytes=32 time=77ms TTL=44
    Reply from 74.125.136.26: bytes=32 time=74ms TTL=44
    Reply from 74.125.136.26: bytes=32 time=74ms TTL=44
    Reply from 74.125.136.26: bytes=32 time=79ms TTL=44
    
    Ping statistics for 74.125.136.26:
          Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
          Minimum = 74ms, Maximum = 79ms, Average = 76ms

    Code:
    [email protected]:~$ sudo iptables -L -n
    Chain INPUT (policy ACCEPT)
    target     prot opt source               destination
    
    Chain FORWARD (policy ACCEPT)
    target     prot opt source               destination
    
    Chain OUTPUT (policy ACCEPT)
    target     prot opt source               destination
    [email protected]:~$
    I am totally in unknown territory here. Any explanation as for what means what is blessed.
    Any ideas...?
     
    Last edited: Dec 4, 2013
  20. Captain Gold

    Captain Gold New Member

Share This Page