On 2022-10-18 15:37, Mark Sapiro wrote:
# cat /lib/systemd/system/mailman.service
PIDFile=/var/run/mailman/mailman.pid
Try changing that to
PIDFile=/var/lib/mailman/data/master-qrunner.pid
Super! That did the job.
#PIDFile=/var/run/mailman/mailman.pid
On 2022-10-18 14:29, Mark Sapiro wrote:
FROM: Me via listn...@listdomain.com
TO: listn...@listdomain.com
CC: m...@mydomain.com
This is expected. See the comment in the code beginning at
On 2022-10-18 12:41, Grant Taylor via Mailman-Users wrote:
I've seen this type of duplication when there were communications problems that
were causing your outbound MTA to send messages multiple times. This usually
happens when there are communications problems and your sending MTA doesn't
The problem: subscribers are all receiving duplicate copies of the original
post and any replies.
Are you saying that each list member receives 2 copies of an original post
addressed only to the list?
Each and every list member receives 2 copies of the post. It is addressed to
the list
Hi,
I've got a list with ~1600 subscribers (Mailman 2.1.39). It gets one or two
messages posted to it each day (by subscribers).
The problem: subscribers are all receiving duplicate copies of the original
post and any replies.
All the subscribers are have "nodupes" switched on, and the list
Hi,
I've got a list with ~1600 subscribers (Mailman 2.1.39). It gets one or two
messages posted to it each day (by subscribers).
The problem: subscribers are all receiving duplicate copies of the original
post and any replies.
All the subscribers are have "nodupes" switched on, and the list
On 2022-10-10 23:14, Stephen J. Turnbull wrote:
> so I had to switch to a new provider. The new v-server is
> debian-based. the release is bullseye which does still provide ...
... browse both the "venv" installation described in
our docs at
On Tue, 2022-08-30 at 22:34 -0500, Omri Kalinsky wrote:
>
> Problem #1:
> One of my friends (who isn't tech savvy and doesn't read
> directions) was my guinea pig and successfully joined. The problem is
> he
> tried to send his first e-mail to the list by simply replying to the
>
On Sun, 2022-09-11 at 16:58 +0300, Odhiambo Washington wrote:
> >
> > And you may first want to edit those new archtoc.html and
> > archtocnombox.html files. By default the search box is at the
> > bottom of
> > the page. I think it's better at the top.
> >
>
>
> Thanks for that hint. It is
On Sun, 2022-09-11 at 16:58 +0300, Odhiambo Washington wrote:
> However, looking at the two files, I see references to:
>
>
>
> I suppose in my case this too has to be modified to reflect the
> correct path.
> With my MM2 installed in /usr/local/mailman2/ the above path then
> should become
>
> Answering myself on #2, I did figure out that the two files should go
> to my
> templates/{language}/ as drop-in replacements. I have done that but
> accessing
> the archives of my list still do not bring the search box as shown
> here -
> https://lists.kictanet.or.ke/pipermail/kictanet/ -
>> ...which I found googling ‘how to disable a mailman 2 list’ because I’d like
>> to know how, too, since we do occasionally have need to do this.)
> The method in that thread is simply moving the lists/ aside. That
> is one way to disable a list, but there are others depending on what you
> > > Before I go down this rabbit hole: was there any particular
> > > reason (back in the day) that Pipermail was favoured (and
> > > implemented) over MHonArc.
> >
> > Mailman was initially implemented by John Viega in the mid 1990s to
> > manage a mailing list for fans of the Dave
> Mark Dale via Mailman-Users writes:
>
> > And of course, any such "nl2br" equivalent will do exactly the same
> > as wrapping with P tags -- with everything left aligned.
> From: Stephen J. Turnbull [mailto:stephenjturnb...@gmail.com]
> Right.
>
>
>> You might get a better result in these messages by removing the "PRE"
>> tags, and wrapping each line with "...", but that's a real
>> hack, and almost certain to make RFC-conforming email look quite ugly,
>> because every line becomes a paragraph, and you'll lose all
>> indentation. Eg, in
>> I'm looking for a way to wrap lines in archived messages
>> And the lines in that block that seem responsible for the PRE tags are ...
>>
>> lines.insert(0, '')
>> lines.append('')
>>
>> My question is: Can those PRE tags be removed and replaced
Hi,
I'm looking for a way to wrap lines in archived messages.
Messages from some mail clients (eg. Gmail) have their lines wrapped to 72
chars in the archived version, while archived messages from others (eg.
Thunderbird, Outlook) display unwrapped lines forcing the reader to scroll
> Its possible to run mailman2 in debian11 (with python3)?
>
> I need the resource of mm2 of turn attachments into links.
>
> In mailman2 has the option scrub_nondigest, and its make this
> perfectily.
>
> I installed the mailman3 in debian 11, but dont realize any way to do
> this.
>> With the default Mailman cron being set as noon daily:
>>
>> If, on a Wednesday (for example), List-1 is set with its digest as Daily --
>> its digest will be sent at noon that day (and every day).
>>
>> And if List-2's digest is set as Weekly, its digest will be held and not
>> sent until
> If you run cron/senddigests daily, periodic digests will be sent daily
> including the first of the week and the first of the month> If you run
> cron/senddigests weekly only, periodic digests will be sent weekly and> if
> you run cron/senddigests monthly only, periodic digests will be sent
Hi,
I've encountered a puzzle where weekly digests are not being sent, and I'm
trying to understand how periodic digests work.
Daily digests and running the command below (as root) seems to work okay.
/usr/bin/python /var/lib/mailman/cron/senddigests -l
Looking at Mailman's cron for
Hi Jayson,
> ... This makes me think she's doing something to cause a complaint to be
> generated, and doesn't realize she's doing it. ...
We get a fairly steady stream of these "complaint" messages from
"staff[AT]hotmail". They don't seem to amount to much and I'm guessing they're
simply a
> These headers (read them in reverse):
>
>> X-Original-To: krnet-ow...@list.krnet.org
>> Delivered-To: krnet-ow...@list.krnet.org
>> Received: from sfo.mailmanlists.us (ip6-localhost [IPv6:::1])
>> by sfo.mailmanlists.us (Postfix) with ESMTP id BAD65451F6;
>> Sat, 12 Mar 2022 04:11:24
Hi Mark,
Just a recap (it's been a couple of days).
Problem: The list is sending a copy of the message (posted by a subscriber) to
the administrator who is not a subscriber.
I've replied to your queries in line.
>> =
>>
>> Mailman server's Postfix log shows:
>>
>> Mar 12 04:11:28 sfo
Original Message
Subject: account
From: Hunter Parker
To: supp...@mailmanlists.net
Date: 1/31/2021, 3:30:02 AM
> On 3/11/22 11:45, Mark Dale via Mailman-Users wrote:
>>
>> Hi,
>>
>> I have just created a new list and the posts from/to subscri
Hi,
I have just created a new list and the posts from/to subscribers are being
received and delivered as expected. All is well there.
However the messages are also being delivered to the administrators who are not
subscribed.
And if the administrator is a subscriber, they receive two copies
> On 10/20/21 7:59 PM, Mark Dale via Mailman-Users wrote:
>>
>> Hi,
>>
>> As a list-member I'm unable to turn off digest-mode via email.
>>
>> To: -request@lists.
>> Subject: set digest off
>>
>>
>> Mailman (v 2.1.34) replies with a
Hi,
As a list-member I'm unable to turn off digest-mode via email.
To: -request@lists.
Subject: set digest off
Mailman (v 2.1.34) replies with an email (The results of your email commands)
but the digest mode does not get set to "Off".
Original Message
From: Bruce Johnson via Mailman-Users [mailto:mailman-users@python.org]
Sent: Monday, August 30, 2021, 21:02 UTC
To: mailman-users@python.org
Subject: [Mailman-Users] Mailman + postfix automatically adding aliases
> But when I do this I get the following.
Original Message
From: Stephen J. Turnbull [mailto:turnbull.stephen...@u.tsukuba.ac.jp]
Sent: Wednesday, April 21, 2021, 18:28 UTC
> In fact, most modern systems will negotiate compressed streams, so if
> you provide a .txt to your webserver, the client will tell the server
>
Original Message
From: Mark Sapiro [mailto:m...@msapiro.net]
Sent: Wednesday, April 21, 2021, 01:53 UTC
> Slightly off topic, but after the cron/nightly_gzip job runs, the
> .txt.gz file will be updated with the contents from the .txt file.
>
> However, the point of this
Original Message
From: Mark Sapiro [mailto:m...@msapiro.net]
Sent: Tuesday, April 20, 2021, 18:55 UTC
> On 4/19/21 10:43 PM, Mark Dale via Mailman-Users wrote:
>>
>> François -- as seen in the mm_cfg modified download txt: the cedille
>> replace by odd
Original Message
From: Mark Sapiro [mailto:m...@msapiro.net]
Sent: Friday, April 9, 2021, 19:07 UTC
> On 4/9/21 5:55 AM, Mark Dale via Mailman-Users wrote:
>>
>> In the archive's downloaded .txt (and also .gz) file, the non-ascii
>> characters are
Apologies for double posting. I sent this to the MM3 list by mistake earlier.
Mailman 2.1.34
Debian 10
Postfix
Hi
I'm hoping someone can shine a light on character encoding issue I've
encountered.
A plain-text email with non-ascii characters in the body gets posted to the
list.
As per Mark
Original Message
From: Mark Sapiro [mailto:m...@msapiro.net]
Sent: Saturday, March 6, 2021, 23:27 UTC
To: mailman-users@python.org
Subject: [Mailman-Users] Re: Pipermail scrubbing ascii txt to ksh attachment
> The patch I posted previously was bad. This one is correct. If you
Original Message
From: Mark Sapiro [mailto:m...@msapiro.net]
Sent: Saturday, March 6, 2021, 23:27 UTC
To: mailman-users@python.org
Subject: [Mailman-Users] Re: Pipermail scrubbing ascii txt to ksh attachment
> On 3/6/21 2:55 PM, Mark Dale via Mailman-Users wr
Original Message
From: Mark Sapiro [mailto:m...@msapiro.net]
Sent: Saturday, March 6, 2021, 01:19 UTC
To: mailman-users@python.org
Subject: [Mailman-Users] Re: Pipermail scrubbing ascii txt to ksh attachment
> On 3/5/21 2:56 PM, Mark Dale via Mailman-Users wr
Original Message
From: Mark Sapiro [mailto:m...@msapiro.net]
Sent: Friday, March 5, 2021, 05:08 UTC
To: mailman-users@python.org
Subject: [Mailman-Users] Re: Pipermail scrubbing ascii txt to ksh attachment
> On 3/4/21 8:36 PM, Mark Dale via Mailman-Users wrote:
>>
&
Original Message
From: Mark Sapiro [mailto:m...@msapiro.net]
Sent: Friday, March 5, 2021, 04:50 UTC
To: mailman-users@python.org
Subject: [Mailman-Users] Re: Pipermail scrubbing ascii txt to ksh attachment
> On 3/4/21 8:36 PM, Mark Dale via Mailman-Users wrote:
>>
Original Message
From: Mark Sapiro [mailto:m...@msapiro.net]
Sent: Friday, March 5, 2021, 01:29 UTC
To: mailman-users@python.org
Subject: [Mailman-Users] Re: Pipermail scrubbing ascii txt to ksh attachment
> Here's something you can try.
>
> Create a file somewhere and give
Original Message
From: Mark Dale via Mailman-Users [mailto:mailman-users@python.org]
Sent: Friday, March 5, 2021, 00:01 UTC
To: mailman-users@python.org
Subject: [Mailman-Users] Re: Pipermail scrubbing ascii txt to ksh attachment
>
> Original Message
Original Message
From: Mark Sapiro [mailto:m...@msapiro.net]
Sent: Thursday, March 4, 2021, 06:04 UTC
To: mailman-users@python.org
Subject: [Mailman-Users] Re: Pipermail scrubbing ascii txt to ksh attachment
> On 3/3/21 3:36 PM, Mark Dale via Mailman-Users wrote:
>> H
Hi Listers,
I've got a client's list to which a plain text email notice is sent
everyday.
Mailman-Version: 2.1.34
Postfix
Debian 10
The message contents are fairly similar each day and the text message
renders in email clients just fine and the .mbox file reads fine also.
However, Pipermail
43 matches
Mail list logo
