Previous 1 2 Next 20 Replies Latest reply: Nov 19, 2010 7:04 AM by Spyros2
lionadmin Level 1 Level 1 (0 points)
All of a sudden I have users receiving others email in large amounts. We have had times when the mail server would send out old mail, but always to the correct recipient. Now I have users receiving mail from and to two different employees. This only started happening since the restart after running 10.6.5 server upgrade.

Message was edited by: lionadmin

Mac OS X (10.6.5)
  • Gerben Wierda Level 1 Level 1 (125 points)
    I have seen the same shortly after the update and have been told this is a known problem with dovecot on OS X where users see mailboxes of other users. I guess and hope they are working feverishly to fix this.
  • ppochobradsky Level 1 Level 1 (0 points)
    We experienced the same issue after updating our mail server to 10.6.5. One commonality was that the affected users were all using POP. IMAP accounts were not affected. Dumping the individual POP accounts and re-adding them as IMAP solved this, as only the correct user's mail is shown. The problem is that every time, we had to archive the inbox first before deleting the POP accounts, so the clients did not lose all emails older than 14 days. With all the confidential emails being sent back and forth, people getting their coworkers' emails is a huge issue—I cannot believe there isn't much bigger stink about this!
  • Rich White Level 1 Level 1 (40 points)
    We also have experienced this issue after the 10.6.5 update. In our case it is not only POP accounts that are affected. Will this be a one-time issue or will this continue?
  • aasun Eble Level 1 Level 1 (0 points)
    we're having the same problem. the day after the reboot from the install, started seeing email deliveries getting crossed between different people. seems to have only lasted for a few hours. haven't noticed it since.

    all of our users are IMAP only. how can we fix this??
  • keeperofthecheese Level 1 Level 1 (90 points)
    A new version of 10.6.5 was posted this afternoon:
    http://support.apple.com/kb/HT4452
    http://support.apple.com/kb/HT4249
  • Spyros2 Level 1 Level 1 (0 points)
    Still, even after installing the latest upgrade, *I cannot authenticate on IMAP.*
    The mail-client claims the password is incorrect, although the smtp authentication with the same passwrd authenticates correctly.

    Any ideas where to look? mail has become unusable.
  • davidh Level 4 Level 4 (1,890 points)
    Spyros - which mail client ? Outlook needs alot of coddling to work with OS X server but it can be done.

    Look on your server at mail.log and the password server logs for when trying to authenticate from the client in question, and post the results.
  • Spyros2 Level 1 Level 1 (0 points)
    Its Apple Mail and or Thunderbird. SMTP authenticates without problems. It worked completely two days ago, as of yesterday night, IMAP does not like the password anymore. Will post the logs.

    Please send complete paths of logs. Do you mean the logs on the server Admin>Mail ?

    *Where are the "Password server logs"???*

    here is the IMAP log of the server admin tool> Mail > IMAP.
    The Ip address is correct.
    Nov 16 22:07:33 MacMini dovecot[58]: imap-login: Disconnected (auth failed, 1 attempts): user=<sjpapa>, method=CRAM-MD5, rip=83.235.169.236, lip=83.235.169.239
    Nov 16 22:07:43 MacMini dovecot[58]: imap-login: Disconnected (auth failed, 1 attempts): user=<sjpapa>, method=CRAM-MD5, rip=83.235.169.236, lip=83.235.169.239
    Nov 16 22:07:48 MacMini dovecot[58]: imap-login: Disconnected (auth failed, 2 attempts): user=<com.apple.calendarserver>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS

    Here the correct SMTP connection:

    Nov 16 22:01:06 MacMini postfix/smtpd[2358]: disconnect from sipepe.static.otenet.gr[83.235.169.236]
    Nov 16 22:04:26 MacMini postfix/anvil[2362]: statistics: max connection rate 1/60s for (smtp:83.235.169.236) at Nov 16 22:01:04
    Nov 16 22:04:26 MacMini postfix/anvil[2362]: statistics: max connection count 1 for (smtp:83.235.169.236) at Nov 16 22:01:04
    Nov 16 22:04:26 MacMini postfix/anvil[2362]: statistics: max cache size 1 at Nov 16 22:01:04
    Nov 16 22:06:35 MacMini postfix/smtpd[2869]: connect from sipepe.static.otenet.gr[83.235.169.236]
    Nov 16 22:06:37 MacMini postfix/smtpd[2869]: disconnect from sipepe.static.otenet.gr[83.235.169.236]
    Nov 16 22:07:35 MacMini postfix/smtpd[2869]: connect from sipepe.static.otenet.gr[83.235.169.236]
    Nov 16 22:07:37 MacMini postfix/smtpd[2869]: disconnect from sipepe.static.otenet.gr[83.235.169.236]

    Mail Access log shows the strange: *account for sjpapa not enabled* !!!@@@???

    Nov 16 22:11:04 MacMini dovecot[58]: auth(default): mechcrammd5: challenge: <1808033637205984.1289938264@localhost>
    Nov 16 22:11:04 MacMini dovecot[58]: auth(default): od(sjpapa,83.235.169.236): *mail account for: sjpapa is not enabled*
    Nov 16 22:11:10 MacMini dovecot[58]: auth(default): mechcrammd5: challenge: <1926542490608660.1289938270@localhost>
    Nov 16 22:11:10 MacMini dovecot[58]: auth(default): od(sjpapa,83.235.169.236): *mail account for: sjpapa is not enabled*
    Nov 16 22:11:11 MacMini dovecot[58]: imap-login: Disconnected (auth failed, 1 attempts): user=<sjpapa>, method=CRAM-MD5, rip=83.235.169.236, lip=83.235.169.239
    Nov 16 22:11:23: --- last message repeated 1 time ---
    Nov 16 22:11:23 MacMini dovecot[58]: auth(default): mechcrammd5: challenge: <6399992169077748.1289938283@localhost>
    Nov 16 22:11:23 MacMini dovecot[58]: auth(default): od(com.apple.calendarserver,127.0.0.1): mail account for: com.apple.calendarserver is not enabled
    Nov 16 22:11:30 MacMini dovecot[58]: imap-login: Authenticate PLAIN failed: Unsupported authentication mechanism.: user=<com.apple.calendarserver>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
    Nov 16 22:11:30 MacMini dovecot[58]: imap-login: Disconnected (auth failed, 2 attempts): user=<com.apple.calendarserver>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
    Nov 16 22:12:00 MacMini dovecot[58]: auth(default): mechcrammd5: challenge: <1639251164309389.1289938320@localhost>
    Nov 16 22:12:00 MacMini dovecot[58]: auth(default): od(com.apple.calendarserver,127.0.0.1): mail account for: com.apple.calendarserver is not enabled
    Nov 16 22:12:07 MacMini dovecot[58]: imap-login: Authenticate PLAIN failed: Unsupported authentication mechanism.: user=<com.apple.calendarserver>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
    Nov 16 22:12:07 MacMini dovecot[58]: imap-login: Disconnected (auth failed, 2 attempts): user=<com.apple.calendarserver>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
    Nov 16 22:12:37 MacMini dovecot[58]: auth(default): mechcrammd5: challenge: <5851295398122361.1289938357@localhost>
    Nov 16 22:12:37 MacMini dovecot[58]: auth(default): od(com.apple.calendarserver,127.0.0.1): mail account for: com.apple.calendarserver is not enabled
    Nov 16 22:12:44 MacMini dovecot[58]: imap-login: Authenticate PLAIN failed: Unsupported authentication mechanism.: user=<com.apple.calendarserver>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
    Nov 16 22:12:44 MacMini dovecot[58]: imap-login: Disconnected (auth failed, 2 attempts): user=<com.apple.calendarserver>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
    Nov 16 22:13:14 MacMini dovecot[58]: auth(default): mechcrammd5: challenge: <9923554979151867.1289938394@localhost>
    Nov 16 22:13:14 MacMini dovecot[58]: auth(default): od(com.apple.calendarserver,127.0.0.1): mail account for: com.apple.calendarserver is not enabled

    Message was edited by: Spyros2

    Message was edited by: Spyros2

    Message was edited by: Spyros2
  • davidh Level 4 Level 4 (1,890 points)
    For the account in question, launch Workgroup Manager, select the account,
    change the mail enabled setting (to "none") , save, and then set it back to "enabled" and hit save.

    As for your "successful SMTP entries," that is not showing any client smtp authentication.

    Start with the first step above.

    For the password server logs, click on "Open Directory" in Server Admin, then click on the logs button.
  • Gerben Wierda Level 1 Level 1 (125 points)
    I downloaded and installed. My logged-in clients went haywire after the update (lost network connection, sometimes able, sometimes not able to sync PHD's, IMAP accounts not online, server admin cannot connect to server). I have rebooted all the clients so they have a fresh connection to the domain and now everything seems to work again.
  • davidh Level 4 Level 4 (1,890 points)
    After updating your server, you should expect all clients to lose their connection.

    This should be planned for and expected, what else (on earth) were you expecting ?
    You MUST reboot your server after the update, so any clients that normally depend on an existing server session (network home directories, eg.) would, of course, have to be rebooted.
  • Gerben Wierda Level 1 Level 1 (125 points)
    If these were mounted directories, yes, but these are portable accounts, which means they have local home directories which are synced (PHD). Something simple as an IMAP connection should re-establish itself after a reboot of a server (I have done this many times). And the fact that Safari on the client could not connect to the internet (could not download pages) where it only needs to DNS on the server was also unexpected.I also did not expect that a fresh launch of Server Admin would not be able to connect to the server (whereas Screen Sharing could connect).

    I have rebooted the server many times in the past without rebooting a client without problems, as soon as the server is up again, everything works fine. I think this is also true for updates in the past. So, this is the first time I experienced this kind of behaviour (and certainly client Safari not working was strange).
  • Spyros2 Level 1 Level 1 (0 points)
    Thank you david!
    The change from mail:None back to enabled did not do anything.
    The SMTP server authenticates correctly as I can see on the connection doctor of Apple-Mail on the McBook. The IMAP (same user, same pw) does not authenticate.

    Digging into the other logs...
    many thanks
Previous 1 2 Next