Roundup Tracker - Issues

Issue 2550649

classification
New issues for issues.roundup-tracker.org should go to roundup-devel@.
Type: rfe Severity: normal
Components: Infrastructure Versions:
process
Status: closed
:
: richard : ber, richard
Priority: normal :

Created on 2010-05-04 21:38 by ber, last changed 2010-05-10 09:32 by richard.

Messages
msg4047 Author: [hidden] (ber) Date: 2010-05-04 21:38
It is quite useful for new issues to go to 
roundup-devel@lists.sourceforge.net.

There are two steps:
a) set this up with issues.roundup-tracker.org in the newissuecopy.py.
(Done as of today.)
b) Make sure that emails from that location go through with the list.
For this we need a list administrator.
msg4048 Author: [hidden] (ber) Date: 2010-05-04 21:45
Email was send from admin@issues.roundup-tracker.org, but I guess it 
is stuck in graylisting of sf right now.
Richard, you are the mailman admin of roundup-devel@ could you
see later if you find this email from this issue in the moderator 
interface and then whitelist the sender?
msg4049 Author: [hidden] (richard) Date: 2010-05-05 04:20
Added the admin address to the -devel whitelist.
msg4052 Author: [hidden] (ber) Date: 2010-05-10 07:15
Hmm there have been at least one more issue
since mailman should have been tinkered to let them through.
(issue2550650 at least).
But I did not see them coming through the list.

Richard could you check on the devel admin Mailman moderation Interface 
if email are hanging there and why?
msg4054 Author: [hidden] (richard) Date: 2010-05-10 09:32
Sorry, added the wrong address. Should be OK now.
History
Date User Action Args
2010-05-10 09:32:31richardsetstatus: open -> closed
messages: + msg4054
2010-05-10 07:15:08bersetstatus: closed -> open
resolution: fixed ->
messages: + msg4052
2010-05-05 04:20:21richardsetstatus: new -> closed
resolution: fixed
messages: + msg4049
2010-05-04 21:45:45bersetassignee: ber -> richard
messages: + msg4048
2010-05-04 21:38:48bercreate