Mailman 3 December 2015 - Mailman-Developers

Re: [Mailman-Developers] Let's try to package mailman3 in Debian!
by Pierre-Elliott Bécue 14 Dec '15

14 Dec '15

Le lundi 14 décembre 2015 à 17:36:10+0100, Simon Hanna a écrit : > On 12/14/2015 05:01 PM, Pierre-Elliott Bécue wrote: > >One can find my work here : https://github.com/P-EB/mailman3-core > >Small bump here, I'd appreciate if somebody finds the time to tell me two > >things: > > > > * Is my config file enough for a start ? > > * Is my systemd service good to have mailman started properly ? > You seem to be missing a "start" at the end of ExecStart Indeed, fixed! Thanks. :) -- PEB

1 0

A list where no subscriber can post: can anyone spot the bad config?
by Terri Oda 10 Dec '15

10 Dec '15

I've got a list where, for some reason, I can post, but no one else seems to be able to. It *looks* like I can post because I was somehow in accept_these_nonmembers. It's a list converted from Mailman 2.1, so I'm suspicious that it's some sort of cruft in the config. I'm pasting in a mildly anonymized version of the config. Can anyone spot anything that could be causing all messages to go to moderation? This list is also on a mailman bundler install that may not have been updated correctly (aka I guessed and tried buildout on it), but the problems with posting predate that. I think, honestly, that I'm at the point where I should dump the rosters and re-recreate all the lists on this machine. (They're relatively small, all under 20 subscribers I think) >>> pprint(vars(m)) {'_list_id': 'gf.lists.example.com', '_preferred_language': 'en', '_sa_instance_state': <sqlalchemy.orm.state.InstanceState object at 0x7f3e5cf32828>, 'accept_these_nonmembers': ['c(a)example.com', 'terri(a)toybox.ca', 'd(a)example.com', 'j(a)example.com', 'a(a)example.com', 'v(a)example.com'], 'admin_immed_notify': True, 'admin_notify_mchanges': True, 'administrators': <mailman.model.roster.AdministratorRoster object at 0x7f3e5cf328d0>, 'administrivia': False, 'advertised': False, 'allow_list_posts': True, 'anonymous_list': False, 'archive_policy': <ArchivePolicy.never: 0>, 'autorespond_owner': <ResponseAction.none: 0>, 'autorespond_postings': <ResponseAction.none: 0>, 'autorespond_requests': <ResponseAction.none: 0>, 'autoresponse_grace_period': datetime.timedelta(90), 'autoresponse_owner_text': '', 'autoresponse_postings_text': '', 'autoresponse_request_text': '', 'bounce_info_stale_after': datetime.timedelta(7), 'bounce_matching_headers': '\n' "# Lines that *start* with a '#' are comments.\n" 'to: friend(a)public.com\n' 'message-id: relay.comanche.denmark.eu\n' 'from: list(a)listme.com\n' 'from: .*(a)uplinkpro.com\n', 'bounce_notify_owner_on_disable': True, 'bounce_notify_owner_on_removal': True, 'bounce_score_threshold': 5, 'bounce_you_are_disabled_warnings': 3, 'bounce_you_are_disabled_warnings_interval': datetime.timedelta(7), 'collapse_alternatives': True, 'convert_html_to_plaintext': True, 'created_at': datetime.datetime(2014, 2, 12, 9, 30, 13, 418107), 'default_member_action': <Action.accept: 3>, 'default_nonmember_action': <Action.accept: 3>, 'description': '', 'digest_footer_uri': 'mailman:///$listname/$language/footer-generic.txt', 'digest_header_uri': None, 'digest_is_default': False, 'digest_last_sent_at': datetime.datetime(2015, 11, 4, 18, 39, 56, 724986), 'digest_members': <mailman.model.roster.DigestMemberRoster object at 0x7f3e5cf32978>, 'digest_send_periodic': True, 'digest_size_threshold': 30.0, 'digest_volume_frequency': <DigestFrequency.monthly: 1>, 'digestable': True, 'discard_these_nonmembers': [], 'display_name': 'Gf', 'emergency': False, 'encode_ascii_prefixes': False, 'filter_action': <FilterAction.discard: 2>, 'filter_content': False, 'first_strip_reply_to': False, 'footer_uri': 'mailman:///$listname/$language/footer-generic.txt', 'forward_auto_discards': True, 'forward_unrecognized_bounces_to': <UnrecognizedBounceDisposition.administrators: 1>, 'gateway_to_mail': False, 'gateway_to_news': False, 'goodbye_message_uri': '', 'header_matches': [], 'header_uri': None, 'hold_these_nonmembers': [], 'id': 1, 'include_rfc2369_headers': True, 'info': '', 'last_post_at': datetime.datetime(2015, 8, 19, 8, 12, 6, 169075), 'linked_newsgroup': '', 'list_name': 'gf', 'mail_host': 'lists.example.com', 'max_days_to_hold': 0, 'max_message_size': 0, 'max_num_recipients': 10, 'member_moderation_notice': '', 'members': <mailman.model.roster.MemberRoster object at 0x7f3e5cf32908>, 'mime_is_default_digest': False, 'moderator_password': None, 'moderators': <mailman.model.roster.ModeratorRoster object at 0x7f3e5cf32898>, 'newsgroup_moderation': <NewsgroupModeration.none: 0>, 'next_digest_number': 1, 'next_request_id': 25, 'nntp_prefix_subject_too': True, 'nondigestable': True, 'nonmember_rejection_notice': '', 'nonmembers': <mailman.model.roster.NonmemberRoster object at 0x7f3e5cf329e8>, 'obscure_addresses': True, 'owner_chain': 'default-owner-chain', 'owner_pipeline': 'default-owner-pipeline', 'owners': <mailman.model.roster.OwnerRoster object at 0x7f3e5cf32860>, 'personalize': <Personalization.none: 0>, 'post_id': 1138, 'posting_chain': 'default-posting-chain', 'posting_pipeline': 'default-posting-pipeline', 'process_bounces': True, 'regular_members': <mailman.model.roster.RegularMemberRoster object at 0x7f3e5cf32940>, 'reject_these_nonmembers': [], 'reply_goes_to_list': <ReplyToMunging.no_munging: 0>, 'reply_to_address': '', 'require_explicit_destination': False, 'respond_to_post_requests': True, 'scrub_nondigest': False, 'send_goodbye_message': True, 'send_welcome_message': True, 'subject_prefix': '[GF] ', 'subscribers': <mailman.model.roster.Subscribers object at 0x7f3e5cf329b0>, 'subscription_policy': <SubscriptionPolicy.confirm_then_moderate: 3>, 'topics': [], 'topics_bodylines_limit': 5, 'topics_enabled': False, 'volume': 22, 'welcome_message_uri': 'mailman:///$listname/$language/welcome.txt'}

2 1

Upgrading from Mailman 3.0 installed with mailman-bundler: sassc error
by Terri Oda 10 Dec '15

10 Dec '15

Hit an issue while upgrading mailman bundler that I'm just going to note here in case it affects anyone else. After upgrading, I go to the web interface and try to log in only to get the following error: “/bin/sh: sassc: command not found” Which as a security person is the type of error message I least like seeing, but that's another story. ;) This thankfully made me think of the last commit message in mailman-bundler, and the commits helped me figure out the rest: https://gitlab.com/mailman/mailman-bundler/commit/3d6555acd640d77f510b786e5… the solution is 1. install rubygem-sass 2. update mailman_web/development.py so that COMPRESS_PRECOMPILERS asks for sass instead of sassc I'm sure I'm going to find a few more bugs as I go, but I wanted to note that one before I forgot. Terri

