[Mailman-Users] Some mailing lists are stuck

[Dominik Hoffmann]

I have a couple of mailing lists on my mailman server that don’t forward 
messages to their members. There are no rules that would block them. It all 
looks like they are stuck in a queue, which would just have to be unstuck. Is 
there a command-line way of doing that?

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] What’s up: Sitelist is missing: mailman

[Dominik Hoffmann]

system.log indicates that I rebooted my server at that time. That’s all I can 
see, however.

> On Mar 24, 2017, at 4:00 PM, Mark Sapiro  wrote:
> 
> On 03/24/2017 12:32 PM, Dominik Hoffmann wrote:
>> Thanks, Mark!
>> 
>> As for more details on the error, I found the following
>> 
>> bounce: no errors
>> posts: no errors
>> qrunner:
>> 
>> Mar 20 11:25:11 2017 (291) Master qrunner detected subprocess exit
>> (pid: 299, sig: None, sts: 15, class: CommandRunner, slice: 1/1) 
> ...
> 
> sts 15 is
> 
> 015 ENOTBLK Block device required
> 
> which means nothing to me without more info. Is there anything from that
> time in Mailman's error log or the server's syslog? Was there some file
> system issue around that time?
> 
> 
>> 
>> This is, I believe the first date, on which I had trouble. I noticed 
>> something was up only two days later. Only today did I notice the extent to 
>> which something was wrong.
>> 
>> smtp:
>> 
>> Silence between March 20, 9:48 AM until today 12:31, when I fixed the 
>> missing mailman list and restarted mailman.
>> 
>> smtp-failure: no errors
>> subscribe: no errors
>> vette: no errors
>> 
>> Any idea, why the instructions at 
>> <https://www.askdavetaylor.com/why_is_mailman_complaining_site_list_is_missing_mailman/>
>>  have me add aliases to /etc/aliases? I don’t recall having to do that, when 
>> I first set up mailman.
> 
> 
> You need aliases for the mailman list as for any other. Whether you need
> to do anything manually depends on your MTA and how it's configured.
> 
> See <https://wiki.list.org/x/12812344>. Also note that the post you're
> looking at is 11 years old and is talking about upgrading from 2.1b
> (over 14 years old) to 2.1.2 (14 years old).
> 
> <http://www.list.org/mailman-install/site-list.html> would probably have
> been a better place to look.
> 
> -- 
> 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/dhoffmann%40uwalumni.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] What’s up: Sitelist is missing: mailman

[Dominik Hoffmann]

Thanks, Mark!

As for more details on the error, I found the following

bounce: no errors
posts: no errors
qrunner:

Mar 20 11:25:11 2017 (291) Master qrunner detected subprocess exit
(pid: 299, sig: None, sts: 15, class: CommandRunner, slice: 1/1) 
Mar 20 11:25:11 2017 (291) Master qrunner detected subprocess exit
(pid: 301, sig: None, sts: 15, class: NewsRunner, slice: 1/1) 
Mar 20 11:25:11 2017 (291) Master qrunner detected subprocess exit
(pid: 298, sig: None, sts: 15, class: BounceRunner, slice: 1/1) 
Mar 20 11:25:11 2017 (291) Master qrunner detected subprocess exit
(pid: 304, sig: None, sts: 15, class: RetryRunner, slice: 1/1) 
Mar 20 11:25:11 2017 (291) Master qrunner detected subprocess exit
(pid: 303, sig: None, sts: 15, class: VirginRunner, slice: 1/1) 
Mar 20 11:25:11 2017 (291) Master qrunner detected subprocess exit
(pid: 297, sig: None, sts: 15, class: ArchRunner, slice: 1/1) 
Mar 20 11:25:12 2017 (291) Master qrunner detected subprocess exit
(pid: 302, sig: None, sts: 15, class: OutgoingRunner, slice: 1/1) 
Mar 20 11:25:12 2017 (291) Master qrunner detected subprocess exit
(pid: 300, sig: None, sts: 15, class: IncomingRunner, slice: 1/1) 

