From: Hadron <hadronquark@gmail.com>
To: info-gnus-english@gnu.org
Subject: Re: info-gnus-english Digest, Vol 49, Issue 12
Date: Sat, 12 May 2007 16:01:11 +0200 [thread overview]
Message-ID: <87odkqw388.fsf@gmail.com> (raw)
In-Reply-To: <mailman.542.1178943769.32220.info-gnus-english@gnu.org>
nospam@dev.null (Alexey Pustyntsev) writes:
> info-gnus-english-request@gnu.org writes:
>
>> MTAs) you'll probably have a better time of it. That MTA also receives
>> the mail for you if you have local delivery. AFAIK gnus cannot deliver
>> mail to you, but needs a backend (calling fetchmail, for instance).
>
> Hi all!
>
> I must tell you guys from my unpleasant experience that fetchmail
> sucks. It has many bugs, security holes and needlessly complex
> configuration file. I used fetchmail + gnus for more than half a
> year. Everything seemed to be OK in the beginning, then, strange
> things started happening like reinjecting over a hundred old messages,
> each of which was scrupulously marked by the gnus as 'duplicate'. When
> I figured out that it was fetchmail's fault I immediately switched to
> getmail (highly recommended), which I've been using successfully since
> that. Yes, just use getmail. It is free, simple, clean and very
> reliable as it was specifically designed to ensure that your mail is
> never lost or misdirected.
And fetchmail was designed to lose and misdirect your mail?
Does anyone else back up these claims?
I have been using fetchmail with procmail for over a year with no issues
whatsoever. Is it better to use "getmail"?
btw, how is fetchmail "insecure"?
next prev parent reply other threads:[~2007-05-12 14:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070511155842.3D0CB149CE@sycore.org>
2007-05-12 4:18 ` Alexey Pustyntsev
[not found] ` <mailman.542.1178943769.32220.info-gnus-english@gnu.org>
2007-05-12 14:01 ` Hadron [this message]
2007-05-13 9:44 ` Kamen TOMOV
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=87odkqw388.fsf@gmail.com \
--to=hadronquark@gmail.com \
--cc=info-gnus-english@gnu.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).