Re: [Mailman-Users] Install mailman-2.1.z with python3.6
On 1/7/19 4:19 PM, Odhiambo Washington wrote: > On Mon, 7 Jan 2019 at 20:37, Mark Sapiro wrote: >> Which is expected because Mailman 2.1 does not support Python 3 and >> never will. > > Noted! I thought I could eliminate python2 from my server :) Not yet, unfortunately. -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958 -- 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] Install mailman-2.1.z with python3.6
On Mon, 7 Jan 2019 at 20:37, Mark Sapiro wrote: > On 1/7/19 1:22 AM, Odhiambo Washington wrote: > > I need to install Mailman2.1 using python3.x, but I have had some > problem. > > > > On my Ubuntu-18.04 server, I have both python2.7 and python3.6. > > Now, everything is all fine with python2.7, but when I use python3.6, it > > bombs out: > > > Which is expected because Mailman 2.1 does not support Python 3 and > never will. > Noted! I thought I could eliminate python2 from my server :) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-) -- 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] mm-handler same as postfix-to-mailman.py
On 1/7/19 2:13 PM, Grant Taylor via Mailman-Users wrote: > I think Sendmail (and other MTAs that I've tested) default to > user@host.domain too. But that's just a default that's easy to change. LOL. Not on IRIX it wasn't. > Or are you saying that you used > MX records to route email to a different machine, possibly a mail hub? That. If you want a single MX accepting mail for the Internet, you have to have virtual domains on it for your every host, and make sure SMTP and/or DNS reliable routes addres@host.domain to address@domain. Which may be easier than I think, I never tried... Granted we're talking "just one" @list.domain here. Well, maybe also @list.domain... and then by strong mathematical induction we arrive at the above. > B) I would hope that other things like SPF / DKIM / DMARC would help > reduce this considerably. But I'm not going to hope enough to hold my > breath. But then you wouldn't need it in mailman: if it's spoofed as per dmarc, you just reject it regardless ot its destination. > C) ¯\_(ツ)_/¯ I suspect it's highly mailing list dependent. - I > personally like to do as much as possible during the SMTP transaction. > So if there is a reasonable way to apply some Mailman filtering logic to > applicable messages, why not do it? Like I said, it's probably whooping 10 extra lines of python -- as long as you use postfix. The question is how much work it is to support other MTAs. -- Dimitri Maziuk Programmer/sysadmin BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu signature.asc Description: OpenPGP digital 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] mm-handler same as postfix-to-mailman.py
On 01/07/2019 09:59 AM, Dmitri Maziuk via Mailman-Users wrote: We used to run irix whose sendmail sent every message from host.domain and every A record had to have an adjacent MX record for e-mail to even work. That way lies madness. Hum. I think Sendmail (and other MTAs that I've tested) default to user@host.domain too. But that's just a default that's easy to change. I thought that SMTP allowed for falling back to an A record to find where to send messages for host.domain. Or are you saying that you used MX records to route email to a different machine, possibly a mail hub? I also thought that SMTP would iterate up through the right hand side of email addresses looking for MX / A records and trying to connect to an SMTP server. Thus it would be possible to have an MX record for domain and all hosts there in would cascade up to said MX record. Or is all of this vagaries of SMTP and too unpredictable / unreliable and best avoided? Rather trivial with postfix but a) we have bona fide subscribers posting rom their gmail instead of subscribed From: -- I want those to get moderated instead of bounced, b) it is of course subject to spoofing, and c) how much of a problem is it IRL? A) Fair enough. I would expect there to be a per-list tunable to either reject or not-reject messages based on list membership. In the scenario that you describe, the messages would not be rejected based on sending email address and assuming the message passes other tests would be passed further into Mailman. B) I would hope that other things like SPF / DKIM / DMARC would help reduce this considerably. But I'm not going to hope enough to hold my breath. C) ¯\_(ツ)_/¯ I suspect it's highly mailing list dependent. - I personally like to do as much as possible during the SMTP transaction. So if there is a reasonable way to apply some Mailman filtering logic to applicable messages, why not do it? In our -- admittedly very lightly loaded -- domains, it's RBL and fail2ban that seem to provide best bang for the buck. *nod* -- Grant. . . . unix || die 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] Install mailman-2.1.z with python3.6
On 1/7/19 1:22 AM, Odhiambo Washington wrote: > I need to install Mailman2.1 using python3.x, but I have had some problem. > > On my Ubuntu-18.04 server, I have both python2.7 and python3.6. > Now, everything is all fine with python2.7, but when I use python3.6, it > bombs out: Which is expected because Mailman 2.1 does not support Python 3 and never will. -- 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] mm-handler same as postfix-to-mailman.py
On Sun, 6 Jan 2019 15:47:01 -0700 Grant Taylor via Mailman-Users wrote: > Hi Jim, > > On 1/4/19 3:40 AM, Jim Ziobro wrote: > > Setting up mailing lists in a separate domain has a nice > > administrative appeal. We used to run irix whose sendmail sent every message from host.domain and every A record had to have an adjacent MX record for e-mail to even work. That way lies madness. > > I did a little more research to see how popular that method might > > be. I got a list of 1922 US universities and 457 have a host > > "lists" and 191 have a host "list..." in their DNS. I surveyed > > a few and ran across: Mailman, Lyris, Sympa, Listserv, Majordomo, > > and Google groups. Many universities outsource their Email to > > Outlook which has it own Group capability. Our university has lyris @ lists.uw, googlegoups, and has recently bought into lookout'365! as well. While we run our own mailman instances. We have "lists" in our little niche. It's the web front-end, our list traffic comes from @domain. So 500 out of 2000 universities having "list(s)" in DNS doesn't really mean all that much. > I think it should be somewhat easy to test the SMTP envelope sender > to see if it's subscribed to a list that is the SMTP envelope > recipient. If the sender is not a subscriber the MTA can reject the > message. Rather trivial with postfix but a) we have bona fide subscribers posting rom their gmail instead of subscribed From: -- I want those to get moderated instead of bounced, b) it is of course subject to spoofing, and c) how much of a problem is it IRL? In our -- admittedly very lightly loaded -- domains, it's RBL and fail2ban that seem to provide best bang for the buck. -- Dmitri Maziuk -- 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] Install mailman-2.1.z with python3.6
I need to install Mailman2.1 using python3.x, but I have had some problem.
On my Ubuntu-18.04 server, I have both python2.7 and python3.6.
Now, everything is all fine with python2.7, but when I use python3.6, it
bombs out:
root@lists:/home/wash/Mailman/2.1.29/mailman-2.1.29# ./configure
--with-cgi-gid=33 --with-mail-gid=117 --with-python=/usr/bin/python3.6
checking for --with-python... /usr/bin/python3.6
checking Python interpreter... /usr/bin/python3.6
checking Python version... 3.6.7
checking dnspython... ok
checking Python's email package... Traceback (most recent call last):
File "conftest.py", line 8, in
version = tuple(int(v) for v in email.__version__.split('.'))
AttributeError: module 'email' has no attribute '__version__'
cat: conftest.out: No such file or directory
checking Japanese codecs... Traceback (most recent call last):
File "conftest.py", line 2, in
unicode('OK', 'iso-2022-jp')
NameError: name 'unicode' is not defined
cat: conftest.out: No such file or directory
checking Korean codecs... Traceback (most recent call last):
File "conftest.py", line 2, in
unicode('OK', 'euc-kr')
NameError: name 'unicode' is not defined
cat: conftest.out: No such file or directory
checking that Python has a working distutils... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking whether make sets $(MAKE)... yes
checking for true... /bin/true
checking for --without-gcc... no
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether #! works in shell scripts... yes
checking for --with-var-prefix... no
checking for --with-permcheck... yes
checking for --with-username... mailman
checking for user name "mailman"... okay
checking for --with-groupname... mailman
checking for group name "mailman"... okay
checking permissions on /usr/local/mailman... File "conftest.py", line 17
if mailmangid <> gid:
^
SyntaxError: invalid syntax
cat: conftest.out: No such file or directory
configure: error:
* Installation directory /usr/local/mailman is not configured properly!
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.", grep ^[^#] :-)
--
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
