Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Administrators

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 04-26-2011, 10:24 AM
Intermediate Member
 
Posts: 19
Default smtp port

Hi,

I wonder what port is used for sending emails out when logged in at web client, and which one is used when sending emails from within Zimbra Desktop? How can I force port 587 usage for both send outs?

Thanks!
Reply With Quote
  #2 (permalink)  
Old 04-26-2011, 10:37 AM
Intermediate Member
 
Posts: 19
Default

This is kinda related to this thread started by me. I'm not sure about the concept behind this, but I'd like to have all outbound emails to be dk signed, and am not sure if they will when using the howto from the link I've posted in my other thread.
Reply With Quote
  #3 (permalink)  
Old 04-26-2011, 10:56 AM
Zimbra Consultant & Moderator
 
Posts: 20,313
Default

When using the Web UI & ZD (connected to a Zimbra server) you use port 80 (or preferably the more secure port 443) to compose an email and send it to the server, when mail is sent from the server to the outside world it uses Port 25 - the same as every other MTA.
__________________
Regards


Bill
Reply With Quote
  #4 (permalink)  
Old 04-26-2011, 11:04 AM
Intermediate Member
 
Posts: 19
Default

Thanks for responding.
Sure, right, that's understandable. But what I want to achieve is to have all emails signed, no matter from where they were sent (ZD/web) and all guides say I should use port 587 for that.
Can this be changed somehow and how? Is there any other way of signing emails when using DKIMProxy that I'm not aware about?
Reply With Quote
  #5 (permalink)  
Old 04-26-2011, 11:08 AM
Zimbra Consultant & Moderator
 
Posts: 20,313
Default

Quote:
Originally Posted by kaosmonk View Post
Thanks for responding.
Sure, right, that's understandable. But what I want to achieve is to have all emails signed, no matter from where they were sent (ZD/web) and all guides say I should use port 587 for that.
Can this be changed somehow and how? Is there any other way of signing emails when using DKIMProxy that I'm not aware about?
Use this instead (I use it and it works well): How to get DKIM (DomainKeys Identified Mail) working with Postfix on RHEL 5 / CentOS 5 using OpenDKIM – Steve Jenkins' Blog
__________________
Regards


Bill
Reply With Quote
  #6 (permalink)  
Old 04-26-2011, 11:34 AM
Intermediate Member
 
Posts: 19
Default

Quote:
Originally Posted by phoenix View Post
Awesome! Will try that and get back to you if it helps!
One more thing - I'm using MailArchiva thus having some options already set:

Code:
smtpd_milters = inet:mailarchiva_IP:chosen_port
milter_default_action = tempfail
and I have changed default milter port to chosen_port (same one from above) with

Code:
zmprov ms mail.server.com zimbraMilterBindPort chosen_port
and that setup works. Now, what needs to be done in order to leave MailArchiva working? Would it be enough if I manually change and add a line like this:

Code:
smtpd_milters = inet:mailarchiva_IP:chosen_port, inet:127.0.0.1:20209
Or should I perform something else? Will I need to switch zimbraMilterBindPort to something else in that case? Should I leave milter_default_action to tempfail or change it to accept (as shown in that howto of yours)?

I'd appreciate any advice in regards to this, as it seems to me that I'm circling around...

You already helped me alot!

Last edited by kaosmonk; 04-26-2011 at 12:13 PM..
Reply With Quote
  #7 (permalink)  
Old 04-26-2011, 01:35 PM
Intermediate Member
 
Posts: 19
Default

Ok, just to check if I'm moving to the right direction... judging by this link, non_smtpd_milters are used for signing only, but I believe that in my case, it wont hurt to have them included in smtpd_milters line too, right? The page also says that milter_default_action shouldn't be set to 'tempfail' as non_smtpd_milters will report a config error; but later on, text says that shouldn't be the problem for mail filters that digitally sign emails...
So... I my case, I suppose I should have something like this:
Code:
smtpd_milters = inet:mailarchiva_ip:portnumber, inet:localhost:dkim_port
non_smtpd_milters = inet:localhost:dkim_port
milter_default_action = tempfail
If I understood it right, I may leave the last parameter at 'tempfail' as it wont affect filter for digitally signing mails, right?

If all this make sense, what I should set for zimbraMilterBindPort at the end?
Reply With Quote
  #8 (permalink)  
Old 04-27-2011, 07:39 AM
Intermediate Member
 
Posts: 19
Default

Hi phoenix, can you please shed some light up to this matter? Would really appreciate it! Thanks!
Reply With Quote
  #9 (permalink)  
Old 04-30-2011, 10:08 AM
Intermediate Member
 
Posts: 19
Default

I have tried to setup this by changing main.cf file and adding
Code:
smtpd_milters = inet:192.168.6.109:8092, inet:127.0.0.1:20209
non_smtpd_milters = inet:127.0.0.1:20209
milter_default_action = accept
milter_protocol = 2
but as soon as I run 'zmmtactl restart', main.cf file gets rewritten. 192.168.6.109 is an IP address of MailArchiva server.

If I try to add another IP address from within Zimbra Admin panel: Server Settings > MTA > Milter Server > MilterServerBindAddress> 127.0.0.1, in main.cf I can see the line
Code:
smtpd_milters = inet:192.168.6.109 127.0.0.1:8092
which I believe is not what I need, as only one port is shown...
and if afterwards I try to set non_smtpd_milters as
Code:
non_smtpd_milters = inet:127.0.0.1:20209
and after running 'zmmtactl restart' I get
Quote:
/opt/zimbra/conf/mta_milter_options: line 2: 127.0.0.1: command not found
What am I doing wrong here? How can I setup both smtpd_milters and non_smtpd_milters to values I want them to have?
Reply With Quote
  #10 (permalink)  
Old 05-05-2011, 02:19 PM
Intermediate Member
 
Posts: 19
Default

bumping this thread - any idea on how to resolve this?
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.