[Mailman-Users] MM3 - allow users to see other list members in

2021-02-11 Thread Stephen J. Turnbull
Stefan Bauer via Mailman-Users writes:

 > is there a way to display all list members on the list overview
 > page?

Not on that page itself.

If you are the list owner (or site owner), on the List Identity page
in List Settings, you can set Members List Visibility to moderators
only, to mailing list members (it says "only" but I'm pretty sure
moderators can see the list membership too), or to anyone.

In each case there will be a "Users" link on the List Overview page
for folks who are allowed to see the membership.

It is generally not a good idea to set it to anyone, as the "anyones"
most interested in your list membership are spammers.  Also, people
sometimes set their display names to embarrassing or somewhat private
things, that they wouldn't use if they thought the whole list could
see it.  Whether there is a risk or how much risk you want to take is
for you to judge, of course.  That's just the generic case.

Steve

--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/


[Mailman-Users] MM3 - allow users to see other list members in

2021-02-11 Thread Stefan Bauer via Mailman-Users
Hi,



is there a way to display all list members on the list overview page?



currently without logging in, one only sees the lists itself.




Thank you.

Stefan
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/


[Mailman-Users] MM3 - nested list - munge_from - Reply-To not persistent

2021-02-09 Thread Stefan Bauer via Mailman-Users
Hi,



is there a way to keep the real sender information in the Reply-To when nested 
lists are used?



We use munge_from and dmarc_mitigate_unconditionally true.



We have following lists:





ALL (RND,IT,SALES)







When Joe sends a mail to RND-list, Joe's Sender-Address is referenced in 
Reply-To.



When Joe sends a mail to ALL, ALL's list-address is referenced in Reply-To and 
not the one from the real sender - Joe.



Is there a way to keep the real-address even if nested lists are used?




thank you!



Stefan
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/


Re: [Mailman-Users] MM3 filter content

2020-03-02 Thread Mark Sapiro
On 3/2/20 12:35 AM, Eduardo Costa via Mailman-Users wrote:
> Hello,
> 
> How do I manage to activate and define the content filters in order to
> remove attachments at MM3?


The list for questions about Mailman 3 is mailman-us...@mailman3.org
.

That said, the MM 3 settings Filter content, Collapse alternatives and
Convert html to plaintext are exposed in Postorius -> Settings -> Alter
messages.

The other settings: filter_action, filter_extensions, filter_types,
pass_extensions and pass_types are not currently exposed in Postorius.
 They can be set via mailman shell.

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


[Mailman-Users] MM3 filter content

2020-03-02 Thread Eduardo Costa via Mailman-Users

Hello,

How do I manage to activate and define the content filters in order to 
remove attachments at MM3?


Best Regards

--
..
 Eduardo Costa
 Centro de Comunicações - Instituto Politécnico de Bragança
 raposo at ipb.pt
 http://www.ipb.pt/~raposo/
..



smime.p7s
Description: S/MIME Cryptographic Signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] MM3 startup issues

2020-01-06 Thread Mark Sapiro
Restoring original Subject:, and doesn't this thread belong on
mailman-us...@msailman3.org - CCing there.

On 1/5/20 11:51 PM, Allan Hansen wrote:
> 
> Thanks again, Mark!
> My responses below.
> 
>> On 1/4/20 5:47 PM, Allan Hansen wrote:
>>>
>>> a. The server was set up with the wrong domain name (our fault), so I had 
>>> to add the ‘correct’ one. I had seen the command ‘Add Domain’ in
>>> the UI and thought that would do it, but Brian kindly sent me a list of 
>>> additional instructions, which we then implemented. That made it possible 
>>> to create a list in the new domain, subscribe people and post messages. 
>>> However, messages are not archived. What extra step is needed to enable 
>>> archiving? 
>>
>>
>> What are the setytings in Postorius -> Settings -> Archiving?
> 
> Archive policy: Private archives
> Archive archivers: hyperkitty, prototype


Are the messages in Mailman's var/archives/prototype/LIST@DOMAIN/new
directory?

Are there messages in Mailman's var/archives/hyperkitty/spool/ directory?

What's the setting for base_url in mailman-hyperkitty.cfg?

Are there any errors in var/logs/mailman.log?

>>> b. When go to the server using the new domain (both before and after 
>>> logging in), I see not just the lists I created in the new domain, but the 
>>> lists created in the old domain. These lists of lists are domain specific 
>>> and should not be listed together. That’s just IMHO, but not serious, as I 
>>> will soon get rid of anything in the old domain. So feel free to ignore 
>>> this one if this is intended, which I could see might be the case.
>>
>>
>> Set
>>
>> FILTER_VHOST = True
>>
>> in settings_local.py
>>
> 
> Yes, Brian told me to do the same. This is the what I wrote back:
> 
> hansen@rccrmail:/opt/mailman/mm$ sudo vi settings.py
> 
> Edited the setting to:
> # Only display mailing-lists from the same virtual host as the webserver
> FILTER_VHOST = True


You shouldn't edit settings.py. You should override the setting by
putting it in settings_local.py.


