Jean-Claude Beaudoin | 3 Jun 2013 02:36
Picon

Fwd: Posts to announcements <at> common-lisp.net denied


Here is below what I get as a reply from mlmmj when
I post something to mkcl-announce <at> common-lisp.net.

This is because somebody (not me) made
announcements <at> common-lisp.net a
subscriber to the list. This kind of redirection
does not work as it is evidenced here below.

As owner of that list, how can I delete an entry
from the list of subscribers?

Thanks,

Jean-Claude

---------- Forwarded message ----------
From: <announcements+owner <at> common-lisp.net>
Date: Sun, Jun 2, 2013 at 7:46 PM
Subject: Posts to announcements <at> common-lisp.net denied
To: jean.claude.beaudoin <at> gmail.com


Hi, this is the mlmmj program managing the mailinglist

announcements <at> common-lisp.net

I'm sorry to inform you that your message could not be delivered to the
list.

In order to post to this list, the list address must be contained
in either the To: or Cc: header.

Thanks.

--- Below this line are the first 100 lines of the denied message --->
 X-Original-To: common-lisp.net--announcements <at> localhost.mlmmj
 Received: from localhost (localhost [127.0.0.1])
        by mail.common-lisp.net (Postfix) with ESMTP id 1F39F3564DB
        for <common-lisp.net--announcements <at> localhost.mlmmj>; Sun,  2 Jun 2013 16:46:24 -0700 (PDT)
 X-Virus-Scanned: Debian amavisd-new at common-lisp.net
 Received: from mail.common-lisp.net ([127.0.0.1])
        by localhost (alpha-cl-net.common-lisp.net [127.0.0.1]) (amavisd-new, port 10024)
        with ESMTP id fGb4Ct_7XOzj
        for <common-lisp.net--announcements <at> localhost.mlmmj>;
        Sun,  2 Jun 2013 16:46:17 -0700 (PDT)
 Received: from alpha-cl-net.common-lisp.net (localhost [127.0.0.1])
        by mail.common-lisp.net (Postfix) with SMTP id 83C2E3566C3
        for <announcements <at> common-lisp.net>; Sun,  2 Jun 2013 16:46:13 -0700 (PDT)
 X-Original-To: common-lisp.net--mkcl-announce <at> localhost.mlmmj
 Received: from localhost (localhost [127.0.0.1])
        by mail.common-lisp.net (Postfix) with ESMTP id 5E76D3566BE
        for <common-lisp.net--mkcl-announce <at> localhost.mlmmj>; Sun,  2 Jun 2013 16:46:13 -0700 (PDT)
 X-Virus-Scanned: Debian amavisd-new at common-lisp.net
 Received: from mail.common-lisp.net ([127.0.0.1])
        by localhost (alpha-cl-net.common-lisp.net [127.0.0.1]) (amavisd-new, port 10024)
        with ESMTP id 9t7CGcCX03qj
        for <common-lisp.net--mkcl-announce <at> localhost.mlmmj>;
        Sun,  2 Jun 2013 16:46:08 -0700 (PDT)
 Received: from mail-oa0-f46.google.com (mail-oa0-f46.google.com [209.85.219.46])
        by mail.common-lisp.net (Postfix) with ESMTPS id AA3F03564DB
        for <mkcl-announce <at> common-lisp.net>; Sun,  2 Jun 2013 16:46:08 -0700 (PDT)
 Received: by mail-oa0-f46.google.com with SMTP id h2so722698oag.33
         for <mkcl-announce <at> common-lisp.net>; Sun, 02 Jun 2013 16:46:07 -0700 (PDT)
 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
         d=gmail.com; s=20120113;
         h=mime-version:in-reply-to:references:date:message-id:subject:from:to
          :content-type;
         bh=j89jVoK9gNTz4UwGnjqI0jbHzG7uQ7qaW36bWEJWZsI=;
         b=s5VZJWPa89iWk8F5TjB1wPxmLnalmwMo0QUPOPqBGM2AKZBatRf8GNzh6oiwYpjVq3
          iK4WdTvvwlPWzTs/dnCQZFOTHYZn41afp/Z3QdB0IMxCQQW09mnGRPP7tMGOIfOpkqKj
          ygIK4hGZuB1JWlx2ZUn5c8j+lzTycXw07roUpEI3qNqKiO6AdPLkpZqx0g0fXpGiyqtm
          1uu7hKF7J94f8CsCwLZsXf0x+ReOu0n9EpYXEd8Tqw7yG+gc1dCiJ6vpXlNH/Cg0QejB
          UGSDGwVr7RDvLRxlwOdNK4Ik60KOlY8QepQ/2N3RpCHxnWSWC9+TDYgeBC0pHAuq4W/B
          6F7g==
 MIME-Version: 1.0
 X-Received: by 10.60.162.70 with SMTP id xy6mr9327236oeb.117.1370216767171;
  Sun, 02 Jun 2013 16:46:07 -0700 (PDT)
 Received: by 10.182.27.70 with HTTP; Sun, 2 Jun 2013 16:46:07 -0700 (PDT)
 In-Reply-To: <CAN3WOFe+V9F3zisLi5cdg9+B8z9Nk22GhM34fqb=1cTtNVgeeg <at> mail.gmail.com>
 References: <CAN3WOFe+V9F3zisLi5cdg9+B8z9Nk22GhM34fqb=1cTtNVgeeg <at> mail.gmail.com>
 Date: Sun, 2 Jun 2013 19:46:07 -0400
 Message-ID: <CAN3WOFej_H6aocTOLr=6Z40pJ6uEBR2VLL7mKgTSePxYKAYpoA <at> mail.gmail.com>
 Subject: Fwd: MKCL 1.1.5 is now available
 From: Jean-Claude Beaudoin <jean.claude.beaudoin <at> gmail.com>
 To: mkcl-announce <mkcl-announce <at> common-lisp.net>
 Content-Type: multipart/alternative; boundary=047d7b41400cac316204de3473db

 --047d7b41400cac316204de3473db
 Content-Type: text/plain; charset=ISO-8859-1

 ---------- Forwarded message ----------
 From: Jean-Claude Beaudoin <jean.claude.beaudoin <at> gmail.com>
 Date: Sun, Jun 2, 2013 at 5:45 PM
 Subject: MKCL 1.1.5 is now available
 MKCL 1.1.5 is now available for general use. It is a bug fix compilation
 release
 that collects all changes currently committed to the MKCL git repository,
 please consult http://common-lisp.net/gitweb?p=projects/mkcl/mkcl.git if
 you need a detailed log.

 The creation of yet another bug fix release in the MKCL 1.1.X series is
 due to the fact that work on MKCL 1.2.0 has hit a bump recently and
 its release will be delayed by a few more months, making a bug
 fix release therefore relevant.

 Upon careful inspection of the major defining macros part of MKCL
 it was realized that a good number of them were not ANSI compliant
 but rather conformed to CLTL2 with a few still only CLTL1 or
 somewhere in between (but clearly not ANSI). To correct this
 situation macros defmacro, defsetf and deftype have been
 completely reimplemented. This effort is the cause of a two months
 delay in the evolution of MKCL 1.2.0.

 Cheers,

 Jean-Claude Beaudoin

 --047d7b41400cac316204de3473db
 Content-Type: text/html; charset=ISO-8859-1
 Content-Transfer-Encoding: quoted-printable

 <div dir=3D"ltr"><br><br><div class=3D"gmail_quote">---------- Forwarded me=
 ssage ----------<br>From: <b class=3D"gmail_sendername">Jean-Claude Beaudoi=
 n</b> <span dir=3D"ltr">&lt;<a href=3D"mailto:jean.claude.beaudoin <at> gmail.co=
 m">jean.claude.beaudoin <at> gmail.com</a>&gt;</span><br>
 Date: Sun, Jun 2, 2013 at 5:45 PM<br>Subject: MKCL 1.1.5 is now available<b=
 r>To: mkcl-announce &lt;<a href=3D"mailto:mkcl-announce <at> common-lisp.net">mk=
 cl-announce <at> common-lisp.net</a>&gt;, mkcl-devel &lt;<a href=3D"mailto:mkcl-=
 devel <at> common-lisp.net">mkcl-devel <at> common-lisp.net</a>&gt;<br>
 <br><br><div dir=3D"ltr"><div><div><div><div><div><div><div><div><div><div>=



