SMTP Submission Port

[manthrax3]

I like using 587 for SMTP submission because it is rarely blocked by firewalls while 25 is almost always blocked.

To enable this in Zimbra, I uncommented the following lines in ~zimbra/postfix/conf/master.cf:

submission inet n - n - - smtpd
-o smtpd_etrn_restrictions=reject
-o smtpd_enforce_tls=yes -o smtpd_sasl_auth_enable=yes

The run:

postfix reload

Works great. This should probably be the default behavior.

bp

[jareep]

I tried this and then tried getting Outlook to send email through SMTP with no luck. The client just sits there "Preparing to send/receive". I'm not really worried about receiving mail through POP/IMAP, I just need to be able to send. My users all use the webUI, but I have 1 user using FileMaker Pro to send emails. It launches Outlook to do the sending, but every since I installed the Zimbra Outlook Connector FileMaker Pro crashes immediately after sending the email. So, I want to get Outlook back to a normal state of operation using something its designed for without 3rd party addins. This user ONLY needs to send using Outlook using FileMaker Pro. All the rest of her mail activity will be using the webUI.

Any ideas why I can't successfully send? I can telnet to port 587 and am greeted with the ESMTP Postfix message, but the Outlook client apparently isn't authenticating or something.

[jdell]

I've seen weirdness with Outlook where some instances would work on por 587 and some would only work on port 465. So, I would enable both and try both:

Port 465 is the 'smtps' line in master.cf, so I'd uncomment all the lines below:

smtps    inet  n       -       n       -       -       smtpd
  -o smtpd_tls_wrappermode=yes -o smtpd_sasl_auth_enable=yes
submission   inet    n       -       n       -       -       smtpd
  -o smtpd_etrn_restrictions=reject
  -o smtpd_enforce_tls=yes -o smtpd_sasl_auth_enable=yes

[jareep]

Got it fixed. For some reason, the firewall port change didn't get applied. Then I had to add our IP range into zimbraMtaMyNetworks, now all is peachy. Thanks for the reply.

[ashbc]

Hello all,

After editing the master.cf file and then either restarting postfix (postfix reload) or Zimbra (zmcontrol stop ... then start) ... I have noticed it over writes the master.cf file back to original state.

After some digging around I found a master.cf.in in the main postfix conf directory and noticed that Zimbra/Postfix reloads the master.cf from this ... so, I made the appropriate changes to both files and everything worked properly after zmcontrol and postfix restarts - my config changes were left unaltered.

Hope this helps someone.

Cheers,

Ash

[fcash]

Don't edit any of the actual config files directly, as they get overwritten everytime Zimbra starts. Instead, edit the <conffile>.in files. These are the initial defaults that get pulled in by Zimbra, and used to create the actual config files.