> Then Brian told me to restart qcluster:
> hansen@rccrmail:/opt/mailman/mm$ sudo systemctl restart qcluster


qcluster is not what you need to restart. You need to restart whatever
is supporting the wsgi interface to Django. This may be uwsgi or
gunicorn or ??. Whatever it is, that's what needs to be restarted.


> I then logged in, but the same lists are showing. It either takes the system 
> a long time to reset or it has ignored the 
> setting.
> Just tried it again, and the lists are all showing. Do I need to manually 
> recompile the file?
> 
>>
>>> c. I then moved on to the templates and added a template for the message 
>>> text to send to new subscribers. That resulted in the following error 
>>> message when I went in as moderator to approve of a new subscription:
>>>
>>> Something went wrong
>>> Mailman REST API not available. Please start Mailman core.
>>
>>
>> Postorius is unable to access core's REST API. Is Mailman running?
> 
> Well, I was able to post to the lists, so I assume it is. Listing at 
> processes, I see a bunch of postgres, python3, nginx, django-adminp but
> nothing explicitly with a ‘mailman’ string.

If you do `ps ax|grep runner=`, what do you see? If you don't see at
least three processes with `--runner=rest:0:1`, stop Mailman and start
Mailman.


>> If so, what's in /opt/mailman/mm/var/logs/mailmansuite.log or whatever it's
>> called - defined as `filename` in the `file` handler in the LOGGING
>> definition in settings(_local).py.
> 
> hansen@rccrmail:/opt/mailman/mm/logs$ tail -f mailmansuite.log
> return Site.objects.get_current(request)
>   File 
> "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/contrib/sites/models.py",
>  line 60, in get_current
> return self._get_site_by_request(request)
>   File 
> "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/contrib/sites/models.py",
>  line 45, in _get_site_by_request
> SITE_CACHE[domain] = self.get(domain__iexact=domain)
>   File 
> "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/db/models/manager.py",
>  line 82, in manager_method
> return getattr(self.get_queryset(), name)(*args, **kwargs)
>   File 
> "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/db/models/query.py", 
> line 408, in get
> self.model._meta.object_name
> django.contrib.sites.models.Site.DoesNotExist: Site matching query does not 
> exist.


This is because of the domain change. In settings(_local).py you have a
setting for SITE_ID. Possibly, setting that in settings_local.py to a
value one greater that the current setting will do. To be certain of the
correct value, you need to look at the django_site table in mailman's
database. That table has 3 columns, id, domain and name. The id for the
row of your domain is what needs to be set as SITE_ID.


> [ABH] At this point I click to accept a subsription request:
> 
> ERROR 2020-01-06 07:32:41,439 699 postorius.middleware Mailman REST API not 
> available
> Traceback (most rec

Re: [Mailman-Users] MM3 startup issues

2020-01-04 Thread Mark Sapiro
On 1/4/20 5:47 PM, Allan Hansen wrote:
> 
> a. The server was set up with the wrong domain name (our fault), so I had to 
> add the ‘correct’ one. I had seen the command ‘Add Domain’ in
> the UI and thought that would do it, but Brian kindly sent me a list of 
> additional instructions, which we then implemented. That made it possible to 
> create a list in the new domain, subscribe people and post messages. However, 
> messages are not archived. What extra step is needed to enable archiving? 


What are the setytings in Postorius -> Settings -> Archiving?


> b. When go to the server using the new domain (both before and after logging 
> in), I see not just the lists I created in the new domain, but the lists 
> created in the old domain. These lists of lists are domain specific and 
> should not be listed together. That’s just IMHO, but not serious, as I will 
> soon get rid of anything in the old domain. So feel free to ignore this one 
> if this is intended, which I could see might be the case.


Set

FILTER_VHOST = True

in settings_local.py


> c. I then moved on to the templates and added a template for the message text 
> to send to new subscribers. That resulted in the following error message when 
> I went in as moderator to approve of a new subscription:
> 
> Something went wrong
> Mailman REST API not available. Please start Mailman core.


Postorius is unable to access core's REST API. Is Mailman running? If
so, what's in /opt/mailman/mm/var/logs/mailmansuite.log or whatever it's
called - defined as `filename` in the `file` handler in the LOGGING
definition in settings(_local).py.

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


[Mailman-Users] MM3 startup issues

2020-01-04 Thread Allan Hansen
After having MM3 installed, I’m trying to get it setup up correctly for my 
lists. I have a couple of issues at this point:

a. The server was set up with the wrong domain name (our fault), so I had to 
add the ‘correct’ one. I had seen the command ‘Add Domain’ in
the UI and thought that would do it, but Brian kindly sent me a list of 
additional instructions, which we then implemented. That made it possible to 
create a list in the new domain, subscribe people and post messages. However, 
messages are not archived. What extra step is needed to enable archiving? The 
instructions we received were these:

How to setup an additional domain to the Mailman 3 server:

• Add the additional domain name to Django Sites and Mail domains via 
the Django admin panel. This will require superuser access.
• Make sure the list admin(s) of any list is registered with Django.
• Setup the new list domain in nginx (/etc/nginx/conf.d). You can copy 
and paste the existing record there to the new record. Just make sure you 
modify the server_name directive in the record to the new domain name. The 
record file name should be newdomainname.com.conf. This will need to be done 
via shell with sudo privileges.
• Test nginx configuratin (nginx -t)
• Reload nginx (nginx -s reload)
• Generate LetsEncrypt Cert (certbot --nginx -d newdomainname.com) 
Before doing this make sure the appropriate DNS records are setup pointing the 
new list domain to your Mailman 3 server otherwise this part will fail.
• Add the new list domain to /opt/mailman/mm/settings_local.py in the 
ALLOWED_HOSTS section.
• Add list domain to Postorius.
• Create the list in Postorius using the new list domain.

b. When go to the server using the new domain (both before and after logging 
in), I see not just the lists I created in the new domain, but the lists 
created in the old domain. These lists of lists are domain specific and should 
not be listed together. That’s just IMHO, but not serious, as I will soon get 
rid of anything in the old domain. So feel free to ignore this one if this is 
intended, which I could see might be the case.

c. I then moved on to the templates and added a template for the message text 
to send to new subscribers. That resulted in the following error message when I 
went in as moderator to approve of a new subscription:

Something went wrong
Mailman REST API not available. Please start Mailman core.

Oh, and Happy New Year to all,

Allan Hansen



--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] MM3 on FreeBSD

