Your IMAP server wants to alert you to the following: 5 (1032) That mail is not currently available.

  • Thread starter Thread starter Lyle
  • Start date Start date
L

Lyle

---------------------------
Microsoft Office Outlook
---------------------------
Your IMAP server wants to alert you to the following: 5 (1032) That
mail is not currently available.
---------------------------
OK
---------------------------

Does anyone know why this message box is shown several times during
each send and recevie, and if there is a way to stop its being shown ?
(2007).
I have two imap and two pop accounts activated. I believe but cannot
verify that the IMAP server is that hosting imap.aim.com. I have about
thirty folders there.
 
Lyle said:
---------------------------
Microsoft Office Outlook
---------------------------
Your IMAP server wants to alert you to the following: 5 (1032) That
mail is not currently available.
---------------------------
OK
---------------------------

Does anyone know why this message box is shown several times during
each send and recevie, and if there is a way to stop its being shown ?
(2007).
I have two imap and two pop accounts activated. I believe but cannot
verify that the IMAP server is that hosting imap.aim.com. I have about
thirty folders there.
Click to expand...

Disable the AOL account in the Send/Receive group and see if the message
occurs. If not, reenable it and disable the other IMAP account. Try again.
That will tell you definitively which IMAP account is causing the issue.
You can then, perhaps, get additional information on the error by disabling
all accounts by that one in the send./receive group (or, create a new
send/receive group with only that account in it and test with that one) and
enabling diagnostic logging (there is no article I can see in the MSKB about
OL 2007 logging specifically; here's a link to OL 2003:
http://support.microsoft.com/kb/300479/en-us) and see if any additional
error indications appear there. You can them take it up with the ISP
hosting the IMAP server.
 
Brian said:
Disable the AOL account in the Send/Receive group and see if the message
occurs. If not, reenable it and disable the other IMAP account. Try again.
That will tell you definitively which IMAP account is causing the issue.
You can then, perhaps, get additional information on the error by disabling
all accounts by that one in the send./receive group (or, create a new
send/receive group with only that account in it and test with that one) and
enabling diagnostic logging (there is no article I can see in the MSKB about
OL 2007 logging specifically; here's a link to OL 2003:
http://support.microsoft.com/kb/300479/en-us) and see if any additional
error indications appear there. You can them take it up with the ISP
hosting the IMAP server.
Click to expand...

Yes, it goes away when I remove the AIM IMAP Account. But I have been
unable to identify any specific IMAP folder that causes the problem
(the numbers 1,4,6,24 don't seem to be helpful; I've experimented but I
have not found anything). There is no problem on Windows Live Mail
Desktop, Thunderbird or Pegasus set up in exactly the same way, so I
doubt this is an IMAP server problem.
Take something up with AOL??????? ... Surely, you jest!
 
Lyle said:
Yes, it goes away when I remove the AIM IMAP Account. But I have been
unable to identify any specific IMAP folder that causes the problem
(the numbers 1,4,6,24 don't seem to be helpful; I've experimented but
I have not found anything).
Click to expand...

Perhaps the diagnostic log will contain more information.
 
Lyle Fairfield said:
It seems to contain only the same string as that which appears in the
Message Box.
Click to expand...

It contains no handshaking information? No record of the commands and
responses passing between the server and the client?
 
Brian said:
It contains no handshaking information? No record of the commands and
responses passing between the server and the client?
Click to expand...

Thank you for staying with me on this. Your last message prompted me to
examine these files more carefully. I found that the alerts came after
polling four particular folders. One of these had only three messages
in it. I opened AIM's webmail http interface and tried to open each of
these messages. Two of the messages would open. One would not open and
Aim reported corruption.
I suppose I could have tired deleting only that message but because the
other three folders had hundreds of messages each I wanted a more
comprehensive solution.
For each of the four folders, in AIM's webmail http interface, I
created a new folder as FolderName2. In Outlook I moved all the
messages from FolderName to FolderName2 (as the webmail interface
allowed me to select only one page of messages at a time). Corrupted
Messages could not be moved and stayed in FolderName. Again, in the
http interface I deleted FolderName and renamed FolderName 2 as
FolderName.
The alerts are gone!
(I suppose I should have checked to see how Thunderbird and Pegasus and
Windows Live Mail Desktop dealt with those folders/messages before I
deleted them but I thought of that too late. I'm proceeding on the
assumption that they don't try to access the messages until requested
to do so.)
Thanks again.
 
Brian said:
It contains no handshaking information? No record of the commands and
responses passing between the server and the client?
Click to expand...

Thank you for staying with me on this. Your last message prompted me to
examine these files more carefully. I found that the alerts came after
polling four particular folders. One of these had only three messages
in it. I opened AIM's webmail http interface and tried to open each of
these messages. Two of the messages would open. One would not open and
Aim reported corruption.
I suppose I could have tired deleting only that message but because the
other three folders had hundreds of messages each I wanted a more
comprehensive solution.
For each of the four folders, in AIM's webmail http interface, I
created a new folder as FolderName2. In Outlook I moved all the
messages from FolderName to FolderName2 (as the webmail interface
allowed me to select only one page of messages at a time). Corrupted
Messages could not be moved and stayed in FolderName. Again, in the
http interface I deleted FolderName and renamed FolderName 2 as
FolderName.
The alerts are gone!
(I suppose I should have checked to see how Thunderbird and Pegasus and
Windows Live Mail Desktop dealt with those folders/messages before I
deleted them but I thought of that too late. I'm proceeding on the
assumption that they don't try to access the messages until requested
to do so.)
Thanks again.
 
Back
Top