From: "Gary R. Van Sickle" <g.r.vansickle@worldnet.att.net>
To: <cygwin@cygwin.com>
Subject: RE: fetchmail still corrupts files ?
Date: Tue, 16 Apr 2002 20:49:00 -0000 [thread overview]
Message-ID: <NCBBIHCHBLCMLBLOBONKMEEBCNAA.g.r.vansickle@worldnet.att.net> (raw)
In-Reply-To: <187370369322.20020416162553@familiehaase.de>
> I cannot confirm that fetchmail is guilty.
> I use fetchmail to retrieve all my mails and feed them to our SMTP
> server. Then I fetch them from the local POP3 server with my windows
> client. No mails with attachments are corrupted!
> So just fetching with fetchmail seems to work ( works for me(tm) )
>
> It seems that another program in the toolchain is
> causing that damage. Mutt? Procmail?
>
It's certainly possible that mutt is the guilty party, as it's rather
aggregiously Unix-text-files-only-please oriented. Do things work if you
configure mutt to go directly to your POP3 server? Or if you change the inbox
format to maildir?
I'm a changelog away from updating mutt to 1.3.28; I could send you the new .exe
if you'd like to try it and see if it makes any difference (and I'd appreciate
the additional testing). Let me know.
--
Gary R. Van Sickle
Brewer. Patriot.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2002-04-17 1:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-16 1:26 Marc Chantreux
2002-04-16 5:51 ` Gerrit P. Haase
2002-04-16 6:39 ` Jason Tishler
2002-04-16 7:59 ` Gerrit P. Haase
2002-04-16 20:49 ` Gary R. Van Sickle [this message]
2002-04-16 21:33 ` Eric Vorrie
2002-04-16 22:08 ` Eric Vorrie
2002-04-17 0:21 ` Marc Chantreux
2002-04-17 4:11 ` Gerrit P. Haase
2002-04-17 5:28 ` Jason Tishler
2002-04-17 6:06 ` Gerrit P. Haase
2002-04-17 10:57 ` Jason Tishler
2002-04-17 5:52 ` Marc Chantreux
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=NCBBIHCHBLCMLBLOBONKMEEBCNAA.g.r.vansickle@worldnet.att.net \
--to=g.r.vansickle@worldnet.att.net \
--cc=cygwin@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).