Re: Weird pop3 issue



"UNIX" <scottnospam@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

Hi All,
I have a frustrating issue that I am hoping to get some help with.

I have recently setup a client on an SPS 2003 Stadard R2 server, and have
the clients using Exchange. Up until a couple of days ago, they were still
using pop accounts at their ISP to send and receive email, and basically
just using Exchange to store their emails, instead of a .pst.

On Friday, I got the MX recods updated to email came directly to their
Exchange server, so we can get rid of the POP3 accounts at the ISP. That all
seems to be working OK, but what I didn't realise is they had a couple of
blackberry phone which also checked their POP3 accounts.

The username and password for their old POP accounts is different to their
new Exchange mailbox logins, so the Blackberries have been re-trying
endlessly since Friday. I'm not sure if that has caused an issue, but now I
can't get some (most) of the users accounts/mailboxes to allow POP3 access.
This was definitely working for at least a couple of accounts that I had
allowing External POP3 client access to, but now one of those has stopped,
and most of the other accounts don't either.

That is the frustrating bit - I can send and receive email using (for
example) Outlook Express using about 3 different usernames and logins on the
Exchange server, but for most of the others, I get an 'Invalid username or
password' error when sending and receiving.

Do the users have similar account names? When they do, Ambiguous Name
Resolution (ANR) can cause problems like this. The cure (in Exchange
2003) is to use a two-part identity for the "login acount" on the
client:

<NTDomain>\<UserID>\<UserAlias>

The <NTDomain>\<UserID> is the "normal" stuff that users provide to
log in. The <UserAlias> qualifies that.

Names like "Symth" and "Smythe", for example, result in multiple
results when looking for "Symth".

Exchange 2007 no longer accepts that format and uses the person's SMTP
email address which must, of course, be unique.


--
Rich Matheisen
MCSE+I, Exchange MVP
MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm
Don't send mail to this address mailto:h.pott@xxxxxxxxxxxxx
Or to these, either: mailto:h.pott@xxxxxxxxxxxxxxx mailto:melvin.mcphucknuckle@xxxxxxxxxxxxx mailto:melvin.mcphucknuckle@xxxxxxxxxxxxxxx
.



Relevant Pages

  • Sending email to mydomain.com
    ... They do not offer an smtp server, ... different from the user account names for the exchange ... I added one user account in the POP3 Mailbox Accounts ...
    (microsoft.public.windows.server.sbs)
  • Re: Critical e-mail problem.
    ... I upgraded from Win2K Server to WinSBS2003 on my desktop ... of my POP3 e-mail accounts as an Exchange Server account. ... I found that I was only receiving mail from the Exchange ... your Outlook profile will have Exchange as its default (and this ...
    (microsoft.public.windows.server.sbs)
  • Re: Critical e-mail problem.
    ... I upgraded from Win2K Server to WinSBS2003 on my desktop ... of my POP3 e-mail accounts as an Exchange Server account. ... I found that I was only receiving mail from the Exchange ... your Outlook profile will have Exchange as its default (and this ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot login to retrieve internet mail
    ... You are correct in that when I connect with one of these accounts (that do ... not work) from an outlook client I am attemting to receive mail. ... > POP client - only the Exchange server for POP, ... > Internet - this is entirely different. ...
    (microsoft.public.exchange.admin)
  • Re: exchange basics
    ... If you find users switching between client ... often pull the mail to a different store (as in POP3) and then wonder why it ... Exchange can inform and enforce quotas on mail storage. ... Server side rules? ...
    (microsoft.public.exchange.design)