date:20160308

Re: [Mailman-Developers] Patch for HyperArch

2016-03-08 Thread Mark Sapiro

On 03/08/2016 04:42 AM, Sebastian Hagedorn wrote:
> 
> Here are the culprits. They are now easy to find, because they are all
> new in the archive :-) (which is public, btw:
> )
> 
...
> 
> Then there are a few broken spam messages:
> 
> --
> 
>> From owner-linux-us...@rrz.uni-koeln.de  Mon Nov  7 14:13:18 2005
...
> Date: 18 ãöîáø 2000
> 
>> From owner-linux-us...@rrz.uni-koeln.de  Mon Nov  7 14:08:09 2005
...
> Date: Sun, 30 Jun 0102 17:30:47 -0600
> 
>> From owner-linux-us...@rrz.uni-koeln.de  Mon Nov  7 14:11:54 2005
...
> Date: Fri, 4 Feb 100 00:51:42 +0100 (MET)


I'm still having difficulty duplicating what you saw.

For the above three messages, the first one just gets detected as an
invalid date and archived under the current date by the current bin/arch.

The other two throw "ValueError: year out of range" at

  File "/var/MM/21/Mailman/Archiver/HyperArch.py", line 984, in
dateToVolName
return time.strftime("%Y-%B",datetuple)

which is a problem, but not the one you saw. I would like to see
messages that cause this error

  File "/usr/lib/mailman/Mailman/Archiver/HyperArch.py", line 601, in
_set_date
self.fromdate = time.ctime(int(self.date))
ValueError: timestamp out of range for platform time_t

that you reported. Can you find those bad messages in the .mbox input
file you used and send them to me?

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
___
Mailman-Developers mailing list
Mailman-Developers@python.org
https://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: 
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

[Mailman-Developers] Mailman3- postorius_standalone Issues

2016-03-08 Thread Stephen J. Turnbull

Fotso Fono writes:

 > Hello, i am trying to set up Mailman3 everything has been moving on
 > well. i ran the command "python manage.py runserver" in
 > postorius_stanalone. when i access localhost:8000 and error pops on
 > the terminal saying "no module middleware found" and an error page
 > is displayed on browser. I tried getting the root of the problem.

 > In postorius_stanalone in the MIDDLEWARE_CLASSES,
 > "postorius.middleware.PostoriusMiddleware" seems to be the one
 > causing the the problem.

Depending on how you set up your installation (you need to tell us
that!!), you *may* be able to just remove that line.  See
https://gitlab.com/mailman/postorius/issues/107 for slightly more
information.

___
Mailman-Developers mailing list
Mailman-Developers@python.org
https://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: 
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

[Mailman-Developers] Mailman3- postorius_standalone Issues

2016-03-08 Thread Fotso Fono

Hello, i am trying to set up Mailman3 everything has been moving on well. i
ran the command "python manage.py runserver" in postorius_stanalone. when i
access localhost:8000 and error pops on the terminal saying "no module
middleware found" and an error page is displayed on browser. I tried
getting the root of the problem.
In postorius_stanalone in the MIDDLEWARE_CLASSES,
"postorius.middleware.PostoriusMiddleware"  seems to be the one causing the
the problem. Please is there any solution to this or have i done something
wrong?? I am new to mailman. thanks in advance
___
Mailman-Developers mailing list
Mailman-Developers@python.org
https://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: 
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

Re: [Mailman-Developers] [Mailman-Developters] GSoC support

2016-03-08 Thread Barry Warsaw

On Mar 06, 2016, at 12:29 AM, Abhilash Raj wrote:

>Right now, Mailman sends each email it receives to the (enabled)
>Archivers through a POST request. We want to have a pub/sub kind of
>model for the emails as well as some of the events that other archivers
>or apps built on top of mailman can consume. Events like ListCreated,
>ListRemoved or something like that.

>On 03/06/2016 12:19 AM, amil shanaka wrote:
>> Hi,
>> thank you for your reply. other than that can we use any open source
>> packages like netty and what prototype do we need to implement regarding
>> pub/sub .. MQTT or AMQP ?   
>
>The idea is to make a common interface that can use any messaging
>back-end that does the Job. I guess MQTT is meant for high latency and
>unreliable network, not much of our use case, so AMQP should be more
>relevant. However, I am not very aware about the current trends in the
>message passing and pub/sub models out there right now.

Something to keep in mind is that internally, the core already employs
zope.events to inform non-local components when certain things happen.

A good example is ConfigurationUpdatedEvent which gets emitted in the
_post_process() method of the Configuration class.  Thus components like the
i18n infrastructure and language manager, the switchboards, style managers,
etc. can respond to the event.

More events can certainly be added, but we already have events such as
ListCreatingEvent/ListCreatedEvent, ListDeletingEvent/ListDeletedEvent, and
AcceptEvent, which is used when the message is accepted for posting, but is as
yet unprocessed by the handler pipeline.