This is, I believe the first date, on which I had trouble. I noticed something 
was up only two days later. Only today did I notice the extent to which 
something was wrong.

smtp:

Silence between March 20, 9:48 AM until today 12:31, when I fixed the missing 
mailman list and restarted mailman.

smtp-failure: no errors
subscribe: no errors
vette: no errors

Any idea, why the instructions at 
<https://www.askdavetaylor.com/why_is_mailman_complaining_site_list_is_missing_mailman/>
 have me add aliases to /etc/aliases? I don’t recall having to do that, when I 
first set up mailman.

> On Mar 24, 2017, at 3:11 PM, Mark Sapiro  wrote:
> 
> On 03/24/2017 09:10 AM, Dominik Hoffmann wrote:
>> My error log shows entries like this
>> 
>> Mar 22 16:52:28 2017 mailmanctl(175): Site list is missing: mailman 
>> Mar 22 16:52:28 2017 (175) Site list is missing: mailman
> ...
> 
>> The question I have for you guys are
>> 
>> 1. How might this have happened?
> 
> 
> The list got deleted. I have no clue as to how. Exactly when did these
> messages start appearing in the error log? What other messages are
> logged in various logs at times between the previous Mailman (re)start
> and then?
> 
> 
>> 2. What is the purpose of the mailman list.
> 
> 
> It is a long standing requirement of Mailman 2.1. Its address is exposed
> as a help/info address on the web admin and listinfo overview pages. Its
> -request address is the From: address in password reminders and it's
> -bounces address is the bounce address of last resort.
> 
> It goes away (along with password reminders) in MM 3.
> 
> -- 
> 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/dhoffmann%40uwalumni.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] What’s up: Sitelist is missing: mailman

[Dominik Hoffmann]

My error log shows entries like this

Mar 22 16:52:28 2017 mailmanctl(175): Site list is missing: mailman 
Mar 22 16:52:28 2017 (175) Site list is missing: mailman

I found directions on how to fix this at 
.

The question I have for you guys are

1. How might this have happened?

