Gnus development mailing list
 help / color / mirror / Atom feed
From: Henrik Grindal Bakken <hgb@ifi.uio.no>
To: ding@gnus.org
Subject: Gnus issues with exchange 2003
Date: Wed, 17 Nov 2010 15:54:56 +0100	[thread overview]
Message-ID: <x2eaal86lvj.fsf@anakin.ifi.uio.no> (raw)


Hi.  At work, I'm stuck with an exchange 2003 server, which I've been
living relatively peacefully with for a while (or perhaps in a truce),
but today I upgraded my emacs (from the git clone of the bzr tree),
giving me a fresh gnus version (it claims 5.13).

Now, this has caused all sorts of problems, not only with the exchange
server.

First question first:
I have this setup
     (setq secondary-select-methods
        '((nnimap "uio"
                   (nnimap-stream ssl)
                   (nnimap-address "localhost")
                   (nnimap-server-port 10993)
                   (nnir-search-engine imap)
                   (imap-username "x"))
           (nnimap "gmail"
                   (nnimap-address "localhost")
                   (nnimap-server-port 10994)
                   (nnimap-stream ssl)
                   (nnir-search-engine imap)
                   (imap-username "y@gmail.com"))
           (nnimap "cisco"
                   (nnimap-address "email.cisco.com")
                   (nnimap-stream ssl)
                   (nnir-search-engine imap)
                   (imap-username "z"))
           (nnimap "tandberg"
                   (nnimap-address "some-internal-imap")
                   (nnimap-stream network)
		   ;(nnimap-stream ssl)
                   (nnir-search-engine imap)
                   (imap-username "xyz"))))

This used to work very well, and the different usernames where used by
default on the different servers.  With the new nnimap, I get asked
for username for each server, and it will always default to my unix
username.  This I could live with (at least if using .authinfo.gpg),
but one problem is that for the "gmail" server, it doesn't ask at all,
it just reuses the username/password from the "uio" server.

Second problem:
On the "tandberg" server, there are lots and lots of shared folders.
Previously, gnus used to find all of them, and I'd deselect them, but
now it finds some 6 or 7 folders in the same subfolder, and nothing
else, most notably my INBOX.

I tried to do a 'a01 LIST "" "*"', and the server responds with lots
and lots of folders.

The *imap log* buffer tells me little.  It has:

14:52:34 393 LIST "" "*"
14:52:35 394 EXAMINE "Public Folders/..."
with the last line repeated (with 395, 396, etc) for a dozen or so
folders, but none of the ones I actually want.


-- 
Henrik Grindal Bakken <hgb@ifi.uio.no>
PGP ID: 8D436E52
Fingerprint: 131D 9590 F0CF 47EF 7963  02AF 9236 D25A 8D43 6E52




             reply	other threads:[~2010-11-17 14:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-17 14:54 Henrik Grindal Bakken [this message]
2010-11-18  9:31 ` Henrik Grindal Bakken
2010-11-21  4:54   ` Lars Magne Ingebrigtsen
2010-11-22 13:24     ` Henrik Grindal Bakken
2010-11-24 21:14       ` Lars Magne Ingebrigtsen

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=x2eaal86lvj.fsf@anakin.ifi.uio.no \
    --to=hgb@ifi.uio.no \
    --cc=ding@gnus.org \
    /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).