aspNetPOP3.POP3AuthenticationException: Bad username and/or password; requested mailbox is not available

Hi,

We are getting the error below about every 30 seconds in the csm_receivers.log and the the csm_receivers_errors.log.

csm_receivers.log error:

-----------------------------------------------

2006-12-06 12:59:00,118 [5268] ERROR [] - Exception occurred in Pop3.CheckForMessages()
Exception: aspNetPOP3.POP3AuthenticationException
Message: Bad username and/or password. aspNetPOP3.POP3ProtocolException: Missing a positive response (+OK) from the POP3 server. The following response was recieved: '-ERR The requested mailbox is not available on this server.'. If you have not enabled logging, more information may be obtained by setting POP3.LogPath and/or using POP3.LogInMemory.
   at aspNetPOP3.POP3.?(? , Boolean )
   at aspNetPOP3.POP3.?(? , Boolean )
   at aspNetPOP3.POP3.?(? , Boolean )
   at aspNetPOP3.POP3.Connect(String username, String password, String server)
Source: aspNetPOP3
   at aspNetPOP3.POP3.Connect(String username, String password, String server)
   at aspNetPOP3.POP3.Connect()
   at CommunityServer.Mail.Receivers.Core.Pop3.?()

-----------------------------------------------

Config: CS 2.0; mail gateway 2.0; running on Windows Server 2000, SP4; Exchange Server running on the same network on a different server; using CS on our intranet (WAN - trusted relationship with other private domains via VPN).

Community Server has been running fine for months and the Mail Gateway add-in has been running fine for several weeks. It seems like the issues started about a week ago but we haven't pinpointed what changed to know what the trigger may be. We have made no config file changes since we got the mail gateway working several weeks ago.

Other symptoms: We have a mailbox set up on our Exchange Server that the mail gateway retrieves mail from to post to one of our forums. It was working fine prior to a week ago; now there are messages waiting in the mailbox unretrieved.

We've tried stopping/restarting the mail gateway services with no effect.

Does anyone know where to look to find the cause?

The error text says to enable logging by setting POP3.LogPath and/or using POP3.LogInMemory -- how do I do that?

Any help appreciated.

Thanks

 

According to that error message, it is failing to log in.  So I'd try and use something like Outlook Express with the same settings Mail Gateway is set to use to log in and make sure you can log in and view the messages.  When setting up OE, make sure to check the option to tell it to leave the messages on the server, so that once you fix it so MG can log in, it will get the waiting messages.

Hi Ken,

Thanks for your reply. It turns out our IT Ops guys brought another Exchange server online and didn't tell us they were splitting off some of the usernames, so the config file was looking at the wrong server. Once we had the right server name and stopped/started the MG services, everything started working again.

Thanks again