2. What is the purpose of the mailman list.
--
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] Amway Order Confirmation [#1095286]

[Dominik Hoffmann]

How would I instruct the list to treat urgent messages like any other?

> On Feb 17, 2017, at 6:41 PM, Mark Sapiro  wrote:
> 
> On 02/17/2017 01:32 PM, Dominik Hoffmann wrote:
>> I get these messages from a particular sender who must have set his message 
>> to urgent. I have no influence over how these messages are sent. What must I 
>> do to my Mailman list, so the messages go through as originally sent and not 
>> in the form shown below?
> 
> 
> I may have missed this in my original reply. Are you saying that the
> message below came from the list? If so, then what is happening is the
> user is posting something with an Urgent: header. It is rejected by
> Mailman and the user then forwards the rejection notice back to the
> list, this time without an Urgent: header.
> 
> The original is not attached either because the user's MUA doesn't
> include it in the forwarded message or your list's content filtering
> doesn't accept message/rfc822 MIME parts.
> 
> 
>>> Begin forwarded message:
>>> 
>>> From: Customer Service 
>>> Subject: Re: ** Order Confirmation [#1095286]
>>> Date: February 17, 2017 at 4:28:39 PM EST
>>> To: -owner@.net
>>> Reply-To: customer.service@***.com
>>> 
>>> Thank you for contacting us.
>>> We have received your e-mail. An ** Customer Service Representative 
>>> will respond to you shortly.
>>> --owner@.net Wrote -
>>> Your urgent message to the mailing list was not authorized
>>> for delivery.  The original message as received by Mailman is
>>> attached.
> 
> -- 
> 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/dhoffmann%40uwalumni.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] Fwd: Amway Order Confirmation [#1095286]

[Dominik Hoffmann]

I get these messages from a particular sender who must have set his message to 
urgent. I have no influence over how these messages are sent. What must I do to 
my Mailman list, so the messages go through as originally sent and not in the 
form shown below?

As it is, Mailman does not attach the original message.

> Begin forwarded message:
> 
> From: Customer Service 
> Subject: Re: ** Order Confirmation [#1095286]
> Date: February 17, 2017 at 4:28:39 PM EST
> To: -owner@.net
> Reply-To: customer.service@***.com
> 
> Thank you for contacting us.
> We have received your e-mail. An ** Customer Service Representative will 
> respond to you shortly.
> --owner@.net Wrote -
> Your urgent message to the mailing list was not authorized
> for delivery.  The original message as received by Mailman is
> attached.

--
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] Need new SMTP provider—SMTP2Go won't allow what they call autoforwarding

[Dominik Hoffmann]

Hi Everyone:

A few months ago STMP2Go was recommended to me, because Verizon discontinued 
authenticated mail relaying for senders not using a verizon.net email address. 
More than the purported attempt to fight spam, I think, this was a way to lock 
people into using Verizon email addresses and making it harder to switch ISPs 
for those who do not want to change email addresses in the process.

SMTP2Go now informs me that the handful of Mailman mailing lists I am running 
for each of my kids, which automatically send copies to me and my wife, in 
addition to the respective child, are a violation of their mail relaying 
policy, because there is no way to eliminate the relaying of spam. They are 
concerned that the mail server that ultimately receives these messages will rat 
on SMTP2Go as having relayed spam, which will make their reputation and the 
deliverability of their other customers’ messages suffer. In my case, however, 
the recipients are all on my personal mail server, which doesn’t do any such 
reporting.

Regardless, what are other Mailman admin’s recommendations for 3rd-party SMTP 
services, hopefully ones, where I will not run into trouble with my 
configuration?

Yours,

Dominik
--
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] Find a smtp server to send out emails

[Dominik Hoffmann]

Hi Leon:

Ever since my ISP, Verizon, quit relaying email messages from addresses not 
ending in @verizon.net, I have been exploring SMTP alternatives. I haven't come 
to a conclusion, but I found an interesting list at

https://www.formget.com/smtp-service-providers/

Dominik

P.S.: I have a stinking suspicion that the primary reason for Verizon's is not 
to combat spam, as stated, but to make it harder for their subscribers to be in 
a position where switching ISPs is easy, because they already use email 
addresses not tied to the ISP.

> On Dec 7, 2016, at 3:05 PM, Leon  wrote:
> 
> Hi, This problem is not caused by mailman, but I still want to give it a
> shot here. I'm hosting a mailing list on top of mailman. Emails are
> supposed to be sent out by AWS ses. However, ses requires that sender
> address must be verified, which leads to a problem that emails sent by
> subscribers to mailing list cannot be sent to other subcirbers, since their
> addresses are not verified. And it is impossible to verified every
> subscriber. Are there smtp service providers allowing unverified email
> address to send out emails, or do I have other solutions?
> 
> Thanks.
> 
> 
> Leon
> --
> 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/dhoffmann%40uwalumni.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] What log file do I check for successful transmission to the SMTP server?

[Dominik Hoffmann]

>From the earliest days of Mac OS X, possibly even on the NextStep OS, /etc/ 
>and /var/ have been really located inside of /private/ with simlinks putting 
>them in the root directory.

