On July 19, 2022 8:43:16 AM UTC, Alessandro Vesely wrote:
>On Mon 18/Jul/2022 12:02:15 +0200 Scott Kitterman wrote:
>> On July 18, 2022 9:37:17 AM UTC, Alessandro Vesely wrote:
>>> On Sun 17/Jul/2022 19:05:58 +0200 John R. Levine wrote:
I made a pull request from Scott's examples, lightly
On Mon 18/Jul/2022 12:02:15 +0200 Scott Kitterman wrote:
On July 18, 2022 9:37:17 AM UTC, Alessandro Vesely wrote:
On Sun 17/Jul/2022 19:05:58 +0200 John R. Levine wrote:
I made a pull request from Scott's examples, lightly edited.
Could we please add a convoluted PSD example?
5322..From do
On July 18, 2022 9:37:17 AM UTC, Alessandro Vesely wrote:
>On Sun 17/Jul/2022 19:05:58 +0200 John R. Levine wrote:
>> I made a pull request from Scott's examples, lightly edited.
>
>
>Could we please add a convoluted PSD example?
>
>5322..From domain
>: psd.example.com
>
>5321.MailFrom domain
>
On Sun 17/Jul/2022 19:05:58 +0200 John R. Levine wrote:
I made a pull request from Scott's examples, lightly edited.
Could we please add a convoluted PSD example?
5322..From domain
: psd.example.com
5321.MailFrom domain
: mail.psd.example.com
DKIM-Signature d=
: signing.psd.example.com
Th
I made a pull request from Scott's examples, lightly edited.
Also added a few lines to the makefile to make a diff between the current
and previous versions.
Regards,
John Levine, jo...@taugh.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading
On July 17, 2022 10:56:38 AM UTC, Alessandro Vesely wrote:
>On Sat 16/Jul/2022 18:15:56 +0200 Scott Kitterman wrote:
>>> However, if you're coding the tree walk, d=; forces you to consider the
>>> assumptions you need to put on the input domain. Namely, it must neither
>>> be the root nor a PS
On Sat 16/Jul/2022 18:15:56 +0200 Scott Kitterman wrote:
However, if you're coding the tree walk, d=; forces you to consider the
assumptions you need to put on the input domain. Namely, it must neither
be the root nor a PSD. Right?
No. It doesn't come up. In 4.8, the input to the tree walk i
On Saturday, July 16, 2022 11:39:31 AM EDT Alessandro Vesely wrote:
> On Sat 16/Jul/2022 16:43:02 +0200 Scott Kitterman wrote:
> > On Saturday, July 16, 2022 7:50:04 AM EDT Alessandro Vesely wrote>>
> >
> >> [...]
> >>
> >>> A mail receiver receives an email with 5322.From domain = example.com,
>
On Sat 16/Jul/2022 16:43:02 +0200 Scott Kitterman wrote:
On Saturday, July 16, 2022 7:50:04 AM EDT Alessandro Vesely wrote>>
[...]
A mail receiver receives an email with 5322.From domain = example.com,
5322.MailFrom domain = example.com, and a DKIM signature with d =
signing.example.com. _d
On Saturday, July 16, 2022 7:50:04 AM EDT Alessandro Vesely wrote:
> Alleluia!
>
> Couple of notes below:
>
> On Sat 16/Jul/2022 09:17:54 +0200 Scott Kitterman wrote:
> > When I have implemented RFCs in the past, I have found the examples to be
> > critical to making sure I understand the RFC cor
Alleluia!
Couple of notes below:
On Sat 16/Jul/2022 09:17:54 +0200 Scott Kitterman wrote:
When I have implemented RFCs in the past, I have found the examples to be
critical to making sure I understand the RFC correctly. Generally, among my
first goals is to ensure I can replicate the example
When I have implemented RFCs in the past, I have found the examples to be
critical to making sure I understand the RFC correctly. Generally, among my
first goals is to ensure I can replicate the examples. There has been enough
back and forth on the list about how the tree walk does/does not wo
12 matches
Mail list logo