2018-11-02 Thread Mark Sapiro
P.S. A better list for Mailman 3 is
.


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


Re: [Mailman-Users] MM3 on FreeBSD

2018-11-02 Thread Mark Sapiro
On 10/22/18 6:41 AM, Odhiambo Washington wrote:
> 
> What next now?? Edit the var/etc/mailman.cfg??


If necessary.


> Then how to launch the MM3 queue runner?


mailman start


> Postorius? HyperKitty? etc?


See .

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


Re: [Mailman-Users] MM3 on FreeBSD

2018-11-02 Thread David Magda
You may want to contact the current MM2 port maintainer,  mandree -at- 
FreeBSD.org

https://www.freshports.org/mail/mailman/


> On Oct 22, 2018, at 09:41, Odhiambo Washington  wrote:
> 
> I have finally read bits of documents here and there and managed to install
> MM3 on a FreeBSD 11.2 server. This is for testing and getting to grasp the
> new monster. Later, I hope I could run my MLs on MM3.
> 
> So, so far, this is what I have done - all successfully:
[…]

--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org


[Mailman-Users] MM3 on FreeBSD

2018-10-22 Thread Odhiambo Washington
Hola a todos!

I have finally read bits of documents here and there and managed to install
MM3 on a FreeBSD 11.2 server. This is for testing and getting to grasp the
new monster. Later, I hope I could run my MLs on MM3.

So, so far, this is what I have done - all successfully:

pkg install python36
pkg install py36-sqlite3
[ln -s /usr/local/bin/python3.6 /usr/local/bin/python3]
python3 -m ensurepip
pip3 install mailman

I have opted to use /opt/mailman3 as the directory for MM3.
So I did:

cd /opt
mkdir mailman3
cd mailman3
mailman info
[Here I got some errors, which Google led me to set some ENV variables]
export LC_ALL=en_US.UTF-8
export LANG=en_US.UTF-8
mailman info

The directory has been populated with some data.

# Then from http://docs.mailman3.org/en/latest/prodsetup.html
pip3 install postorius
pip3 install hyperkitty
pip3 install mailman-hyperkitty
pip3 install uwsgi

All those installed successfully. However, I am not sure where they
installed into on my FreeBSD, but I guess no es importa :)

What next now?? Edit the var/etc/mailman.cfg??

Then how to launch the MM3 queue runner? Postorius? HyperKitty? etc?


TIA


-- 
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft."
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] MM3 book in the works

2018-02-09 Thread Rich Kulawiec
On Sat, Jan 13, 2018 at 06:34:03PM +, Tom Browder wrote:
> Good deal, Rich, that book is sorely needed IMHO! Is there any place we can
> sign up to get a copy or see its status?

I'm currently shoving Markdown into my brain at an accelerated pace
while simultaneously stitching together a number of already-written
modules into something that might vaguely resemble cohesive chapters.
This is not happening in a particular order, e.g., chapters 7 and 3
may emerge before chapter 1.  But as soon as they're ready, I'll make
pieces available for review.

---rsk
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] MM3 book

