Gnus development mailing list
 help / color / mirror / Atom feed
From: Kirk Strauser <kirk@strauser.com>
Subject: IMAP splitting problems with Exchange server
Date: Tue, 06 Jan 2004 14:01:07 -0600	[thread overview]
Message-ID: <878ykksv7g.fsf@strauser.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1236 bytes --]

I'm using Gnus v5.10.3 (from Debian/unstable) to read mail on an Exchange
5.5 server via IMAP.  It works well in general, but I'm having problems
splitting my incoming mail.

I'm using a simple group mail splitting setup ('to-address' group parameters
defined where appropriate), and if I visit my inbox ('nnimap+lan:INBOX' and
hit 'B q' on a mail that I think should be split into another group, I get
the expected result (example: 'This message would go to zope.user').
However, if I try to respool the message with 'B r', I get errors like:

Copying to nnimap: (1503)...
Protocol Error: "Invalid ASTRING for folder name found in APPEND command"
Couldn't Copy article 1503: Protocol Error: "Invalid ASTRING for folder name found in APPEND command"
nnimap: Updating info for nnimap+lan:INBOX...done

My "test" group was originally named "Mailing lists/Zope", but I thought
that the "/" might be causing the problem, so I created the new "zope.user"
group and moved all of the "Mailing lists/Zope" messages into it.

Any thoughts of where I might look to troubleshoot or fix this?  I'm going
crazy with having all of my mail come into my inbox - how can people without
mail filters stand this?
-- 
Kirk Strauser

[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]

             reply	other threads:[~2004-01-06 20:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-06 20:01 Kirk Strauser [this message]
2004-01-06 21:33 ` Kai Grossjohann
2004-01-06 22:14   ` Kirk Strauser
2004-01-07  8:31     ` Kai Grossjohann
2004-01-07 15:21       ` Kirk Strauser
2004-01-07  8:54 ` Yair Friedman
2004-01-07 15:30   ` Kirk Strauser
2004-01-07 19:20     ` Simon Josefsson
2004-01-07 22:00       ` David S Goldberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878ykksv7g.fsf@strauser.com \
    --to=kirk@strauser.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).