Hi Grant,

I have just seen at the Mixmin YAMN pinger that
the chains for all YAMN Remailers from Zax to your
YAMN Remailer are broken.

Regards
Stefan

On 12/3/21 11:51 AM, Stefan Claas wrote:
> Hi Grant,

Hi,

> I have just seen at the Mixmin YAMN pinger that the chains for all
> YAMN Remailers from Zax to your YAMN Remailer are broken.

I don't know what domain name the remailer in question was using.

But I did find that I had a misconfiguration for yamn@sinless.space. I
have now corrected that. (Flub when adding sinless to my config.)

--
Grant. . . .
unix || die

On 2021-12-04 2:15 a.m., Grant Taylor wrote:
> On 12/3/21 11:51 AM, Stefan Claas wrote:
>> Hi Grant,
>
> Hi,
>
>> I have just seen at the Mixmin YAMN pinger that the chains for all
>> YAMN Remailers from Zax to your YAMN Remailer are broken.

This sounds a lot like the problem that Tincture pinger experienced when
he upgraded his pinger's YAMN version to 0.2.4. Return pings from tncmm
remailer to Tincture pinger stopped being delivered.

> I don't know what domain name the remailer in question was using.
>

The remailers in question are

yamn@mixmin.net
yamn2@mixmin.net
yamn3@mixmin.net
yamn4@mixmin.net

All 4 are running YAMN v2.0.4.

--
SEC3

YAMN Tutorials - https://sec3.net/yamnhelp

On 2021-12-04 11:01 a.m., SEC3 wrote:

> yamn@mixmin.net
> yamn2@mixmin.net
> yamn3@mixmin.net
> yamn4@mixmin.net
>
> All 4 are running YAMN v2.0.4.

Correction v0.2.4.

On 2021-12-04 2:15 a.m., Grant Taylor wrote:
> On 12/3/21 11:51 AM, Stefan Claas wrote:
>> Hi Grant,
>
> Hi,
>
>> I have just seen at the Mixmin YAMN pinger that the chains for all
>> YAMN Remailers from Zax to your YAMN Remailer are broken.
>
> I don't know what domain name the remailer in question was using.

If you are referring to the From: address that YAMN sends out on its
outgoing messages it is mix@nowhere.invalid. This remains unchanged from
the previous YAMN versions.

# Outgoing message using YAMN 0.2c

Yamn-Pooled-Date: 3 Dec 2021
To: yamn@remailer.privacy.at
From: mix@nowhere.invalid
Subject: yamn-0.2c

::
Remailer-Type: yamn-0.2c

-----BEGIN REMAILER MESSAGE-----
20480
a4cd5dca63b699f2649a6a1239cd32acee4306f7904c5a1c127b5092e0028396
2QIuOUK6PDvGaezMOkylCtamsky3ta2RpZwCWjm8VtW5F/Fav4GH2lZvTaiYeY06
bGO5xr8IqpgMbSYKsRu3KVPLfZ/2kKFyfJHbHhF47appyyp1z0/EmSEXfVBKlDua
<SNIP>

# Outgoing message using YAMN 0.2.4

Yamn-Pooled-Date: 4 Dec 2021
To: yamn@remailer.privacy.at
From: mix@nowhere.invalid
Subject: yamn-0.2.4

::
Remailer-Type: yamn-0.2.4

-----BEGIN REMAILER MESSAGE-----
20480
6aa507a4e428594b838cdc35e09e890412fb4b52ab2f260e5225b7dd2953c932
CIZU7vOhGr4XC9FdfhdryVcyiY4xelttJ3c9nj4S3G5K8Nn+mjkDqdR4Q9ZvBs93
atF5M0bPMaHXBrGqKhLtQkk/mgCQ159F05q6YO4AO2g3M5BF+hX/TAjzR6K/oWZy
<SMIP>

--
SEC3

YAMN Tutorials - https://sec3.net/yamnhelp

On 12/4/21 9:01 AM, SEC3 wrote:
> This sounds a lot like the problem that Tincture pinger experienced when
> he upgraded his pinger's YAMN version to 0.2.4. Return pings from tncmm
> remailer to Tincture pinger stopped being delivered.

Hopefully that's resolved.

> The remailers in question are
>
> yamn@mixmin.net
> yamn2@mixmin.net
> yamn3@mixmin.net
> yamn4@mixmin.net
>
> All 4 are running YAMN v2.0.4.