2018-02-09 Thread Mark Sapiro
On 02/09/2018 04:01 AM, Ert Retre via Mailman-Users wrote:
> I would love to see a new book on MM3.  Anyone know of such a project
> proposed or in the works?
> 
> FWIW, the new Perl 6 world (see https://perl6.org) has produced several
> books in the last year and some were started via various “fund me” websites.
> 
> Best regards,


Interesting. The above text exactly duplicates that in a post to this
list a few weeks ago. See that post and replies in the archives at
.

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


[Mailman-Users] MM3 book

2018-02-09 Thread Ert Retre via Mailman-Users
I would love to see a new book on MM3.  Anyone know of such a project
proposed or in the works?

FWIW, the new Perl 6 world (see https://perl6.org) has produced several
books in the last year and some were started via various “fund me” websites.

Best regards,
--
Alexander Garcia
https://www.drillanddriver.com


 
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] MM3 book in the works

2018-01-18 Thread Stephen J. Turnbull
Besides Rich's forthcoming book, Barry has an existing chapter on
Mailman's architecture in The Architecture of Open Source
Applications, Vol. II (eds. Amy Brown and Greg Wilson).

Tom Browder writes:
 > On Sat, Jan 13, 2018 at 12:07 Rich Kulawiec  wrote:

 > > I've been working on a book about mailing list management and usage --
 > > including MTAs, MLMs (such as Mailman), processes, best practices, etc.
 > > The MM material to this point has been MM2-centric, but I've been running
 > > various instances of MM3 and accumulating experience with it.

--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] MM3 book in the works

2018-01-16 Thread Barry Warsaw
On Jan 13, 2018, at 09:38, Rich Kulawiec  wrote:

> I've been working on a book about mailing list management and usage --
> including MTAs, MLMs (such as Mailman), processes, best practices, etc.
> The MM material to this point has been MM2-centric, but I've been running
> various instances of MM3 and accumulating experience with it.
> 
> This is intended -- somewhat -- as a modern version of "Managing
> Mailing Lists" by Schwartz, which is now 20 years old.  Obviously
> the landscape has changed quite a bit since then; I don't think
> we need to worry much about UUCP-style addresses any more, but we
> do need to worry about DMARC.  And so on.
> 
> I can't see leaving out MM2 at this point, because a LOT of people are
> running and are going to be running it for years.  But it would seem
> a disservice not to cover MM3.  So I suspect, at the risk of some
> duplication, both with have to make the cut.

Very cool, Rich.  And I think you’ve got exactly the right focus.  Best of luck 
and do let us know when you’ve got something you need reviewed, or if you have 
any questions at all (esp. regarding MM3).

-Barry



signature.asc
Description: Message signed with OpenPGP
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] MM3 book in the works

2018-01-13 Thread Tom Browder
On Sat, Jan 13, 2018 at 12:07 Rich Kulawiec  wrote:

> On Sat, Jan 13, 2018 at 05:27:01PM +, Tom Browder wrote:
> > I would love to see a new book on MM3.  Anyone know of such a project
> > proposed or in the works?
>
> I've been working on a book about mailing list management and usage --
> including MTAs, MLMs (such as Mailman), processes, best practices, etc.
> The MM material to this point has been MM2-centric, but I've been running
> various instances of MM3 and accumulating experience with it.


Good deal, Rich, that book is sorely needed IMHO! Is there any place we can
sign up to get a copy or see its status?

Best regards,

-Tom
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] MM3 book in the works

2018-01-13 Thread Rich Kulawiec
On Sat, Jan 13, 2018 at 05:27:01PM +, Tom Browder wrote:
> I would love to see a new book on MM3.  Anyone know of such a project
> proposed or in the works?

I've been working on a book about mailing list management and usage --
including MTAs, MLMs (such as Mailman), processes, best practices, etc.
The MM material to this point has been MM2-centric, but I've been running
various instances of MM3 and accumulating experience with it.

This is intended -- somewhat -- as a modern version of "Managing
Mailing Lists" by Schwartz, which is now 20 years old.  Obviously
the landscape has changed quite a bit since then; I don't think
we need to worry much about UUCP-style addresses any more, but we
do need to worry about DMARC.  And so on.

I can't see leaving out MM2 at this point, because a LOT of people are
running and are going to be running it for years.  But it would seem
a disservice not to cover MM3.  So I suspect, at the risk of some
duplication, both with have to make the cut.

---rsk
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org


[Mailman-Users] MM3 book in the works

2018-01-13 Thread Tom Browder
I would love to see a new book on MM3.  Anyone know of such a project
proposed or in the works?

FWIW, the new Perl 6 world (see https://perl6.org) has produced several
books in the last year and some were started via various “fund me” websites.

Best regards,

-Tom
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] MM3 and analytics

2017-07-15 Thread Mark Sapiro
On 07/15/2017 07:52 AM, Tom Browder wrote:
> Are there any hooks or plugins or known solutions to gathering MM3
> analytics similar to, say, Dada Mail?


For Mailman 3 specific posts, please join the mailman-us...@mailman3.org
list at

and post there.

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


[Mailman-Users] MM3 and analytics

2017-07-15 Thread Tom Browder
Are there any hooks or plugins or known solutions to gathering MM3
analytics similar to, say, Dada Mail?

Thanks.

-Tom
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org


[Mailman-Users] MM3/HyperKitty and importing Malman2 lists

2015-07-10 Thread Stephen J. Turnbull
Isaac Bennetch writes:

 > I feel I'm missing something here, any idea what it could be?

Dunno what's going with your import, but you probably won't find the
core HyperKitty devs here -- they are mostly on
mailman-develop...@python.org.

Sorry I can't be of more direct help!

Steve
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org


[Mailman-Users] MM3/HyperKitty and importing Malman2 lists