> On Oct 15, 2016, at 12:09 AM, Mark Sapiro  wrote:
> 
> On 10/14/2016 07:30 PM, Dominik Hoffmann wrote:
>> Does the fact that I don't have a file called smtp-failure at 
>> /usr/local/mailman/logs/ mean that no SMTP errors have occurred, as far as 
>> Mailman is concerned?
> 
> 
> Yes. Assuming that that is the directory that contains at least the
> qrunner and error logs and probably also smtp, post, subscribe, etc., it
> means that log has never been written and Mailman has not had any
> failures in it's SMTP transactions.
> 
> This means that everything Mailman tried to deliver to the MTA was
> successfully delivered. It doesn't mean the MTA successfully delivered
> the message(s) to the next relay. For that kind of failure, there should
> be bounces recorded in the bounce log, but they won't say why. For that
> you need the MTA log (maybe /var/log/mail.log or
> /private/var/log/mail.log - my Macbook has a symlink /var ->
> /private/var, but I may have created that).
> 
> -- 
> 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/dhoffmann%40uwalumni.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] What log file do I check for successful transmission to the SMTP server?

[Dominik Hoffmann]

> On Oct 15, 2016, at 12:09 AM, Mark Sapiro  wrote:
> 
> On 10/14/2016 07:30 PM, Dominik Hoffmann wrote:
>> Does the fact that I don't have a file called smtp-failure at 
>> /usr/local/mailman/logs/ mean that no SMTP errors have occurred, as far as 
>> Mailman is concerned?
> 
> 
> Yes. Assuming that that is the directory that contains at least the
> qrunner and error logs and probably also smtp, post, subscribe, etc., it
> means that log has never been written and Mailman has not had any
> failures in it's SMTP transactions.
> 
> This means that everything Mailman tried to deliver to the MTA was
> successfully delivered. It doesn't mean the MTA successfully delivered
> the message(s) to the next relay. For that kind of failure, there should
> be bounces recorded in the bounce log, but they won't say why. For that
> you need the MTA log (maybe /var/log/mail.log or
> /private/var/log/mail.log - my Macbook has a symlink /var ->
> /private/var, but I may have created that).
> 
> -- 
> 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/dhoffmann%40uwalumni.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] What log file do I check for successful transmission to the SMTP server?

[Dominik Hoffmann]

Does the fact that I don't have a file called smtp-failure at 
/usr/local/mailman/logs/ mean that no SMTP errors have occurred, as far as 
Mailman is concerned?

> On Oct 14, 2016, at 7:12 PM, Mark Sapiro  wrote:
> 
> On 10/14/2016 03:56 PM, Dominik Hoffmann wrote:
>> So, all of my testing has so far been with email addresses that have their 
>> destination on the same system as the one, on which Mailman is running. I 
>> just tried a list that has all external destinations.
>> 
>> What log files should I look at to see, what might be going wrong?
> 
> 
> If there are problems in Mailman's SMTP delivery to the MTA, they will
> be logged in Mailman's smtp-failure log. Also, whether the message is
> rejected by the MTA at SMTP time or accepted and then rejected later
> there should be an entry in Mailman's bounce log, although this doesn't
> contain diagnostic info.
> 
> Also the MTA's logs should have complete info.
> 
> -- 
> 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/dhoffmann%40uwalumni.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] What log file do I check for successful transmission to the SMTP server?

[Dominik Hoffmann]

So, all of my testing has so far been with email addresses that have their 
destination on the same system as the one, on which Mailman is running. I just 
tried a list that has all external destinations.

What log files should I look at to see, what might be going wrong?
--
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] Administrative requests page for migrated lists uses wrong old server fqdn for data submission

[Dominik Hoffmann]

