-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Roman Neuhauser replied to me: >> I suspect that the listserv is choking on the "#" symbol. This is >> undoubtably a bug in their software. For one thing, it should not >> have accepted the email address as far along as it did. > Eh? That email address is completely valid. Sure it is, but the mailing list software doesn't think so, or at least part of it does. What I meant by the above was that if the software was going to choke on the email address, it should have done so right away, instead of allowing it to get fully subscribed and then deciding that it was not valid at some other point in the workflow leading up to actually sending you some email. >> Well, all I can recommend then is perhaps trying an email address without >> the "#" sign if possible. > Funny thing, I've managed to sign to pgsql-general with the address > displayed above when I sent the very first subscribe command from > that address. That suggests that the bug shows up The address is fully subscribed to the list, both Marc and I can verify that. The problem is that it fails some other check when mail is sent to it. Why in the world that logic is not centralized, I cannot imagine. Marc wrote: > Nope, that isn't it .. the thing is, from this end, I can't see/find any > problems ... he's subscribed to the list: Marc, I was able to view that weird whitespace message by going to "Subcribers", entering "neuhauser" in the search box, and then "clicking"[1] on the troublesome name in question. [1] I actually use links, so there is no mouse clicking involved, but I've never been able to find a better verb to use there. :) - -- Greg Sabino Mullane greg@xxxxxxxxxxxx PGP Key: 0x14964AC8 200602282257 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iD8DBQFEBRxDvJuQZxSWSsgRAjfbAJ4oowDAt5sweySUv+EsL476bmXj0ACfVDM9 1TAipT8ucu9yc2jODt8zcCU= =/Rql -----END PGP SIGNATURE-----
