Re: Goal: Setup transport that runs a header check to strip out specific header for emails from specific source

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

Re: Goal: Setup transport that runs a header check to strip out specific header for emails from specific source

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

Re: Goal: Setup transport that runs a header check to strip out specific header for emails from specific source

On 5/10/2016 11:07 AM, Viktor Dukhovni wrote: On Tue, May 10, 2016 at 01:15:59AM -0500, deoren wrote: # sender_dependent_default_transport_maps.conf # # This entry is matching against gmail.com because Google Calendar # delivers notifications to your associated Gmail account. To # receive them

Re: Goal: Setup transport that runs a header check to strip out specific header for emails from specific source

On Tue, May 10, 2016 at 01:15:59AM -0500, deoren wrote: > # sender_dependent_default_transport_maps.conf > # > # This entry is matching against gmail.com because Google Calendar > # delivers notifications to your associated Gmail account. To > # receive them on your outside email account you have

Re: Goal: Setup transport that runs a header check to strip out specific header for emails from specific source

On 5/7/2016 2:18 PM, Viktor Dukhovni wrote: > >> On May 7, 2016, at 8:31 AM, Wietse Venema wrote: >> >>> What I'm currently trying to get working is a service entry in master.cf >>> that has its own header checks conf file. This service would only be >>> used for specific

Re: Goal: Setup transport that runs a header check to strip out specific header for emails from specific source

On 2016-05-07 19:16, /dev/rob0 wrote: On Sat, May 07, 2016 at 11:05:07AM +0200, Christian Kivalo wrote: On 2016-05-07 10:27, Viktor Dukhovni wrote: >On Sat, May 07, 2016 at 09:59:00AM +0200, Christian Kivalo wrote: > >>>Looking at those emails, I see that >>>calendar-notificat...@google.com is

Re: Goal: Setup transport that runs a header check to strip out specific header for emails from specific source

On Sat, May 07, 2016 at 11:05:07AM +0200, Christian Kivalo wrote: > On 2016-05-07 10:27, Viktor Dukhovni wrote: > >On Sat, May 07, 2016 at 09:59:00AM +0200, Christian Kivalo wrote: > > > >>>Looking at those emails, I see that > >>>calendar-notificat...@google.com is the source address. I added >

Re: Goal: Setup transport that runs a header check to strip out specific header for emails from specific source

> On May 7, 2016, at 8:31 AM, Wietse Venema wrote: > >> What I'm currently trying to get working is a service entry in master.cf >> that has its own header checks conf file. This service would only be >> used for specific sender addresses in order to limit the header

Re: Goal: Setup transport that runs a header check to strip out specific header for emails from specific source

On 5/7/2016 7:31 AM, Wietse Venema wrote: > deoren: >> What I'm currently trying to get working is a service entry in master.cf >> that has its own header checks conf file. This service would only be >> used for specific sender addresses in order to limit the header removal >> to just those

Re: Goal: Setup transport that runs a header check to strip out specific header for emails from specific source

deoren: > What I'm currently trying to get working is a service entry in master.cf > that has its own header checks conf file. This service would only be > used for specific sender addresses in order to limit the header removal > to just those email notifications generated by Google Calendar.

Re: Goal: Setup transport that runs a header check to strip out specific header for emails from specific source

On 2016-05-07 10:27, Viktor Dukhovni wrote: On Sat, May 07, 2016 at 09:59:00AM +0200, Christian Kivalo wrote: >Looking at those emails, I see that calendar-notificat...@google.com is >the source address. I added the entry to my check_sender_access table >with an action of 'FILTER

Re: Goal: Setup transport that runs a header check to strip out specific header for emails from specific source

On Sat, May 07, 2016 at 09:59:00AM +0200, Christian Kivalo wrote: > >Looking at those emails, I see that calendar-notificat...@google.com is > >the source address. I added the entry to my check_sender_access table > >with an action of 'FILTER strip-automated-headers:' > > You could probably get

Re: Goal: Setup transport that runs a header check to strip out specific header for emails from specific source

Since Postfix (2.11) is my MTA and it supports removing headers, I'd like to have it strip this one. I found that I can include this line in the same file I use for the other header checks applied to ALL mail: /^Auto-Submitted:/IGNORE but then it will affect all mail and I'd rather not

Goal: Setup transport that runs a header check to strip out specific header for emails from specific source

Hi, I use Google Calendar to remind me of various tasks to complete. I want to setup an event, add an email reminder for the event and then setup a Sieve filter for Dovecot (processed by Pigeonhole) to generate a notification to an email-to-text gateway address so I can receive a short text