Thanks very much, Mark, for the pointer to the FAQ! In particular, it seemed 
like FAQ 4.27 (cf. <https://wiki.list.org/x/4030702>) was most relevant.

Accordingly, I added the lines

RewriteEngine on
RewriteCond %{HTTPS}off [NC]
RewriteRule ^/mailman(/.*)  https://%{HTTP_HOST}/mailman$1   
[L,R=permanent]

to

/etc/apache2/extra/httpd-mailman.conf

which is included in

/Library/Server/Web/Config/apache2/httpd_server_app.conf

on the line

Include /private/etc/apache2/extra/httpd-mailman.conf


I also edited

/usr/local/mailman/Mailman/mm_cfg.py

to include the line

DEFAULT_URL_PATTERN = 'https://%s/mailman/'

Finally, I ran

/usr/local/mailman/bin/withlist -l -a -r fix_url

again.

This made it all work!

> On Oct 13, 2016, at 6:09 PM, Mark Sapiro  wrote:
> 
> On 10/13/2016 01:51 PM, Dominik Hoffmann wrote:
>> 
>> One thing that still doesn't work is submission of the pending moderator 
>> requests. When I hit Submit All Data, the page simply reloads without any of 
>> the moderation directives having been taken into account.
> 
> 
> See <https://wiki.list.org/x/4030602>.

--
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] Administrative requests page for migrated lists uses wrong old server fqdn for data submission

[Dominik Hoffmann]

Great! Thanks, Mark!

I ran

/usr/local/mailman/bin/withlist -l -a -r fix_url

and now all my lists actually show up on the "Overview of all 
new-server.domain.com mailing lists" page.

One thing that still doesn't work is submission of the pending moderator 
requests. When I hit Submit All Data, the page simply reloads without any of 
the moderation directives having been taken into account.

Getting really close to having this thing up and running completely.

> On Oct 13, 2016, at 4:38 PM, Mark Sapiro  wrote:
> 
> On 10/13/2016 12:19 PM, Dominik Hoffmann wrote:
>> 
>> When editing the list settings, there were references to 
>> "old-server.domain.com" in the host_name field on the General Options page, 
>> and I changed that to "new-server.domain.com".
>> 
>> What do I need to fix, in order for the button submission to go through 
>> properly?
> 
> 
> You need to run Mailman's fix_url. See this FAQ
> <https://wiki.list.org/x/4030616>.
> 
> -- 
> 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] Administrative requests page for migrated lists uses wrong old server fqdn for data submission

[Dominik Hoffmann]

My mailing lists were migrated from a machine running Mac OS X Server 10.6 
(Snow Leopard) [let's refer to it by the fdqn old-server.domain.com], where 
mailman was supplied and supported out of the box. The destination was an OS X 
Server 10.11 (El Capitan) system running Server 5.2 [let's refer to it by the 
fdqn new-server.domain.com], which required the manual installation of mailman 
from source.

I copied the requisite directories archives, data, lists and qfiles from 
/var/mailman/ to /usr/local/mailman/. I then ran

/usr/local/mailman/bin/check_perms -f

which made sure that these were given the proper permissions for the new system.

Let's say my mailing list is named "family." I can now bring up

https://new-server.domain.com/mailman/admin/family

I can change all settings to my heart's content, and they all take. However, 
when I try to "Tend to pending moderator requests" and click on the Submit All 
Data button on

https://new-server.domain.com/mailman/admindb/family

it directs me to

http://old-server.domain.com/mailman/admindb/family

which has been decommissioned.

When editing the list settings, there were references to 
"old-server.domain.com" in the host_name field on the General Options page, and 
I changed that to "new-server.domain.com".

What do I need to fix, in order for the button submission to go through 
properly?
--
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] Cron has issues with gate_news

[Dominik Hoffmann]

Another observation:

4. Moving the Crontab from root to _mailman had no effect.

> On Oct 13, 2016, at 11:43 AM, Dominik Hoffmann  wrote:
> 
> There are still a few of things to mop up, after an otherwise successful 
> installation of Mailman on OS X El Capitan with Server 5.2.
> 
> Every 5 min my admin user account on the server gets an email from the Cron 
> Daemon that has this line:
> 
> IOError: [Errno 13] Permission denied: 
> '/usr/local/mailman/locks/gate_news.lock.ipheion.hoffmann.homeunix.net.54220.0'
> 
> Here are my observations:
> 
> 1. I currently have no file at /usr/local/mailman/locks/ whose name starts 
> with "gate_news".
> 
> 2. My root Crontab has these lines:
> 
>   # Every 5 mins, try to gate news to mail. You can comment this one out
>   # if you don't want to allow gating, or don't have any going on right 
> now,
>   # or want to exclusively use a callback strategy instead of polling.
>   # 0,5,10,15,20,25,30,35,40,45,50,55 * * * * /usr/bin/python -S 
> /usr/local/mailman/cron/gate_news
> 
>   In other words, the gate_news cron job is commented out.
> 
> 3. I have run /usr/local/mailman/bin/check_perms -f, but that has had no 
> impact.

