Mailman 3 July 2015 - Mailman-Developers

Re: [Mailman-Developers] Merging users
by Abhilash Raj 29 Jul '15

29 Jul '15

Hi Aurelien, On 21 July 2015 at 22:09, Aurelien Bompard <aurelien(a)bompard.org> wrote: > Hey devs! > > I'm hitting a problem when migrating from 2.1 to 3, but I think it's a > generic issue (or rather a missing feature) and I'd like to fix it. > > If I try to associate an existing address to an existing user (without > this address obviously), the Mailman API will reply with a 400 error > "User already exists". Postorius currently does not detect that and > just errors out with a 500 page (but that's not the issue here). > I tried doing this on a mailman shell, and I was able to associate an existing address with an existing user. And, I was able to reproduce the 404 error when using the REST API. I think it is a bug in the REST API. > I think I need to merge the two users, and that's currently not > supported. I believe it would be a useful feature, so I'd like to > discuss it here. IMHO, the only tricky part would be to merge the > preferences associated with each user, but if I know which of my two > users has priority, I can just resolve the conflicts that way. > Are you talking about merging Postorius' users or Mailman's users here? What I feel is that it would be a useful feature for Postorius. Mailman already as decoupled users and addresses. In case we want to merge two users, we can just associate the second user's address with the first user and delete the second user. Here I am assuming that first user has priority and his preferences are to be saved. Whereas in Postorius this is quite a big problem. I don't think we can add multiple addresses to a django.contrib.auth.User model. Even though we have a custom MailmanUser model too, but for logging in a user we depend on django's User model. This means, the user can never login to his same account through the alternate address. What do you think? -- thanks, Abhilash Raj

1 0

Re: [Mailman-Developers] Trying to get started developing Mailman
by Thomas Storey 26 Jul '15

26 Jul '15

After I made those aforementioned changes (sorry email got sent prematurely) I have finally managed to send to and receive mail from my local list successfully. Thank you for your help! I'm sure I'll be back with more questions in the future. On Sun, Jul 26, 2015 at 1:00 PM Thomas Storey <storey.thomas(a)gmail.com> wrote: > Thanks for your continued help Mark! Sorry for the untidy list usage. > When I first subscribed to this list about a month and a half ago I set my > subscription to digest mode, but it seems the password I have stored in my > password manager is incorrect, so I can't set it off, which has not been > helpful for this discussion obviously. Thank you for bearing with me! > > In my /etc/postfix/main.cf file I indeed had both virtual_alias_maps and > transport_maps set to my /.../mailman/var/data/postfix_lmtp file. I removed > the virtual_alias_map setting and tried again, and did in fact get some > encouraging behavior. > > After that, sending mail to mailman(a)augusta.net did not bounce, and > indeed did make it to the list, but the list was unable to send mail to > users subscribed to the list. I looked in the mail.log again and saw: > NOQUEUE: reject: RCPT from localhost[127.0.0.1]: 550 5.1.1 < > thomas(a)augusta.net>: Recipient address rejected: User unknown in local > recipient table; ... > After some searching around, I found that the transport maps settings > sometimes don't work and it's better to use aliases. > So I removed the local_recipients_maps and relay_domains lines, and mapped > the alias_maps and alias_database lines to my > /.../mailman/var/data/postfix_lmtp files in my main.cf file. I also > removed the mailman lines in master.cf (the ones that look like this: > mailman unix - n n - - pipe > flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py > ## ${nexthop} ${user} > >

1 0

Re: [Mailman-Developers] Trying to get started developing Mailman
by Thomas Storey 26 Jul '15

26 Jul '15

Thanks for your continued help Mark! Sorry for the untidy list usage. When I first subscribed to this list about a month and a half ago I set my subscription to digest mode, but it seems the password I have stored in my password manager is incorrect, so I can't set it off, which has not been helpful for this discussion obviously. Thank you for bearing with me! In my /etc/postfix/main.cf file I indeed had both virtual_alias_maps and transport_maps set to my /.../mailman/var/data/postfix_lmtp file. I removed the virtual_alias_map setting and tried again, and did in fact get some encouraging behavior. After that, sending mail to mailman(a)augusta.net did not bounce, and indeed did make it to the list, but the list was unable to send mail to users subscribed to the list. I looked in the mail.log again and saw: NOQUEUE: reject: RCPT from localhost[127.0.0.1]: 550 5.1.1 < thomas(a)augusta.net>: Recipient address rejected: User unknown in local recipient table; ... After some searching around, I found that the transport maps settings sometimes don't work and it's better to use aliases. So I removed the local_recipients_maps and relay_domains lines, and mapped the alias_maps and alias_database lines to my /.../mailman/var/data/postfix_lmtp files in my main.cf file. I also removed the mailman lines in master.cf (the ones that look like this: mailman unix - n n - - pipe flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py ## ${nexthop} ${user}

