Displaying 3 results from an estimated 3 matches for "sonic308".
2019 Apr 09
2
sieve match ANY header
...>
List-Subscribe: <http://121.242.224.101/lists/admin/?p=subscribe>
List-Unsubscribe: <http://121.242.224.101/lists/admin/?p=unsubscribe&uid=fb545e011f371409028a40346e99f6ff&jo=1>
Message-ID: <0.0.8.0.1D4BD9273731DDA.4A40C20 at scotiabank-ses.com>
Received: from sonic308-11.consmr.mail.ne1.yahoo.com (sonic308-11.consmr.mail.ne1.yahoo.com [66.163.187.34])
Received-SPF: pass (google.com: domain of notification at facebookmail.com designates 66.220.155.142 as permitted sender) client-ip=66.220.155.142;
X-Cyberoam-smtpxy-version: 1.0.6.3
X-EN-OrigIP: 190.5.95.101...
2019 Apr 10
0
sieve match ANY header
...ist with IPs in those header. But I did check. None. Some false matches along the lines of
List-Unsubscribe: <mailto:465465-4654-117-162.xxx.xxx.xxx-gmail at abuse.*munged*.com>
> Message-ID: <0.0.8.0.1D4BD9273731DDA.4A40C20 at scotiabank-ses.com>
Not an IP
> Received: from sonic308-11.consmr.mail.ne1.yahoo.com (sonic308-11.consmr.mail.ne1.yahoo.com [66.163.187.34])
Yes, I said received.
> Received-SPF: pass (google.com: domain of notification at facebookmail.com designates 66.220.155.142 as permitted sender) client-ip=66.220.155.142;
Yes, this is also a Received header...
2019 Apr 08
2
sieve match ANY header
On 4/8/2019 4:55 PM, @lbutlr via dovecot wrote:
> On 8 Apr 2019, at 16:35, Shawn Heisey via dovecot <dovecot at dovecot.org> wrote:
>> I would like to create a sieve rule where I do a regex match on ALL headers, not a specific header.
>
> This is a really bad idea. Headers can be quite long, contain data that you do not have control over, and checking all headers will be very