Re: ezmlm and BATV

On Thu, Aug 02, 2007 at 09:27:11AM -0700, John Keith wrote:
> Here's one link I found:
> http://tools.ietf.org/html/draft-levine-mass-batv-00

FWIW All links I have found to actual published standards documentation
are marked as drafts that have expired.

> A subscriber joins a list with email address [email protected].  The
> list is configured with -u, so that list posting is restricted to
> subscribers to the list.
> 
> When this user decides to post a message to the list, ezmlm looks at the
> envelope sender, [email protected], and rejects the
> posting because that address does not exist in the subscriber list.

Actually, this simplifies the problem somewhat.  Decoding the BATV
signed address into a database address would have to happen in quite a
number of places.  For example, how would such a sender initially
subscribe or later unsubscribe?

Also, from reading the draft above, it indicates that the encoded
address should be [email protected].  Is that what you
are seeing or the reverse that you posted above?

If ezmlm-idx always strips of the leading prvs=CODE= part, is that
sufficient to communicate with systems utilizing BATV?  That would mean
that the plain address is stored in the database, and all email (except
for bounces created automatically by qmail) would be sent to the plain
address.

> So I guess my question is: are we the only people receiving such
> complaints?

From the lack of responses, I would have to say yes.

-- 
Bruce Guenter <[email protected]>                http://untroubled.org/
	I do custom software development.  Email me for details.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQFHApJN6W+y3GmZgOgRAkMsAKCRy4bYHGXyf9WV/NLEvfH3f+kqSQCaA4Gg
NPJHUQAXKEs5s/u2kH15kw4=
=sMLO
-----END PGP SIGNATURE-----