SMTP Client Restriction

I've been reading the many posts related to SMTP Authentication and I've never really seen a clear answer anywhere about this situation:

* End user has e-mail account setup in Windows Mail with POP/SMTP access to my server
* End user has SMTP Authentication turned on from previous hosting server
* Everything's moved to my EHCP server and now end user gets a prompt asking for SMTP Authentication information. Same settings as POP doesn't work.
* Turned off client authentication and e-mails send correctly (MAJOR SECURITY HOLE)
* Need authentication to work and open relay closed.

My tests:

* Telnet into EHCP server on port 25 and did command-line test with e-mail from and valid recipient on my server
* No errors, message went through successfully (MAJOR SECURITY HOLE - OPEN RELAY)

My config:
Here's the output of postfix/ (removed my domain name and IP for security purposes):

# See /usr/share/postfix/ 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 (Ubuntu)
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 = /usr/share/doc/postfix
# TLS parameters
smtpd_tls_cert_file = /etc/postfix/smtpd.cert
smtpd_tls_key_file = /etc/postfix/smtpd.key
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.
myhostname =
alias_maps = hash:/etc/aliases
alias_database = hash:/etc/aliases
myorigin = /etc/mailname
mydestination = localhost, myip
relayhost =
mynetworks =,,,, myip/24
mailbox_command = procmail -a "$EXTENSION"
mailbox_size_limit = 0
recipient_delimiter = +
inet_interfaces = all
html_directory = /usr/share/doc/postfix/html
virtual_alias_domains =
virtual_alias_maps = proxy:mysql:/etc/postfix/, proxy:mysql:/etc/postfi$
virtual_mailbox_domains = proxy:mysql:/etc/postfix/
virtual_mailbox_maps = proxy:mysql:/etc/postfix/
virtual_mailbox_base = /home/vmail
virtual_uid_maps = static:5000
virtual_gid_maps = static:5000
smtpd_sasl_auth_enable = yes
broken_sasl_auth_clients = yes
smtpd_recipient_restrictions = permit_mynetworks,permit_sasl_authenticated,check_client_access hash:/var/lib/pop-before-smtp/hosts,reject_unauth_destination
virtual_create_maildirsize = yes
virtual_mailbox_extended = yes
virtual_mailbox_limit_maps = proxy:mysql:/etc/postfix/
virtual_mailbox_limit_override = yes
virtual_maildir_limit_message = "The user you are trying to reach is over quota."
virtual_overquota_bounce = yes
proxy_read_maps = $local_recipient_maps $mydestination $virtual_alias_maps $virtual_alias_domains $virtual_mailbox_maps $virtual_mailbox_domains $relay_recipient_maps $canonical_maps $sender_canonical_maps $recipient_canonical_maps $relocated_maps $mynetworks $virtual_mailbox_limit_maps

  • Can you type here your telnet session, so that i will do same test, on my server,
  • One way to try: use latest version of, 0.29.09 (or preferably , which is 0.29.10) click on options->fix main configuration, then, use in this one: smtpd_recipient_restrictions = permit_mynetworks,permit_sasl_authenticated,reject_unauth_destination (this is different in your config, from what should be)
  • I acknowledge that, email sending with smtp auth in ehcp ver 0.29.10 and before, is not enabled by default, and is not perfectly configured so that everything is smooth... I mean, still I could not find a safe, secure, easy way (of email installation) of doing email sending with smtp auth...
  • So, you and I should think about this, and figure out... once a day, I remember that I did succeed that, as I described above, but I dont know if that will work for you too...
  • The idea is: enable tls/ssl , enable smtp auth, then remove pop-before-smtp in this is the idea
  • This may help too:
  • I agree that, without smtp auth, this is open relay, and is not recomended.. and is not secure... open to spammers...
  • Let me know if you can completely solve this, so that I will integrat this completely in ehcp..
  • I will also try and include in ehcp if I can, if I have time..
  • Hello, here is link to the great how-to about your problem:

    check it out.