One important implementation detail is that it's currently not very convenient
to register new event subscribers.  mailman.app.events.initialize() is where
this happens, but it's all hard coded.  Ideally there would be a .cfg/.ini
file or some such that this would read dynamically to add new event
subscribers.

Anyway, with all that, I think you could fairly easily write a pubsub
component that responded to the events you care about.

Cheers,
-Barry
___
Mailman-Developers mailing list
Mailman-Developers@python.org
https://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: 
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

Re: [Mailman-Developers] Patch for HyperArch

2016-03-08 Thread Sebastian Hagedorn


--On 7. März 2016 um 14:35:47 -0800 Mark Sapiro  wrote:


If an exception is caught, the date is simply set to the current time.


I understand the patch, but I'm not sure if setting the current time is
appropriate. In particular, the self.__super_set_date(message) method,
if it doesn't find a valid date: or x-list-received-date: header in the
message will set the time to that of the previous article + 1 second.


I suppose that didn't work, because there were multiple such messages in a 
row, if you can even call them that ;-)



In any case, I'd like to understand more about why/how the issue occurs.
To that end, I'd like to see a copy of the offending message from the
mbox file. Also, I wonder if bypassing the error and setting a date
which will almost certainly archive the message in the wrong period is
better than fixing the message in the mbox.


The thing is that initially I had no way of finding out which messages 
caused the problem. That's why I primarily looked for a way to just 
complete the job of rebuilding the archive. I agree that there may be 
better solutions. I could imagine skipping such broken messages, for 
example.


Here are the culprits. They are now easy to find, because they are all new 
in the archive :-) (which is public, btw: 
)


-

From foo@bar  Mon Nov  7 14:08:46 2005

169562

From foo@bar  Mon Nov  7 14:08:46 2005

27203

From foo@bar  Mon Nov  7 14:08:46 2005

108420

From foo@bar  Mon Nov  7 14:08:46 2005

35662

--

Don't ask me how they ended up in that .mbox file in the first place ;-)
I assume they are an artefact from the time when we moved from Majordomo to 
Mailman.


Then there are a few broken spam messages:

--

From owner-linux-us...@rrz.uni-koeln.de  Mon Nov  7 14:13:18 2005
Received: (from daemon@localhost)
   by mail1.rrz.Uni-Koeln.DE (8.9.3/8.9.3) id CAA05687
   for linux-users-out; Mon, 18 Dec 2000 02:34:21 +0100 (MET)
Received: from horizon.barak-online.net (horizon.barak.net.il 
[206.49.94.218])

   by mail1.rrz.Uni-Koeln.DE (8.9.3/8.9.3) with ESMTP id CAA05681
   for ; Mon, 18 Dec 2000 02:34:18 +0100 
(MET)
Received: from rrz.uni-koeln.de (pop09-1-ras1-p146.barak.net.il 
[212.150.107.146])

   by horizon.barak-online.net (8.9.3/8.9.1) with SMTP id DAA28082
   for linux-us...@rrz.uni-koeln.de; Mon, 18 Dec 2000 03:33:39 +0200 
(IST)

Message-Id: <200012180133.daa28...@horizon.barak-online.net>
From: mnadiv
REPLY-TO: mna...@barak-online.net
X-Mailer: EzyMassMailer V2.xx
Date: 18 ãöîáø 2000

From owner-linux-us...@rrz.uni-koeln.de  Mon Nov  7 14:08:09 2005
Received: from mail1.rrz.Uni-Koeln.DE (localhost [127.0.0.1])
   by mail1.rrz.Uni-Koeln.DE (8.12.3/8.12.2) with ESMTP id 
g5UBbvtD027896
   (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 
verify=NOT)
   for ; Sun, 30 Jun 2002 
13:37:57 +0200 (MEST)

Received: (from daemon@localhost)
   by mail1.rrz.Uni-Koeln.DE (8.12.3/8.12.3/Submit) id g5UBbvU7027895
   for linux-users-out; Sun, 30 Jun 2002 13:37:57 +0200 (MEST)
Received: from yahoo.com ([213.201.170.67])
   by mail1.rrz.Uni-Koeln.DE (8.12.3/8.12.2) with SMTP id 
g5UBbstC027887
   for ; Sun, 30 Jun 2002 13:37:55 +0200 
(MEST)
Received: from [181.21.240.177] by f64.law4.hottestmale.com with asmtp; 01 
Jul 0102 04:46:55 -0900
Received: from 15.9.163.146 ([15.9.163.146]) by m10.grp.snv.yahui.com with 
QMQP; Sun, 30 Jun 0102 19:38:13 -0800

Reply-To: 
Message-ID: <025b58a45d4d$4771c5b1$6dd17ce3@warwgu>
From: 
To: susann...@yahoo.com
Subject: Hello
Date: Sun, 30 Jun 0102 17:30:47 -0600

--

There is a single legitimate message with a broken Date header:

From owner-linux-us...@rrz.uni-koeln.de  Mon Nov  7 14:11:54 2005
Received: (from daemon@localhost)
   by mail1.rrz.Uni-Koeln.DE (8.9.3/8.9.3) id AAA14125
   for linux-users-out; Fri, 4 Feb 2000 00:50:08 +0100 (MET)
