Closed
Bug 1069710
Opened 10 years ago
Closed 9 years ago
email address blocked or tb-support-crew mailing list hung?
Categories
(Infrastructure & Operations :: Infrastructure: Mail, task)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: wsmwk, Unassigned)
Details
On 9/17 approx 8:36AM EST I sent two emails to tb-support-crew@mozilla.org which appears to have not been processed, because I did not get a copy, and I don't see them in the mailing list archives. I am an adminstrator for the list, and I also don't see any pending requests. subject of the two emails are - [general] McAfee and Not Responding, more of - [general] TB31 and HWA (hardware acceleration)
Reporter | ||
Comment 1•10 years ago
|
||
I last posted to the list on 9/9. That may well be the last post to the lst by anyone.
Reporter | ||
Comment 2•10 years ago
|
||
perhaps my email is blocked or labelled as spam by mozilla, because today I sent an email to a different mailing, tb-planning, with subject "message threading bugs" and didn't see it go through.
Summary: tb-support-crew mailing list hung? → email address blocked or tb-support-crew mailing list hung?
Reporter | ||
Comment 3•10 years ago
|
||
This morning my tb-planning posting went through. And also a second posting I just made to tb-planning but none of my tb-support-crew postings went through
Comment 4•10 years ago
|
||
i just clicked "Deliver" on wayne's postings from the september 17, 2014. hopefully that means they will get delivered
Reporter | ||
Comment 5•10 years ago
|
||
they just came through. Did it say why they were held?
Comment 6•10 years ago
|
||
nope (In reply to Wayne Mery (:wsmwk) from comment #5) > they just came through. Did it say why they were held? nope it just thought it was spam for some reason, weird that an administrator of a list is blocked, so maybe it's postini? (and not mailman!)
Comment 7•9 years ago
|
||
Are you also a member? Mailman will also hold mail in moderation if you are not a member (eventhough you are an administrator). In any case postini is out of the loop of these things, and if its hitting the mailman server more than likely its a moderation issue.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Reporter | ||
Comment 8•9 years ago
|
||
(In reply to Ed Lim [:limed] from comment #7) > Are you also a member? Mailman will also hold mail in moderation if you are > not a member (eventhough you are an administrator). Yes, I am a member. > In any case postini is > out of the loop of these things, and if its hitting the mailman server more > than likely its a moderation issue. I've seen mention of a spam "score" in an email on another mailing list that I admininister. 1. Is there way that I can set mailman to filter on spam scores? 2. Is there a way to whitelist an address in mailman? 3. catch all question - are there any reference docs beyond what's in the mailman web UI?
Flags: needinfo?(limed)
Comment 9•9 years ago
|
||
(In reply to Wayne Mery (:wsmwk) from comment #8) > (In reply to Ed Lim [:limed] from comment #7) > > Are you also a member? Mailman will also hold mail in moderation if you are > > not a member (eventhough you are an administrator). > > Yes, I am a member. > > > In any case postini is > > out of the loop of these things, and if its hitting the mailman server more > > than likely its a moderation issue. > > I've seen mention of a spam "score" in an email on another mailing list that > I admininister. > 1. Is there way that I can set mailman to filter on spam scores? Yes you can do this, however we front mail.mozilla.org (aka mozilla.org mailman) with Google message security, so while there will be spam headers it will not be similar to what spamassassin sets > 2. Is there a way to whitelist an address in mailman? Yes there is and it is all listed here http://www.gnu.org/software/mailman/mailman-admin/sender-filters.html > 3. catch all question - are there any reference docs beyond what's in the > mailman web UI? Yep right here: http://www.gnu.org/software/mailman/mailman-admin/index.html
Flags: needinfo?(limed)
You need to log in
before you can comment on or make changes to this bug.
Description
•