For probably at least the past week or so, I have noticed that my BIS account has gone back to polling once every ten to fifteen minutes whereas a few weeks ago messages would pop up on the BB faster than Mail.app on the mac (which doesn't support IMAP IDLE). I'm on a 8900 with TMO as indicated in the title and it's the same situation be it on UMA or EDGE. Anyone else out there experiencing the same issues?

I haven't noticed that and am also running TMO w/an 8900.

I am also with TMO and IMAP Idle is working perfect just like it has for about the last year. Maybe your email host quit supporting it?

Hmm, just talked to my sysadmin, and he grabbed this for me:

Jun 24 23:13:10 Hera dovecot: imap-login: Login: user=<*****>, method=PLAIN, rip=67.223.70.103, lip=205.134.160.110, TLS

Jun 24 23:13:10 Hera dovecot: IMAP(*****): Disconnected: Logged out bytes=156/6316

So it looks like it's connecting and then immediately disconnecting....

Even more detailed logging....

>>>>>>
Jun 24 23:31:26 Hera dovecot: imap-login: Login: user=<*****>, method=PLAIN, rip=67.223.70.103, lip=205.134.160.110, TLS
Jun 24 23:31:26 Hera dovecot: IMAP(*****): Effective uid=1001, gid=1001, home=/home/*****
Jun 24 23:31:26 Hera dovecot: IMAP(*****): maildir: root exists (/home/*****/Maildir)
Jun 24 23:31:26 Hera dovecot: IMAP(*****): maildir++: root=/home/*****/Maildir, index=, control=, inbox=/home/*****/Maildir
Jun 24 23:31:26 Hera dovecot: IMAP(*****): Disconnected: Logged out bytes=156/5505
<<<<<<

Wirelessly posted

Have you tried removing the email from your phone completly and then re adding it.

Weird

IMAP has never worked for me on my T-Mo BB.

It works fine though on the nextel and sprint BBs.

ok, a couple searches on these here forums turned up that resending service books might be the way to go. So, I did that but I also took the draconian step of removing the account and readding it. So, either that or resending the service books resolved this "issue". Let's hope it's over and done with!

Yeah, did it. Either removing it and re-adding the account to BIS resolved the issue or forcing the resend of service books. Thanks for the suggestion.