Failure Notice (attempt to send to freebsd-test at lists.freebsd.org was rejected so trying freebsd-test at freebsd.org)

[Piotr Kozera]

your security system sucks


your security system sucks


your security system sucks


your security system sucks


your security system sucks


your security system sucks


your security system sucks


your security system sucks


your security system sucks


your security system sucks


your security system sucks


your security system sucks


your security system sucks


W dniu 24.01.2021 o 08:15, Philip Paeps pisze:
> On 2021-01-24 15:11:31 (+0800), Mark Millard wrote:
>
>> On 2021-Jan-23, at 22:40, Philip Paeps <philip at freebsd.org> wrote:
>>>
>>> On 2021-01-24 14:36:33 (+0800), Mark Millard wrote:
>>>
>>>> On 2021-Jan-23, at 22:29, Philip Paeps <philip at freebsd.org> wrote:
>>>>
>>>>> On 2021-01-23 22:25:03 (-0800), Mark Millard via freebsd-test wrote:
>>>>>> Begin forwarded message:
>>>>>>
>>>>>>> From: "Philip Paeps" <philip at freebsd.org>
>>>>>>> Subject: Re: Failure Notice (attempt to send to 
>>>>>>> freebsd-test at lists.freebsd.org was rejected)
>>>>>>> Date: January 23, 2021 at 22:13:51 PST
>>>>>>> To: "Mark Millard" <marklmi at yahoo.com>
>>>>>>>
>>>>>>> Thanks for trying ... and I've clearly not had enough coffee.
>>>>>>>
>>>>>>> The correct address is freebsd-test at freebsd.org. :-)
>>>>>>>
>>>>>>> Could you try that again please? Sorry about that!
>>>>>>>
>>>>>>> Philip
>>>>>>
>>>>>> No problem: I'll try the other email address.
>>>>>
>>>>> Thank you!
>>>>>
>>>>> Interesting ... freebsd-test is configured identically to 
>>>>> freebsd-current but *does* the DMARC munging correctly.
>>>>> I really have no idea what's going on with the freebsd-current list.
>>>>
>>>> Any chance that it is associated with listing more than
>>>> one list (cross posting)?
>>>
>>> That was what I thought originally.  When we first noticed the 
>>> problem, it was a message you cross-posted to freebsd-arm@ and 
>>> freebsd-current at .  The freebsd-arm@ list was misconfigured to not 
>>> munge.  I've since fixed that.
>>>
>>> Your most recent message to freebsd-current@ was sent only to that 
>>> list though, and it wasn't munged.  And freebsd-current@ definitely 
>>> has munging configured.  Looking more closely, I can't actually find 
>>> evidence of any address munging on freebsd-current@ ... so that list 
>>> is behaving badly.
>>
>>
>> FYI: I logged in and showed my list subscriptions:
>>
>> QUOTE
>> List subscriptions for marklmi at yahoo.com on freebsd.org
>>
>> Click on a link to visit your options page for the requested mailing 
>> list.
>>
>>     • freebsd-amd64
>>     • freebsd-arm
>>     • freebsd-current
>>     • freebsd-git
>>     • freebsd-hackers
>>     • freebsd-ports, nomail
>>     • freebsd-ppc
>>     • freebsd-stable, nomail
>>     • freebsd-toolchain
>>     • freebsd-uboot
>> END QUOTE (other than the page shows 1-10 numbering)
>>
>> So "keeps unsubscribing" for freebsd-current@ would seem to
>> mean something is also re-subscribing me: I did not
>> subscribe again.
>>
>> Although, as I remember, I had nomail for freebsd-current
>> but now it is listed as enabled (until I changed it
>> back).
>>
>> I frequently subscribe to enable sending without bothering
>> moderators --but read on line, at least for "busy" lists.
>
> Oh.  I probably inadvertently cleared your nomail bit on 
> freebsd-current@ earlier today.  Sorry about that.
>
> I'm very confused by what's up with freebsd-current at .  As far as I can 
> tell the 'munging configured but not happening' behaviour is exclusive 
> to that list.  And I can't see any settings that would cause it.
>
> Philip
>
-- 
Piotr Kozera
tel.: 794 25 22 35
e-mail: piotr.kozera at vixi.pl
Vixi Technology&Ideas Piotr Kozera
NIP 6782887315