• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Outgoing mail.domain.com servers not working

T

tungsten

Guest
Hi all,

Odd problem here and I'm at the end of my rope trying to sort it out.

Currently, all outgoing mail that attempts to send through any mail.domain.com (or IP address) on our CentOS 4.4 - Plesk 8.2 server is not working.

My settings in MAIL under Server are as follows:

Relaying is set to:
[*] Authorization required:
[*] Pop lock time 20 min
[*] SMTP

Antivirus is off.
SPF spam protection is off.
No DNS blackhole lists set.
Use only full account names is set.
There are no firewalls on.
There are no IPTABLE rules blocking any of my IPs.
At present I am not running OSSEC or any other intrusion protection while I try and sort this out.

I have doubled checked my IP address(es) and they resolve when checking # host IP without issue.

Strangely enough, picking mail up from the server is working like a charm via 3rd party mail clients. Additionally when you login via webmail, sending directly from your account is not a problem either.

I'm going to try a reboot tonight, but basically, after that, I'm down to zero ideas. Any help would be very much appreciated.

Anyone have this same problem? Anyone have a similar issue? How did you resolve it?
 
To follow up, after a full reboot last night, my outbound mail.domain.com servers are working again.

I'm still pretty clueless as to what broke during the 8.1.1 > 8.2 upgrade ... and there is nothing in the log files showing connections are being refused. It just stopped working. Seems to be back in order now.

If I find more details, I post them up in case anyone else runs into the same problem.
 
Hm... after 12 hours or so, my mail.domain.com outgoing servers have stopped responding again. Lovely. Anyone experiencing this behavior as well?
 
I am having exactly the same problem.

Qmail appears to be running. I can receive mail to my account using Thunderbird and can send and receive mail using webmail but when I try to reply to a mail using Thunderbird it's as if the mail server can't be found.

I have checked and rechecked all the login information, I've rebooted, checked all the DNS settings but with no luck.

Any ideas please?
 
Sorry for the double post but I thought the following info from DNS Stuff might be useful.

mail.mydomain.com claims to be non-existent host server1.myserver.com:
220 server1.myserver.com ESMTP
 
It may sound silly, but did you set your Outlook (or Firebird) so that the SMTP server requires authentication? It's under 'More Settings' -> 'Outgoing Mail.'

If that's not it, post your DNS settings here.
 
Hola Pheonix,

Yeah. We are testing this on both PC (winXP - Outlook, Outlook Express and Thunderbird) and OS X (Mail and Thunderbird). We have tried with authentication and without for outgoing.

DNS settings for one of the domains in question:

75.126.162.95 / 24 PTR doowahdesign.com.
doowahdesign.com. NS ns.doowahdesign.com.
doowahdesign.com. A 75.126.162.95
doowahdesign.com. MX (10) mail.doowahdesign.com.
ftp.doowahdesign.com. CNAME doowahdesign.com.
mail.doowahdesign.com. A 75.126.162.95
ns.doowahdesign.com. A 75.126.162.95
webmail.doowahdesign.com. A 75.126.162.95
www.doowahdesign.com. CNAME doowahdesign.com.

Thanks for the reply.
 
I was able to ping your mail server and it responded properly (kind of) when I tried to telnet mail.doowahdesign.com 25 I got a 220 answer - but from a different domain. It answered as www.visuallizard2.net. When I ping that (www.visuallizard2.net) I get an IP number from the same ISP - SoftLayer Technologies Inc.

I think you may need to contact them about this.
 
Thanks again Pheonix. I've contacted them and will post any relevant solution(s) up here.
 
I had the same issue and I ran the following which seemed to do the trick.

/usr/local/psa/admin/sbin/websrvmng -u --vhost-name=domain.tld

Just replace domain.tld with your domain name.
 
QMAIL Pop's Not Able to Send HELP !!!!!

Very frustrated. It's plain to see this is some sort of; not my cause issue. I need this working ASAP. Has anyone come up with a simple fix? Everything was up2date/fine until the end of the month. This is not the 1st time I have gone through this.

Thanks
 
I too am having a similar problem.

Just upgraded to 8.2 and no email client can download any email. It seems that the mail.domain.com is the problem.

It connects, hangs at authorising... then gets the following error from Outlook Express

+++++++++++++++++++++++++++++++++++++++++++++++++++++++

There was a problem logging onto your mail server. Your Password was rejected. Account: 'mail.domain.com', Server: 'mail.domain.com', Protocol: POP3, Server Response: '-ERR Login failed.', Port: 110, Secure(SSL): No, Server Error: 0x800CCC90, Error Number: 0x800CCC92

+++++++++++++++++++++++++++++++++++++++++++++++++++++++
 
OK guys... very easy fix.

Go to Server / Mail and use the following

"Use of short (webmaster) and full (webmaster@domain.com) POP3/IMAP mail account names is allowed"


Solves this issue!!
 
SAME PROBLEM HERE

Actually I had the same issue. If POP3 Lock TIME IS ON, you will have problems using SMTP Authentication (e.g. with a Password).

If you login to POP3 and have pop3 lock time on, you become whitelisted in a sense (authenticated) so your IP can send mail for the period of lock that you have it set for. Then, if you try to use SMTP during this period, QMAIL will show this error:

503 You are already authenticated.

This error results in a 5.5.0 which email clients think means something like a relay restricted error and you'll have issues.

Turn off POP3 lock time and force everyone to use SMTP authentication. It will solve all your problems.
 
Back
Top