I see lots of messages going to yamn(|2|3|4)@mixmin.net, but I don't see
any coming in from those addresses.

Do you see anything in MTA logs on the sending end?

--
Grant. . . .
unix || die

On 2021-12-05 10:19 p.m., Grant Taylor wrote:
> On 12/4/21 9:01 AM, SEC3 wrote:
>> This sounds a lot like the problem that Tincture pinger experienced
>> when he upgraded his pinger's YAMN version to 0.2.4. Return pings from
>> tncmm remailer to Tincture pinger stopped being delivered.
>
> Hopefully that's resolved.
>
>> The remailers in question are
>>
>> yamn@mixmin.net
>> yamn2@mixmin.net
>> yamn3@mixmin.net
>> yamn4@mixmin.net
>>
>> All 4 are running YAMN v2.0.4.
>
> I see lots of messages going to yamn(|2|3|4)@mixmin.net, but I don't see
> any coming in from those addresses.
>
> Do you see anything in MTA logs on the sending end?

You would need to ask Zax about that. He operates mixmin.net. I am just
a third party observer that has noticed an ongoing problem between tncmm
YAMN remailer and services (pingers and remailers) that use the latest
YAMN version.

One idea I had: Could you be running a procmail rule or some other rule
that acts on the presence in mail messages of the string "yamn-0.2c"?
That string was present in YAMN v0.2c messages but it is absent in the
latest YAMN v0.2.4 messages. In my previous message I provided
side-by-side comparisons of this.

--
SEC3

YAMN Tutorials - https://sec3.net/yamnhelp

On 12/5/21 8:35 PM, SEC3 wrote:
> You would need to ask Zax about that. He operates mixmin.net. I am just
> a third party observer that has noticed an ongoing problem between tncmm
> YAMN remailer and services (pingers and remailers) that use the latest
> YAMN version.

ACK

> One idea I had: Could you be running a procmail rule or some other rule
> that acts on the presence in mail messages of the string "yamn-0.2c"?
> That string was present in YAMN v0.2c messages but it is absent in the
> latest YAMN v0.2.4 messages. In my previous message I provided
> side-by-side comparisons of this.

Yes, there is a rule that acts on that string, and other strings.

:0
* Subject: (yamn-0.2a|yamn-0.2c|remailer-(adminkey|conf|help|key|stats))
{
:0
${ORGMAIL}/.Incoming/
}

That rule puts known messages into the incoming folder that yamn checks.

I have added yamn-0.2.4 to the filter.

If that rule doesn't match it puts messages in the Inbox which I monitor
the count of.

--
Grant. . . .
unix || die

On 2021-12-06 12:40 a.m., Grant Taylor wrote:

>> One idea I had: Could you be running a procmail rule or some other
>> rule that acts on the presence in mail messages of the string
>> "yamn-0.2c"? That string was present in YAMN v0.2c messages but it is
>> absent in the latest YAMN v0.2.4 messages. In my previous message I
>> provided side-by-side comparisons of this.
>
> Yes, there is a rule that acts on that string, and other strings.
>
>    :0
>    * Subject:
> (yamn-0.2a|yamn-0.2c|remailer-(adminkey|conf|help|key|stats))
>    {
>       :0
>       ${ORGMAIL}/.Incoming/
>    }
>
> That rule puts known messages into the incoming folder that yamn checks.
>
> I have added yamn-0.2.4 to the filter.

It looks like that solved it! There are no longer any mixmin-tncmm
broken chains being reported at Mixmin Yamn pinger.

<https://www.mixmin.net/yamn/mlist.html>

--
SEC3

YAMN Tutorials - https://sec3.net/yamnhelp

On 12/6/21 6:59 AM, SEC3 wrote:
> It looks like that solved it! There are no longer any mixmin-tncmm
> broken chains being reported at Mixmin Yamn pinger.

Cool!

Thank you for help diagnosing things SEC3.

--
Grant. . . .
unix || die

On 2021-12-06 11:58 a.m., Grant Taylor wrote:
> On 12/6/21 6:59 AM, SEC3 wrote:
>> It looks like that solved it! There are no longer any mixmin-tncmm
>> broken chains being reported at Mixmin Yamn pinger.
>
> Cool!
>
> Thank you for help diagnosing things SEC3.

You're welcome!

--
SEC3

YAMN Tutorials - https://sec3.net/yamnhelp