Stephane Magnenat wrote:
On Saturday 15 October 2005 13.11, you wrote:
Stephane Magnenat wrote:
Package: courier-imap-ssl
Severity: normal
The debian sarge version of courier-imap-ssl (I suppose normal imap too,
btu I'm using ssl) exhibits strange behaviours for newly created
messages (not newly received). Indeed, it looks like that immediately
after uploading a message to the mail server, the mail server does not
report this message as existing. This creates buggy behaviours in some
groupware clients such as kontact (see kde bug report #113550,
https://bugs.kde.org/show_bug.cgi?id=113550).
What are "newly created" messages ? How do you upload
messages ? Which clients are exposing this bug ?
Your courier-imap configuration files ?
I'm using kontact from kde, which uses imap server to store contact, calendar
and notes entries as emails. By newly created message, I mean a newly created
contact, calendar entry or notes, i.e. a email that the imap client upload to
the imap server, not a mail received through the server mail system.
I've attached my imap related courier files. They are bare debian ones, I
haven't touched them.
Sam Varshavchik (upstream author of courier-imap) wrote to me:
--snip--
Without looking at a protocol log, the description sounds like the
client expects the server to report a new message in the folder
immediately at the conclusion of an APPEND or a COPY command.
This is wrong. There's nothing in IMAP that guarantees that the server
will report any new contents of the folder at the conclusion of an
APPEND or a COPY.
That's what the NOOP command is for.
--snap--
Can you please set IMAPDEBUGFILE in imapd configuration file and send the
resulting protocol log to me ?
Bye
Racke
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
