So, body @ (a) munging, unmunged in original mail,
displays on web GUI:
munged:
postmaster(a)[127.0.0.1]
postmaster(a)example.com
unmunged:
<postmaster@localhost>
@example.com
@localhost
postmaster@localhost
Posted unmunged from GUI, exact same as above.
And in the archive itself ugh,
slightly worse, but not even the same set!:
munged:
<postmaster(a)localhost>
postmaster(a)example.com
postmaster(a)localhost
unmunged:
@example.com
@localhost
postmaster(a)[127.0.0.1]
Posted unmunged from GUI, exact same as above.
And note that @ (a) munging is applied to body,
not headers.
And I don't think Mailman 3 has an option to turn off munging.
So, unmunged in original mail,
displays on web GUI:
munged:
postmaster(a)[127.0.0.1]
postmaster(a)example.com
unmunged:
<postmaster@localhost>
@example.com
@localhost
postmaster@localhost
And in the arhive itself ugh,
slightly worse, but not even the same set!:
munged:
<postmaster(a)localhost>
postmaster(a)example.com
postmaster(a)localhost
unmunged:
@example.com
@localhost
postmaster(a)[127.0.0.1]
In any case, that applies to body,
headers in archive aren't @ (a) munged.
On 2024-07-07 03:15, Michael Paoli wrote:
> Mailman 3 testing (@lists.BALUG.org) ...
>
> For the interested and/or curious,
That's me!
> actively testing Mailman 3 at present
> (so far looking at least "reasonable enough", and does have some pretty
> spiffy features too). If curious and/or want to try it out,
> have a peek here:
> https://lists.balug.org/mailman3/
It does look nice, for sure.
I'm subscribed (via email to ...-request@...), however, when I go to the
web page and try to log in, I get:
> Server error
>
> An error occurred while processing your request.
I'd expect a different result (I do not yet have an account via the web
interface).