[Mailman-Users] Importing from 2.1.12-18.el6 to 2.1.15-17.el7
Hello, everyone. Will "config_list -I" work to import settings from version 2.1.12-18 to 2.1.15-17? Thanks! Dean -- 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] Importing from 2.1.12-18.el6 to 2.1.15-17.el7
This is Mailman 2.1.15-17, qmail, CentOS 7. I've got a new server and set up a test list, say, myl...@mydomain.com. Subscribers include m...@mydomain.com (the same domain the list is on) and various addresses from other domains/servers (a couple of servers I run, plus Gmail and AT&T.) Mail sent to myl...@mydomain.com from any subscriber gets archived -- and distributed to m...@mydomain.com. But none of the other subscribers receive the list mail. Non-list, regular mail works fine. Using m...@mydomain.com I can send to anyone (and they receive it) and receive from anyone. I know less about mail than just about anything else in the world, so any suggestions as to what might be wrong would be appreciated. Thanks! Dean -- 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] Mail delivered locally but not to remote domains
Sorry for not changing the subject last time. This is a server using the Plesk 12 control panel. The answer was: "Ensure that 'localhost' IP addresses is white listed in Plesk. Go to Tools & Settings > Mail Server Settings > White list To verity it open Tools & Settings > Mail Settings > White List and check whether it contain the following addresses: '::1/128' and '127.0.0.1'." Their knowledgebase article is at http://kb.odin.com/en/123649. Thank you! Dean -Original Message- From: Mailman-Users [mailto:mailman-users-bounces+dean.collins=insightplanners@python.org] On Behalf Of Mark Sapiro Sent: Friday, May 15, 2015 12:59 PM To: mailman-users@python.org Subject: Re: [Mailman-Users] Importing from 2.1.12-18.el6 to 2.1.15-17.el7 On 05/15/2015 12:28 PM, Dean Collins wrote: > > Subscribers include m...@mydomain.com (the same domain the list is on) > and various addresses from other domains/servers (a couple of servers > I run, plus Gmail and AT&T.) > > Mail sent to myl...@mydomain.com from any subscriber gets archived -- > and distributed to m...@mydomain.com. But none of the other subscribers > receive the list mail. In order to be sure about anything, I'd need to see some logs like Mailman's smtp-failure log and the MTA logs, except I don't know anything about qmail. However, based on past experience I can say the following. 1) Mailman is delivering to the local MTA (qmail) and the mail is being delivered to local addresses but not being sent to remote domains. 2) Other locally generated mail is being sent to remote domains. When this happens it is probably an IPv4 vs. IPv6 issue. Here's one scenario. It may not be exactly this in your case, but you should be able to translate. The MTA has an idea of what addresses constitute the local network and will relay mail from those addresses to the outside. This includes say the IPv4 local host, something like 127.0.0.1, but not the IPv6 local host ::1. Mailman, by default, delivers to 'localhost'. 'localhost' in turn is defined as the IPv6 ::1 address. Thus Mailman's mail comes to the MTA from ::1 which is not in the MTA's notion of the local network, so the MTA refuses to relay the mail. This can be fixed in multiple ways. You can add the IPv6 local host to the MTA's local network. You can change /etc/hosts to associate 127.0.0.1 rather than ::1 with 'localhost'. You can set SMTPHOST in mm_cfg.py to something that will work. E.g., SMTPHOST = '127.0.0.1' Note that since I haven't seen your logs, the above scenario may be off. Perhaps it would be that Mailman is sending via the IPv4 loopback and qmail wants IPv6, but the idea is the same. -- 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/dean.collins%40insight planners.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
[Mailman-Users] Re: mailman v2.x
OMG! Shut up! -Original Message- From: Chip Davis Sent: Wednesday, August 26, 2020 8:47 PM To: mailman-users@python.org Subject: [Mailman-Users] Re: mailman v2.x OK Brian, so your answers to my questions are: "I have a profit motive to encourage MM3 adoption" ... and ... "I'm baffled that all the people on the Mailman *2* discussion list are not scrambling to adopt MM3" Have I got that about right? For the record, I have enjoyed exemplary support from all three of my "cheap budget hosts" whenever I've had an issue. And yes, one of them is A2. I will sign off of this thread by pointing out that your first contribution to it was a reply to my posting supporting Jim's generous offer to help support the MM2 community, in which you stridently attempted to convince us to convert over to MM3 instead. Respectfully, we decline. -Chip- On 8/26/2020 11:17 PM, Brian Carpenter wrote: > On 8/26/20 10:29 PM, Chip Davis wrote: >> What I don't understand is your vitriolic objection to Jim's offer. >> How is that any skin off your nose? Do you see this as a zero-sum >> game in which every MM2 instance that doesn't "upgrade" is a threat >> to MM3? If it's as superior as you claim, there should be a >> thunderous stampede to adopt MM3. The bazaar will speak eloquently. >> What, exactly, is the cock you have in this pit? >> >> Bottom Line: As long as there are inexpensive cPanel hosts running >> Mailman 2, *I have no choice*. So I greatly appreciate Jim's offer >> to pick up the burden and allow Mark to move on. > > I watched for years how cheap budget hosts provided crap support for > the software that they hosted. I watched Mark for years take on that > extra burden of making up for their crap support because of it via the > old MM2 user list. > > I am sure Mark has moved on from Mailman 2, at least he has said that > on numerous occasions. It is you folks that won't let him. You want to > keep using MM2 and you want the developers to keep supporting it. That > pressure can/does hinder the work on Mailman 3. > > I really did not like Jim's comment and that set me off: > > "I hate to say this, but I'm sensing an exclusivity in your and Mark's > comments. Is Mailman a open source project or is it an exclusive > club?" > > I really don't like your comments either towards me in the quote above > and the way you mis-represented Mailman 3 in your reply to Odhiambo. I > offer shared and dedicated environments for Mailman 3 and none of my > clients have to worry about the complexities of Mailman 3 at all. I > didn't like the way Carl quoted an old piece of information and when > he was corrected, proceeded to dig in his heels. I didn't like a > lurker who never posted to any Mailman list before, suddenly come out > of the woodwork to mock me on the use of "long life" > > By the way there is always a choice. I have been offering Mailman 3 > shared list hosting for almost 2 years now. It's that few extra > dollars a month that is a budget breakers for cheap host users. Oh > well. > > I know now that none of you have any intention of using or supporting > Mailman 3. My pro MM3 comments have been mocked, ignored, and > discarded. Ok. Fine. I think none of you has shown any respect or > appreciation in the work that has been done to propel the Mailman > project into the modern web development world. That shows that all you > really care about is your wallets and how much you may have to work to > move your lists to a Mailman 3 environment. This isn't about Mailman > at all. It's about how can have a mailing list and stay using a cheap > budget host. For Jim? Well I don't really care why he doesn't use > Mailman 3. I think his claims about wanting to support Mailman is a > joke. If he really wanted to support the Mailman project, then he > would throw his weight behind Mailman 3. > -- 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 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] Re: mailman v2.x
Yay! Most useless, uninformative post of the day! Quoting Dmitri Maziuk : On 9/13/2020 6:17 PM, Chip Davis wrote: Ironically, I was writing in support of Mark's and Stephen's position on the matter. As a member of Mark's cohort, the odds are I'll never need a "New! Improved!" MM2, or MM3. You wish: at some point "they" will upgrade the hardware and/or the OS to fix whatever horrible security hole is ending the world as we know it this week, and the upgrade will kill python 2 compatibility. Or some obscure python 2 library nobody knew existed. "Them" being cPanel of RedHat or Cluebuntu, or any number of other players who aren't Mark and Stephen. Dima -- 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 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] check_arch script changing owner
Using Mailman version: 2.1.33 packaged for cPanel. Running the script I obtained from https://www.msapiro.net/scripts/check_arch changes directory and file permissions and ownership. For example, in /archives/private/: drwxr-x--- 5mailman usernamelistname_mydomain.org becomes drwxrwxr-x5rootrootlistname_mydomain.org And the list then stops archiving. Is there a way to adjust the script? Or run some command afterwards to set things back to where they were? Thanks for any help! Dean Collins -- 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] Re: check_arch script changing owner
Thanks! Dean -Original Message- From: Mark Sapiro Sent: Tuesday, October 26, 2021 11:55 AM To: mailman-users@python.org Subject: [Mailman-Users] Re: check_arch script changing owner On 10/25/21 11:11 AM, Dean Collins wrote: > Using Mailman version: 2.1.33 packaged for cPanel. > > Running the script I obtained from > https://www.msapiro.net/scripts/check_arch changes directory and file > permissions and ownership. For example, in /archives/private/: > > drwxr-x--- 5mailman usernamelistname_mydomain.org > > becomes > > drwxrwxr-x5rootrootlistname_mydomain.org > > And the list then stops archiving. Don't run Mailman scripts as root. Always run them as the Mailman user. > Is there a way to adjust the script? Or run some command afterwards to > set things back to where they were? You can run chmod and chown to set things back, but even if the script is run as root, I don't see how this would happen. The script opens the file read-only and only reads it. This must be a cPanel thing. See https://wiki.list.org/DOC/Mailman%20and%20CPanel -- 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 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 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] Re: check_arch script changing owner
Okay, I figured out how to prune with cPanel installations. Your (Mark's) script is much faster, of course, but this works. During the process, I turned off archiving in the web interface, though I don't know whether that was necessary. In cPanel, the archives are in /usr/local/cpanel/3rdparty/mailman/archives/private. Move the archive directory out of the way: mv listname listname.save Edit/prune the listname.mbox file (or empty it with cp /dev/null). Turn archiving back on, send a test message, confirm it's been archived, delete the listname.save directory. Anyway, thanks again! Dean -Original Message- From: Mark Sapiro Sent: Tuesday, October 26, 2021 11:55 AM To: mailman-users@python.org Subject: [Mailman-Users] Re: check_arch script changing owner On 10/25/21 11:11 AM, Dean Collins wrote: > Using Mailman version: 2.1.33 packaged for cPanel. > > Running the script I obtained from > https://www.msapiro.net/scripts/check_arch changes directory and file > permissions and ownership. For example, in /archives/private/: > > drwxr-x--- 5mailman usernamelistname_mydomain.org > > becomes > > drwxrwxr-x5rootrootlistname_mydomain.org > > And the list then stops archiving. Don't run Mailman scripts as root. Always run them as the Mailman user. > Is there a way to adjust the script? Or run some command afterwards to > set things back to where they were? You can run chmod and chown to set things back, but even if the script is run as root, I don't see how this would happen. The script opens the file read-only and only reads it. This must be a cPanel thing. See https://wiki.list.org/DOC/Mailman%20and%20CPanel -- 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 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 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/
