[Esapi-user] Delivery Status Notification (Failure)

Kevin W. Wall kevin.w.wall at gmail.com
Tue Jul 1 01:16:54 UTC 2014


The *correct* email address are
    <esapi-user at lists.owasp.org> and <esapi-dev at lists.owasp.org>

You had:
<owasp-esapi-dev at owasp.org> and <owasp-esapi-users at owasp.org>

There is no 'owasp-' prefix and the ESAPI user list is singular, not plural.

-kevin

On Mon, Jun 30, 2014 at 8:05 PM, Jim Manico <jim.manico at owasp.org> wrote:
> ?????
>
> --
> Jim Manico
> @Manicode
> (808) 652-3805
>
> Begin forwarded message:
>
> From: Mail Delivery Subsystem <mailer-daemon at googlemail.com>
> Date: July 1, 2014 at 8:03:14 AM GMT+8
> To: jim.manico at owasp.org
> Subject: Delivery Status Notification (Failure)
>
> Hello jim.manico at owasp.org,
>
> We're writing to let you know that the group you tried to contact
> (owasp-esapi-users) may not exist, or you may not have permission to post
> messages to the group. A few more details on why you weren't able to post:
>
> * You might have spelled or formatted the group name incorrectly.
> * The owner of the group may have removed this group.
> * You may need to join the group before receiving permission to post.
> * This group may not be open to posting.
>
> If you have questions related to this or any other Google Group, visit the
> Help Center at
> http://support.google.com/a/owasp.org/bin/topic.py?topic=25838.
>
> Thanks,
>
> owasp.org admins
>
>
>
> ----- Original message -----
>
> X-Received: by 10.66.159.34 with SMTP id wz2mr54819990pab.96.1404172994624;
>        Mon, 30 Jun 2014 17:03:14 -0700 (PDT)
> Return-Path: <jim.manico at owasp.org>
> Received: from mail-pa0-f50.google.com (mail-pa0-f50.google.com
> [209.85.220.50])
>        by mx.google.com with ESMTPS id
> tp10si24869208pbc.170.2014.06.30.17.03.14
>        for <owasp-esapi-users at owasp.org>
>        (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
>        Mon, 30 Jun 2014 17:03:14 -0700 (PDT)
> Received-SPF: pass (google.com: domain of jim.manico at owasp.org designates
> 209.85.220.50 as permitted sender) client-ip=209.85.220.50;
> Authentication-Results: mx.google.com;
>       spf=pass (google.com: domain of jim.manico at owasp.org designates
> 209.85.220.50 as permitted sender) smtp.mail=jim.manico at owasp.org
> Received: by mail-pa0-f50.google.com with SMTP id bj1so9455937pad.23
>        for <owasp-esapi-users at owasp.org>; Mon, 30 Jun 2014 17:03:14 -0700
> (PDT)
> X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
>        d=1e100.net; s=20130820;
>        h=x-gm-message-state:from:mime-version:date:message-id:subject:to
>         :content-type;
>        bh=dF/IjWdc191QWX8eO2uFIO4UwzZJPqWfFaxTMU7ZfYI=;
>        b=DDzUhLyQ9Vb7PGGDmheDdAuI+xMSYldCVewfSEPEl5CVQCuaxrPS+CKu1bnPOeMKD1
>         PyDjP7uHBFHwBChclBCHcYkAh7L/JB58/P77WS9MT9WXna+qFi6VXqjfenat1GEpriuF
>         yvqOZDj5vMuNjkkkkAa4DOj9x5gEsbI16pq+K+ltVKSWBLv2/CmKs8ZoMrZsxtNuxs1h
>         7xWaw+GnjgdcfnsQAdj2F5TLIeFz8nJ2yry7GgYaGHlLTogBeKHZMIJCQ30Ax0wQTssl
>         s7r/XoUIx8Hu4s3purIJ9eZovQ9vMdlY5EagcQEmAMQPgUG8TiuUHxdSZfZoquJSbj4L
>         rQ8w==
> X-Gm-Message-State:
> ALoCoQm/xmHRmVAxqvu+Uil/XkUs3qwz/SDwHWGSFhTlkJbMSVr1nxsfY+/8JVgZ8av1Adpht2Is
> X-Received: by 10.66.254.37 with SMTP id af5mr55039947pad.113.1404172994283;
> Mon, 30 Jun 2014 17:03:14 -0700 (PDT)
> From: Jim Manico <jim.manico at owasp.org>
> Mime-Version: 1.0 (1.0)
> Date: Tue, 1 Jul 2014 08:03:16 +0800
> Message-ID: <4358926730822974487 at unknownmsgid>
> Subject: Code > Criticism
> To: owasp-esapi-dev <owasp-esapi-dev at owasp.org>,
>    owasp-esapi-users <owasp-esapi-users at owasp.org>
> Content-Type: multipart/alternative; boundary=047d7b15adb58721e604fd168031
>
> Folks,
>
> Are there any bugs or features in ESAPI that you would especially like to
> see squashed or built? I'd like to turn my criticism into code and help the
> project again. I plan to dive back in after July 6th after I finish current
> travel.
>
> https://code.google.com/p/owasp-esapi-java/issues/list
>
> I'm a bit rusty but I am sure I can at least start by working on some of
> the easy stuff. ;)
>
> We also have a pretty robust emerging platform for various reviews such as
> Ohlol/BlackDuck and our new OWASP central build server. I'd also like to
> start throwing DelendencyChecker at ESAPI as part of the build process. We
> are soon to get static analysis reports from various vendors that may be
> interesting. Vendor neutrality is not "no vendors" but an even playing
> field for any to participate. Perhaps we can get a few community members to
> help do code review of checkins as a regular part of the process.
>
> I know I've been quite critical of ESAPI and Jeff but it's because I think
> ESAPI is super important and needs some love. I'm very willing to get my
> hands dirty to help make it better.
>
> Anyone with me?
>
> Aloha,
> --
> Jim Manico
> @Manicode
> (808) 652-3805



-- 
Blog: http://off-the-wall-security.blogspot.com/
NSA: All your crypto bit are belong to us.


More information about the Esapi-user mailing list