I've noticed that as people reply to threads on my mailman instance, I see
copies of the footer pile up at the bottom of each message.
Rants about top/inline/bottom posting aside, I thought it would be a smart
feature of mailman to look for a copy of the footer in any incoming message
before
Where the current behavior is 'always append footer'. I think these options
are worth implementing:
'Append footer for just the first message'
'Append footer if footer not already present in quoted text'
On Thu, Aug 27, 2015 at 1:02 PM, Seun Ojedeji seun.ojed...@gmail.com
wrote:
Hi,
I think
Hi,
I think it will be a good feature to have. Thinking about it's
implementation however assumes that every mail clients uses the thread view
mail option. Also those who subscribe in the middle of a conversion will
most likely not get the footer.
Nerveless it's good to have it for use according
You may be interested in this thread:
https://mail.python.org/pipermail/mailman-users/2012-April/073181.html
Laura
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ:
Tried running an update today and received this message:
Setting up mailman (1:2.1.16-2ubuntu0.1) ...
Looking for enabled languages (this may take some time) ... done.
Removing unmodified files from /etc/mailman/eu done.
Directory /etc/mailman/eu not empty, not removed.
*... {repeat above
Hi guys.
I'm struggling since a while since MailMan will sometimes put messages
into the Held queue even though I did my very best to set all config
options so that MailMan won't... :-(
Is there a way to once and for all forbid MailMan to put messages into
the queue so that a moderator has to
Hello, List is running on Mailman version 2.1.20.
Last several days began receiving hundreds of bot subscription requests (all
gmail addresses).
All of format like:
blech+12345...@gmail.com
zark+98765...@gmail.com
etc.
I entered following regex lines in Privacy Options - Subscription Rules -
Hello, We have a list running on Mailman version 2.1.20.
Over the last several days began receiving hundreds of bot subscription
requests (all gmail addresses).
All of format like:
blech+12345...@gmail.com
zark+98765...@gmail.com
In attempt to solve this issue, entered the following regex
Hi,
First, apologies if this has been discussed before. I run a number of mailman lists on a Centos 6 platform and mailman 2.1.12-25. This version was updated in July as follows:
https://rhn.redhat.com/errata/RHSA-2015-1417.html and included fixes for a number of DMARC issues. Including ...
Hi,
First, apologies if this has been discussed before. I run a number of mailman lists on a Centos 6 platform and mailman 2.1.12-25. This version was updated in July as follows:
https://rhn.redhat.com/errata/RHSA-2015-1417.html and included fixes for a number of DMARC issues. Including ...
Are there any guidelines for adding authentication and /or authorization
mechanisms to the Mailman web user interface?
Specifically, I was wondering if there is any kind of guidance for
authenticating the user via an HTTP header (e.g. HTTP_REMOTE_USER) so that an
authenticating reverse proxy
Hi guys.
I'm reposting this as I haven't received any feedback -- can anyone help
me, please?
Kind regards,
Ralf
On 2015-08-25 13:29 , Ralf G. R. Bergs wrote:
Hi guys.
I'm struggling since a while since MailMan will sometimes put messages
into the Held queue even though I did my very best
Mark writes:
First, apologies if this has been discussed before. I run a number
of mailman lists on a Centos 6 platform and mailman 2.1.12-25. This
version was updated in July as follows:
https://rhn.redhat.com/errata/RHSA-2015-1417.html and included
fixes for a number of DMARC issues.
I am again trying to answer a query from a list member about spelling errors in
his postings that show up in his list messages, but not in his copy of the sent
message.
Initially we thought this was because he was composing in html, and that his
mail client wasn't including an accurate
Woody Mon via Mailman-Users writes:
So I tried entering RegExp ^.*+ but Mailman rejected this entry.
That's illegal syntax for a regexp because + is an operator.
The version you want is ^.*\+. However, that is a very bad idea if
you have any posters with email skills, because embedding + in
billy noah writes:
Downgrade detected, from version 0x20112f1 to version 0x20110f0
This is probably not safe.
The basic answer is You're going to need help from Ubuntu experts
anyway because the package database is out of sync with reality, so go
ask them.
That said, there are three
Billy Crook writes:
Am I just missing where this setting is, or has this not been
thought of yet.
It's been thought of, and it's just plain hard to do, because
automatically editing mail bodies robustly is just plain hard to do.
If you have a vast majority of users who use the same MUA, you
17 matches
Mail list logo
