Plesk 12.x / Linux :: Can't Change SMTP Banner To Something Other Than Hostname
Jan 30, 2015
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.
OS = CentOS 6.5 (Final) Plesk version = 12.0.18 Update #7, last updated at July 11, 2014 12:46 PM
I have been trying to make my sites better suited to anti spam measures. The only warning I have left to work out is:
Warning - Reverse DNS does not match SMTP Banner
In the Plesk settings i do have the outgoing mail setting set to Send from domain IP addresses and use domain names in SMTP greeting - still I get the warning.
I am using Post fix. This is a 1and1 dedicated server and I am using custom name servers for this domain. I believe the smtp banner is matching the main ip and not the domain.
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).
after learning that server aliases are not available for PPA, we are needing to rename our service nodes. We have looked through the documentation, and did see the ppa.hostname command for the management node but there does not seem to be an equivalent for service nodes.
I have a client on a dedicated IP, today we needed to downgrade the web hosting plan. As the web hosting plan puts users on a default shared IP, this plan change also changed the dedicated IP to the shared one causing some propagation issues for a small period of time.
I have contacted WHMCS about this asking if they had a way of changing the clients plan but keeping the IP address intact as this could lead to some very undesirable outcomes. They explained that it is not their fault and to contact Parallels.
I know I can change the plan directly in Plesk however by initiating the plan change via WHMCS, everything is automated.
I enter one of my IPs or the hostname belonging to this IP, followed by the Plesk port, and I get redirected to the "main" hostname of the server, which was set in Plesk. But at this moment that hostname is used by another server (my old server) and so I'm redirected to the other server and cannot access Plesk on the new server.
I don't know why Plesk reacts like this, because it did not on the old server. Here the problem more detailed:
I'm just configuring my new server with Plesk 11. My old server uses Plesk 10. On my old server / in Plesk 10 I have the following scenario:
- I have several IPs (10) - Each IP is used for a different domain - Each IP has it's domain as the reverse entry (configured outside of the server/Plesk) - Each IP is set to "Dedicated" in Plesk - I set Plesk to listen only on one of these IPs (and different port) - Several domains are created in Plesk, but not a domain for my Plesk IP - The server's name is one of the domains (required for mails not being recognized as spam) - The hostname of the Plesk IP is one assigned by my provider (something like x-x-x-x.xyzservers.com) - Entering the IP of Plesk redirects to the "Plesk hostname" => Plesk can be accessed by using x-x-x-x.xyzservers.com:myport
And under Plesk 11 (here comes the problem):
- Still several IPs (but less: 4) - One IP should be used for Plesk, one for domain X, one for domain Y and the last one for the other domains - Reverse entries are x-x-x-x.xyzservers.com for Plesk IP, domain X/Y for two other IPs and the main domain for the last IP - Plesk IP and the two single domain IPs are configured as dedicated, the last one as shared - At this point I did not configure any domains in Plesk - Server's name is the same as my old server (the main domain) => Entering any IP with the Plesk port redirects to the servers hostname, e.g. my main domain, which is still on the old server. => Result: I cannot access Plesk!
Of course I could just change the hostname of the server via SSH (just have to find out how to do this), but why does Plesk react in another way now? Or is the problem that I cannot change Plesk to listen on only one IP?
the hostname is www.domain.com also in the serversettings of plesk. When we go to http://www.domain.com:8443 we become redirected to https://www:8443. The only way to connect to plesk is to use https the redirect from http doesnt work.
I have a server that I use to host my primary domain, and I have a cople Plesk servers, now I updated the hostnames of all the servers like
Code: s1.de.myserverplace.de
Now when the plesk server sends a mail it goes in spam always,
In the SPF records of the primary domain sits this
Code: myserverplace.de. IN TXT "v=spf1 a mx a:myserverplace.de a:s1.de.myserverplace.de ip4:148.251.100.157 ip4:144.76.163.46 ip6:2a01:4f8:201:81b8::60 ?all"
But when I actually send the mail in the headers of the received mail I get this.
Code: Received: from s1.de.myserverplace.de (s1.de.myserverplace.de. [144.76.163.46]) by mx.google.com with ESMTPS id p2si2158952wjy.73.2015.05.14.04.09.17 for <mymailtestacount@gmail.com> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Seems this started when upgrading to a version of 12. It was working a few days ago and only seems to affect mailing lists. I found a google Cached thread here where Igor was assisting some folks as late as Aug 4 and referenced this was "reported to development (PPP-10678 for your reference)" it seems the forums on Parallels changed or something because several Google links are not working and resulting in having to used cached results for the two links below.
I am able to disable SPF and the e-mails go through just fine however this was working with SPF enabled before a recent upgrade.
Page 1 [URL] ....
Page 2 [URL] ....
This is the error message displayed in /var/log/maillog Sep 24 01:38:35 controlpanel postfix/smtpd[3725]: connect from localhost[127.0.0.1] Sep 24 01:38:35 controlpanel postfix/smtpd[3725]: D565017C013E: client=localhost[127.0.0.1] Sep 24 01:38:35 controlpanel greylisting filter[3899]: Starting greylisting filter...
I have a few vps on different providers and I was shoring up my hostnames to make them more cohesive for the different servers.
I placed a request with a well-known, premium vps provider this morning at 9am EDT and am still awaiting them to complete the host name change. They came back immediately and said an admin would have to handle and then noting for hours. At approx 2p EDT, I asked for an update and I received a response at nearly 4pm EDT saying they were still waiting for their admin to get back.
Keep in mind this is a fully-managed, not cheap, vps with a very good rep here on wht.
Am I expecting too much?
I'd change it myself, but I'm unable to do so with virtuozzo.
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 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 (info@example.com) 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: info@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.
I want to add a new port for SMTP (1024) as a client's ISP block 25, 587 and 2525. I tried following this guide: [URL] ... but it doesn't work with Parallels Plesk Panel 11.5 ...
How to add an additional SMTP port to Qmail in Plesk 11.5?
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 postfix/smtp plesk12 centos7, I create mailbox add password. For example my domain is a.com from roundcube all work no problem.
My script isn't working look like this:
SMTP CONFIGURATION (LEAVE DEFAULT IF YOU USE mail() ) SMTP HOST smtp.a.com SMTP PORT 587 SMTP Secure tls SMTP Auth true SMTP USERNAME test@a.com SMTP PASSWORD my password
And the script dont send emails to user, say that Mailer Error: SMTP connect() failed. In dns settings I don't have smtpa.com host only have mail.a.com why from scripts don't send email to users?
Just got a strange problem on my plesk server. (11.0.9)
Qmail isn't working...
In Home>Tools & Settings>Services management SMTP "Server (QMail)" is stoppped.
When I try to start it, it say "Information: Please allow for some time for the service to start." but never starts...
In command line i try to restart it with "service qmail restart" and it says "OK" also if i run "service qmail status" it says "qmail-send (pid 2880) is running..."
but, it really doesn't work... queue is getting bigger and smtp isnt responding...!
actually i want to know is this sending this email by my smtp server?
Feb 23 14:49:36 nsxxxxxx /var/qmail/bin/relaylock[9836]: /var/qmail/bin/relaylock: mail from 187.5.81.179:51251 (187-5-81-179.bsaco701.dsl.brasiltelecom.net.br) Feb 23 14:49:37 nsxxxxxx qmail-queue-handlers[9838]: Handlers Filter before-queue for qmail started ... Feb 23 14:49:37 nsxxxxxx qmail-queue-handlers[9838]: from=Frederick59c@brasiltelecom.net.br Feb 23 14:49:37 nsxxxxxx qmail-queue-handlers[9838]: to=info@xxxxxxxxxx.be Feb 23 14:49:37 nsxxxxxx qmail-queue-handlers[9838]: 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?
