Let me start this email by saying thank you to whoever fixed the
problem. I found a bunch of "Welcome to..." / "Results from delayed
command" message pairs in my mail this morning, and a batch of
messages from each of sql, performance, and hackers mailing lists.
# [EMAIL PROTECTED] / 2006-02-28 20:07:09 -0400:
> %mj_shell -p xxxx who pgsql-general | grep -i sigpipe.cz
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
>
> In fact, he's been registered since Jul '05:
Yes, that was the date I first received "must be approved by
maintainers" messages. However, I didn't receive any email to that
address until Monday when I retried the same
subscribe-set pgsql-general noprefix [EMAIL PROTECTED]
command, only this time I sent it from the [EMAIL PROTECTED]
address, not [EMAIL PROTECTED] A few minutes later, I had
majordomo's welcome to and the traffic started flowing in. My other
subscriptions (sql, hackers, performance) were in limbo until this
morning (CET).
> Address: [EMAIL PROTECTED]
> Address is valid.
> Address Mailbox: [EMAIL PROTECTED]
> Registered as
> [EMAIL PROTECTED]
> Registered on Wed Jul 27 06:44:37 2005
> Data last changed on Mon Feb 27 09:20:21 2006
> Subscribed to 1 lists
>
> pgsql-general:
> Subscribed as [EMAIL PROTECTED]
> Subscribed on Mon Feb 27 09:20:21 2006
> Last changed on Mon Feb 27 09:20:21 2006
> Receiving each message as it is posted
> Subscriber flags:
> prefix
That's strange, as you can see above, the command I sent was
"subscribe-set $list noprefix", yet the listing shows prefix. I can
confirm that messages I receive from all the lists have munged
subjects, although I used subscribe-set noprefix in all
subscriptions.
> So I'm not 100% certain *what* the problem is :(
majordomo claimed I was subscribed, but didn't send me the traffic.
# [EMAIL PROTECTED] / 2006-03-01 04:07:13 -0000:
> 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.
> Greg Sabino Mullane [EMAIL PROTECTED]
That's a completely different bug, the web interface doesn't escape
the +, which is then interpreted as urlencoded space. You might want
to make sure that the web interface protects the addresses it uses
as request parameters by encoding / decoding them according to
RFC1738. Otherwise, malicious users might be able to use specially
crafted email addresses as trojan horses.
Again, thanks for approving the subscriptions.
--
How many Vietnam vets does it take to screw in a light bulb?
You don't know, man. You don't KNOW.
Cause you weren't THERE. http://bash.org/?255991
---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend
