684164 - Callek unable to get SeaMonkey announcement posts through announce@

Status: RESOLVED WORKSFORME

(mozilla.org :: Discussion Forums, task)

Description

[Justin Wood (:Callek)]

For the past few months, I have been continually sending (and approving) SeaMonkey releases to the announce@ list.

I send it in e-mail form, and approve from the pending messages in the list admin. None of these messages for the last while have gone through, even on days I approve similar Firefox announces, those Firefox announces show up in newsgroups/list and mine never go through.

I just had a similar experience with my SeaMonkey 2.3.2 release. I (as of a few seconds ago) re-sent a mail to announce@ just for the sake of someone trying to figure this out.

I have no idea what setting changed, and from my look through the settings nothing in there should be stopping me, if I approve it from the mod queue.

Comment 1

[Dave Miller [:justdave]]

The post you just sent appears to have worked.

Comment 2

[Dave Miller [:justdave]]

http://groups.google.com/group/mozilla.announce/browse_thread/thread/7a26fe0f1985b88c

Comment 3

[Justin Wood (:Callek)]

Looks like this worked this time, I'm going to reopen when I send the (normal) announce for 2.3.3 just to see if it will work when one of you approve it again, if that works, at least we can try and narrow things down more.

Comment 4

[Justin Wood (:Callek)]

Ok, I just sent both SeaMonkey 2.4 Beta 1, and 2.3.3 announcements in via my normal way.

Please approve, and lets figure out this issue once and for all.

Comment 5

[Justin Wood (:Callek)]

Just sent SeaMonkey 2.4 Beta 2 e-mail, and still no action from You guys on approving the existing e-mails. I tried approving 2.4 Beta 1 and it looks like I am getting hit by some filter since it did not go to the list/newsgroup, even though I got an acknowledgement e-mail about it.

I would really appreciate this getting tracked down.

Comment 6

[Justin Wood (:Callek)]

now that I am sending these through with announce@ as the ONLY to, and it is going through that way, I'm resolving... even though I still would have liked a better solution that requiring a completely separate e-mail.