bouncing email and "from" address

[Jan Eden]

On 2024-07-24 17:49, Ofer Inbar wrote:

> On Wed, Jul 24, 2024 at 09:17:13PM +0100,
> Peter Flynn <peter at silmaril.ie> wrote:
> > >However .. when I use the "bounce" feature, mutt is not using my From:
> > >header.  It's generating a From: address using the actual name of the
> > >individual host, hymie at alfred.nasalinux.net , and I don't want it to
> > >do that.
> > 
> > My understanding is that this EXACTLY NOT the behaviour of 'b'. I
> > used to use 'b' a lot in client support, when someone would email me
> > with a query that should really be dealt with by someone else. So it
> > should work like Forward, but it explicitly NOT mess with the
> > headers, and preserve the original sender, so that the recipient is
> > completely unaware that it has been "rerouted" through my mailbox.
> > The most important thing is that when they reply the reply CORRECTLY
> > goes back to the person who send it. With Forward, the reply would
> > come back to me, which would be completely pointless.
> > 
> > Why yours is creating a different address is a mystery to me.
> 
> mutt's "bounce" is the email standard re-send feature.
> It should send a message with a series of new headers added:
>   Resent-From: 
>   Resent-Date: 
>   Resent-Message-ID: 
>   Resent-To: 

My current employer's SMTP server unfortunately prevents bounces,
because I am not authorized to send messages on behalf of the original
senders (Resent-* headers are obviously not taken into account). This is
unfortunate, because I relied heavily on this feature in previous years.

- Jan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <http://lists.mutt.org/pipermail/mutt-users/attachments/20240725/ad98d559/attachment.asc>