2015-07-10 Thread Isaac Bennetch
Hi,

Thanks for the good work bringing us Mailman3. I'm doing a new install,
which is intended to import data from a different server which had been
running Mailman2. I've used the mailman-bundler to install and have a
few questions. At this point, I'm still using the SQLite backend but
have hopes of using MySQL (I know MySQL better than PostgreSQL, and the
manual seems to imply that sticking with SQLite may not be ideal).

I'm currently attempting to import the old mbox into Hyperkitty[0],
which I think I've adapted in to

> ./bin/django-admin hyperkitty-import --pythonpath
eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/ -l test...@example.org
/home/mailman/old-list.mbox

Which doesn't say much (full output below[1]), but didn't fully work.
Out of approximately 18300 messages, only six are visible to me through
the "Mailing-List Archives" web page, and one of them has a very strange
date. It is the second message of the mbox, from 9 Apr 2001, but appears
in the web page with approximately the date/time of the import: 9 July
2015  7:27 p.m. Additionally, the remaining five messages are all the
most recent -- with the exception of the most recent message not
appearing at all.

Additionally, if I use the Search box to search for a word that I know
appears in (at least) one message, I get no results found.

I feel I'm missing something here, any idea what it could be?

Furthermore, I haven't found any substantial documentation on importing
a subscriber list from Mailman2; is there anything that will allow me to
transfer subscribers, their digest preference, and so on without
requiring them all to resubscribe manually?

Thanks in advance,
~isaac


0 - https://hyperkitty.readthedocs.org/en/latest/development.html

1 -
> Importing from mbox file /home/mailman/old-list.mbox to test...@example.org
> /No 'Message-Id' header in email from None about None
> -No 'Message-Id' header in email from None about None
> \No 'Message-Id' header in email from None about None
> |No 'Message-Id' header in email from None about None
> /No 'Message-Id' header in email from None about None
> -No 'Message-Id' header in email from None about None
> \No 'Message-Id' header in email from None about None
> |No 'Message-Id' header in email from None about None
> /No 'Message-Id' header in email from None about None
> -No 'Message-Id' header in email from None about None
> \No 'Message-Id' header in email from None about None
> |No 'Message-Id' header in email from None about None
> Computing thread structure
> Synchronizing properties with Mailman
> /usr/local/src/mailman-bundler/eggs/Django-1.7.8-py2.7.egg/django/db/models/fields/__init__.py:1282:
>  RuntimeWarning: DateTimeField MailingList.created_at received a naive 
> datetime (2015-07-04 14:30:22.803087) while time zone support is active.
>   RuntimeWarning)
> 
> WARNING 
> /usr/local/src/mailman-bundler/eggs/Django-1.7.8-py2.7.egg/django/db/models/fields/__init__.py:1282:
>  RuntimeWarning: DateTimeField MailingList.created_at received a naive 
> datetime (2015-07-04 14:30:22.803087) while time zone support is active.
>   RuntimeWarning)
> 
> The full-text search index will be updated every minute. Run the 'manage.py 
> runjob update_index' command to update it now.


--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] MM3/Delivery Problem

2014-11-01 Thread Guillaume Libersat
Awesome!
Do you think it will be easy to migrate from an existing sqlite database
to a postgres one through SQLAlchemy? I tried to do it manually a few
days ago... and it took me such a long time writing ah-hoc scripts
for almost nothing (the database is not really usable).
I'm really interested in testing the new backend if you need testers :)

Cheers,

Guillaume

Le 31/10/2014 19:55, Barry Warsaw a écrit :
> On Oct 31, 2014, at 07:47 PM, Guillaume Libersat wrote:
>
>> The problem is now fixed... I don't really know what happened but it
>> seems it was related to sqlite3 and database locking.
>>
>> Thanks for helping, if I manage to find what really happened, I'll file
>> a bug report.
> Very soon (perhaps this weekend) I will land the port to SQLAlchemy as our ORM
> layer for MM3 in the trunk.  This is based on great work by Abhilash and
> Aurelien.  There have been some reports of SQLite locking problems in MM3 and
> it will be interesting to see whether the port from Storm to SA will fix that.
>
> Cheers,
> -Barry
> --
> Mailman-Users mailing list Mailman-Users@python.org
> https://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Security Policy: http://wiki.list.org/x/QIA9
> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
> Unsubscribe: 
> https://mail.python.org/mailman/options/mailman-users/glibersat%40sigill.org

-- 
http://sigill.org

--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] MM3/Delivery Problem

2014-10-31 Thread Barry Warsaw
On Oct 31, 2014, at 07:47 PM, Guillaume Libersat wrote:

>The problem is now fixed... I don't really know what happened but it
>seems it was related to sqlite3 and database locking.
>
>Thanks for helping, if I manage to find what really happened, I'll file
>a bug report.

Very soon (perhaps this weekend) I will land the port to SQLAlchemy as our ORM
layer for MM3 in the trunk.  This is based on great work by Abhilash and
Aurelien.  There have been some reports of SQLite locking problems in MM3 and
it will be interesting to see whether the port from Storm to SA will fix that.

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


