Problem with echolot 2.1
Peter Palfrader
peter@palfrader.org
Fri, 7 Mar 2003 21:23:56 +0100
--DKU6Jbt7q3WqK7+M
Content-Type: text/plain; charset=iso-8859-15
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Thu, 06 Mar 2003, Hermes Admin wrote:
> I just started seeing problems with echolot pings from other pingers
> to my remailer.
>=20
> Mixmaster (on Linux) is reporting these error messages now (when it
> didn't before Echolot 2.1 was released):
>=20
> Notice: Blocked header line: From: Echolot Pinger <estragon@remailer.frel=
l.eu.org> matches /^From:/
>=20
> The pinger changes, so I know it's not just Frell. Mixmaster said this
> about my own pinger when I upgraded to 2.1.
>=20
> Do I have a misconfiguration somewhere or is there a bug in Echolot 2.1?
Neither.
What you see in your log is just a notice that Mixmaster _removed_ a
header line from a message to be send.
Echolot 2.1 started to collect From: headers of remailers. Every other
ping is now sent with a user supplied From header. Most remailers (like
yours) just remove the header and send the message on, while also
logging this event.
I'll probably change Echolot for the next release to only try a user
supplied From header if no current information (2 days?) is already on
file for a certain node. This should cut down on probably annoying log
entries while still making the information available.
I hope this answers your question - if not, let me know.
Peter
--=20
PGP signed and encrypted | .''`. ** Debian GNU/Linux **
messages preferred. | : :' : The universal
| `. `' Operating System
http://www.palfrader.org/ | `- http://www.debian.org/
--DKU6Jbt7q3WqK7+M
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2rc1 (GNU/Linux)
iD8DBQE+aP/c3nqvbpTAnH8RAtKGAKDAWLJ/ihID+NFQP0/NBfOFgRfqdACgi7Al
m4X/4D/yjWzW0FsyIUnzQzQ=
=aFxN
-----END PGP SIGNATURE-----
--DKU6Jbt7q3WqK7+M--