-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Kaja P. Christiansen wrote:

In the internal code for (La)TeX system, the control sequences use the @ character as a text character; on TeX related lists there are often examples of such internal code. Unfortunately, the archiver (mailman 2.1.2) converts a 'string1@string2' pattern to an email address. So, if a posting has a line with something like:

\put(\strip@pt\@tempdimb,\strip@pt\@tempdimc)

this line will appear in the archives as

\put(\strip at pt\@tempdimb,\strip at pt\@tempdimc)

where 'strip at pt' are links pointing to the listinfo page. See:

http://www.tug.org/pipermail/test/2003-July/000000.html

Is there a workaround to prevent this behaviour?

Set ARCHIVER_OBSCURES_EMAILADDRS to 0 in mm_cfg.py and restart the mailman daemon. You may also have to regenerate the list archives to get this to fix existing archives. Here's the comments about this setting from Defaults.py:

# Pipermail archives contain the raw email addresses of the posting
# authors.  Some view this as a goldmine for spam harvesters.  Set this
# to true to moderately obscure email addresses, but note that this
# breaks mailto: URLs in the archives too.
ARCHIVER_OBSCURES_EMAILADDRS = 1

Todd OpenPGP -> KeyID: 0xD654075A | URL: www.pobox.com/~tmz/pgp

We are free not because we claim freedom, but because we PRACTICE it. -- William Faulkner

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) Comment: When crypto is outlawed bayl bhgynjf jvyy unir cevinpl.

iD8DBQE/J+3Cuv+09NZUB1oRAuJHAJ9B1CDR05toSdIuSBrIh3RA1X/cxgCgmUSV ne8bFyihdjB8mt4E1Ciisyo= =S3OY -----END PGP SIGNATURE-----