Results 1 to 2 of 2

Thread: 3 accounts cannot pop email via proxy server - remaining 250 + accounts work fine

  1. #1
    portscanner is offline Active Member
    Join Date
    Feb 2011
    Posts
    33
    Rep Power
    4

    Default 3 accounts cannot pop email via proxy server - remaining 250 + accounts work fine

    Using: 7.1.4_GA_2555.RHEL6_64-20120105094542

    Architecture - running Centos 6.4 on all machines
    One machine - (zimbra1) used for ldap and logging (running snmp, ldap, proxy, logger, apache, mta, spell, memcached, store and core) no public ip addresses
    Two machines - (mx1 and mx2) mx servers (running mta and core only)
    One machine - (mail4) used for proxy only from the Internet (mta, memcached, core, store, spell, proxy, apache)
    One machine - (mailstore2) used for mail store - all ,mailboxes are on it - has no public ip addresses (store, core, spell, mta, memcached, proxy, apache)

    Senerio: two weeks ago Mailstore1 (now turned off) had a dying drive in the raid array. Size of drives, memory, processor, etc, we decided to upgrade to a new machine. Set up new machine, and over the weekend moved mailboxes from Mailstore1 to Mailstore2 (using a script I have used multiple times in the past). Monday morning - everything is running good. Friday - we remove Mailstore1 and turn it off (zmprov deleteServer Mailstore1.domain.com) About 30 minutes later, we have three accounts out of 263 that cannot POP their email. The web interface works fine. Just cannot use POP3.

    The following line appears in the nginx.log
    2013/11/18 08:20:10 [error] 18520#0: *71 recv() failed (111: Connection refused) while reading response from upstream, client: 172.17.2.121, server: 0.0.0.0:110, login: "joe@domain.com", upstream: 172.17.2.48:7110 (172.17.2.121:44025-172.17.2.21:110) <=> (172.17.2.21:51570-)

    (the above are actual ip addresses)

    After many hours of pulling hair out the two following items were discovered:
    1. Adding an alias for each of those three users (example: joe1@domain.com) and using that as the username for POP3, they could log in
    2. Modifying their email client to bypass the proxy server by using port 7110 and their email address (not the alias) they could log in (obviously this will not work via the Internet as the mailstore has no public ip addresses)

    I have done a
    /opt/zimbra/libexec/zmslapcat .
    and
    /opt/zimbra/libexec/zmslapcat -c .
    and studied the results and cannot see anything different about these accounts.

    Can anyone suggest some other place to look?
    Does the proxy server have a cache we can flush?

  2. #2
    portscanner is offline Active Member
    Join Date
    Feb 2011
    Posts
    33
    Rep Power
    4

    Default

    Update - I just noticed the log in the nginx.log has the ip address of the old mailstore

    2013/11/18 08:20:10 [error] 18520#0: *71 recv() failed (111: Connection refused) while reading response from upstream, client: 172.17.2.121, server: 0.0.0.0:110, login: "joe@domain.com", upstream: 172.17.2.48:7110 (172.17.2.121:44025-172.17.2.21:110) <=> (172.17.2.21:51570-)

    172.17.2.48 - is the ip address of the old mailstore - which is turned off and removed from the zimbra system. The fqdn of the server has also been removed from the dns. So where is it getting that IP address from?

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Replies: 5
    Last Post: 11-28-2012, 11:48 AM
  2. Moving Accounts - Jetty/Work Fills Up
    By Chewie71 in forum Administrators
    Replies: 3
    Last Post: 01-13-2010, 03:44 PM
  3. Replies: 0
    Last Post: 11-03-2009, 02:08 PM
  4. Replies: 2
    Last Post: 03-20-2006, 10:50 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
  •