Re: [Mailman-Users] MM3/Delivery Problem

2014-10-31 Thread Guillaume Libersat
The problem is now fixed... I don't really know what happened but it
seems it was related to sqlite3 and database locking.

Thanks for helping, if I manage to find what really happened, I'll file
a bug report.

Cheers,

Guillaume

Le 30/10/2014 20:13, Mark Sapiro a écrit :
> On 10/30/2014 07:48 AM, Guillaume Libersat wrote:
>> We're running a mailman 3.0.0b at ulists.org and so far it was working
>> quite well. Since a few days, email delivery seems to be broken, but
>> only for the posts, not bounces.
>> When someone subscribes, he gets the welcome message.
>> When someone posts, nothing is delivered. Same when posting from hyperkitty.
>
> I'll note a few things below, but this list is mostly still oriented
> towards Mailman 2.1. The MM 3 folks pay much more attention to the
> mailman-develop...@python.org list and the #mailman irc channel on
> freenode.net.
>
>
>> Here's what happens when en email is sent to a list:
>>
>> On the MM3 side:
>>
>> Oct 30 15:34:36 2014 (1387)
>> <20141030143436.1389.15...@mailman.ulists.org> smtp to t...@ulists.org
>> for 1 recips, completed in 0.0919508934021 seconds
>> Oct 30 15:34:36 2014 (1387)
>> <20141030143436.1389.15...@mailman.ulists.org> post to t...@ulists.org
>> from test-requ...@ulists.org, 1177 bytes
>
> This says the post was sent to 1 recipient. If there's nothing in
> Mailman's smtp-failure log, it was accepted by the outgong MTA.
>
>
>> and on the smtp side:
>>
>> Oct 30 15:34:36 mailman postfix/qmgr[7675]: CEF7719628BC:
>> from=, size=718, nrcpt=1 (queue active)
>> Oct 30 15:34:36 mailman postfix/lmtp[2526]: CEF7719628BC:
>> to=, relay=127.0.0.1[127.0.0.1]:8024, delay=0.14,
>> delays=0.0
>> 6/0.04/0/0.04, dsn=2.0.0, status=sent (250 Ok)
>> Oct 30 15:34:36 mailman postfix/qmgr[7675]: CEF7719628BC: removed
>
> This is the incoming post being delivered to Mailman. We already know
> that succeeded.
>
>
>> Any idea of what I should check?
>
> What is in the outgoing MTA logs for the post from
> test-boun...@ulists.org to the list member?
>

-- 
http://sigill.org

--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] MM3/Delivery Problem

2014-10-30 Thread Mark Sapiro
On 10/30/2014 07:48 AM, Guillaume Libersat wrote:
> 
> We're running a mailman 3.0.0b at ulists.org and so far it was working
> quite well. Since a few days, email delivery seems to be broken, but
> only for the posts, not bounces.
> When someone subscribes, he gets the welcome message.
> When someone posts, nothing is delivered. Same when posting from hyperkitty.


I'll note a few things below, but this list is mostly still oriented
towards Mailman 2.1. The MM 3 folks pay much more attention to the
mailman-develop...@python.org list and the #mailman irc channel on
freenode.net.


> Here's what happens when en email is sent to a list:
> 
> On the MM3 side:
> 
> Oct 30 15:34:36 2014 (1387)
> <20141030143436.1389.15...@mailman.ulists.org> smtp to t...@ulists.org
> for 1 recips, completed in 0.0919508934021 seconds
> Oct 30 15:34:36 2014 (1387)
> <20141030143436.1389.15...@mailman.ulists.org> post to t...@ulists.org
> from test-requ...@ulists.org, 1177 bytes


This says the post was sent to 1 recipient. If there's nothing in
Mailman's smtp-failure log, it was accepted by the outgong MTA.


> and on the smtp side:
> 
> Oct 30 15:34:36 mailman postfix/qmgr[7675]: CEF7719628BC:
> from=, size=718, nrcpt=1 (queue active)
> Oct 30 15:34:36 mailman postfix/lmtp[2526]: CEF7719628BC:
> to=, relay=127.0.0.1[127.0.0.1]:8024, delay=0.14,
> delays=0.0
> 6/0.04/0/0.04, dsn=2.0.0, status=sent (250 Ok)
> Oct 30 15:34:36 mailman postfix/qmgr[7675]: CEF7719628BC: removed


This is the incoming post being delivered to Mailman. We already know
that succeeded.


> Any idea of what I should check?


What is in the outgoing MTA logs for the post from
test-boun...@ulists.org to the list member?

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


[Mailman-Users] MM3/Delivery Problem

2014-10-30 Thread Guillaume Libersat
Hi,

We're running a mailman 3.0.0b at ulists.org and so far it was working
quite well. Since a few days, email delivery seems to be broken, but
only for the posts, not bounces.
When someone subscribes, he gets the welcome message.
When someone posts, nothing is delivered. Same when posting from hyperkitty.

Here's what happens when en email is sent to a list:

On the MM3 side:

