Hi guys. I'm having problems receiving emails they simply don't arrive. The sender does not get any errors or mail returned. I've tried to send an email to myself using the same domain and that sends but not returns. I'm using Roundcube and I have tried Outlook 2016 set up as IMAP I'm behind a router and have checked the firewall and port forwarding is ok. I've checked the firewall in ispconfig and the ports are open and forwarding as well. DNS checks out and as far as I can tell the mx records and cnames are all fine. I've spent a few days looking for a solution in the hope that I didn't need to bother anyone... but now I've drawn a blank. If anyone can help I'd be delighted. I've attached the mail log and also the master.cf in the hope that it helps.
Just tested the mail server and here's the log. It seems to be working: Code: Resolving hostname... Connecting... Connection: opening to mail.recom.co.uk:25, timeout=300, options=array ( ) Connection: opened SERVER -> CLIENT: 220 recom.co.uk ESMTP Postfix (Ubuntu) CLIENT -> SERVER: EHLO tools.wormly.com SERVER -> CLIENT: 250-recom.co.uk 250-PIPELINING 250-SIZE 20971520 250-VRFY 250-ETRN 250-STARTTLS 250-AUTH PLAIN LOGIN 250-AUTH=PLAIN LOGIN 250-ENHANCEDSTATUSCODES 250-8BITMIME 250 DSN CLIENT -> SERVER: STARTTLS SERVER -> CLIENT: 220 2.0.0 Ready to start TLS CLIENT -> SERVER: EHLO tools.wormly.com SERVER -> CLIENT: 250-recom.co.uk 250-PIPELINING 250-SIZE 20971520 250-VRFY 250-ETRN 250-AUTH PLAIN LOGIN 250-AUTH=PLAIN LOGIN 250-ENHANCEDSTATUSCODES 250-8BITMIME 250 DSN CLIENT -> SERVER: MAIL FROM: SERVER -> CLIENT: 250 2.1.0 Ok CLIENT -> SERVER: RCPT TO: SERVER -> CLIENT: 250 2.1.5 Ok CLIENT -> SERVER: DATA SERVER -> CLIENT: 354 End data with . CLIENT -> SERVER: Date: Wed, 20 Sep 2017 20:39:23 +0000 CLIENT -> SERVER: To: [email protected] CLIENT -> SERVER: From: Wormly SMTP Test CLIENT -> SERVER: Subject: Wormly SMTP Test Message CLIENT -> SERVER: Message-ID: <[email protected]> CLIENT -> SERVER: MIME-Version: 1.0 CLIENT -> SERVER: Content-Type: text/plain; charset=iso-8859-1 CLIENT -> SERVER: CLIENT -> SERVER: This message was sent using the Wormly SMTP testing tool by this user: CLIENT -> SERVER: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.90 Safari/537.36 OPR/47.0.2631.80 CLIENT -> SERVER: 82.69.15.167 CLIENT -> SERVER: CLIENT -> SERVER: . SERVER -> CLIENT: 250 2.0.0 Ok: queued as 54C351E02A26 CLIENT -> SERVER: QUIT SERVER -> CLIENT: 221 2.0.0 Bye Connection: closed Message completed successfully.
That log file didn't include anything for mail delivery attempts/success, only your imap logins and a localhost connection (which I assume is ispconfig checking the service) - try sending yourself an email from an outside source and see what shows up; if nothing, you're probably not getting a connection at all, but if your server is answering as you show.... maybe check your MX records and see if mail is delivering somewhere else? For a small log snippet like that, please paste as text, not a document format, it makes it easier for everyone and less chance of bad things (eg. virus type in the zip or odt file).
Code: #dig mail.recom.co.uk ;; ANSWER SECTION: mail.recom.co.uk. 3600 IN A 82.69.15.167 #dig mx recom.co.uk ;; ANSWER SECTION: recom.co.uk. 3600 IN MX 10 mail.recom.co.uk. DNS seems to be fine if the 82.69.15.167 is your ip address (check by visiting http://myip.sh or http://canihazip.com/s) or from mailmachine execute: curl http://canihazip.com/s and see if ip's match. I do think that the mail.log should show incomming mails? Code: Sep 21 07:06:14 panel amavis[27242]: (27242-17) Passed CLEAN {RelayedInternal}, LOCAL [127.0.0.1] <[email protected]> -> <[email protected]>, Message-ID: <[email protected]>, mail_id: 4QTNR0-52KkK, Hits: -0.001, size: 574, queued_as: 250F1BD9E0, dkim_new=default:tsictdiensten.nl, 235 ms Sep 21 07:06:14 panel postfix/smtp[4906]: DA5CDBD9DF: to=<[email protected]>, relay=127.0.0.1[127.0.0.1]:10024, delay=0.3, delays=0.04/0.02/0/0.24, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 250F1BD9E0) Sep 21 07:06:14 panel postfix/qmgr[2292]: DA5CDBD9DF: removed Sep 21 07:06:14 panel dovecot: lda([email protected]): sieve: msgid=<[email protected]>: stored mail into mailbox 'INBOX' Sep 21 07:06:14 panel postfix/pipe[4921]: 250F1BD9E0: to=<[email protected]>, relay=dovecot, delay=0.07, delays=0.01/0.02/0/0.04, dsn=2.0.0, status=sent (delivered via dovecot service) Did you check with your provider if you are allowed to host your own mail server at home?
Thanks for the replies. The mail log that I posted already should have shown attempts of me sending mail to mail.recom.co.uk by a third party domain and also attempts to send mail to itself. The log doesn't seem to show any incoming information. According to Zen (that's the isp I'm using) they don't block ports The ip address shown from the dig report is the correct ip. I'm wondering if this is a firewall issue perhaps. I'm running a NAT router and have configured the port 25,110,143 to port forward and told to listen on the ip 82.69.15.167
Code: TCP ports 20 - FTP Data 21 - FTP Command 22 - SSH 25 - Email 53 - DNS 80 - HTTP (Webserver) 110 - POP3 (Email) 143 -Imap (Email) 443 - HTTPS (Secure web server) 993 - IMAPS (Secure Imap) 995 - POP3S (Secure POP3) 3306 - MySQL Database server 8080 - ISPConfig web interface 8081- ISPConfig apps vhost UDP ports 53 - DNS 3306 - MySQL https://www.faqforge.com/linux/whic...g-3-server-and-shall-be-open-in-the-firewall/
Thanks Tuumke I've checked and I have all these set to open. I've also used an online service to try and tunnel through the ports to see if they are open, and they seem to be. I've just had a thought though. I changed the internal network ip on the server after installing ISPConfig and updated the information in the Ispconfig>system>Server ip address. Rebooted the server (as it wasn't online at the time) but other than that I'm a little puzzled.
Still lost on this one... Anyone any suggestion please. Can Postfix be re-installed to make sure I've not somehow messed it up during installation?
Login to webmail on your server and send an email to the same address that you are logged in with webmail, when the mail arrives after a few seconds in the webmail account, then you postfix setup is fine. Then you should run the test script and post the result: https://www.howtoforge.com/community/threads/please-read-before-posting.58408/
Thank you for your suggestion. I just tried to send a mail to the mail address I'm sending from and used Roundcube and didn't get the mail back. It went just fine and then never seen again. Does that suggest that Postfix is at fault?
Please redo the test and then post the lines that got added in mail.log (at the end of the log) from this test.
Ok I sent mail to the same account as I was sending from with Roundcube. Here's the last few lines from /var/log/mail.log Code: Sep 22 14:09:54 recom dovecot: imap([email protected]): Logged out in=50 out=484 Sep 22 14:10:01 recom dovecot: imap-login: Login: user=<[email protected]>, method=PLAIN, rip=82.69.15.167, lip=192.168.178.34, mpid$ Sep 22 14:10:01 recom dovecot: imap([email protected]): Logged out in=78 out=1152 Sep 22 14:10:01 recom postfix/smtpd[18718]: connect from localhost[::1] Sep 22 14:10:01 recom postfix/smtpd[18718]: lost connection after CONNECT from localhost[::1] Sep 22 14:10:01 recom postfix/smtpd[18718]: disconnect from localhost[::1] commands=0/0 Sep 22 14:10:01 recom dovecot: imap-login: Disconnected (disconnected before auth was ready, waited 0 secs): user=<>, rip=::1, lip=:$ Sep 22 14:10:01 recom dovecot: pop3-login: Disconnected (no auth attempts in 0 secs): user=<>, rip=::1, lip=::1, secured, session=<E$ Sep 22 14:10:09 recom dovecot: imap([email protected]): Logged out in=715 out=5486 Sep 22 14:10:24 recom postfix/smtpd[18718]: warning: hostname thedirect-mailer.net does not resolve to address 94.102.51.31: Name or$ Sep 22 14:10:24 recom postfix/smtpd[18718]: connect from unknown[94.102.51.31] Sep 22 14:10:27 recom postfix/smtpd[18718]: warning: unknown[94.102.51.31]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Sep 22 14:10:27 recom postfix/smtpd[18718]: disconnect from unknown[94.102.51.31] ehlo=1 auth=0/1 rset=1 quit=1 commands=3/4 Sep 22 14:10:54 recom dovecot: imap-login: Login: user=<[email protected]>, method=PLAIN, rip=::1, lip=::1, mpid=18888, secured, ses$ Sep 22 14:10:54 recom dovecot: imap([email protected]): Logged out in=50 out=484 Sep 22 14:11:10 recom dovecot: imap-login: Login: user=<[email protected]>, method=PLAIN, rip=82.69.15.167, lip=192.168.178.34, mpid$ Sep 22 14:11:54 recom dovecot: imap-login: Login: user=<[email protected]>, method=PLAIN, rip=::1, lip=::1, mpid=18953, secured, ses$ Sep 22 14:11:54 recom dovecot: imap([email protected]): Logged out in=50 out=484 Sep 22 14:12:00 recom dovecot: imap([email protected]): Logged out in=590 out=4857 Sep 22 14:12:25 recom dovecot: imap-login: Login: user=<[email protected]>, method=PLAIN, rip=82.69.15.167, lip=192.168.178.34, mpid$ Sep 22 14:12:54 recom dovecot: imap-login: Login: user=<[email protected]>, method=PLAIN, rip=::1, lip=::1, mpid=19018, secured, ses$ Sep 22 14:12:54 recom dovecot: imap([email protected]): Logged out in=50 out=484 Sep 22 14:12:57 recom dovecot: imap([email protected]): Logged out in=590 out=4840
OK I think I've found the problem. Although DNS and MX records were set up correctly at the server and the glue records were set up correctly at the register, I had two issues. One receiving email ans the other was problematic fpt authorisation. Using third parties I've check the server and found no obvious problem, until now that is. Early in the hours I decided the only way to solve this is to build the system again and it was then I discovered that the router was broadcasting a dns name. This router isn't suppose to have this feature,so I wasn't looking for it. In fact it seems to be quite a bit of scripting in order to prevent the dns at the router. The router is a FritzBox 3490 which is the cut back version of the 7490. The 7490 version has VoIP and many services that require dns, so I guess the cut back version I have has some of these services in the operating system of the router all be it redundant. So the router was broadcasting recom.fritz.box and that would cause no end of problems... in fact I'm surprised it worked at all
