[Owasp-leaders] ABORT the OWASP Email Lists
dinis.cruz at owasp.org
Thu Jun 7 06:37:04 UTC 2012
Matt, its great that you are trying to solve this, but this just shows the
need that we have to have dedicated (even part-time) professional
network/application support for OWASP.
Like Jim mentioned, the Mailing list are a real problem since these issues
have dramatically affected the usability of one of the most solid and
useful OWASP community resources we have (and in the projects I'm involved
, there is a direct negative impact due to this)
On that topic, there was a note last month that we had hired such resource.
Has it happend? if so who it is? And if not, we need to put some urgency in
this hire, since we need help!
For example, when we say *'lets move from Mailman to Google Groups',* who
is going to do it? Are we really expecting all our project/chapter leaders
to do it?
Btw, these problems just show how great of a job Larry did during all those
years he managed the OWASP Mailing lists (amongst other things).
On 3 June 2012 18:08, Matt Tesauro <matt.tesauro at owasp.org> wrote:
> Jim was in Austin recently and asked me about this. I have no problem
> with list admin's deciding to move lists over to Google groups if they
> believe that's best for their recipients/group. Do what you need to do to
> further OWASP's mission.
> However, since I talked with Jim, there's some news about lists.owasp.org:
> (1) The mail server on lists.owasp.org was setup with very low defaults
> for inbound mail. This was causing a bottle neck and mail was being
> spooled for excessively long times on the Barracuda filtering host(s). I
> have since changed Sendmail (ugh) to allow unlimited inbound email from
> Barracuda since that is the only source the mail server on lists will
> actually answer (both on the firewall and MTA configuration level).
> Additionally, Barracuda already filters out SPAM and spool mail if the
> mail server on lists gets overwhelmed (which is doubtful).
> (2) Very shortly (I'd say 1 to 2 weeks out, lists.owasp.org will be
> migrated to a new host. One of two options will be used:
> Option #1: Migrate to Open Source Labs (OSL) who hosts Mailman lists for
> numerous open source projects already. I am working through the details
> and potential problems with that choice currently, though its is the
> preferred option.
> Option #2: Migrate to Rackspace managed cloud where the migration will
> allow a more optimized mail server configuration and changing from Sendmail
> (ugh) to Postfix as the MTA/mail server. OWASP will still need to manage
> Mailman but Rackspace will mange OS, monitor, backup, etc.
> In the middle of this Mailman mess, I've had medical issues with family
> members, a funeral, am in the middle of relocating my family to San
> Antonio, and I have (so far) avoided needing back surgery . Basically, my
> spring has sucked. So between working my day job, selling my current house
> and finding/buying a new one, I've had very little free time.
> For the curious who are still reading this, I've attached a couple of
> screenshots from Barracuda to give you an idea of the volume of traffic on
> * blocked-spam.png = a partial listing of the SPAM blocked at 9:02 AM this
> morning by Barracuda. While lists still has issues, we are not seeing a
> ton of SPAM thanks to Barracuda.
> * inbound-overview.png = an overview of inbound email to lists.
> * outbound-overview.png = an overview of outbound emails from lists (note
> the 6.6 GB outbound bandwidth on May 28th)
> As soon as the migration plan is finalized, I'll let you know. It looks
> the migration will take at most 1 hour of downtime (though Barracuda will
> just spool mail during any downtime) so there shouldn't be loss of mail or
> a large interruption in service.
> -- Matt Tesauro
> OWASP Board Member
> OWASP WTE Project Lead
> http://AppSecLive.org - Community and Download site
> On Tue, May 29, 2012 at 11:45 AM, Jim Manico <jim.manico at owasp.org> wrote:
>> The OWASP emails lists are beyond messed up right now.
>> I call for a full abort to Google Groups as an interstitial measure
>> until this is resolved by the foundation.
>> Several projects have already quietly made this move, and several
>> chapters are considering it now.
>> So, if your chapter or project is struggling with the Mailmain mess, do
>> not ask for permission, just make the move to Google groups as you see
>> fit until a workable solution presents itself. What we have now is NOT
>> workable at all.
>> Innovation and Experimentation are our core values so GO FOR IT.
>> My 2 cents,
>> Jim Manico
>> Connections Committee Chair
>> Cheatsheet Series Product Manager
>> OWASP Podcast Producer/Host
>> jim at owasp.org
>> OWASP-Leaders mailing list
>> OWASP-Leaders at lists.owasp.org
> OWASP-Leaders mailing list
> OWASP-Leaders at lists.owasp.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OWASP-Leaders