Oct 30 15:34:36 2014 (1387)
<20141030143436.1389.15...@mailman.ulists.org> smtp to t...@ulists.org
for 1 recips, completed in 0.0919508934021 seconds
Oct 30 15:34:36 2014 (1387)
<20141030143436.1389.15...@mailman.ulists.org> post to t...@ulists.org
from test-requ...@ulists.org, 1177 bytes

and on the smtp side:

Oct 30 15:34:36 mailman postfix/qmgr[7675]: CEF7719628BC:
from=, size=718, nrcpt=1 (queue active)
Oct 30 15:34:36 mailman postfix/lmtp[2526]: CEF7719628BC:
to=, relay=127.0.0.1[127.0.0.1]:8024, delay=0.14,
delays=0.0
6/0.04/0/0.04, dsn=2.0.0, status=sent (250 Ok)
Oct 30 15:34:36 mailman postfix/qmgr[7675]: CEF7719628BC: removed

Any idea of what I should check?

Thanks a lot !

Guillaume
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] MM3 Test "" Hangs

2014-02-26 Thread Tom Browder
On Wed, Feb 26, 2014 at 12:45 AM, Stephen J. Turnbull
 wrote:
> Tom Browder writes:
...
> Actually, I do have a couple of ideas.  First, you should always
> report the whole error trace (if you think that's ugly in an email,
...

Thanks, Steve, for the good advice.

-Tom
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org


[Mailman-Users] MM3 Test "" Hangs

2014-02-25 Thread Stephen J. Turnbull
Tom Browder writes:

We really appreciate your efforts to test the betas of Mailman 3.  But
please do be aware that although there are sites already successfully
using Mailman 3 in production, the development team doesn't recommend
use of any of the components (core, Postorius, HyperKitty) in
production yet.

 > I have no idea what to do next,

Nothing. :-)  I've already Cc'd (and set Reply-To to) mailman-developers,
which is a more appropriate place for this report.  (Many Mailman-Users
are not interested in MM3 yet, while Mailman-Developers are by
definition, as MM2 is basically end-of-life.  Also, some relevant
developers may read mailman-developers more frequently than they read
mailman-users.)

Actually, I do have a couple of ideas.  First, you should always
report the whole error trace (if you think that's ugly in an email,
attach it as a file).  In this particular case, I suspect that the
problem is in the test before the one that caused the Exception, which
failed leaving the database locked.  It would be very helpful to
identify that test, which would probably be the *first* frame in the
trace.

Second, you should look in the server's logs to see if there were any
errors that might have caused the incomplete transaction.

 > and help or ideas would be greatly appreciated. 

If you have no idea, then reporting to the developers is the best you
can do.  Use "Mailman Developers"  or
report via Launchpad.

Pretty clearly what's happened is that some previous test locked the
database (probably anything that accesses the database does so at
least long enough to read the whole record), and either (1) that test
failed to unlock the database, (2) the test framework failed to unlock
the database, or (3) the tests were improperly sequenced in some way
and the database didn't get unlocked.  It's quite possible that this
failure could never be replicated in actual use, as tests often mock
up some component that would normally ensure that any pending
transaction gets discarded and the database unlocked.

Unfortunately I don't have an up-to-date test installation (it's on my
list for early next week), and looking at the test file doesn't tell
me anything.  Perhaps Barry has an idea for a fix, or a workaround.
And there's probably a way to skip that test, but I don't know nose
very well.

Steve

Original report follows:

 > i have started investigating MM3 for my new, remote server and
 > branched from lp:mailman, lp:postorius, and lp:hyperkitty.
 > 
 > I started in the MM3 branch directory and followed instructions in
 > src/mailman/docs/START.rst.
 > 
 > I got the virtualenv ready to go and, in the local mailman branch
 > directory, I executed:
 > 
 >   $  node2 -v
 > 
 > All tests chug along nicely until:
 > 
 >   /usr/local/src/0-mailman3/src/mailman/rest/docs/membership.rst ...
 > 
 > and it hangs longer than I think it should.  After a  the last
 > few trace-back lines are:
 > 
 >   File 
 > "/home/virtualenvs/mm3/local/lib/python2.7/site-packages/storm-0.20-py2.7-linux-i686.egg/storm/database.py",
 > line 374, in raw_execute
 > self._run_execution(raw_cursor, args, params, statement)
 >   File 
 > "/home/virtualenvs/mm3/local/lib/python2.7/site-packages/storm-0.20-py2.7-linux-i686.egg/storm/database.py",
 > line 388, in _run_execution
 > self._check_disconnect(raw_cursor.execute, *args)
 >   File 
 > "/home/virtualenvs/mm3/local/lib/python2.7/site-packages/storm-0.20-py2.7-linux-i686.egg/storm/database.py",
 > line 454, in _check_disconnect
 > return function(*args, **kwargs)
 > sqlite3.OperationalError: database is locked
 > 
 > Note I am running the MM3 installation, via ssh, on a remote host
 > running Debian 7, 32-bit. (Note also postfix is running.)
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org


[Mailman-Users] MM3 Test "" Hangs

