Gnus development mailing list
 help / color / mirror / Atom feed
From: Daniel Simms <dsimms@alink.net>
Subject: pop mailboxes
Date: 03 Feb 1997 15:32:58 -0800	[thread overview]
Message-ID: <x5bua18nyt.fsf@ba.alink.net> (raw)

hi all,

Well, I (finally!) started using gnus for email over the weekend and 
I have some problems, of course.  Whee!

Pop mail spool files, which begin with "^po:", get caught by ange-ftp
after the first *get-new-news.  It's only after the first fetching
since nnmail-get-new-mail loads ange-ftp's password reading function
halfway through the first pass.  I couldn't see how to cleanly fix
this, so I tried forcing ange-ftp to unload at the end of fetching
mail, but that didn't really work since ange-ftp has all sorts of
other non-gnus functions hooked from hell to breakfast.  I ended up
tweaking nnmail to also look for "^po;" and used that instead of
"po:".

While respooling old mail, I noticed that splitting into a
non-existant group isn't so useful.  Is there some way to get gnus to
auto-create non-existant groups?

I check mail from several different pop mailboxes, and wrapped
pop3-movemail so that I could explicitly specify maildrop, host, port,
authentication scheme, and password in the spool file variable, more
like vm does.  And then I was bored so I added some code to save the
passwords on sucessful authorization.  (I also added some flags to
allow leaving mail on the server, which isn't all that useful except
for some testing, since I haven't added the UIDL matching code yet.)
Does anybody want this?  Richard, Lars?


Anyway, thanks again to everybody who makes gnus work.

-- 
Daniel Simms           "You don't have to pretend to be interested in 
dsimms@alink.net        me you know.  I know I'm only a menial robot."
(408) 720-6161                           -- Marvin, _HhGttG_


             reply	other threads:[~1997-02-03 23:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-02-03 23:32 Daniel Simms [this message]
1997-02-04 19:41 ` Lars Magne Ingebrigtsen
1997-02-04 23:00   ` Daniel Simms
1997-02-04 23:13     ` Lars Magne Ingebrigtsen
1997-02-04 23:55       ` Daniel Simms
1997-02-05  1:41         ` Lars Magne Ingebrigtsen
1997-02-05  5:03           ` Paul Franklin
1997-02-05  9:01           ` Daniel Simms
1997-02-05  3:08         ` Rich Pieri
1997-02-05  8:35           ` Daniel Simms
1997-02-05 16:13             ` Rich Pieri
1997-02-05  4:50         ` Paul Franklin

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=x5bua18nyt.fsf@ba.alink.net \
    --to=dsimms@alink.net \
    /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).