From: Harry Putnam <reader@newsguy.com>
Subject: Re: [nnimap] make gnus look in specific dir on server
Date: Tue, 18 Nov 2003 09:12:44 -0600 [thread overview]
Message-ID: <m3brr9ww0j.fsf@newsguy.com> (raw)
In-Reply-To: <iluy8ud3hbt.fsf@latte.josefsson.org>
Simon Josefsson <jas@extundo.com> writes:
> Harry Putnam <reader@newsguy.com> writes:
>
>> Simon Josefsson <jas@extundo.com> writes:
>>
>>> Harry Putnam <reader@newsguy.com> writes:
>>>
>>>> How can I make gnus thru nnimap look at the mail spool on the imap
>>>> server?
>>>>
>>>> Using the simple setup from gnus info I'm taken to the username
>>>> $HOME. But the mail is at /var/spool/imap/mail/$LOGNAME on the
>>>> server.
>>>
>>> This is server-specific, so you need to ask the server admins, but I
>>> believe some servers map the mail spool to INBOX in IMAP.
>>
>> Well, it works from Mozilla with that same server. That is, in
>> Mozilla setup it asks for the path to the spool, then looks there for
>> mail. So there must be someway to pass that info from nnimap.
>
> Does it work to subscribe to the group
> nnimap+192.168.0.4:/var/spool/imap/mail/$LOGNAME? Adding it to
> nnimap-list-pattern is another option, if you prefer to subscribe to
> groups via the server buffer.
> This is server-specific, so you need to ask the server admins, but I
> believe some servers map the mail spool to INBOX in IMAP.
Forgot to mention: It is the University of Washington server (UM)
And that I am the poor excuse for an admin on that server. I
compiled it specifically to look in /var/spool/imap/mail/$LOGNAME.
That location works from both mutt and Mozilla. Mozilla asks for the
path during setup. With mutt I can get there like this
mutt -f mutt -f imap://$LOGNAME@$HOST//var/spool/imap/mail/$LOGNAME
I've tried this too:
[...]
(nnimap-address "192.168.0.4:/var/spool/imap/mail/reader_exp")
[...]
Subscribing as you suggested like this:
U nnimap+192.168.0.4:/var/spool/imap/mail/reader_exp
Does work. However when pressing <RET> on the resulting server, it
still takes me to ~/$LOGNAME on the server. I'm experimenting with
the pattern now.
Looks like this works:
(nnimap-list-pattern ("/var/spool/imap/mail/*"))
Although I end up with long group names that way.
I think this must mean my compile job on imap didin't do what I
thought it would. Its still passing out ~/ as default.
next prev parent reply other threads:[~2003-11-18 15:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-18 5:05 Harry Putnam
2003-11-18 6:19 ` Simon Josefsson
2003-11-18 13:57 ` Harry Putnam
2003-11-18 14:02 ` Simon Josefsson
2003-11-18 15:12 ` Harry Putnam [this message]
2003-11-18 20:45 ` Kai Grossjohann
2003-11-18 22:01 ` Harry Putnam
2003-12-29 21:38 ` Steinar Bang
2003-12-29 22:29 ` Steinar Bang
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=m3brr9ww0j.fsf@newsguy.com \
--to=reader@newsguy.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).