[OFF TOPIC] Re: Pigeonhole Sieve Vacation Reply-To peculiarity with inbound AWS-SES

[Marc]

> 
> >> The actual problem is that Pigeonhole responds to to=<010301863b0211fe-
> 9416f5b2-7e18-4c03-a5e5-2204dd7946f8-000000 at sa-east-1.amazonses.com> instead
> of to=<rolf at example.de>.
> 

Yes indeed, why are companies misusing the envelope for something different than it should be. The worst thing is even that these uniquely generated envelopes are often not accepting email on them, as the RFC's describe.

Set your envelope correctly to rolf at example.de