I have a problem related to imap with mozilla-1.5/netscape 7.1 or any
recent mozilla version. It relates to the state if the client/server
connection, duplicate INBOX messages, the semantics of the INBOX.msf
file and such. Please read on:
1. I have an external email account with an IMAP interface
and clients on multiple machines.
2. Because of space limitations, I periodicaly must delete messages on
the server (not using the client, but directly via the email provider
3. Hence my local INBOX contains more messages than the server, which
is all fine and dandy (most of the time).
Here is the problem:
Every once in a while the client/server get into a funny mutual state
and the client (or maybe it is the server) decides to download ALL my
messages again. Now I have an INBOX which is 1.5X the size it should be
(remember, not 2x, since I have deleted some messages on the server). So
I fire up "mutt -f INBOX" and delete all the duplicate messages with
some mutt wizardry. Now of course INBOX.msf is wrong, so I have to
restore it somehow. So I remove INBOX.msf, restart the client, and hope
that netzilla will rebuild it for me. But no, it uses the server-side
(incomplete) INBOX as source, and now I have a complete INBOX with an
incomplete INBOX.msf, and I cannot see all the messages in the INBOX
from the client (I still can from mutt, but I want netzilla!).
My global question is simple: After doctoring the INBOX, how can I get
netzilla and the server both into a good state where the INBOX.msf is in
good shape and everyone is happy?
Some related questions are:
Q1. How can I get netzilla to create the INBOX.msf from the local INBOX
file instead of the server INBOX file?
Q2. ...and at the same time avoid that the server thinks I'm out of sync
and dump more duplicate mail at me?
I know one way of solving Q1 (make a copy of INBOX to local folder/file
dummyINBOX, delete the duplicates in mutt, delete dummyINBOX.msf,
restart netzilla, watch it recreate dummyINBOX.msf, copy to
INBOX.msf). The problem is when I replace INBOX.msf, netzilla gets in
the funny state again, and starts wanting to dump email one me.
Q3. How can I doctor the INBOX.msf file so that the server thinks I'm
up to date??
Q4. Is there a standalone/commandline inbox2msf program anywhere?
Q5. Where is the INBOX.msf format documented?
Q6. How does he client/server decide from INBOX.msf that all the
messages need to be transferred again.
I did hunt around on the web and usenet quite a bit to try and answer
but no luck. Are there and netscape/mozilla/imap wizards out there that
can lend a hand?
Bonus question: Why doesn't the mozilla/netscape email client allow
quick selection of messages that are TO some user, only FROM some user?
The msf file seems to contain all the email addresses, so why not?