--
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] Cron has issues with gate_news

[Dominik Hoffmann]

There are still a few of things to mop up, after an otherwise successful 
installation of Mailman on OS X El Capitan with Server 5.2.

Every 5 min my admin user account on the server gets an email from the Cron 
Daemon that has this line:

IOError: [Errno 13] Permission denied: 
'/usr/local/mailman/locks/gate_news.lock.ipheion.hoffmann.homeunix.net.54220.0'

Here are my observations:

1. I currently have no file at /usr/local/mailman/locks/ whose name starts with 
"gate_news".

2. My root Crontab has these lines:

# Every 5 mins, try to gate news to mail. You can comment this one out
# if you don't want to allow gating, or don't have any going on right 
now,
# or want to exclusively use a callback strategy instead of polling.
# 0,5,10,15,20,25,30,35,40,45,50,55 * * * * /usr/bin/python -S 
/usr/local/mailman/cron/gate_news

   In other words, the gate_news cron job is commented out.

3. I have run /usr/local/mailman/bin/check_perms -f, but that has had no impact.
--
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] Installing Mailman on OS X El Capitan--can’t find source of erroneous call of binary at /usr/share/mailman/mail/mailman

[Dominik Hoffmann]

/usr/local/mailman/bin/genaliases did do the trick. Thanks so much, Mark!

> On Oct 12, 2016, at 3:10 PM, Dominik Hoffmann  wrote:
> 
> I think, actually, that that may have done the trick. I started getting some 
> test messages I had sent to the list earlier, which must have been queued. I 
> will have to do more testing later, when I have time.
> 
>> On Oct 12, 2016, at 11:36 AM, Dominik Hoffmann  
>> wrote:
>> 
>> /usr/local/mailman/bin/genaliases did not produce any output. Does this mean 
>> that it didn't change anything or simply did so silently?
> --
> 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/dhoffmann%40uwalumni.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] Installing Mailman on OS X El Capitan--can’t find source of erroneous call of binary at /usr/share/mailman/mail/mailman

[Dominik Hoffmann]

I think, actually, that that may have done the trick. I started getting some 
test messages I had sent to the list earlier, which must have been queued. I 
will have to do more testing later, when I have time.

> On Oct 12, 2016, at 11:36 AM, Dominik Hoffmann  wrote:
> 
> /usr/local/mailman/bin/genaliases did not produce any output. Does this mean 
> that it didn't change anything or simply did so silently?
--
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] Installing Mailman on OS X El Capitan--can’t find source of erroneous call of binary at /usr/share/mailman/mail/mailman

[Dominik Hoffmann]

/usr/local/mailman/bin/genaliases did not produce any output. Does this mean 
that it didn't change anything or simply did so silently?

> On Oct 12, 2016, at 11:24 AM, Mark Sapiro  wrote:
> 
> On 10/12/2016 08:16 AM, Mark Sapiro wrote:
>> 
>> I don't know how these aliases are generated in your setup, but assuming
>> you have Mailman's Postfix integration, that path comes from the
>> WRAPPER_DIR setting in Mailman/Defaults.py. That in turn is based on
>> EXEC_PREFIX which is often the same as PREFIX. These things are set from
>> options to configure when Mailman is configured.
>> 
>> Did you start your installation by running configure? If so, what is the
>> configure command from config.log, is there a --prefix= option or a
>> --exec-prefix= option - the defaults for these are
>> --prefix=/usr/local/mailman and --exec-prefix=(the prefix value).
>> 
> 
> 
> Or perhaps everything is configured correctly but your Postfix aliases
> are just left from a prior install and all you need do is run Mailman's
> bin/genaliases.
> 
> -- 
> 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/dhoffmann%40uwalumni.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] Installing Mailman on OS X El Capitan--can’t find source of erroneous call of binary at /usr/share/mailman/mail/mailman

