On Tue, Apr 19, 2022 at 09:45:12PM -0600, @lbutlr wrote:
> On 2022 Apr 15, at 16:53, Viktor Dukhovni wrote:
> > On Fri, Apr 15, 2022 at 04:30:19PM -0600, @lbutlr wrote:
> >
> >> However, it is *very* common for a BBC email to have a To header with
> >> no email address in it at all,
> >
> > Thi
On 2022 Apr 15, at 16:53, Viktor Dukhovni wrote:
> On Fri, Apr 15, 2022 at 04:30:19PM -0600, @lbutlr wrote:
>
>> However, it is *very* common for a BBC email to have a To header with
>> no email address in it at all,
>
> This violates RFC5322 and earlier versions.
No it does not.
> The "To:" h
On Tue, Apr 19, 2022 at 03:25:53PM -0300, SysAdmin EM wrote:
> should also be corrected in the file sender_canonical?
>
> /@gmail.com/ nore...@kiusys.com
>
> /@gmail.cl/ nore...@kiusys.com
>
> /@hotmail.com/ nore...@kiusys.com
>
> /@outlook.com/ nore...@kiusys.com
>
> /@satena.com/ nore...@ki
On Tue, Apr 19, 2022 at 05:33:50PM -0700, Dan Mahoney wrote:
> Does postfix have any support for TLS reporting (RFC8460)?
>
> Technically, one need not be using MTA-STS to benefit from this. We
> get monitoring of this with our dmarc monitoring provider, and it
> feels like it would be useful to
Hey there,
Does postfix have any support for TLS reporting (RFC8460)?
Technically, one need not be using MTA-STS to benefit from this. We get
monitoring of this with our dmarc monitoring provider, and it feels like it
would be useful to send these reports as well.
-Dan
SysAdmin EM:
> Thanks for the help.
>
> should also be corrected in the file sender_canonical?
>
> /@gmail.com/ nore...@kiusys.com
> ...
> /@.*/ nore...@kiusys.com
Sorry, I can't help you with that.
Wietse
Thanks for the help.
should also be corrected in the file sender_canonical?
/@gmail.com/ nore...@kiusys.com
/@gmail.cl/ nore...@kiusys.com
/@hotmail.com/ nore...@kiusys.com
/@outlook.com/ nore...@kiusys.com
/@satena.com/ nore...@kiusys.com
/@mayair.com/ nore...@kiusys.com
/@gmail.co/ nore..
> On 19 Apr 2022, at 10:22 am, Wietse Venema wrote:
>
> If you must do this, why not copy the entire From: value?
>
>/^From:(.+@example\.com\b.+) Reply-To:$1
>
> Note: the \b matches a word boundary, and the \. matches . instead
> of every character.
Since '\b' will also match before a
Wietse Venema:
> SysAdmin EM:
> > Hi!!
> >
> > I am using the prepend option as follows:
> >
> > / From: (.*@mydomain.com)/ PREPEND Reply to: $1
> >
> > When the mail arrives I see that it does this way:
> >
> > Reply-to: "nore...@equair.com.ec" < >
> > I see an additional symbol added (<)
>
SysAdmin EM:
> Hi!!
>
> I am using the prepend option as follows:
>
> / From: (.*@mydomain.com)/ PREPEND Reply to: $1
>
> When the mail arrives I see that it does this way:
>
> Reply-to: "nore...@equair.com.ec" <
> I see an additional symbol added (<)
The '<' was already present in the From:
Hi!!
I am using the prepend option as follows:
/ From: (.*@mydomain.com)/ PREPEND Reply to: $1
When the mail arrives I see that it does this way:
Reply-to: "nore...@equair.com.ec" <
11 matches
Mail list logo