Hi, Karl. Yeah, it was 250 lines or so.

As you noticed, I managed to break the list while trying to improve things. I think it's back now.

Meanwhile, I've been seeing messages in my gmail folder. I added a filter rule to not flag cypherpunks messages as spam.

For your gmail setup, are you using the web interface (i.e., https://www.gmail.com or similar)? Or, are you using IMAP/POP to download messages to another client? I realized that if you are downloading, the stuff gmail filters as spam might simply not be visible.

If you haven't already, try the web interface, and select the Spam folder, to see whether there is anything from cpunks there.

Best,
  Greg

On Thu, May 27, 2021 at 05:14:37PM -0400, Karl wrote:
> Hey,
>
> Thanks so much for sharing this.  I'm okay with others on the list
> seeing my loglines, if that's ever an issue.
>
> So you know, I see 250 loglines here, not 900+ .  I don't see mailman
> bounces listed here.
>
> It looks like the development sources of mailman store bounce delivery
> status notifications as of 1 month ago:
> https://gitlab.com/mailman/mailman/-/commit/e1d20b316024990535aeedc54aa84cd11a668317
> .
>
> I see you resolved the spamassassin configuration issue around 09:30
> today, timezone unspecified.
>
> It looks like the way to log mailman bounces a bit better would be to
> open up mailman/model/bounce.py and add temporary output to
> BounceProcessor.register around line 80:
>         with open('/var/tmp/' + email + '.bouncelog', 'a') as bouncelog:
>             bouncelog.write(str(msg) + "\n")
>
> Bounces from me would then hopefully end up in
> /var/tmp/gmkarl@gmail.com.bouncelog .
>
> On 5/27/21, Greg Newby <gbnewby@pglaf.org> wrote:
> > Here are the 900+ logfile messages for your email address, in case you find
> > anything informative.
> >
> > As noted, I've made a few changes. These include:
> > - turning off outbound spamassassin for cypherpunks list traffic, via
> > whitelist
> > - adding a bad spamc.cf setting, then fixing it (pertains to maximum message
> > length of messages, which isn't a factor in the cpunks list)
> > - removing blacklist checking, as mentioned on the list
> >
> > The bounce score in Mailman isn't much of an issue: if you get unsubscribed,
> > I can easily add you back. But I don't know where those bounces came from -
> > Mailman doesn't provide an easy way, even for a list admin, to recover
> > specific bounce details.
> >
> > I'm not paranoid about surveillance on the cypherpunks list, since it's an
> > open list with open archives. The subscriber list is kept confidential
> > within Mailman (so only I can see it), but anyone that could tap the network
> > would know who messages were going to. So, it's confidential, but barely
> > secure.
> >
> > The standard techniques like John linked to are much more likely to be
> > damaging, or potentially damaging, to the cypherpunks list:
> > https://cryptome.org/2012/07/gent-forum-spies.htm
> >
> > Meanwhile, though, it's distressing that gmail seems to be filtering. I
> > indeed confirmed that a list message went to the spam folder, but it was
> > visible there (i.e., it didn't simply disappear, for me).
> >
> > Best,
> >   Greg
> >
> > On Thu, May 27, 2021 at 01:23:10PM -0400, Karl wrote:
> >> >> Maybe some day a cronjob that filters logs for only people who post,
> >> >> or only who have an option set, could make for public logs eventually
> >> >> ...
> >> >
> >> > Yes, that would be aligned with the transparency that is the philosophy
> >> > of
> >> > the list.
> >> >   Best,
> >> >     Greg
> >> >
> >>
> >> grep --fixed-strings --file=one_email_address_per_line.txt
> >> /var/log/mailman/bounce.log > public_logfile
> >>
> >> mailman is written in python; i'm thinking of how hackable it might be.
> >>
> >> sorry to be bugging you, it's sad the bounces don't show up in the
> >> logs =S  really some malicious sotware could be messing with us.
> >> cleaning logfiles is such a basic part of malicious software.
> >