[Dominik Hoffmann]

Thanks for the offer! I don't think, I want to go the MacPorts route at this 
point. I am thinking about it, though!

> On Oct 12, 2016, at 11:16 AM, Timothy Jasionowski  
> wrote:
> 
> I’m one of the few people who has blazed this trail on the newer versions of 
> OS X Server, mainly using the macports installation method with a few 
> modifications.  If you want to email me off the list, I can share my 
> insights.  Alternately, search the archives for my previous posts/fixes for 
> this, as I’ve tried to document my challenges.
> 
> Timothy
> 
>> On Oct 11, 2016 (Wk 42), at 4:46 PM, Dominik Hoffmann 
>>  wrote:
>> 
>> Hi:
>> 
>> I have followed Allan Herman's March 29, 2013, instructions for installing 
>> Mailman on OS X Mountain Lion. The difference is that my system is OS X El 
>> Capitan running Server 5.2. Nonetheless, I have not run into any 
>> contradictions. It appears that the choices for the locations of the various 
>> configuration files made when transitioning from Mac OS X Snow Leopard to 
>> Mac OS X Lion to OS X Mountain Lion have remained stable.
>> 
>> However, I am now banging my head against the wall, because my server's SMTP 
>> logs contain these lines:
>> 
>> Oct 11 16:04:04 ion local[56963]: fatal: execvp 
>> /usr/share/mailman/mail/mailman: No such file or directory
>> 
>> Allan installs his Mailman deployment in /usr/local/, and I have learned 
>> that in one of the more recent iterations of OS X, Apple chose to lock down 
>> /usr/share/, so that even the sudo command does not make modifications 
>> possible, which I learned, when I tried to create a simlink there. I kept 
>> getting the "Operation not permitted." error. I learned that this is due to 
>> System Integrity Protection (SIP), introduced in OS X El Capitan.
>> 
>> I am now on a quest to locate from where the call to mailman originates, so 
>> that I can edit the corresponding configuration file, replacing 
>> "/usr/share/" with "/usr/local/".
>> 
>> Any pointers would be much appreciated.
>> 
>> Dominik Hoffmann
>> 
>> 
>> --
>> 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/timothy.d%40jasionow.ski
> 

--
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] Installing Mailman on OS X El Capitan--can’t find source of erroneous call of binary at /usr/share/mailman/mail/mailman

[Dominik Hoffmann]

Thanks very much!

I looked through Defaults.py and found

PYTHON  = '/usr/bin/python'
PREFIX  = '/usr/local/mailman'
EXEC_PREFIX = '${prefix}'
VAR_PREFIX  = '/usr/local/mailman'

This looks normal to me and is verbatim from Allan Herman's instructions, which 
get their configure call from Larry Stone's May 1, 2010, instructions (also on 
this mailing list):

./configure --prefix=/usr/local/mailman --with-cgi-gid=_www 
--with-mail-gid=_mailman

I can't find any reference to "--exec-prefix=" in config.log.

Dominik