Marco Antoniotti | 27 May 2013 13:26
Picon

Fwd: Delivery Status Notification (Failure)

One more mailing list not working….

Cheers

MA



Begin forwarded message:

Subject: Delivery Status Notification (Failure)
Date: May 27, 2013 11:13:20 AM GMT+02:00

This is an automatically generated Delivery Status Notification.

Delivery to the following recipients failed.

      cdr-discuss <at> common-lisp.net



Reporting-MTA: dns;mail.disco.unimib.it
Received-From-MTA: dns;vpn08.vpn.disco.unimib.it
Arrival-Date: Mon, 27 May 2013 11:13:18 +0200

Final-Recipient: rfc822;cdr-discuss <at> common-lisp.net
Action: failed
Status: 5.1.1
Diagnostic-Code: smtp;550 5.1.1 <cdr-discuss <at> common-lisp.net>: Recipient address rejected: User unknown in virtual mailbox table

From: Marco Antoniotti <marcoxa <at> cs.nyu.edu>
Subject: Re: [cdr-discuss] ECLM and ELS 2013 -- CDR Meeting?
Date: May 27, 2013 11:13:13 AM GMT+02:00


Dear all,

so, is there any interest in making a CDR BoF at ECLM or ELS?  I have a few ideas about a (short) list of topics for discussion.

