Vivien M. wrote:
it does look like Randy hit the bounce option in pine
A bounce that does not say "undeliverable"?
Michel.
Vivien M. wrote:
it does look like Randy hit the bounce option in pine
A bounce that does not say "undeliverable"?
Michel.
I tried this, in Pine it adds:
Resent-Date: Wed, 15 Oct 2003 07:06:06 +0200 (CEST)
Resent-From: Mikael Abrahamsson <swmike@swm.pp.se>
Resent-Subject: RE: Extreme BlackDiamond
to the headers, that's it. Also, it just continues to add to the
SMTP-headers of the email (doesnt start fresh with what mail servers has
been passed), so I am not sure that theory holds water that this was an
accident.
## On 2003-10-14 21:51 -0700 Michel Py typed:
> Vivien M. wrote:
> it does look like Randy hit the bounce option in pineA bounce that does not say "undeliverable"?
That would be manual bounce(that is resend with the same headers/body)
and _not_ an MTA bounce
Mikael Abrahamsson writes on 10/15/2003 10:42 AM:
to the headers, that's it. Also, it just continues to add to the
SMTP-headers of the email (doesnt start fresh with what mail servers has
been passed), so I am not sure that theory holds water that this was an
accident.
In mutt, it'd be "edit and resend as new" -
esc e
Add something like: bcc: nanog@merit.edu
:wq
In mutt you can simply 'bounce' to nanog@merit.edu with the same effect and
less keystrokes.
Joe Rhett writes on 10/15/2003 3:36 PM:
In mutt, it'd be "edit and resend as new" -
esc e
Add something like: bcc: nanog@merit.edu
:wqIn mutt you can simply 'bounce' to nanog@merit.edu with the same effect and
less keystrokes.
But the guy said he didn't want previous smtp headers to be preserved.
"b" would preserve the previous headers in the email.