> On Oct 12, 2016, at 11:16 AM, Mark Sapiro  wrote:
> 
> On 10/11/2016 01:46 PM, Dominik Hoffmann wrote:
>> 
>> I have followed Allan Herman's March 29, 2013, instructions for installing 
>> Mailman on OS X Mountain Lion. The difference is that my system is OS X El 
>> Capitan running Server 5.2. Nonetheless, I have not run into any 
>> contradictions. It appears that the choices for the locations of the various 
>> configuration files made when transitioning from Mac OS X Snow Leopard to 
>> Mac OS X Lion to OS X Mountain Lion have remained stable.
>> 
>> However, I am now banging my head against the wall, because my server's SMTP 
>> logs contain these lines:
>>> Oct 11 16:04:04 ion local[56963]: fatal: execvp 
>>> /usr/share/mailman/mail/mailman: No such file or directory
>> 
>> Allan installs his Mailman deployment in /usr/local/, and I have learned 
>> that in one of the more recent iterations of OS X, Apple chose to lock down 
>> /usr/share/, so that even the sudo command does not make modifications 
>> possible, which I learned, when I tried to create a simlink there. I kept 
>> getting the "Operation not permitted." error. I learned that this is due to 
>> System Integrity Protection (SIP), introduced in OS X El Capitan.
>> 
>> I am now on a quest to locate from where the call to mailman originates, so 
>> that I can edit the corresponding configuration file, replacing 
>> "/usr/share/" with "/usr/local/".
> 
> 
> It comes from PID 56963 which looks like a Postfix 'local' delivery
> agent instance. I.e., it's in your Postfix aliases.
> 
> I don't know how these aliases are generated in your setup, but assuming
> you have Mailman's Postfix integration, that path comes from the
> WRAPPER_DIR setting in Mailman/Defaults.py. That in turn is based on
> EXEC_PREFIX which is often the same as PREFIX. These things are set from
> options to configure when Mailman is configured.
> 
> Did you start your installation by running configure? If so, what is the
> configure command from config.log, is there a --prefix= option or a
> --exec-prefix= option - the defaults for these are
> --prefix=/usr/local/mailman and --exec-prefix=(the prefix value).
> 
> -- 
> 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/dhoffmann%40uwalumni.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] Update mailman MacServer5

[Dominik Hoffmann]

On 09/04/2016 12:53 AM, Matthias Schmidt via Mailman-Users wrote:

> Hello,
> 
> now I’m stuck here:
> 
> local[74919]: fatal: execvp /usr/share/mailman/mail/mailman: No such file or 
> directory
> 
> local is owned by postfix so far I found out.
> What I can’t find is where this line is to be able to correct it (Spotlight 
> also finds nothing)
> 
> thanks
> Matthias 

Hallo, Matthias,

How did you solve your problem. I have the same issue, but the mailing list 
thread doesn't show, what you did to address this, only that it evidently 
ceased to be broken.

Yours,

Dominik Hoffmann
--
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] Installing Mailman on OS X El Capitan--can’t find source of erroneous call of binary at /usr/share/mailman/mail/mailman

[Dominik Hoffmann]

Hi:

I have followed Allan Herman's March 29, 2013, instructions for installing 
Mailman on OS X Mountain Lion. The difference is that my system is OS X El 
Capitan running Server 5.2. Nonetheless, I have not run into any 
contradictions. It appears that the choices for the locations of the various 
configuration files made when transitioning from Mac OS X Snow Leopard to Mac 
OS X Lion to OS X Mountain Lion have remained stable.

However, I am now banging my head against the wall, because my server's SMTP 
logs contain these lines:

Oct 11 16:04:04 ion local[56963]: fatal: execvp 
/usr/share/mailman/mail/mailman: No such file or directory

Allan installs his Mailman deployment in /usr/local/, and I have learned that 
in one of the more recent iterations of OS X, Apple chose to lock down 
/usr/share/, so that even the sudo command does not make modifications 
possible, which I learned, when I tried to create a simlink there. I kept 
getting the "Operation not permitted." error. I learned that this is due to 
System Integrity Protection (SIP), introduced in OS X El Capitan.

I am now on a quest to locate from where the call to mailman originates, so 
that I can edit the corresponding configuration file, replacing "/usr/share/" 
with "/usr/local/".

Any pointers would be much appreciated.

Dominik Hoffmann


--
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