All the best

MA




On Feb 17, 2013, at 14:08 , Pascal Costanza <pc <at> p-cos.net> wrote:

Hi,

Sounds good…

Pascal

On 15 Feb 2013, at 20:22, Marco Antoniotti <marcoxa <at> cs.nyu.edu> wrote:

Hi

how about setting up an "official" CDR meeting at ECLM and ELS 2013?

Just an idea….

--
Marco Antoniotti



_______________________________________________
cdr-discuss mailing list
cdr-discuss <at> common-lisp.net
http://lists.common-lisp.net/cgi-bin/mailman/listinfo/cdr-discuss

--
Pascal Costanza



--
Marco Antoniotti






--
Marco Antoniotti


Jean-Claude Beaudoin | 23 May 2013 21:43
Picon

Updating of GIT repositories mirrored on common-lisp.net is broken!

For projects that mirror their GIT repositories on
common-lisp.net it looks very much like the automatic
(cron based) updating has been broken since last April, 23.

I think the problem comes from a stale lock file named
cron.root.update-git-mirrors.run in directory /custom/run.
Could someone with root access remove that stale lock
and assure that the updating script can then run properly?

Thanks,

Jean-Claude Beaudoin

Raymond Toy | 15 May 2013 05:55
Picon

More mailing list issues


Can't remember if I mentioned this before, but when I submit a ticket
to trac, trac sends and email to the ticket mailing list.
(cmucl-ticket in this case).

But the message is held for moderation because it's coming from a
wrong address, I guess.  In this case, the From address is
cmucl-devel <at> .  

This used to work, without me having to approve of every message.

Did some old configuration not get restored or do I now need to update
something?

Ray

Drew C | 4 May 2013 00:23
Picon

Fwd: mailing lists: please restore all


Ok, I have set up all mailing lists over the last few days. Sorry about the time it took, but it was a lot of work to make sure things were ok. 

There was approximately 60+ mailing lists at the start of this week. I have re-enabled all of them as was asked :

root <at> alpha-cl-net:~# for ml in `find /home/drewc/ml`;  do    _BN=/var/spool/mlmmj/$(basename $ml) ;   if [ ! -d $_BN ]  ;   then     echo not found $_BN ;    sh $ml;   else echo "Found $ml" ;   fi ;  done 

ls /home/drewc/ml | wc -l
1272

Again, sorry about the time.

 -- drewc


On Mon, Apr 29, 2013 at 2:00 PM, Erik Huelsmann <ehuels <at> gmail.com> wrote:

On Sun, Apr 28, 2013 at 12:50 PM, Marco Antoniotti <marcoxa <at> cs.nyu.edu> wrote:

On Apr 28, 2013, at 10:58 , Anton Vodonosov <avodonosov <at> yandex.ru> wrote:

> There are mailing lists that are still down.
>
> I believe it is wrong approach to send emails to mailing list owners and
> restore only lists where list owners replied explicitly that the list is needed.

I second that.

If there were any reactions to this mail, can we make those public, so not every interested person needs to inquire separately?

Can I be updated on the status of mailing lists?


Regards,

Erik.


Raymond Toy | 2 May 2013 05:19
Picon

Mailing list changes?

Did something change with the mailing lists again?

Yesterday and today I got a bunch of welcome messages.  Yesterday was
for mailing lists that were already working (like cmucl-imp,
cmucl-announce).  Today, I got some for editor-hints-devel and cmucl-help.

Also, I got an welcome message for f2cl-annooi <at> common-lisp.net.  I can't
help but think that's a typo for f2cl-announce.  Can someone fix that,
please?

Ray

Anton Vodonosov | 28 Apr 2013 10:58
Picon
Favicon

mailing lists: please restore all

There are mailing lists that are still down.

I believe it is wrong approach to send emails to mailing list owners and
restore only lists where list owners replied explicitly that the list is needed.

Other way araound: all lists should be restored and only those explicitly requested
may be removed.

Note, the owner may be inactive, but there are other people who need the lists:
other subscribers, future subscribers, etc.

Best regards,
- Anton

Anton Vodonosov | 28 Apr 2013 10:56
Picon
Favicon

mailing lists: archives

The Internet is full of links to the common-lisp.net mailing list archives.
http://lists.common-lisp.net/pipermail/{list-name}/(year}-December/{some-numbers}.html

Today all these links are broken. I believen it is necessary to restore old mailmain archives.

I hope new mailing list sofware keeps archives. It is necessary to publish a link to new and old
archives on the mailins list info page. 

