IMAP Problem with ONE USER

I added a new user a month back to our SBS 2003 server and he recently wanted
to set up remote email at home via IMAP4 as many others in the organization
do. Following instructions I gave him the set up failed, and I have since
tested and sure enough his account seems to fail every time. This is odd as
I use IMAP myself for this email connection for my cell phone and many other
users in the network use IMAP as well.

I checked that his account has default settings, with IMAP4 enabled and sure
enough it does. I disabled IMAP and re-enabled it for him to no avail. I
changed his password to no avail. I stopped and started up the exchange
services to no avail.

I then created another new user using the exact same settings as this user,
but with a different name. This user had no problems with IMAP4 at all right
from the get go. This leads me to the probable solution of simply creating a
new account for him but that's a pain for him as then we have to export all
his settings and import them into the new account. I'd rather just get his
IMAP4 working on his current account.

I can not find any information about how to solve this one. Can someone
please tell me where to start?

Russ
Thu Sep 18 20:51:27 PDT 2008

You do know, you can use RPC over HTTP and it's 100 times better than IMAP?

You also didn't say if this was a PC or a Mac?
on a Mac I don't have a clue.

PC, Delete is outlook profile and start again
and make sure he hasn't installed a firewall that's blocking it.

But Honestly setup RPC over HTTPS
Outlook 2003 comes with SBS licenses so you can install it on his home PC

And it works like a charm

Russ

--
Russell Grover - SBITS.Biz
Microsoft Gold Certified Partner
Microsoft Small Business Specialist
World Wide 24hr Remote SBS2003 Support - http://www.SBITS.Biz


"Keven" <Keven@discussions.microsoft.com> wrote in message
news:0CA15B2F-78B6-42A4-870A-8EED2D13019A@microsoft.com...
>I added a new user a month back to our SBS 2003 server and he recently
>wanted
> to set up remote email at home via IMAP4 as many others in the
> organization
> do. Following instructions I gave him the set up failed, and I have since
> tested and sure enough his account seems to fail every time. This is odd
> as
> I use IMAP myself for this email connection for my cell phone and many
> other
> users in the network use IMAP as well.
>
> I checked that his account has default settings, with IMAP4 enabled and
> sure
> enough it does. I disabled IMAP and re-enabled it for him to no avail. I
> changed his password to no avail. I stopped and started up the exchange
> services to no avail.
>
> I then created another new user using the exact same settings as this
> user,
> but with a different name. This user had no problems with IMAP4 at all
> right
> from the get go. This leads me to the probable solution of simply
> creating a
> new account for him but that's a pain for him as then we have to export
> all
> his settings and import them into the new account. I'd rather just get
> his
> IMAP4 working on his current account.
>
> I can not find any information about how to solve this one. Can someone
> please tell me where to start?

Cliff
Thu Sep 18 21:03:03 PDT 2008

create the new user and use a tool that migrates profiles. XP and Vista
both let you copy a profile, and USMT can do this as well.

Based on the info you provided, I assume you've tried testing from multiple
machines, so you've eliminated the machine as the problem. That leaves
something goofy in the user account. Since he's having this problem from
home, I assume the home machine is not joined to the domain. So that would
eliminate it being a profile issue as well. That pretty much leaves a
broken/corrupt active-directory property mucking up his account...good luck
tracking that down. It is *easier* to create a new account. Test. Migrate
profile. Test again. Pass the info back to the user. Have him test. That
way you know when it breaks again (if it does at all.)

-Cliff


"Keven" <Keven@discussions.microsoft.com> wrote in message
news:0CA15B2F-78B6-42A4-870A-8EED2D13019A@microsoft.com...
> I added a new user a month back to our SBS 2003 server and he recently
> wanted
> to set up remote email at home via IMAP4 as many others in the
> organization
> do. Following instructions I gave him the set up failed, and I have since
> tested and sure enough his account seems to fail every time. This is odd
> as
> I use IMAP myself for this email connection for my cell phone and many
> other
> users in the network use IMAP as well.
>
> I checked that his account has default settings, with IMAP4 enabled and
> sure
> enough it does. I disabled IMAP and re-enabled it for him to no avail. I
> changed his password to no avail. I stopped and started up the exchange
> services to no avail.
>
> I then created another new user using the exact same settings as this
> user,
> but with a different name. This user had no problems with IMAP4 at all
> right
> from the get go. This leads me to the probable solution of simply
> creating a
> new account for him but that's a pain for him as then we have to export
> all
> his settings and import them into the new account. I'd rather just get
> his
> IMAP4 working on his current account.
>
> I can not find any information about how to solve this one. Can someone
> please tell me where to start?

Keven
Thu Sep 18 21:32:03 PDT 2008

Ok, thanks for the reply guys and I have to first of all mention that the
solution was odd. It ends up when I created the user I had a typo and the
onsite admin there corrected the user's name. So fo this example I'll call
the user's log in name as I typed it in "XXX". Onsite admin changed it to
the proper which I'll call "YYY". The Exchange mailbox is still called "XXX"
though, even though the user is now logging in as username "YYY". This
doesn't cause a problem for anything in outlook or owa etc.. but it ends up I
find out (by staring at IMAP4 reference guides for an hour) that if the
mailbox is not named the same as the user name that you have to reference it
in the login! So the solution, given this example was that for IMAP purposes
the user had to log in as username of "Domain/YYY/XXX" and password as per
usual. Note that it is a / not a \ on the fully qualified user name. Odd,
but true for IMAP.

As for the RPC over HTTP, I would LOVE to use this for all purposes and
simply can't! The problem is that many of these users are connecting to
many exchange servers, and as any one knows who has a windows mobile phone
"THERE CAN BE ONLY ONE" exchange account and is the same for outlook unless
you are cool shutting down your outlook and restarting it over and over
(which I being someone who has an account on 6 SBS servers out there am not
patient enough for) then IMAP really is the next best thing to use.

I know, before anyone tells me why you can only have one exchange account
open at a time, why you can only have one.. but that doesn't stop it from
being one of the only really sucky parts of the oulook experience!

Thanks all who responded, and I hope this reference helps someone else who
might have this issue in the future.



"Keven" wrote:

> I added a new user a month back to our SBS 2003 server and he recently wanted
> to set up remote email at home via IMAP4 as many others in the organization
> do. Following instructions I gave him the set up failed, and I have since
> tested and sure enough his account seems to fail every time. This is odd as
> I use IMAP myself for this email connection for my cell phone and many other
> users in the network use IMAP as well.
>
> I checked that his account has default settings, with IMAP4 enabled and sure
> enough it does. I disabled IMAP and re-enabled it for him to no avail. I
> changed his password to no avail. I stopped and started up the exchange
> services to no avail.
>
> I then created another new user using the exact same settings as this user,
> but with a different name. This user had no problems with IMAP4 at all right
> from the get go. This leads me to the probable solution of simply creating a
> new account for him but that's a pain for him as then we have to export all
> his settings and import them into the new account. I'd rather just get his
> IMAP4 working on his current account.
>
> I can not find any information about how to solve this one. Can someone
> please tell me where to start?