Received: from mailhost.informatik.uni-bonn.de 
(olymp.informatik.uni-bonn.de [131.220.4.1])

   by mail1.rrz.Uni-Koeln.DE (8.9.3/8.9.3) with ESMTP id AAA14116
   for ; Fri, 4 Feb 2000 00:50:06 +0100 
(MET)
Received: from zeus.informatik.uni-bonn.de (zeus.informatik.uni-bonn.de 
[131.220.5.25])

   by mailhost.informatik.uni-bonn.de (Postfix) with ESMTP
   id 15D5562E9; Fri,  4 Feb 2000 00:51:32 +0100 (MET)
Received: (from guertler@localhost)
   by zeus.informatik.uni-bonn.de (8.8.8+Sun/8.8.8) id AAA19251;
   Fri, 4 Feb 2000 00:51:43 +0100 (MET)
From: Michael Guertler 
Message-Id: <22032351.aaa19...@zeus.informatik.uni-bonn.de>
Subject: Re: AVI -> MPEG
To: ocor...@astro.uni-bonn.de (Oliver Cordes)
Date: Fri, 4 Feb 100 00:51:42 +0100 (MET)

At the very least I would suggest that arch should dump the headers of the 
offending message, so that it can be repaired, but I'm open for other 
suggestions.


Cheers
Sebastian
--
   .:.Sebastian Hagedorn - We

Re: [Mailman-Developers] Pastebin considered "suboptimal" [was: Mailman-bundler installation]

2016-03-08 Thread Adam McGreggor

On Tue, Mar 08, 2016 at 05:42:33PM +0900, Stephen J. Turnbull wrote:
> Daman Singh writes:
>  > Here is a small suggestion, instead of pasting terminal text here you
>  > should consider using pastebin.

On the plus side, it was as text, not as a screen shot of a terminal
session…

> -1.  Pastebin goes away, making the post useless to anybody who
> experiences the same problem in the future.  Even while it lasts, it
> mean you have to search the whole web rather than site:mail.python.org
> for something you *know* you saw on mailman-developers.  (Google
> doesn't care, I suspect, but you can thin out the results quite
> quickly with a site: spec.)

And of course, follow the link to read the contents, rather than just
seeing it in your mail client (with the added bonus of being able to
make in-line replies; rather than clone (as pastebin doesn't have fork
like gists do))

-- 
"Unless specified in detail, all drinks are champagne in Lottie's 
 parlour."
-- Vile Bodies (Waugh)
___
Mailman-Developers mailing list
Mailman-Developers@python.org
https://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: 
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

Re: [Mailman-Developers] Mailman-bundler installation

2016-03-08 Thread Aditya Divekar

Hi,

Thanks Simon. I followed the docs and now Mailman 3.0 is up and running :)

And I'll keep that in mind henceforth @Daman Singh. Thanks.

Aditya.
___
Mailman-Developers mailing list
Mailman-Developers@python.org
https://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: 
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

Re: [Mailman-Developers] Mailman-bundler installation

2016-03-08 Thread Stephen J. Turnbull

Simon Hanna writes:

 > Mailman-bundler is for production setups and to just try it out.

So?  Of course he has to have a checkout to participate in
development, but given that we don't have a migration story yet, and
bundler keeps throwing errors for people, I don't see why developers
shouldn't use bundler as well as a from-checkout build.

Of course if a person's main interest is coding, bundler is
potentially something of a waste of time.

Steve
___
Mailman-Developers mailing list
Mailman-Developers@python.org
https://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: 
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

[Mailman-Developers] Pastebin considered "suboptimal" [was: Mailman-bundler installation]

2016-03-08 Thread Stephen J. Turnbull

Daman Singh writes:

 > Here is a small suggestion, instead of pasting terminal text here you
 > should consider using pastebin.

-1.  Pastebin goes away, making the post useless to anybody who
experiences the same problem in the future.  Even while it lasts, it
mean you have to search the whole web rather than site:mail.python.org
for something you *know* you saw on mailman-developers.  (Google
doesn't care, I suspect, but you can thin out the results quite
quickly with a site: spec.)

Steve



___
Mailman-Developers mailing list
Mailman-Developers@python.org
https://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: 
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

Re: [Mailman-Developers] Patch for HyperArch

[Mailman-Developers] Mailman3- postorius_standalone Issues

[Mailman-Developers] Mailman3- postorius_standalone Issues

Re: [Mailman-Developers] [Mailman-Developters] GSoC support

Re: [Mailman-Developers] Patch for HyperArch

Re: [Mailman-Developers] Pastebin considered "suboptimal" [was: Mailman-bundler installation]

Re: [Mailman-Developers] Mailman-bundler installation

Re: [Mailman-Developers] Mailman-bundler installation

[Mailman-Developers] Pastebin considered "suboptimal" [was: Mailman-bundler installation]

9 matches

Site Navigation

Mail list logo

Footer information