3 3

MM3 trying to buildout / errors
by fsantiago＠garbage-juice.com 10 Dec '15

10 Dec '15

Why on centos 7 do i receive the following when attempting to build MM3 using the mailman-bundler package: (venv)[mailman3@mail mailman-bundler-3.0.0]$ buildout Creating directory '/downloads/mailman-bundler-3.0.0/eggs'. Creating directory '/downloads/mailman-bundler-3.0.0/bin'. Creating directory '/downloads/mailman-bundler-3.0.0/parts'. Creating directory '/downloads/mailman-bundler-3.0.0/develop-eggs'. Develop: '/downloads/mailman-bundler-3.0.0/.' warning: no files found matching '*.in' under directory 'mailman_bundler' warning: no files found matching '*.in' under directory 'deployment' warning: no files found matching 'deployment/mailman-web.logrotate.conf' Getting distribution for 'djangorecipe'. warning: no previously-included files found matching 'Makefile' warning: no previously-included files found matching '*.yml' warning: no previously-included files found matching 'bootstrap.py' Got djangorecipe 2.1.2. Getting distribution for 'Django'. no previously-included directories found matching 'django/contrib/admin/bin' warning: no previously-included files matching '__pycache__' found under directory '*' File "build/bdist.linux-x86_64/egg/django/conf/app_template/apps.py", line 4 class {{ camel_case_app_name }}Config(AppConfig): ^ SyntaxError: invalid syntax File "build/bdist.linux-x86_64/egg/django/conf/app_template/models.py", line 1 {{ unicode_literals }}from django.db import models ^ SyntaxError: invalid syntax File "/downloads/mailman-bundler-3.0.0/eggs/tmpR9TGDA/Django-1.9-py2.7.egg/django/conf/app_template/apps.py", line 4 class {{ camel_case_app_name }}Config(AppConfig): ^ SyntaxError: invalid syntax File "/downloads/mailman-bundler-3.0.0/eggs/tmpR9TGDA/Django-1.9-py2.7.egg/django/conf/app_template/models.py", line 1 {{ unicode_literals }}from django.db import models ^ SyntaxError: invalid syntax Got Django 1.9. Getting distribution for 'zc.recipe.egg>=2.0.0a3'. Got zc.recipe.egg 2.0.3. Getting distribution for 'collective.recipe.cmd'. warning: no previously-included files matching '*.pyc' found anywhere in distribution warning: no previously-included files found matching 'bootstrap.py' warning: no previously-included files found matching 'buildout.cfg' warning: no previously-included files found matching 'tox.ini' Got collective.recipe.cmd 0.11. Getting distribution for 'z3c.recipe.filetemplate'. Got z3c.recipe.filetemplate 2.2.0. templates: No template found for these file names: *.in While: Installing. Getting section templates. Initializing section templates. Error: No template found for these file names: *.in (venv)[mailman3@mail mailman-bundler-3.0.0]$ ?????? Thanks. - Fabian S.

2 1

Fwd: Request to mailing list Tom rejected
by Fabian Santiago 09 Dec '15

09 Dec '15

Someone subscribed a list to this list? Sincerely, Fabian Santiago Sent from my iPhone Begin forwarded message: > From: tom-owner(a)esestudios.com > Date: December 8, 2015 at 1:03:36 AM EST > To: fsantiago(a)garbage-juice.com > Subject: Request to mailing list Tom rejected > > Your request to the Tom mailing list > > Posting of your message titled "[Mailman-Developers] MM3 trying to > buildout / errors" > > has been rejected by the list moderator. The moderator gave the > following reason for rejecting your request: > > "Blind carbon copies or other implicit destinations are not allowed. > Try reposting your message by explicitly including the list address in > the To: or Cc: fields." > > Any questions or comments should be directed to the list administrator > at: > > tom-owner(a)esestudios.com

2 1