On 5/10/2016 2:07 PM, Viktor Dukhovni wrote:
On Tue, May 10, 2016 at 01:46:57PM -0500, deoren wrote:
# match on ALL Gmail accounts.
@gmail.com autosieve
I would not expect the messages generated by Sieve to be sent from
"gmail.com". These auto-generated messages are created on your
machine, and should be sent by some user on your machine (envelope
sender, not rfc822 "From:" header). Figure out which user sends
Sieve-generated mail.
The incoming Google Calendar notifications from Google's servers are what
I'm attempting to match against. Once I get that working I would enable the
local Sieve script.
That won't work, because "sender_dependent_default_transport_maps"
only modifies the "default" transport, and will almost never affect
the delivery of inbound mail.
I thought you wanted to strip "Auto-Submitted" from outbound mail.
If you need this to happen upstream of inbound delivery to Sieve,
you need a different solution.
Please correct me if I am wrong, but even if I send to the local
delivery agent that's still not "outbound" from the perspective of
Postfix, so that wouldn't work either, right?
My goal is to match on the incoming notifications from a remote server,
strip out the Auto-Submitted header so a local Sieve rule will agree to
match against those emails and then generate a new custom notification email
(not using any of the existing text, headers, etc).
I think you need to convince Sieve to selectively violate RFC3834,
perhaps there's a way to do that in Sieve.
If I can't convince Pigeonhole to allow me to violate that RFC, then I
suppose I would have to do what Wietse mentioned and use a content
filter. Perhaps accept the whole email, strip the specific header and
then send back to the submitting email address?
Thanks for your help with this.
