On Nov 4, 2007, at 1:28 PM, Roxanne Sandesara wrote:
Instead of simply assuming that the newest iteration of Apple's Mail
client is at fault - or not - let's actually constructively try to
determine wherein the problem does lie. I am afraid I myself do not
yet have access to a Leopard installation, so I cannot perform these
steps. But my suggestion would be:
Agreed.
1) Attempt each of the functions that have yielded reproduceable
problems thus far, Harry.
2) At each attempt, then check the log files generated by Courier-
IMAP to see if you can find associated errors on that end.
3) If possible (not sure if you have a Mac developer's kit handy),
seek out the log files being generated by Mail on the local machine,
to see if you can find the recorded error messages when Mail makes
these attempts.
I'll see if I can capture some of this information.
Someone else has done something similar:
http://www.nabble.com/courier-imap-issues-on-deleting-mails-with-Mail.app-on-OS-X-10.5%09%28leopard%29---tf4698374.html
In the meantime...
If we can gather the error messages, we may be able to determine, at
the least, what the miscommunication is between Mail and Courier-
IMAP. It would seem clear that Mail is sending commands to the IMAP
server. And that these commands are not being understood by QMT's
Courier-IMAP server.
The error message displayed on the client's side is:
The IMAP command "UID COPY" failed for the mailbox "INBOX" with this
server error: Error in IMAP command received by server...
other errors reported, when trying to move files into a folder, was:
The IMAP command “APPEND” (to Drafts) failed with server error:
Invalid mailbox name.."
This appears oddly similar to problems encountered back under OS X
10.3 (Panther), whereas the problem was also related to the naming of
the INBOX (as far as I recalled, it *had* to be all caps INBOX, or
else problems would manifest, and *again* this was restricted to
Courier-IMAP implementations.
Details:
http://www.macosxhints.com/article.php?story=2003111411334739
http://www.mail-archive.com/[EMAIL PROTECTED]/msg02461.html
http://www.nabble.com/courier-imap-issues-on-deleting-mails-with-Mail.app-on-OS-X-10.5%09%28leopard%29---tf4698374.html
Let's find out what is being sent and make sure that it is in fact
correct. If it is in fact correct, then it can be presented as an
error to those maintaining Courier-IMAP for resolution. If it is
not, but the other systems you have tested against are managing to
account for its imperfect structure, then at least you have
something to then present to Apple so that they can make the attempt
to track down and fix the problem on their end.
Seeing as how some of the above are taken from the Courier-IMAP
mailing list, it is starting to get on their radar. How it will be
addressed is another issue.
Apple may be standards-compliant nearly to a fault, but they are not
infallible. Let us approach the situation calmly, rationally, and
methodically.
Agreed. It just irks me when the standard response to bringing
attention to an issue, or potential issue is "Tell Apple to fix their
shit" (which is the knee-jerk reaction I received from 2 other sources
earlier today).
As for me, in the immediate future, I moved some affected accounts of
clients using Leopard and/or iPhones to my Postfix/Dovecot
combination, which appears to be doing just fine, and is reporting no
issues.
Harry