Also it is desiable that new archives include imported old messages, so that we see topic
threads inunterrupted, and search work for the whole archive body, instead of making
user to preform two searches: in the old archives and in the new.

Best regards,
- Anton

Anton Vodonosov | 28 Apr 2013 10:47
Picon
Favicon

mailing lists: listinfo page

I think every project which has mailing list on common-lisp.net has on the project page a link
to http://common-lisp.net/cgi-bin/mailman/listinfo/{list-name}.

Today all these links form all project pages are broken.

For those who unaware about the listinfo page. It allowed, for project owner to:
- change list options
- see the mailing list subscribers
- maybe something else I don't remember

For users it allsows to:
- subscribe
- unsubscribe
- change subscriptions options (e.g. receive every email, receive a digest, do not receive emails; and
other options).

Also this page linkns to the mailing list archives.

I think this functionality should be restored.

Best regards,
- Anton

Jean-Claude Beaudoin | 25 Apr 2013 09:47
Picon

Re: Questions about new mailing lists setup on common-lisp.net


On Wed, Apr 24, 2013 at 2:02 PM, Drew Crampsie <drew.crampsie <at> gmail.com> wrote:
> 1- Is there a web based interface to browse the archive of a list?

Not yet. It is trivial to do and will be done, but this is the first time it has been requested ,and there are only 15 or so messages that need archived (lists are not very busy it seems), so it will be done shorty. It is trivial to do so : http://mlmmj.org/archive/mlmmj/2010-08/0000002.html and http://mlmmj.org/docs/readme-archives/ .

> 2- Is the mailman era archive of each list now simply
    unreachable from the web? 

It shouldn't be. Give me a http:// URL that should work?

> 3- Is there a web based interface for new users to subscribe
    to a list? 

not really, though it may be done soon. But, <a href="mailto:projectfoo-devel+subscribe <at> common-lisp.net"> ... </a> is easy enough for now.

>  From what I understand now there is no password associated
     with a subscription to a list, nor is there any password
     associated with the owner/admin role of a list.  

Can you tell me what you have read that makes it seem like very very insecure? Also, what are you talking about "password associated
     with ..."?

> Am I wrong
in believing that now someone simply has to send emails 
with a forged From: field to hijack control of the list/subscription?

Well, what made you believe that? Is there a simple way that folks can easily hijack a list over email? 

As far as I know, it was audited by a company that worries about such things, http://mlmmj.org/docs/readme-security/ , and does not have a problem... can you please show me how/where/when you are able to hijack a list? mlmmj-test <at> common-lisp.net is a great place to start, and please feel free to hijack it.

Let me know if I have answered all the questions, and let me know the security holes you have discovered.

 -- drewc


Indeed you have answered all the questions I asked and this does clarify the current situation.

Thank you,

Jean-Claude Beaudoin



 





 

 


On Wed, Apr 24, 2013 at 2:00 AM, Jean-Claude Beaudoin <jean.claude.beaudoin <at> gmail.com> wrote:

I have been trying to figure out the new project mailing lists setup
on common-lisp.net for the last few hours. I think I more or less
understand now how the lists setup is to be used but I still
have a few questions left:

1- Is there a web based interface to browse the archive of a list?

2- Is the mailman era archive of each list now simply
    unreachable from the web?

3- Is there a web based interface for new users to subscribe
    to a list?  Or, do we have to explain them on the project page
    that they need to send email to say
    "projectfoo-devel+subscribe <at> common-lisp.net" in order
    to subscribe to the projectfoo-devel list?

4- From what I understand now there is no password associated
     with a subscription to a list, nor is there any password
     associated with the owner/admin role of a list.  Am I wrong
     in believing that now someone simply has to send emails
     with a forged From: field to hijack control of the list/subscription?

Thanks,

Jean-Claude Beaudoin



Jean-Claude Beaudoin | 24 Apr 2013 11:00
Picon

Questions about new mailing lists setup on common-lisp.net


I have been trying to figure out the new project mailing lists setup
on common-lisp.net for the last few hours. I think I more or less
understand now how the lists setup is to be used but I still
have a few questions left:

1- Is there a web based interface to browse the archive of a list?

2- Is the mailman era archive of each list now simply
    unreachable from the web?

3- Is there a web based interface for new users to subscribe
    to a list?  Or, do we have to explain them on the project page
    that they need to send email to say
    "projectfoo-devel+subscribe <at> common-lisp.net" in order
    to subscribe to the projectfoo-devel list?

4- From what I understand now there is no password associated
     with a subscription to a list, nor is there any password
     associated with the owner/admin role of a list.  Am I wrong
     in believing that now someone simply has to send emails
     with a forged From: field to hijack control of the list/subscription?

Thanks,

Jean-Claude Beaudoin


Gmane