• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved Fresh Plesk installation not sending mail

kevin agodev

New Pleskian
Hi everyone,

I have an issue with my fresh plesk installation with Debian 8.
All my mails are not sending from my domains. I think that I have a misconfiguration of postfix service but I'm not sure.

I can receive emails and send to local mail adresses but when I try to send mail to external mails nothing is sent and all emails are stored in Queue. The logfile display a lot of "Connection time out" messages.

Thank you for your help!

Here is my postfix main.cf file :

# See /usr/share/postfix/main.cf.dist for a commented, more complete version


# Debian specific: Specifying a file name will cause the first
# line of that file to be used as the name. The Debian default
# is /etc/mailname.
#myorigin = /etc/mailname

smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
biff = no

# appending .domain is the MUA's job.
append_dot_mydomain = no

# Uncomment the next line to generate "delayed mail" warnings
#delay_warning_time = 4h

readme_directory = no

# TLS parameters
smtpd_tls_cert_file = /etc/postfix/postfix.pem
smtpd_tls_key_file = $smtpd_tls_cert_file
smtpd_use_tls = yes
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache

# See /usr/share/doc/postfix/TLS_README.gz in the postfix-doc package for
# information on enabling SSL in the smtp client.

smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination
myhostname = server1.cms-apps.com
alias_maps = hash:/etc/aliases, hash:/var/spool/postfix/plesk/aliases
alias_database = hash:/etc/aliases
myorigin = /etc/mailname
mydestination = localhost.com, localhost, localhost.localdomain
relayhost =
mynetworks =
mailbox_size_limit = 0
recipient_delimiter = +
inet_interfaces = all
inet_protocols = all
virtual_mailbox_domains = $virtual_mailbox_maps, hash:/var/spool/postfix/plesk/virtual_domains
virtual_alias_maps = $virtual_maps, hash:/var/spool/postfix/plesk/virtual
virtual_mailbox_maps = , hash:/var/spool/postfix/plesk/vmailbox
transport_maps = , hash:/var/spool/postfix/plesk/transport
smtpd_tls_security_level = may
smtp_tls_security_level = may
smtp_use_tls = no
smtpd_timeout = 3600s
smtpd_proxy_timeout = 3600s
disable_vrfy_command = yes
smtpd_sender_restrictions = check_sender_access hash:/var/spool/postfix/plesk/blacklists, permit_sasl_authenticated
smtpd_client_restrictions = permit_mynetworks, permit_sasl_authenticated
smtp_send_xforward_command = yes
smtpd_authorized_xforward_hosts = 127.0.0.0/8 [::1]/128
smtpd_sasl_auth_enable = yes
smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination
virtual_mailbox_base = /var/qmail/mailnames
virtual_uid_maps = static:30
virtual_gid_maps = static:31
smtpd_milters = , inet:127.0.0.1:12768
sender_dependent_default_transport_maps = hash:/var/spool/postfix/plesk/sdd_transport_maps
virtual_transport = plesk_virtual
plesk_virtual_destination_recipient_limit = 1
mailman_destination_recipient_limit = 1
virtual_mailbox_limit = 0
smtpd_tls_ciphers = medium
smtpd_tls_mandatory_ciphers = medium
tls_medium_cipherlist = HIGH:!aNULL:!MD5
smtpd_tls_mandatory_protocols = TLSv1 TLSv1.1 TLSv1.2
smtpd_tls_protocols = TLSv1 TLSv1.1 TLSv1.2
message_size_limit = 10240000
 

Attachments

  • main.cf.txt
    2.7 KB · Views: 1
  • master.cf.txt
    7 KB · Views: 0
Hi,

Could you telnet to outside server to 25/tcp port? Did you check firewall settings? Is it cloud environment or not?
 
Hi,
Thank you for your interest.

telnet gmail-smtp-in.l.google.com 25 >> KO
telnet gmail-smtp-in.l.google.com 587 >> KO
telnet smtp.google.com 25 >> KO
but
telnet smtp.google.com 587 >> Success

Yes it's a cloud VPS. My ISP is 1and1.
I'm root on the system, the ISP support told me that ports are ok. I also added the plesk firewall module and the outgoing policy is allow for all (see screenshot).

I suppose that I perhaps need a SSL or something like this to get it work?

Thank you
 

Attachments

  • plesk_firewall_rules.jpg
    plesk_firewall_rules.jpg
    462.8 KB · Views: 15
As I found out recently 1and1 block port 25 by default on their cloud VPS servers, you have to raise a support ticket and get them to unblock the port.

You can't unblock it yourself by just adding a firewall rule in the Cloud control panel, they have to do it for you.
 
Thank you a lot, after contacting again the support they opened me the outbound 25 port...
My mails are now correctly sent !
 
As I found out recently 1and1 block port 25 by default on their cloud VPS servers, you have to raise a support ticket and get them to unblock the port.

You can't unblock it yourself by just adding a firewall rule in the Cloud control panel, they have to do it for you.

Is this true?? I have been banging my head against the wall for HOURS trying to get email to send and you are telling me that it's a CLOSED PORT?

I called but tech support is getting slammed with something tonight - let's see what happens...
 
Is this true?? I have been banging my head against the wall for HOURS trying to get email to send and you are telling me that it's a CLOSED PORT?

I called but tech support is getting slammed with something tonight - let's see what happens...

Yes it's true. After few days trying to resolve this issue and linstening one 1and1 support team memeber saying me again and again that all ports were opened I tried again to call them and I spoke with another support team member who finally told me "Yes of course the outgoing 25 port is closed, You didn't know that?".. After few seconds he opened me the port and now all is ok..

You should reach the support and ask them to open the port (not visible in their "cloud view" firewall rules).
 
Back
Top