1 0

Re: [Mailman-Developers] Trying to get started developing Mailman
by Mark Sapiro 25 Jul '15

25 Jul '15

On 7/25/15 4:37 AM, Thomas Storey wrote: > Thanks for the help. I have double-checked my postfix configuration to make > sure it is like yours, but my mail to the list still bounces. > mail.log looks like this when I try to send a message to the list (in this > case named mailman(a)augusta.net): > ... > Jul 25 07:20:39 augusta postfix/local[4490]: C40252006E5: > to=<lmtp:[127.0.0.1]:8024@localhost>, orig_to=<mailman(a)augusta.net>, > relay=local, delay=0.26, delays=0.24/0/0/0.03, dsn=5.1.1, status=bounced > (unknown use$ ... > essentially, bounced because of unknown user > and the actual bounce notification in /var/mail/thomas is similar: > > <"lmtp:[127.0.0.1]:8024"@localhost> (expanded from <mailman(a)augusta.net>): > unknown user: "lmtp:[127.0.0.1]:8024" It looks like you have configured some Mailman generated file in Postfix as virtual_alias_maps that should be transport_maps. If you installed via mailman-bundler, the suggested Postfix config lines should be in deployment/postfix-main.cf. If you still have trouble, post the output of 'postconf -n'. > On Sat, Jul 25, 2015 at 6:02 AM <mailman-developers-request(a)python.org> > wrote: > >> Send Mailman-Developers mailing list submissions to >> mailman-developers(a)python.org ... Please don't quote entire digests in list replies. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Gsoc Status Update: Dashboard for Admins
by Bhavesh Goyal 25 Jul '15

25 Jul '15

Hey ! I Just updated my Blog with an update of The Project Progress so far. Attached to The Blog is also a preview of The Dashboard for those who have't been able to test it yet on their machine. Interested people can have a look at Blog Link: http://towardsgsoc15.wordpress.com Regards, Bhavesh

1 0

Re: [Mailman-Developers] Trying to get started developing Mailman
by Thomas Storey 25 Jul '15

25 Jul '15

Thanks for the help. I have double-checked my postfix configuration to make sure it is like yours, but my mail to the list still bounces. mail.log looks like this when I try to send a message to the list (in this case named mailman(a)augusta.net): Jul 25 07:20:39 augusta postfix/pickup[4387]: C40252006E5: uid=1000 from=<thomas@augusta> Jul 25 07:20:39 augusta postfix/cleanup[4488]: C40252006E5: message-id=< 20150725112039.C40252006E5(a)augusta.net> Jul 25 07:20:39 augusta postfix/qmgr[4388]: C40252006E5: from=<thomas@augusta>, size=343, nrcpt=1 (queue active) Jul 25 07:20:39 augusta postfix/local[4490]: C40252006E5: to=<lmtp:[127.0.0.1]:8024@localhost>, orig_to=<mailman(a)augusta.net>, relay=local, delay=0.26, delays=0.24/0/0/0.03, dsn=5.1.1, status=bounced (unknown use$ Jul 25 07:20:39 augusta postfix/cleanup[4488]: D113C2006F1: message-id=< 20150725112039.D113C2006F1(a)augusta.net> Jul 25 07:20:39 augusta postfix/bounce[4509]: C40252006E5: sender non-delivery notification: D113C2006F1 Jul 25 07:20:39 augusta postfix/qmgr[4388]: D113C2006F1: from=<>, size=2158, nrcpt=1 (queue active) Jul 25 07:20:39 augusta postfix/qmgr[4388]: C40252006E5: removed Jul 25 07:20:39 augusta postfix/local[4490]: D113C2006F1: to=<thomas@augusta>, relay=local, delay=0.05, delays=0.03/0/0/0.03, dsn=2.0.0, status=sent (delivered to mailbox) Jul 25 07:20:39 augusta postfix/qmgr[4388]: D113C2006F1: removed essentially, bounced because of unknown user and the actual bounce notification in /var/mail/thomas is similar: <"lmtp:[127.0.0.1]:8024"@localhost> (expanded from <mailman(a)augusta.net>): unknown user: "lmtp:[127.0.0.1]:8024" --C40252006E5.1437823239/augusta.net Content-Description: Delivery report Content-Type: message/delivery-status Reporting-MTA: dns; augusta.net X-Postfix-Queue-ID: C40252006E5 X-Postfix-Sender: rfc822; thomas@augusta Arrival-Date: Sat, 25 Jul 2015 07:20:39 -0400 (EDT) Final-Recipient: rfc822; "lmtp:[127.0.0.1]:8024"@localhost Original-Recipient: rfc822; mailman(a)augusta.net Action: failed Status: 5.1.1 Diagnostic-Code: X-Postfix; unknown user: "lmtp:[127.0.0.1]:8024" I have tried with and without a user on my system named "mailman", either way the message bounces if sent to mailman(a)augusta.net, but with a user it goes through if sent to mailman@localhost (when there is a user), which I find odd. I can send mail to other users fine with <name>@augusta.net. Thanks for any further assistance! Sorry for the newbish questions. On Sat, Jul 25, 2015 at 6:02 AM <mailman-developers-request(a)python.org> wrote: > Send Mailman-Developers mailing list submissions to > mailman-developers(a)python.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://mail.python.org/mailman/listinfo/mailman-developers > or, via email, send a message with subject or body 'help' to > mailman-developers-request(a)python.org > > You can reach the person managing the list at > mailman-developers-owner(a)python.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Mailman-Developers digest..." > > > Today's Topics: > > 1. Trying to get started developing Mailman (Thomas Storey) > 2. Re: Trying to get started developing Mailman (Mark Sapiro) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 24 Jul 2015 16:37:40 +0000 > From: Thomas Storey <storey.thomas(a)gmail.com> > To: mailman-developers(a)python.org > Subject: [Mailman-Developers] Trying to get started developing Mailman > Message-ID: > <CABqwFzN_HH28NyC46VfXtP59izwJBDU53Z6T94kCKS+JaP_5= > w(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > Hello Mailman developers, > > I am trying to get started developing Mailman but I am having difficulty > setting up a local development/test environment on my machine (Ubuntu 14.04 > LTS). I used black-perl's lovely development bootstrap to set up my virtual > environments and initially install Mailman and postorious, but I can't seem > to get a mailing list to actually work! > > I followed the excellent documentation at > http://mailman.readthedocs.org/en/latest/src/mailman/docs/MTA.html to > configure postfix and Mailman to talk to each other. I created a mailing > list called "testlist" through the postorious interface. I subscribed > myself and a testuser to the list, but sending mail via: > > echo "test body text" | mail -s "test subject" testlist(a)augusta.net > > simply results in a bounced email message in /var/mail/thomas (my user on > my machine). > augusta.net is the domain I specified during postfix configuration. > Sending > mail like above to "testuser(a)augusta.net" works perfectly (mail appears in > /var/mail/testuser). The only reason I made it is because Mailman won't let > you make a list @localhost. > > Does anyone have any advice for setting up a local-only mailing list > environment so I can test behavior as I poke around in the code? Ideally I > want to be able to just send emails via the command line to the local > Mailman instance and have Mailman send emails out to local users that are > subscribed to its lists. I am stumped as to how to get this going, and I > feel like I must be fundamentally misunderstanding how things are supposed > to be done. > > Thanks for any guidance you can give me. > > -Thomas > > > ------------------------------ > > Message: 2 > Date: Fri, 24 Jul 2015 09:52:15 -0700 > From: Mark Sapiro <mark(a)msapiro.net> > To: mailman-developers(a)python.org > Subject: Re: [Mailman-Developers] Trying to get started developing > Mailman > Message-ID: <55B26D3F.4000606(a)msapiro.net> > Content-Type: text/plain; charset=windows-1252 > > On 7/24/15 9:37 AM, Thomas Storey wrote: > > ... but sending mail via: > > > > echo "test body text" | mail -s "test subject" testlist(a)augusta.net > > > > simply results in a bounced email message in /var/mail/thomas (my user on > > my machine). > > > And what does the bounce (or Postfix's mail.log) say is the reason why > it's undeliverable? > > > > Does anyone have any advice for setting up a local-only mailing list > > environment so I can test behavior as I poke around in the code? Ideally > I > > want to be able to just send emails via the command line to the local > > Mailman instance and have Mailman send emails out to local users that are > > subscribed to its lists. I am stumped as to how to get this going, and I > > feel like I must be fundamentally misunderstanding how things are > supposed > > to be done. > > > My main development machine's IP is actually in DNS as msapiro.net. I > have Postfix on that machine configured with mydomain and myhostname = > msapiro.net and mydestination = msapiro.net, localhost.localdomain, > localhost. > > My other machines (traveling laptops) are similar, but I also have > > 127.0.0.1 msapiro.net > > in /etc/hosts to override the DNS. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers(a)python.org > https://mail.python.org/mailman/listinfo/mailman-developers > > > ------------------------------ > > End of Mailman-Developers Digest, Vol 315, Issue 13 > *************************************************** >

1 0

Re: [Mailman-Developers] Trying to get started developing Mailman
by Mark Sapiro 24 Jul '15

24 Jul '15

On 7/24/15 9:37 AM, Thomas Storey wrote: > ... but sending mail via: > > echo "test body text" | mail -s "test subject" testlist(a)augusta.net > > simply results in a bounced email message in /var/mail/thomas (my user on > my machine). And what does the bounce (or Postfix's mail.log) say is the reason why it's undeliverable? > Does anyone have any advice for setting up a local-only mailing list > environment so I can test behavior as I poke around in the code? Ideally I > want to be able to just send emails via the command line to the local > Mailman instance and have Mailman send emails out to local users that are > subscribed to its lists. I am stumped as to how to get this going, and I > feel like I must be fundamentally misunderstanding how things are supposed > to be done. My main development machine's IP is actually in DNS as msapiro.net. I have Postfix on that machine configured with mydomain and myhostname = msapiro.net and mydestination = msapiro.net, localhost.localdomain, localhost. My other machines (traveling laptops) are similar, but I also have 127.0.0.1 msapiro.net in /etc/hosts to override the DNS. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Trying to get started developing Mailman
by Thomas Storey 24 Jul '15

24 Jul '15

Hello Mailman developers, I am trying to get started developing Mailman but I am having difficulty setting up a local development/test environment on my machine (Ubuntu 14.04 LTS). I used black-perl's lovely development bootstrap to set up my virtual environments and initially install Mailman and postorious, but I can't seem to get a mailing list to actually work! I followed the excellent documentation at http://mailman.readthedocs.org/en/latest/src/mailman/docs/MTA.html to configure postfix and Mailman to talk to each other. I created a mailing list called "testlist" through the postorious interface. I subscribed myself and a testuser to the list, but sending mail via: echo "test body text" | mail -s "test subject" testlist(a)augusta.net simply results in a bounced email message in /var/mail/thomas (my user on my machine). augusta.net is the domain I specified during postfix configuration. Sending mail like above to "testuser(a)augusta.net" works perfectly (mail appears in /var/mail/testuser). The only reason I made it is because Mailman won't let you make a list @localhost. Does anyone have any advice for setting up a local-only mailing list environment so I can test behavior as I poke around in the code? Ideally I want to be able to just send emails via the command line to the local Mailman instance and have Mailman send emails out to local users that are subscribed to its lists. I am stumped as to how to get this going, and I feel like I must be fundamentally misunderstanding how things are supposed to be done. Thanks for any guidance you can give me. -Thomas

1 0

Merging users
by Aurelien Bompard 21 Jul '15

21 Jul '15

Hey devs! I'm hitting a problem when migrating from 2.1 to 3, but I think it's a generic issue (or rather a missing feature) and I'd like to fix it. If I try to associate an existing address to an existing user (without this address obviously), the Mailman API will reply with a 400 error "User already exists". Postorius currently does not detect that and just errors out with a 500 page (but that's not the issue here). I think I need to merge the two users, and that's currently not supported. I believe it would be a useful feature, so I'd like to discuss it here. IMHO, the only tricky part would be to merge the preferences associated with each user, but if I know which of my two users has priority, I can just resolve the conflicts that way. Am I missing something? Do you agree it would be a useful feature to have? Aurélien

1 0

Member moderation action via Postorius?
by Daniel Miller 20 Jul '15

20 Jul '15

Is there a way to view and toggle a member's moderation action (member.moderation_action according to [1]) from Postorius? I would like to be able to see this from the member list. Dan [1] https://pythonhosted.org/mailman/src/mailman/model/docs/membership.html#mod…

1 0