From: Martin Steffen <msteffen@ifi.uio.no>
Subject: Re: failure of gnus to determine boundaries of emails
Date: 15 Oct 2006 13:46:18 +0200 [thread overview]
Message-ID: <m3r6x9er91.fsf@cm-84.209.8.188.chello.no> (raw)
In-Reply-To: <v9odsdhn32.fsf@marauder.physik.uni-ulm.de>
>>>>> "Reiner" == Reiner Steib <reinersteib+gmane@imap.cc> writes:
Reiner> On Sat, Oct 14 2006, Martin Steffen wrote:
>> PS: I'm working with emacs-version 21.4.1 nd gnus-version v5.9.0
Reiner> Gnus 5.9 is old. Could you upgrade to 5.10.8 (latest stable
Reiner> release) or to Emacs 22 (CVS, but quite stable; it will enter
Reiner> pretest soon) which includes 5.11.
I guess, I won't be able to convince the admins here that they should live
on the CVS cutting edge... They will support the default emacs/gnus
combination which comes shipped (resp. upgraded) with their Red-Hat
distribution, and I guess that's understandable. I might try on my laptop
though
Reiner> I don't think the problem lies in Gnus. I use a similar setup
Reiner> (but with nnml) without any problems:
Actually, I at least guess, it's not a gnus/emacs-version problem, since I
use the same set-up for ages, at least since emacs-19 (or even 18) and the
corresponding neolithic gnus-version back then :-)
However, here nobody seems able to can help, all are content with
squirrel-web-access, but I'm not yet ready to give-up :-)
Maybe you are right, and the problem is not gnus. Because, at my laptop I
have in the meantime managed, and there it was _not_ the error of gnus (at
least as far as I understand). It seems that the way I used fetchmail
caused the problem.
To be more specific: using the following two different
.fetchmailrc-specifications:
(1) poll server.some.where with proto IMAP user 'user1' there is 'user2' here options keep fetchall ssl
(2) poll server.some.where with proto IMAP user 'user1' there is 'user2' here and wants mda "/usr/bin/procmail" options keep fetchall ssl
(1) now works at my laptop, (2) on the other hand fetches the emails, procmail split
them into nnfolder-files, and gnus reads them in, but with the mentioned problem
of not finding the boundaries appropriately.
So far, so good, the problem is that (1) does _not_ work at my desktop at work, with
the same emacs-version and the same gnus-version and the same settings. Probably, I will have to
find out how I can use fetchmail in that environment, since (1) does not work at all, and
(2) has the mentioned problem.
Anyway, my gnus settings are:
- mail-source-directory = ((directory :path "~/Mail/spool/" :suffix ".spool"))
- mail-sources = ((directory :path "~/Mail/spool/" :suffix ".spool"))
- gnus-secondary-select-methods's value is
((nnfolder "")
(nntp "news.gmane.org"))
- gnus-default-nntp-server's value is "news.uio.no"
- gnus-directory's value is "~/Mail/spool/"
and furthermore:
(setq nnmail-use-long-file-names t)
(setq nnmail-tmp-directory "~/Mail/spool")
(setq nnmail-use-procmail t)
(setq nnmail-procmail-directory "~/Mail/spool")
But, as indicated, maybe indeed gnus is not the culprit (unlike I said),
since at least on one machine the configuration works now. Only
not yet at work.
I try to research that further, and also I try to compare the format of the
spool-files to see what influence the "mda"-specification has on it.
Martin
prev parent reply other threads:[~2006-10-15 11:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-14 13:32 Martin Steffen
2006-10-15 10:48 ` Reiner Steib
2006-10-15 11:46 ` Martin Steffen [this message]
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=m3r6x9er91.fsf@cm-84.209.8.188.chello.no \
--to=msteffen@ifi.uio.no \
/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).