At 03:07 PM 8/20/99 +0200, Vincent Lefevre wrote:
On Fri, Aug 20, 1999 at 04:40:40 +0300, Mikko Hänninen wrote:
[snip]
Maybe a quick hack would be best here, like writing a script that
would first remove the Delivered-To header and then remail it
manually (eg. "grep -v ^Delivered-To:" piped to
Try the attached patch. I'll also put it into stable.
Index: copy.c
===
RCS file: /home/roessler/cvsroot/mutt/copy.c,v
retrieving revision 2.4
diff -u -u -r2.4 copy.c
--- copy.c 1999/02/02 15:47:51 2.4
+++ copy.c
On Fri, Aug 20, 1999 at 04:40:40 +0300, Mikko Hänninen wrote:
I'm not sure what is the "right way" to solve your problem. Both
mutt and qmail are working as they have been designed to do. You
might want to ask for suggestions on the qmail list, as this is more
of a qmail than mutt problem
Vincent --
...and then Vincent Lefevre said...
%
% Is there a way to remove the delivered-to line when bouncing a message?
From the bounce command in mutt, I don't think so. It would be a
little ugly, but you could always save the message to another mailbox,
edit that mailbox and remove any
David Thorburn-Gundlach [EMAIL PROTECTED] wrote on Thu, 19 Aug 1999:
Oh, yeah -- I got sidetracked above :-) I'm no pop expert, but I've
bounced messages to myself and to friends before, and they always get
it. Why do you say that the delivered-to entry for ens-lyon.fr caused
it to not be
On Thu, Aug 19, 1999 at 17:31:12 +0300, Mikko Hänninen wrote:
David Thorburn-Gundlach [EMAIL PROTECTED] wrote on Thu, 19 Aug 1999:
Oh, yeah -- I got sidetracked above :-) I'm no pop expert, but I've
bounced messages to myself and to friends before, and they always get
it. Why do you say
Vincent Lefevre [EMAIL PROTECTED] wrote on Fri, 20 Aug 1999:
This may actually be qmail's loop detection kicking in... At least
that's what I'd guess.
Yes: the message comes from vinc17.org, it has automatically been
forwarded to [EMAIL PROTECTED], and I've bounced it to vinc17.org.
I'm
