Smtp service (qmail) stops responding on port 25: # time telnet localhost 25 Trying 127.0.0.1... quit quit Connected to localhost.localdomain (127.0.0.1). Escape character is '^]'. quit quit Connection closed by foreign host.
real 4m10.629s user 0m0.000s sys 0m0.002s
After server restart or sometimes apache stop or ixnetd restart its responding for a some random time, and then again it stops to respond. Plesk panel show it as stopped but qmail itself running in memory, and does other its work, it just stops responding at port 25, or responds with a huge delay.
I've tried change it to postfix, reconfigured with mchk, repaired with repair.sh -r, disabled and uninstalled parallels antivirus, antispam, dnsbl, disabled firewall, disabled smtp lock. Checked apache, dns. Enabled submission port which works when 25 port doesnt, but i need working 25 port.
Nothing solves problem, its just stops responding after some random time. There is no errors on maillog.
I think this problem occured after recent plesk microupdate, because i didn't do anything to server configuration in last months.
This article says it might be dnsbl [URL] .... but it disabled(from plesk panel) on my server, maybe there is way to focefully kill any relation to dnsbl?
Plesk info: OS Red Hat Enterprise Linux Server 5.9 (Tikanga) Panel version 11.5.30 Update #50, last updated at May 18, 2015 05:21 PM The system is up-to-date; last checked at May 17, 2015 10:56 PM
update: xinetd restart is definitely brings smtp alive, but it goes off after random period of time (5min ~ couple hours)
After migrating our existing client base from legacy Plesk 9.x servers and Expand to PPA, clients phoned in with mail sending problems. These clients are using submission port 587 because their ISPs intercept port 25.
Existing client, Outlook error message:
"None of the authentication methods supported by this client are supported by your server"
Testing with Thunderbird, error message:
"An error occurred while sending mail. The mail server responded: 5.7.0 Must issue a STARTTLS command first. Please verify that your email address is correct in your Mail preferences and try again."
It seems a "fresh" PPA requires STARTTLS on e-mail clients. It is furthermore confirmed that Thunderbird detects the e-mail server settings as dependant on TLS.
The problem is that TLS doesn't seem to work properly by default.
In order to preserve our existing customer base, we follow: [URL] ....
Bottom line, in your /etc/postfix/master.cf, change the line that says "submission" from this:
Currently I am using Linux + cPAnel and using the port 25 for email sevrer. Currently we facing 1 problem is, some user's ISP is not support port. May I know how can I add additional port into server and allow users to send mail by different port?
Is anyone successfully using cPanel with smtp port 587 and have a working email account?
After deciding that Plesk wasn't for me due to the lack of reference material in this and other forums, I had my hosting company, ServInt, delete my old vps and install a new one with cPanel.
Everything went fine until I configured my email. Just like with Plesk, I cannot access the smtp server via Outlook. I can ping it successfully, but it either terminates the connection or doesn't recognize the correct user name and password. With Plesk, it was a simple matter of enabling the use of port 587.
Not so with cPanel, at least for me. Even though the Exim service is enabled and another instance is enabled on port 587, I still can't connect. Thought it might be CFS, which is new to me with this install, so made sure it was disabled. Opened up a ticket with ServInt and even their techs can't get it functioning, so _they've_ opened up a ticket with cPanel.
Hence the title of this post, I can't beleive that I'm the only one whose had this problem before because blocking port 587 has been done by BellSouth/AT&T for many years now.
Nothing like having your company email down for over 6 hours to keep you up at night.
I am using Plesk Panel 11.0.9 (latest updates applied) on CentOS 6.4. at Strato. Unfortunately I can not send email from outside of the server (thunderbird). As I am not familiar wwith mail server configuration at all I would expect that plesk panel does that for me (right?)
* I can send emails via web mail. * I can receive emails in thunderbird, but sending runs into a timeout. * The plesk firewall configuration does have a rule for smtp (but I don't see for which port), so I would expect it is not a firewall issue * I would like to send with some security (starttls and encrypted password), but sending does currently also not work with any combination of (non-)security setting.
My domain has been migrated from another provider, I added it myself via Plesk panel later. The only mail-related change I did without plesk panel was to copy the mailboxes from my old server to /var/qmail/mailnames. But this should not effect sending email...
I need changing the nginx port. I've followed various threads and have created a custom nginxDomainVirtualHost.php file at: /usr/local/psa/admin/conf/templates/custom/domain, while the website indeed moves to the port I have set, a second nginx thread starts at port 80 and takes over in it's place.
I need to put varnish at port 80 and cannot do so until all services relinquish control on port 80.
Followed clues here: [URL] ....
some here: [URL] .....
Turn's out to be able to change the nginx port to a non-standard port you need to edit 6 files
I am having trouble with setting up an email account to set up the email I go to Mail > Create Email Address > and enter email address (firstname.lastname@example.org) and check the "access to control panel" and create a password and also check "mailbox" .
But in the email client, when I go to use SMTP and I enter the following info:
- SMTP Server: example.com - username: email@example.com - password: password I created above - port 25 - user TLS
I get this error: Your other email provider is responding too slowly. Please try again later, or contact the administrator of your other domain for further information.
Now with Plesk 12 (and I suppose all previous versions) we can't change the SMTP banner to something other than the hostname.But If server host different IPs with different domains,only the primary IP do not have problems for email delivability all other domains are marked spam.This is a critical issue for email deliverability. Very critical issue that should be solved asap.the only solution that we found with our systemists is to remove Plesk, but sure it's not what I would like to do.
We are seeing intermittent slow responses from SMTP on a RHEL6 server running Qmail on Plesk 11.5. The response is being measured from a remote Zabbix server.
The response time seems to be slow (>10s) for a period of 2-3 minutes and then returns to normal (<1s). All other services continue to be ok during the period of slowness.
The server_args line in /etc/xinetd.d/smtp_psa already contains "-Rt0" and all the DNS servers in /etc/resolv.conf are resolving properly.
From looking at the maillog file the server was receiving about 35 SMTP connections a minute at the time of the slowdown. We have the server configured to use 2 x RBL's.
I wonder if we are hitting a limit on the maximum amount of SMTP connections. The file /var/qmail/control/concurrencyincoming does not exist so, according to the Qmail manual, there shouldn't be a limit on the number of incoming SMTP connections.
I use PLESK 11 on one of my servers, and use NS.mydomain & NS1.mydomain, everything works fine, DNS Zones are OK, reverse DNS is OK...
Except on MXTOOLBOX this :
SMTP Valid Hostname > Reverse DNS is not a valid Hostname SMTP Reverse > DNS Mismatch OK - 195.154.XXX.XXX resolves to mydomain.eu SMTP Banner Check > OK - Reverse DNS matches SMTP Banner
Tried so many searches on Google, but no response and always 3 same pages from MXTOOLBOX.
I migrated IP of this server in datacenter, because they ask us to do it, so in /etc/hosts for example I found old IP, I changed it, restart network interface, but always the same thing... postfix too (changed IP and restart).
actually i want to know is this sending this email by my smtp server?
Feb 23 14:49:36 nsxxxxxx /var/qmail/bin/relaylock: /var/qmail/bin/relaylock: mail from 22.214.171.124:51251 (187-5-81-179.bsaco701.dsl.brasiltelecom.net.br) Feb 23 14:49:37 nsxxxxxx qmail-queue-handlers: Handlers Filter before-queue for qmail started ... Feb 23 14:49:37 nsxxxxxx qmail-queue-handlers: from=Frederick59c@brasiltelecom.net.br Feb 23 14:49:37 nsxxxxxx qmail-queue-handlers: firstname.lastname@example.org Feb 23 14:49:37 nsxxxxxx qmail-queue-handlers: handlers_stderr: SKIP
After upgrading to Plesk 12, I switched on email sending limit to 50 emails per hour per account and also changed mail config to start using domain names in SMTP and less than 12 hours later became blacklisted by CBL - hotmail and live rely on this blacklist - ; the argument was we were sending bots and malware. This server has been under ASL since over a year now and we are positive its clean; still we did a full scan and nothing came up and none of the mail accounts were even close to sending 50 emails per hour. Being sure we were not sending spam nor malware contacted CBL and got whitelisted ..... for less than 24 hours. This happened three days in a row until we switched back to the previous mail settings where domains are not used in SMTP greeting and since then, we haven't had any trouble with CBL. how can we prevent being blacklisted while using domain names in SMTP greetings?
i'm running 12.0.18#34 on PCS dedicated server. i recently discovered that some of the default jails on fail2ban that is shipped with Plesk 12 were not working correctly. Let me explain what i mean. For instance, the plesk-panel jail. The logs were parsed correctly, the command was successfully appended in iptables list, the fail2ban log was updated. Still, the intruder was not blocked. I kept reading "already banned" on the fail2ban.log but actually there was no blocking.
After some checks, i found out that fail2ban default configuration states SSH as default blocking port. that means, the block was working but only for ssh hits. thus the plesk-panel admin page hits were passing through.
since i added port=http,https on jail.local > plesk-panel and did it a restart on fail2ban service, only then did it start to actually block incoming hits.
I think this should be verified by programmers group and maybe include a fix in some future minor update.