2014-02-25 Thread Tom Browder
i have started investigating MM3 for my new, remote server and
branched from lp:mailman, lp:postorius, and lp:hyperkitty.

I started in the MM3 branch directory and followed instructions in
src/mailman/docs/START.rst.

I got the virtualenv ready to go and, in the local mailman branch
directory, I executed:

  $  node2 -v

All tests chug along nicely until:

  /usr/local/src/0-mailman3/src/mailman/rest/docs/membership.rst ...

and it hangs longer than I think it should.  After a  the last
few trace-back lines are:

  File 
"/home/virtualenvs/mm3/local/lib/python2.7/site-packages/storm-0.20-py2.7-linux-i686.egg/storm/database.py",
line 374, in raw_execute
self._run_execution(raw_cursor, args, params, statement)
  File 
"/home/virtualenvs/mm3/local/lib/python2.7/site-packages/storm-0.20-py2.7-linux-i686.egg/storm/database.py",
line 388, in _run_execution
self._check_disconnect(raw_cursor.execute, *args)
  File 
"/home/virtualenvs/mm3/local/lib/python2.7/site-packages/storm-0.20-py2.7-linux-i686.egg/storm/database.py",
line 454, in _check_disconnect
return function(*args, **kwargs)
sqlite3.OperationalError: database is locked

Note I am running the MM3 installation, via ssh, on a remote host
running Debian 7, 32-bit. (Note also postfix is running.)

I have no idea what to do next, and help or ideas would be greatly appreciated.

Best regards,

-Tom
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] MM3

2013-06-10 Thread Jan Lausch
Dear all,
  
Stephen J. Turnbull wrote:
> Yeah, this is a problem. There's been a lot of water flowed under
> that bridge since then, but you can only see it if you look at the
> source trees (I mean the NEWS files, not the .py files :-).


Thanks for getting me up to speed.
I am looking forward to the final thing and I think I just might give the beta 
a try this summer on a staging machine...
And thank you for putting your free time into MM! You guys are great!

Best regards,
Jan
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] MM3 [was: Re: Custom Pages]

2013-06-07 Thread Stephen J. Turnbull
Jan Lausch writes:

 > I mean, the main wiki page
 > http://wiki.list.org/display/DEV/Mailman+3.0 has been last updated
 > 3 years ago.

Yeah, this is a problem.  There's been a lot of water flowed under
that bridge since then, but you can only see it if you look at the
source trees (I mean the NEWS files, not the .py files :-).

It would be nice if somebody would take a look at the state of the
world and update the front page of the wiki and maybe ghost-write a
blog entry for Barry.

I personally might be in a position to do it at reasonable personal
cost around mid-summer (I'm mentoring a GSoC student so will need to
get back up to speed on the state of the art), but not before then.

Steve
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] MM3 [was: Re: Custom Pages]

2013-06-06 Thread Mark Sapiro
On 06/06/2013 05:52 AM, Jan Lausch wrote:
> 
> I really don't want to complain at people who donate spare time for good, 
> please don't take this as offensive, but is there any indication of a release 
> date or a mayor pre-release or, well, let's be honest: is there any progress 
> at all?


To add a bit to Barry's reply, there have been a few beta releases of
the core. At least one site is using it in production.

Postorius is still alpha, but much is going on.

Look at the commits at
 and
 and the bug
trackers and you'll see much is being done and many are involved.

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


Re: [Mailman-Users] MM3 [was: Re: Custom Pages]

2013-06-06 Thread Barry Warsaw
On Jun 06, 2013, at 02:52 PM, Jan Lausch wrote:

>What's up with MM3? 
>Is there any indication on when it will be ready?

Yes, although most of the conversation happens on mailman-developers these
days.  I expect we'll see a lot of great progress on Postorius (the new web
ui) during this year's Google Summer of Code, which should bring that
component much closer to release.  We'll do a join release of the core + ui
after that.

-Barry
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


[Mailman-Users] MM3 [was: Re: Custom Pages]

2013-06-06 Thread Jan Lausch
Guys,


> Also, my attitude would be much different if we were talking about
> something that was not already at the end of its life cycle.

This brings me to a question I keep asking myself once every year for quite 
some time now: 

What's up with MM3? 
Is there any indication on when it will be ready?

I really don't want to complain at people who donate spare time for good, 
please don't take this as offensive, but is there any indication of a release 
date or a mayor pre-release or, well, let's be honest: is there any progress at 
all?

I mean, the main wiki page http://wiki.list.org/display/DEV/Mailman+3.0 has 
been last updated 3 years ago. Still, their list of work to be done looks good 
- but that's probably only the tip of the work to be done. On the other hand 
the frontend works don't even seem to have begun properly (no templating engine 
chosen, only mockups)...

I really don't want to be impolite and I know that you aren't in charge, but: 
Do you know anything more than us? Is there any work going on? Is it dead? 

I have been living with mailman limitations for so many years now and still it 
is one very reliable and great work of code - but still there's so much more 
this could be and let's face it: mailing lists aren't currently gaining ground 
as the web develops. I believe many people could have great use for a modern 
state of the art mailing engine with the features that are currently up to date.

Regards,
jan
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org