Page 1 of 3
Mail Server Connect Fail
Posted: Tue May 12, 2015 1:58 pm
by pweb
Cannot get connection to mail server(s) to enable e-mail alerts.
* admin->Mail Settings
* Input smtp settings
* "test settings" (button)
Error spawned: 220 mailpod.hostingplatform.com ESMTP
Have tried different mail servers for different accounts with all permutations of smtp settings.
Any suggestions?
TIA
Re: Mail Server Connect Fail
Posted: Tue May 12, 2015 2:36 pm
by jdalrymple
Start by nmapping the server:
Code: Select all
[root@localhost ~]# nmap -p 25 smtp.gmail.com
Starting Nmap 5.51 ( http://nmap.org ) at 2015-05-12 14:36 CDT
Nmap scan report for smtp.gmail.com (74.125.193.108)
Host is up (0.0070s latency).
Other addresses for smtp.gmail.com (not scanned): 74.125.193.109
rDNS record for 74.125.193.108: ig-in-f108.1e100.net
PORT STATE SERVICE
25/tcp open smtp
Nmap done: 1 IP address (1 host up) scanned in 0.13 seconds
Of course use your mail server, not Google's.
Re: Mail Server Connect Fail
Posted: Tue May 12, 2015 3:03 pm
by pweb
Thanks for the response.
I'm doing an eval to see whether Log Server will work for us and just loaded the .ova package.
It doesn't appear to have nmap present.
Thanks anyway.
Re: Mail Server Connect Fail
Posted: Tue May 12, 2015 3:34 pm
by jolson
Any chance you could install nmap?
Re: Mail Server Connect Fail
Posted: Tue May 12, 2015 3:55 pm
by pweb
Thanks for the reply.
I suspect the problem is elsewhere.
I have tried specification of the smtp server by IP address in lieu of FQDN and receive the same error.
Have also tried other security parameters and mail ports other than 25 with no success.
Any other ideas?
TIA
Re: Mail Server Connect Fail
Posted: Tue May 12, 2015 3:58 pm
by jdalrymple
pweb wrote:I have tried specification of the smtp server by IP address in lieu of FQDN and receive the same error.
Have also tried other security parameters and mail ports other than 25 with no success.
These steps will not resolve a situation where your firewall is preventing access to an SMTP port, which is a very common security practice in both internal and external networks to prevent spamming and virus/malware spread. Please install nmap using the command jolson provided then run it against your smtp server as I indicated. This is truly what needs to be done to troubleshoot your problem.
Re: Mail Server Connect Fail
Posted: Tue May 12, 2015 4:37 pm
by pweb
nmap installed as instructed.
server specified as instructed ... scan performed with results: 587/tcp open submission.
"Test button" spawns: 220 mailpod.hostingplatform.com ESMTP
Don't know whether this is significant but:
* Log server installed in VirtualBox
* VirtualBox installed on my Win 7 workstation
* Workstation also hosts my mail clients, which work o.k.
* Syslogs received ok in Log Server, and queries seem to function fine.
Any further ideas?
Re: Mail Server Connect Fail
Posted: Tue May 12, 2015 4:46 pm
by jdalrymple
A bit silly on my part - I apologize. If you were getting a 220 error it is not a network issue. Sorry for my haste. That said is this an Exchange server? We've had some interesting problems with Exchange, some resolved, some as of yet unresolved. The easy solution is to have your Exchange admins allow you to relay through port 25 from this box, but this is often not an option. If this isn't Exchange what type of box is it?
Re: Mail Server Connect Fail
Posted: Tue May 12, 2015 4:52 pm
by pweb
Two separate mail servers tried, neither of which is Exchange.
* Cloud server serviced by NetworkSolutions
* Self-owned BlueOnyx (linux) server at one of our branches
Re: Mail Server Connect Fail
Posted: Wed May 13, 2015 1:13 pm
by jolson
Let's try testing your smtp server:
yum install telnet
telnet smtp.test.server 587
At this point you should connect to the smtp server. Can you issue any commands to it? Try the following, one line at a time. Report the output from your smtp server here.
The above may not work exactly as described, as I don't know the nature of your SMTP server. The output should be useful enough though.