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.
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:
I have a reseller account that uses WHM/cPanel. So of course, SquirrelMail and Horde are already installed. I like to check my email at work, but unfortunatley, my employer blocks connections for say mydomain.com:2095.
Is there a way around this? I'm too much of a noob to try and install Horde again, bypassing the cPanel. I use Horde as the example because I need a good calendar and address book.
I have a contact form using .php to forward the contents of the form to my email-ad, but turns out, that something i cant do with my free hosting plan.
i was wondering if anyone knew any services (free) that allow mail forwarding where i can host my .php script together with all associated files and simply link to them from my site?
that would be great! thanks!
(not sure where exactly this post belongs, but it's got something to do with my hosting so im posting it here. if any mods think it should be somewhere else, just move it to where you feel it is appropriate )
if i try to telnet to yahoo's mail server, i get this:
[root: #] telnet mx1.mail.yahoo.com 25 Trying 220.127.116.11... telnet: connect to address 18.104.22.168: Connection timed out Trying 22.214.171.124... telnet: connect to address 126.96.36.199: No route to host Trying 188.8.131.52... telnet: connect to address 184.108.40.206: No route to host Trying 220.127.116.11... telnet: connect to address 18.104.22.168: No route to host
but it works from one of my other hosted servers. this keeps mail building up in my queue as it cannot send mail out cause the connection times out.
I can telnet locally to send myself email. This is my own dedicated server.
i have no idea whats up - default policy is ACCEPT in the OUTPUT chain of iptables.
for a SMTP server / hints at how it might be done to accomodate the following :
One single email will be sent. If it doesn't get sent on the first try by one server, another server at another location will attempt the connection and will send out the email then.
Is there a prebuilt solution that anyone knows that will help with these things ? If not, do you know of any ways that this might be possible to be done - even if you don't know the exact details of how it should be done - any help in finding out something like this would help .
Note : Linux / Windows / FreeBSD / Solaris is fine. So whatever OS it is, it's fine by me.
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 (email@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: firstname.lastname@example.org - 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.
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: email@example.com Feb 23 14:49:37 nsxxxxxx qmail-queue-handlers: handlers_stderr: SKIP
i have this weird problem of emails not gettign delivered and i am hosting with theplanet. Every email is sitting on the queue and not delivered.
i checked with dnsreport and it says
Timed out [Last data sent: [Did not connect]]
and my exim_mainlog shows
R=dk_lookuphost defer (-1): host lookup did not complete 2008-06-03 04:49:59 SMTP command timeout on connection
i have restarted exim, checked firewall and still i am unable to fix my problem!
i again checked with dnsreport and my nameservers are failing
NS FAIL NS A timeout occurred getting the NS records from your nameservers! None of your nameservers responded fast enough. They are probably down or unreachable. I can't continue since your nameservers aren't responding. If you have a Watchguard Firebox,
it's due to a bug in their DNS Proxy, which must be disabled (31 Jul 2006 UPDATE: several years after being informed of this, there is a rumor that there is a fix that allows the Watchguard DNS proxy to work).
We have a few users that use SSL email and we decided to purchase a cheap single-root SSL cert over at namecheap for the host name so that it would end the "self-signed cert" whining.
We got the cert installed and it works great for WHM/cPanel and also works for SSL over IMAP and POP3, but the very first email anyone sends (SMTP) per day gives this warning (Outlook Express):
The server you are connected to is using a security certificate that could not be verified. A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
It seems obvious that the cert used by the SMTP system is not the new one we installed.
We used WHM's SSL/TLS -> Change Server Certificates link to install the cert.