Cannot connect to SMTP server (Outgoing Mail)

[dahund]

Hey hope someone can help, i just started using parallel plesk i have configured using basic firewall etc. everything works fine, but after reboot i cant send mails (SMTP) i get the error "connect error 10060" but i can send mails via the webmail panel?

i also tried telnet to server ip port 25 with no luck it fails? in the firewall setting is standard an have worked up until reboot. can anyone help?

/A

 

[dahund]

changed port

using this article i changed port to 2525

http://kb.parallels.com/en/837

i can now telnet and get a reply "telnet mypress.dk 2525" but iam i have also changed the port in mail client but now it wont recognize my password...

any ideas ?

 

[dahund]

mail password that is! for outgoing mail.

 

[dahund]

Fixed it dont follow the above guide

Do this instead login to server (linux) run

"sudo vim /etc/postfix/master.cf"

press "i" insert under this line: smtp "inet n - - - - smtpd -o" so it looks like this:

smtp inet n - - - - smtpd -o
port inet n - - - - smtpd -o

press "esc" write ":wq"

restart postfix via plesk panel..

 

[Eric Pretorious]

Many Internet service providers and enterprise or institutional networks restrict the ability to connect to remote MTAs on port 25. The accessibility of a Mail Submission Agent on port 587 enables nomadic users to continue to send mail via their preferred submission servers even from within others' networks.

First: Traditionally, access to your MTA (i.e., TCP:25) is blocked by almost all ISP's so you'll need to use the MSA (i.e., TCP:587) or use SMTPS (i.e., TCP:465).

SMTPS refers to a method for securing SMTP with transport layer security. It is intended to provide authentication of the communication partners, as well as data integrity and confidentiality.

SMTPS is not a proprietary protocol and not an extension of SMTP. It is just a way to secure SMTP at the transport layer.

Second: To test your MTA's functionality, login to your sever (e.g., using SSH) and test localhost:25 (e.g., using telnet).

Third: Verify that your MSA supports ESMTP, SMTP Authentication and SMTPS:

The main identification feature is for ESMTP clients to open a transmission with the command EHLO (Extended HELLO), rather than HELO (Hello, the original RFC 821 standard). A server will respond with success (code 250), failure (code 550) or error (code 500, 501, 502, 504, or 421), depending on its configuration. An ESMTP server would return the code 250 OK in a multi-line reply with its domain and a list of keywords to indicate supported extensions. A RFC 821 compliant server would return error code 500, allowing ESMTP clients to try either HELO or QUIT.

SMTP Authentication, often abbreviated SMTP AUTH, is an extension of the Simple Mail Transfer Protocol whereby an SMTP client may log in, using an authentication mechanism chosen among those supported by the SMTP server. The authentication extension is mandatory for submission servers.

[root@www ~]# telnet localhost 25
Trying ::1...
Connected to localhost.
Escape character is '^]'.
220 www.example.com ESMTP Postfix
EHLO example.com
250-www.example.com
250-PIPELINING
250-SIZE 10240000
250-ETRN
250-[B][COLOR="Green"]STARTTLS[/COLOR][/B]
250-[B][COLOR="Green"]AUTH[/COLOR][/B] CRAM-MD5 DIGEST-MD5 [COLOR="DarkOrange"]PLAIN LOGIN[/COLOR]
250-XFORWARD NAME ADDR PROTO HELO SOURCE PORT IDENT
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 DSN
quit
221 2.0.0 Bye
Connection closed by foreign host.

Fourth: NEVER send your e-mail password over the network unencrypted. It can easily be intercepted if, for example, by network peers if you're using unencrypted Wi-Fi (as is common in cafes, libraries, and other retail hotspots). (i.e., Check your MUA's account settings to verify that all communications are sent using SSL or TLS.)

HTH,
Eric Pretorious
Truckee, CA

 

[dahund]

Thx for reply

Hope its not to much but can you recommend a guide to securing postfix using SSL?

/A

 

[Eric Pretorious]

Hope its not to much but can you recommend a guide to securing postfix using SSL?

AFAIK, Postfix is secured by default to use the SSL certificate configured for the subscription. Use your MUA to verify this. (By default, PP uses the self-signed Parallels certificate. Your MUA will complain about this when you first configure your MUA's account settings.)

 

[dahund]

Yes i noticed in the /etc/postfix/main.cf file, but Outlook express wont recognize it, when i check it it fails with no error except that it cant connect to server?

Maybe it could be a certificate problem, iam using the standard self signed one.. but shouldnt it just complain that its selfsigned?