Re: Weird pop3 issue
- From: "UNIX" <scottnospam@xxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 31 Mar 2008 07:47:38 +1100
Hi Rich,
There are a couple that are similar - eg. pblackie as opposed to
dblackie, but the there are others that are completely different - eg.
atantau.
I'll try the alias idea and let you know though.
"Rich Matheisen [MVP]" <richnews@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:kbpvu3dr89qmfsambmrutmof61e90uaqv3@xxxxxxxxxx
"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
.
- Follow-Ups:
- Re: Weird pop3 issue
- From: UNIX
- Re: Weird pop3 issue
- References:
- Weird pop3 issue
- From: UNIX
- Re: Weird pop3 issue
- From: Rich Matheisen [MVP]
- Weird pop3 issue
- Prev by Date: Re: Showing Mail-Enabled Groups in Custom GAL
- Next by Date: Re: Weird pop3 issue
- Previous by thread: Re: Weird pop3 issue
- Next by thread: Re: Weird pop3 issue
- Index(es):
Relevant Pages
|
Loading