Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: port 587

Hybrid View

  1. #1
    Join Date
    Apr 2006
    Posts
    47
    Rep Power
    0

    Default port 587

    doez zimbra smtp listen on port 25 *AND* 587? thank you

  2. #2
    Join Date
    Aug 2005
    Location
    San Mateo, CA
    Posts
    4,789
    Rep Power
    19

    Default

    Just 25 as I recall.
    Looking for new beta users -> Co-Founder of Acompli. Previously worked at Zimbra (and Yahoo! & VMware) since 2005.

  3. #3
    Join Date
    Sep 2005
    Posts
    2,103
    Rep Power
    14

    Default

    That's this bug: http://bugzilla.zimbra.com/show_bug.cgi?id=5194

    We've pretty much decided to punt on it, unless it gets lots of votes (ahem). There's a note in the bug on how to enable it.
    Bugzilla - Wiki - Downloads - Before posting... Search!

  4. #4
    Join Date
    Apr 2006
    Posts
    47
    Rep Power
    0

    Default

    that's really too bad. We can't go forward w/out port 587 working. More and more customers can't reach us through port 25 due to isp port filtering.

  5. #5
    Join Date
    Jul 2008
    Location
    Corvallis, OR
    Posts
    54
    Rep Power
    7

    Default

    These days 587 is a requirement; we *try* to push customers to 465/ssl, but there are still a lot of broken mail clients out there...

  6. #6
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,587
    Rep Power
    58

    Default

    Quote Originally Posted by useopenid View Post
    These days 587 is a requirement; we *try* to push customers to 465/ssl, but there are still a lot of broken mail clients out there...
    Yes but port 587 is the correct Submission port (465 is not correct and has been deprecated) for clients to submit mail, it's not the port for connecting SMTP servers. The original question was about 'listening' on port 25 & 587,. If the o/p wanted to receive mail on port 587 because their port 25 was blocked then that would be incorrect and they should use a mailhop service that rerouted mail to another port. If the problem is that other mail servers are blocked from sending on port 25 then those servers should relay through their ISPs mail servers - that should only happen on residential type IP addresses, a business ISP service should not be blocking port 25.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  7. #7
    Join Date
    Jul 2009
    Posts
    34
    Rep Power
    6

    Default

    I have no argument with your points, but I *do* block port 25 on my business network (egress filtering) in an attempt to thwart and detect spam-sending malware. I have rules that allow connects only to certain hosts on port 25. If your zimbra host was outside your firewall, and you did egress filtering, and you used smtp clients, you'd need to add such a rule.

  8. #8
    Join Date
    Jul 2008
    Location
    Corvallis, OR
    Posts
    54
    Rep Power
    7

    Default

    I wasn't aware 465 had been deprecated, it just seemed more efficient (albeit only slightly) to connect with SSL to start with, but that does make it even more imperative for 587 to be properly supported. I just upgraded zimbra and had to remember to fix the postfix config file to get 587 back. We are a regional ISP moving to zimbra and port 25 is problematic in several areas:

    1. outsourced dialup service to provide access outside our local calling area blocks port 25
    2. customers with services here who use other isps for access (e.g. comcast) which block port 25
    3. we want to firewall the mail server so it only accepts incoming mail from the spam filter appliance to keep spammers from bypassing it

    Point 1 is the only one specific to our being an ISP, 2 and 3 could easily apply to anyone running zimbra

  9. #9
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,587
    Rep Power
    58

    Default

    Quote Originally Posted by useopenid View Post
    I wasn't aware 465 had been deprecated, it just seemed more efficient (albeit only slightly) to connect with SSL to start with, but that does make it even more imperative for 587 to be properly supported. I just upgraded zimbra and had to remember to fix the postfix config file to get 587 back.
    If by 'properly supported' you mean available by default then it is in Zimbra 6.x
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  10. #10
    Join Date
    Sep 2005
    Posts
    2,103
    Rep Power
    14

    Default

    Um - did you read the bug? The change to make port 587 work is pretty simple.
    Bugzilla - Wiki - Downloads - Before posting... Search!

Similar Threads

  1. initializing ldap...FAILED(256)ERROR
    By manjunath in forum Installation
    Replies: 39
    Last Post: 06-07-2013, 11:27 AM
  2. Installation Problem - Possibly LDAP
    By geroshea in forum Installation
    Replies: 5
    Last Post: 03-16-2007, 05:47 AM
  3. Error 256 on Installation
    By RuinExplorer in forum Installation
    Replies: 5
    Last Post: 10-19-2006, 10:19 AM
  4. Getting problems in FC4 while instalation
    By kitty_bhoo in forum Installation
    Replies: 13
    Last Post: 09-12-2006, 11:34 PM
  5. Help Please... Zimbra error message too slow...
    By nazeeronline in forum Installation
    Replies: 20
    Last Post: 09-06-2006, 06:35 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •