[Mailman-Users] Re: Duplicate emails being received

[Mark Dale via Mailman-Users]

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
PIDFile=/var/lib/mailman/data/master-qrunner.pid
...

# service mailman stop
Warning: The unit file, source configuration file or drop-ins of 
mailman.service changed on disk. Run 'systemctl daemon-reload' to reload units.

# systemctl daemon-reload
# service mailman stop
# service mailman start

# pstree
/ MAILMAN RUNNING

# ps -fwwu list

/ ALL RUNNERS RUNNING

**


/var/run is typically a symlink to /run, but 
https://mail.python.org/archives/list/mailman-users@python.org/message/OOVT765SIUYN5U3X3HGO3YNAMFJW7NHY/
 says you couldn't find a `mailman.pid` anywhere.


Yes. For "mailman.pid" nothing is found with either "find" or "locate".

For "master-qrunner.pid" -- no problem ...

# locate master-qrunner.pid
/var/lib/mailman/data/master-qrunner.pid

# find / -type f -iname "master-qrunner.pid"
/var/lib/mailman/data/master-qrunner.pid


**





--
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: Duplicate emails being received

[Mark Dale via Mailman-Users]

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 
https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/view/head:/Mailman/Handlers/CookHeaders.py#L201
 for why we do this.


Got it. Thank you.




# ps -fAww |grep python
root   432 1  0 00:36 ?    00:00:00 /usr/bin/python3 
/usr/bin/fail2ban-server -xf start
list   745 1  0 00:38 ?    00:00:00 /usr/bin/python 
/usr/lib/mailman/bin/mailmanctl -s start
list   751   745  2 00:38 ?    00:00:04 /usr/bin/python 
/var/lib/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s
nobody 913   911  0 00:40 ?    00:00:00 /usr/bin/python 
/usr/local/bin/mpanel-memory-graph
root   921   908  0 00:40 pts/0    00:00:00 grep python



There should be more. Where are ArchRunner, BounceRunner, CommandRunner, 
IncomingRunner, NewsRunner, VirginRunner and RetryRunner? Did you edit them out?

What does `ps -fwwu list` show?



I hadn't edited then out, but when I ran "ps -fAww |grep python" again just 
now, they're all present now.
Good to know that all those are supposed to be there (in case there's a "next 
time").
And "ps -fwwu list" shows the same.


# ps -fAww |grep python
root   432 1  0 00:36 ?00:00:20 /usr/bin/python3 
/usr/bin/fail2ban-server -xf start
nobody5348  5343  0 03:45 ?00:00:00 /usr/bin/python 
/usr/local/bin/mpanel-memory-graph
list  5407 1  0 03:47 ?00:00:00 /usr/bin/python 
/usr/lib/mailman/bin/mailmanctl -s start
list  5408  5407  0 03:47 ?00:00:00 /usr/bin/python 
/var/lib/mailman/bin/qrunner --runner=ArchRunner:0:1 -s
list  5409  5407  0 03:47 ?00:00:00 /usr/bin/python 
/var/lib/mailman/bin/qrunner --runner=BounceRunner:0:1 -s
list  5410  5407  0 03:47 ?00:00:00 /usr/bin/python 
/var/lib/mailman/bin/qrunner --runner=CommandRunner:0:1 -s
list  5411  5407  0 03:47 ?00:00:00 /usr/bin/python 
/var/lib/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s
list  5412  5407  0 03:47 ?00:00:00 /usr/bin/python 
/var/lib/mailman/bin/qrunner --runner=NewsRunner:0:1 -s
list  5413  5407  0 03:47 ?00:00:00 /usr/bin/python 
/var/lib/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s
list  5414  5407  0 03:47 ?00:00:00 /usr/bin/python 
/var/lib/mailman/bin/qrunner --runner=VirginRunner:0:1 -s
list  5415  5407  1 03:47 ?00:00:00 /usr/bin/python 
/var/lib/mailman/bin/qrunner --runner=RetryRunner:0:1 -s
root  5422  5416  0 03:47 pts/000:00:00 grep python

*


/// DID THAT PID FILE REAPPEAR?
# find / -type f -iname "mailman.pid"
/// NO RESULT. ... shrug ...



I suspect an issue with the Debian/Ubuntu package. What is the content of 
/etc/systemd/system/mailman.service?


# cd /etc/systemd/system/
# ls -la
... mailman-qrunner.service -> /lib/systemd/system/mailman.service


# cat /lib/systemd/system/mailman.service
[Unit]
Description=Mailman Master Queue Runner
After=network.target

[Service]
Type=forking
PIDFile=/var/run/mailman/mailman.pid
ExecStart=/usr/lib/mailman/bin/mailmanctl -s start
ExecStop=/usr/lib/mailman/bin/mailmanctl stop
ExecReload=/usr/lib/mailman/bin/mailmanctl restart
Restart=always
RestartSec=3s
RestartPreventExitStatus=1

[Install]
WantedBy=multi-user.target
Alias=mailman-qrunner.service


***

It seems that it was looking for the PID file in "/run/mailman/mailman.pid" (below) and 
the above says it lives at "/var/run/mailman/mailman.pid"

Oct 18 00:30:13 syd systemd[1]: mailman.service: Can't open PID file 
/run/mailman/mailman.pid (yet?) after start: No such file or directory

--
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: Duplicate emails being received

[Mark Dale via Mailman-Users]

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 
receive the confirmation from receiving MTAs that they have accepted the 
message.  This might be a result of a timeout setting being too low on your 
sending MTA.


Thanks for that pointer.
 
At the moment the Postfix smtpd_timeout = 60s. I think the original default is 300s.


The restart (as per Mark S.'s advice) has got the mail back to one copy. If it 
goes off the rails again I'll experiment with that timeout.

 

Given that your message to the mailman-users mailing list came to the list 
twice, which didn't involve your instance of Mailman, I sort of suspect you 
have lower level / SMTP problems


That was my bad. I had a cert error and thinking the message hadn't been sent, 
I resent it.
* 

I think that your MTA's logs will be a very good place to start looking.  At 
least to see if there is evidence of problems or not.


There is one timeout error (unrelated I think) that gets repeated every hour 
approx. for just one recipient.

Oct 17 18:31:47 syd postfix/smtpd[30094]: timeout after END-OF-MESSAGE from 
mpv-out-cfd-1.REDACTED-DOMAIN.COM[REDACTED-IP4-ADDRESS]



--
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: Duplicate emails being received

[Mark Dale via Mailman-Users]

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 AND CCed to the poster's own email address.

EG.  FROM: Me via listn...@listdomain.com
   TO: listn...@listdomain.com
   CC: m...@mydomain.com

**


Ensure you don't have multiple runners processing the same slice of their 
queues. See https://wiki.list.org/x/4030715 for the procedure to stop ALL 
Mailman processes and then start it only once.


I stepped through this (results below). After a reboot, there is only one 
runner.

/var/lib/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s

**



Examine the Received: headers of both copies to determine the paths that the 
message takes from poster to recipient.



I "diffed" the headers of both emails to check, and the message paths are the 
same.

**


After the reboot, I posted a test to the list(just the list address, no CC) and 
now just the one copy of the message is delivered (although it wrote my address 
into the CC field).

FROM: Me via listn...@listdomain.com
TO: listn...@listdomain.com
CC: m...@mydomain.com   

So far so good. I'll keep an eye on the qrunner over the next few days. It came 
good last time I restarted the qrunner, then went bad. But as you say, there 
may well have been more than one runner doing their bit.

Here are the steps and results I went through.


# service mailman stop

# ps -fAww |grep python
root   432 1  0 Oct01 ?00:48:57 /usr/bin/python3 
/usr/bin/fail2ban-server -xf start
nobody5659  5658  0 00:25 ?00:00:00 /usr/bin/python 
/usr/local/bin/mpanel-memory-graph
root  5687  5642  0 00:26 pts/000:00:00 grep python
// I SHOULD HAVE CHECKED THAT BEFORE STOPPING MAILMAN


# service mailman start
/// FAILED TO START
...
Oct 18 00:30:12 syd systemd[1]: Starting Mailman Master Queue Runner...
Oct 18 00:30:13 syd mailmanctl[5791]: Starting Mailman's master qrunner.
Oct 18 00:30:13 syd systemd[1]: mailman.service: Can't open PID file 
/run/mailman/mailman.pid (yet?) after start: No such file or directory


/// oh? MAYBE IT LIVES SOMEWHERE ELSE
# find / -type f -iname "mailman.pid"
/// NO RESULT

/ hmmm, AM I PANICKING YET?
#reboot
/ phew..., MAILMAN RUNNING AFTER REBOOT.

# pstree
systemd─┬─agetty
├─cron
..
├─mailmanctl───python
├─master─┬─anvil
│├─2*[bounce]
...

# ps -fAww |grep python
// LOOKS LIKE ONLY 1 RUNNER. So far, so good.

root   432 1  0 00:36 ?00:00:00 /usr/bin/python3 
/usr/bin/fail2ban-server -xf start
list   745 1  0 00:38 ?00:00:00 /usr/bin/python 
/usr/lib/mailman/bin/mailmanctl -s start
list   751   745  2 00:38 ?00:00:04 /usr/bin/python 
/var/lib/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s
nobody 913   911  0 00:40 ?00:00:00 /usr/bin/python 
/usr/local/bin/mpanel-memory-graph
root   921   908  0 00:40 pts/000:00:00 grep python


/// DID THAT PID FILE REAPPEAR?
# find / -type f -iname "mailman.pid"
/// NO RESULT. ... shrug ...

All seems well, the list is delivering single copies of the message (for now).

Thank you Mark for that advice. Very much appreciated.

--
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] Duplicate emails being received

[Mark Dale via Mailman-Users]

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 is set to replies to go 
to "This list".

I restarted the qrunner with: bin/mailmanctl -s  restart

That seemed to resolve things for a moment but then it started up again.

Does anyone have any tips or pointers?

Cheers.

 
--

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] Duplicate emails being received

[Mark Dale via Mailman-Users]

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 is set to replies to go 
to "This list".

I restarted the qrunner with: bin/mailmanctl -s  restart

That seemed to resolve things for a moment but then it started up again.

Does anyone have any tips or pointers?

Cheers.
--
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: Hevy resource footprint forces backdrop to mailman 2.1

[Mark Dale via Mailman-Users]

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 https://docs.mailman3.org/en/latest/install/virtualenv.html
and Brian Carpenter's Debian installation guide at
https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10.  Then
choose the guide you find more compatible with your thinking, and
follow that.




See also: "Installing Mailman3 on Debian 11": Tom Kisner -- Jul 9, 2022

https://kn6q.org/installing-mailman-3-on-debian-11


Kelly Close's guide "Mailman 3 Setup Using Ubuntu Bionic" works for Debian 
Bullseye.

https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5PlantPTs/edit





--
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: Welcome E-mail Reply To

[Mark Dale via Mailman-Users]

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 
> welcome e-mail, so he e-mailed my-list-requ...@mailmanlists.org and
> not 
> my-l...@mailmanlists.org. Wouldn't surprise me if others do the same 
> thing. Is there any option to change the address the welcome e-mail 
> comes from? Is there any other good ways to mitigate this problem?



You could edit the text of the "Welcome email" and have an alert at the
top of the message with something like:

///
DO NOT reply to this email.
To post a message to the list, address it to my-l...@mailmanlists.org
///

See: General Options > 
Edit the public HTML pages and text files > 
Welcome email text file


--
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: Search box for archives

[Mark Dale via Mailman-Users]

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 not documented in the HOWTO.
> 
> 

It is well documented in the How-To:

http://bakacsin.ki.iif.hu/~kissg/project/mailman+namazu/

"Search ... In case of private lists this program checks if user is
authorized to access archive content. (Note: authorization is based on
regular membership only. Server and list administrator access rights
are disregarded. Enabling admin staff to search archives may be subject
of further development.) "

The HOW-TO is very good. It was written in 2007 so a couple of things
have changed (like package names). It needs VERY close attention to be
paid to the detail that the author has taken the trouble to write. I
wish all documentation was as good as this.



--
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: Search box for archives

[Mark Dale via Mailman-Users]

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 "/mailman/cgi-bin/search" ?? 
> 
> When I do a search now, I end up with an error saying "The requested
> URL was not found on this server." and the resulting URL in the
> address bar is:
> 
> https://lists.kictanet.or.ke/cgi-bin/search?query=odhiambo=Search%21=KICTANet=20=normal=score
> 


Firstly, check your mm_cfg.py file. In my case it is: 

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

Note that there is no "cgi-bin" in the above URL.

If that's the same for you, then yes you need to edit the new
archtoc.html and archtocnombox.html files accordingly.

There are 2 strings in each file that would need to be edited so they
look like:

1. 

2. [How to search]

Then rebuild the archive again: 

bin/arch --wipe 

And it won't hurt to tell Namazu to re-index the archive(s):

ls /var/lib/namazu/mailman | xargs $HOME/bin/mailman_index 

 

 



--
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: Search box for archives

[Mark Dale via Mailman-Users]

> 


> 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/ - and I am thinking
> that
> there's something
> minor that I am still missing.

Once you've swapped in the new archtoc.html and archtocnombox.html
files you need to run bin/arch --wipe 

The renewed archive will then have the search box.

If your archive is private you have to be logged as a member to use the
search. It won't allow you to search if you're logged in as an
administrator.

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.




--
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: Question on outputting all lists and list owners and a process for batch disabling of lists without an owner

[Mark Dale via Mailman-Users]

>> ...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 
> actually want. ...



To disable a list:

chmod 000 $PATH/lists/


And to re-enable it:

chmod 2775 $PATH/lists/
--
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: How to wrap text in archived messages

[Mark Dale via Mailman-Users]

 
>  > > 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 Mathews Band. I don't know 
>  > why pipermail was chosen, but MHonArc was fairly new at that time and 
>  > pipermail was probably more mature.


> I doubt that Hypermail (the original code) was more mature than
> MHonArc, but it was written in Python and so considered more
> appropriate for bundling with Mailman. ...
> As far as I can recall, Pipermail never been especially recommended
> over 3rd party solutions like MHonArc or external services like
> mailarchive.com, it's just easy to use because it's guaranteed to be
> there, we provide support for it, and it turned out to be "good
> enough" for an awful lot of lists.
> 

Many thanks Steve and Mark. 
--
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: How to wrap text in archived messages

[Mark Dale via Mailman-Users]

> 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.
> 
> I'm not sure that we couldn't do better nowadays with libraries that
> will handle the same DOM that browsers do, but it certainly wasn't
> possible in 1994.  And even with those libraries it would require a
> complete rearchitecture of the archiver.
> 
> Steve
> 


I did some tests with Sympa (v6.2.88) which uses MHonArc (v2.6.19): it does a 
pretty good job of rendering archived HTML messages with things like lists, 
code, etc -- and eliminating the need for the horizontal scrolling.

That got me Googling for How-to's on integrating MHonArc with Mailman. There's 
a fair bit of conversation around this from days long ago, and a patch for 
using MHonArc written by Mark S. back in 2014.

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-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: How to wrap text in archived messages

[Mark Dale via Mailman-Users]

>> 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 the code blocks you posted, all the lines will
>> end up flush left.  If your members are posting code or poetry, or
>> using indented block quotations etc, they're likely to be extremely
>> unhappy with the result.

D'oh! I just saw the error in my whole way of thinking.

And of course, any such "nl2br" equivalent will do exactly the same as wrapping 
with P tags -- with everything left aligned.

But thank you Steve, for taking the time and trouble to explain. It is indeed a 
whole can of worms. Much to learn.

/Mark 

//

Python's standard library does have a textwrap module, but I'm not at
all sure it's suitable for this.  If you know that the long lines of a
message are actually paragraphs, you can use something like

from textwrap import wrap
# work backward because wrapping changes indicies of later lines
for i in range(len(lines) - 1, -1, -1):
# NDT = detect_prefix(lines[i])
lines[i:i+1] = wrap(lines[i], initial_indent=NDT, subsequent_indent=NDT)

If a line is indented or has a quoting prefix, you have to detect that
for yourself and set NDT to that prefix.  Something like

import re
prefix_re = re.compile('[ >]*')
def detect_prefix(line):
m = prefix_re.match(line)
return m.group(0)

should capture most indentation and quoting prefixes, but there are
other conventions.

Whether you use P elements or the textwrap module, it's probably a
good idea to find out how long the long lines are, and what percentage
of the message they are, and avoid trying to wrap a message that looks
like it "mostly" has lines of reasonable length.  If you don't, and
your target is the old "typewriter standard" width of 66, and somebody
using an RFC-conforming MUA just prefers 72, you'll reformat their
mail into alternating lines of about 60 characters and 10 characters.
Yuck ...

Which of the above would work better for you depends a lot on the
typical content of your list.  But issues with quoting and indentation
are likely to have you tearing your hair out.


//
--
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: How to wrap text in archived messages

[Mark Dale via Mailman-Users]

>> 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 with
>> something equivalent to PHP's "nl2br" (which inserts a line break
>> BR in place of new line entries)?

> No, because there *are no* newlines to break those very long lines.
> These MUAs use newline to mean "paragraph break", not "line break".


But there are "newlines" and there isn't any need to insert linebreaks into 
those long lines -- they just need to wrap. 

Looking at, for example, a message that originally has 3 paragraphs of text:


%(body)s


**




First paragraph that is a really long line of text.

Second paragraph that is a really long line of text.

Third paragraph that is a really long line of text.



*

If those PRE tags are removed, then all 3 lines get joined up and displayed as 
one continuous line. It solves the non-wrap problem but it looses the 
"paragraphs". So that's a no go.

As said, if this was PHP we could use the "nl2br" function - which inserts line 
breaks before all newlines.


  -- would give us ...   


///

First paragraph of body that is a really long line of text.

Second paragraph of body that is a really long line of text.

Third paragraph of body that is a really long line of text.



The BR tags would preserve the space between the lines and give the appearance 
of paragraphs in the HTML Pipermail archive page. Granted the HTML would not be 
strictly kosher, but then neither are the PRE tags strictly kosher as they're 
are not being used as they should be. The main thing is that the lines would 
wrap according the to width of the window and eliminate the need for horizontal 
scrolling.
 


> 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 the code blocks you posted, all the lines will
> end up flush left.  If your members are posting code or poetry, or
> using indented block quotations etc, they're likely to be extremely
> unhappy with the result.

Agreed. To horrible to even think about.

> 
> Python's standard library does have a textwrap module, but I'm not at
> all sure it's suitable for this.  If you know that the long lines of a
> message are actually paragraphs, you can use something like
> 
> from textwrap import wrap
> # work backward because wrapping changes indicies of later lines
> for i in range(len(lines) - 1, -1, -1):
> # NDT = detect_prefix(lines[i])
> lines[i:i+1] = wrap(lines[i], initial_indent=NDT, 
> subsequent_indent=NDT)
> 

This is sort of where I was looking to go, but as you've pointed out, there's 
no telling if the text will be in paragraphs, code blocks etc.

Does the Python code snippet that I mentioned ...

def nl2br(s):
return '\n'.join(s.split('\n'))

... make any sense as a Python equivalent of PHP's "nl2br" function (to 
accomplish the insertion of the BR line break tags)?


Cheers,
Mark



--
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] How to wrap text in archived messages

[Mark Dale via Mailman-Users]

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

Looking at the HTML page source -- in both cases (wrapped and unwrapped) I see 
the message content is enclosed by PRE tags. 




Lorem ipsum dolor sit amet, consectetur ...

Ut enim ad minim veniam, quis nostrud ...


  



The template (article.html) contains the following:
...


%(body)s


...

>From what I can figure out, the PRE tags come from
>.../mailman/Mailman/Archiver/HyperArch.py in a block of code lines 1290 to 
>1314 ...

///

def format_article(self, article):
# called from add_article
# TBD: Why do the HTML formatting here and keep it in the
# pipermail database?  It makes more sense to do the html
# formatting as the article is being written as html and toss
# the data after it has been written to the archive file.
lines = filter(None, article.body)
# Handle   directives
if self.ALLOWHTML:
self.__processbody_HTML(lines)
self.__processbody_URLquote(lines)
if not self.SHOWHTML and lines:
lines.insert(0, '')
lines.append('')
else:
# Do fancy formatting here
if self.SHOWBR:
lines = map(lambda x:x + "", lines)
else:
for i in range(0, len(lines)):
s = lines[i]
if s[0:1] in ' \t\n':
lines[i] = '' + s
article.html_body = lines
return article




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 with something 
equivalent to PHP's "nl2br" (which inserts a line break BR in place of new line 
entries)?

A Google search for such an equivalent gives me ...

def nl2br(s):
return '\n'.join(s.split('\n'))

With zero understanding of Python my attempts to implement this have failed so 
far and I may well be barking up the wrong tree completely. Any clues or 
pointers gratefully received.

Thanks.
--
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: Mailman2 x Debian 11 x Python3

[Mark Dale via Mailman-Users]

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

FWIW, I installed Python2 on Debian 11 and attempted to install Mailman 2 but 
after hitting a stack of package dependency issues found it easier to just 
rebuild with Debian 10, install Mailman 2, then dist-upgrade the server to 
Debian 11. There is most likely a world of pain yet to come down on me.  
--
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: Weekly and month digests

[Mark Dale via Mailman-Users]

>> 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 noon the next Monday (the first day of the week). The Daily 
>> digest of the List-1 will also get sent that Monday.
>>
>> Have I understood correctly?

From: Mark Sapiro [mailto:m...@msapiro.net]

> 
> No.
> 
> All list's digests will be sent daily at noon.
> 
> I think you are confused about what the digest_volume_frequency setting does. 
> It has nothing to do with when digests are sent. It only controls how often 
> the digest's volume number is incremented and issue number is reset.
> 

Ahhh. Now I understand. Thank you very much for setting me straight on that, 
and for your patience.

Best,
Mark
--
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: Weekly and month digests

[Mark Dale via Mailman-Users]

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

Sorry if I'm being thick headed with this. I think I understand. Just to be 
clear ...

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 noon the next Monday (the first day of the week). The Daily digest of the 
List-1 will also get sent that Monday.

Have I understood correctly?



 

 
--
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] Weekly and month digests

[Mark Dale via Mailman-Users]

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 digests I see the command for daily digests:

cat /var/lib/mailman/cron/crontab.in

...
# Noon, mail digests for lists that do periodic as well as threshhold delivery.
0 12 * * * /usr/bin/python -S /var/lib/mailman/cron/senddigests
...

All good there.


For weekly and monthly digests to be sent should I add additional lines to 
Mailman's "crontab.in" (or even the system's crontab)? For example:

# 3:00 PM every Friday
0 15 * * 5 /usr/bin/python -S /var/lib/mailman/cron/senddigests
# 9:00 AM first day of each month
0 9 1 * * /usr/bin/python -S /var/lib/mailman/cron/senddigests


Or does the "senddigests" script handle weekly and monthly digests by 
retrieving info from somewhere?

And if so, where does Mailman get the information as to which digests should be 
sent weekly or monthly? 

And also if so, what day of the week/month should it be sending by default for 
those digests?


Thanks in advance if anyone can straighten my head out on this.

/Mark



 

 


--
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: The Hotmail complaint saga continues

[Mark Dale via Mailman-Users]

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 result of people leaving messages in their junk folder (where they've 
been delivered automatically).
 
> 1. Is Linode, my VPS provider, also receiving these complaints? If so, I'm 
> surprised they haven't at least sent me a notice telling me about them.

The "complaint" messages that we receive are addressed to 
"postmater[AT]the.sending.servers.domain". They don't appear to be BCCed to the 
hosting company.


> 2. Does anyone know if having received these complaints might cause Microsoft 
> to be more likely to add my IP to their infamous block list? ...

Quite possibly it does. Once or twice a year Microsoft will block our list 
messages. The log files will show that our server is on their network block. 
The process is then:

A. Check that ALL your DNS records are in order (double check your DMARC, DKIM, 
SOA) and that your IP isn't blacklisted anywhere: https://mxtoolbox.com

B. Check that your server's IP reputation is okay at: 
https://talosintelligence.com

C. If you're all good with A and B, complete Microsoft's de-list form - 
https://sender.office.com

D. Your request will generally be refused initially so you need to reply 
(sometimes more than once) and explain that all your records are in order, the 
nature of your list, subscribers are double-opt in, and the measures you have 
put in place to prevent spam being sent.

E. I've found them to be responsive and generally there is a positive result 
within a day or two. 


/Mark
--
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: Messages being delivered to administrators who are not subscribed.

[Mark Dale via Mailman-Users]

> 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 + (UTC)
>> X-Original-To: kr...@list.krnet.org
>> Delivered-To: kr...@list.krnet.org
>> Received: from mout01.posteo.de (mout01.posteo.de [185.67.36.65])
>>   by sfo.mailmanlists.us (Postfix) with ESMTPS id A87C4451D4
>>   for ; Sat, 12 Mar 2022 04:11:21 + (UTC)

> 
> say the message was received by the list and resent by the list to 
> krnet-owner. Is krnet-ow...@list.krnet.org a member of the list?


Bingo! There you have it :-) 

Thank you very much yet again Mark. I think I'm now sufficiently humbled for 
not seeing that.

Best,
Mark 
--
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: Messages being delivered to administrators who are not subscribed.

[Mark Dale via Mailman-Users]

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 postfix/smtp[1158]: 6B3E7452E0: to=, 
>> relay=svn.postmark.io[95.217.216.206]:25, delay=2.1, 
>> delays=0.05/0.19/1.4/0.41, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 
>> 427CE3EE82)

> 
> 
> That's the final delivery to m...@postmark.io. What are the earlier log 
> messages showing the message arriving and being delivered to command 
> `/var/lib/mailman/mail/mailman post krnet` and maybe to command 
> `/var/lib/mailman/mail/mailman owner krnet`.


# grep "/var/lib/mailman/mail/mailman post krnet" mail.log

Mar 12 04:11:23 sfo postfix/local[1152]: A87C4451D4: to=, 
relay=local, delay=1.7, delays=1.7/0.01/0/0.05, dsn=2.0.0, status=sent 
(delivered to command: /var/lib/mailman/mail/mailman post krnet)


# grep "/var/lib/mailman/mail/mailman owner krnet" mail.log

Mar 12 04:11:25 sfo postfix/local[1152]: BAD65451F6: 
to=, relay=local, delay=0.39, 
delays=0.1/0.01/0/0.28, dsn=2.0.0, status=sent (delivered to command: 
/var/lib/mailman/mail/mailman owner krnet)




> 
> I.e there should be a whole chain of log messages for queue id 6B3E7452E0, 
> and then before that, how the message got to whatever queued it with id 
> 6B3E7452E0.


All I'm seeing for "6B3E7452E0" is:


Mar 12 04:11:26 sfo postfix/smtpd[1148]: 6B3E7452E0: client=ip6-localhost[::1]
Mar 12 04:11:26 sfo postfix/cleanup[1151]: 6B3E7452E0: 
message-id=<3366ecfd5912a33298f3b66849a74...@posteo.net>
Mar 12 04:11:26 sfo opendkim[13925]: 6B3E7452E0: ip6-localhost [::1] not 
internal
Mar 12 04:11:26 sfo opendkim[13925]: 6B3E7452E0: not authenticated
Mar 12 04:11:26 sfo opendkim[13925]: 6B3E7452E0: s=2017 d=posteo.ch SSL 
error:04091068:rsa routines:int_rsa_verify:bad signature
Mar 12 04:11:26 sfo opendkim[13925]: 6B3E7452E0: bad signature data
Mar 12 04:11:26 sfo postfix/qmgr[14048]: 6B3E7452E0: 
from=, size=3120, nrcpt=1 (queue active)
Mar 12 04:11:28 sfo postfix/smtp[1158]: 6B3E7452E0: to=, 
relay=svn.postmark.io[95.217.216.206]:25, delay=2.1, delays=0.05/0.19/1.4/0.41, 
dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 427CE3EE82)


>> =
>>
>> Header of the received message shows the message as having come from the 
>> Mailman server, and identifies the list correctly.

> 
> 
> What are the headers - full received chain and any Mailman added headers, 
> i.e. List-*:, etc.
> 



>From - Sat Mar 12 15:12:14 2022
X-Account-Key: account61
X-UIDL: 18236140259a
X-Mozilla-Status: 0001
X-Mozilla-Status2: 
X-Mozilla-Keys: 

Return-Path: 
Delivered-To: m...@postmark.io
Received: from svn.postmark.io
by svn.postmark.io with LMTP
id V9iBHHAdLGIcZxIASR0QWA
(envelope-from )
for ; Sat, 12 Mar 2022 05:11:28 +0100
Received: from sfo.mailmanlists.us (sfo.mailmanlists.us [167.71.156.220])
by svn.postmark.io (Postfix) with ESMTPS id 427CE3EE82
for ; Sat, 12 Mar 2022 05:11:28 +0100 (CET)
Received: from sfo.mailmanlists.us (ip6-localhost [IPv6:::1])
by sfo.mailmanlists.us (Postfix) with ESMTP id 6B3E7452E0
for ; Sat, 12 Mar 2022 04:11:26 + (UTC)
Authentication-Results: sfo.mailmanlists.us;
dkim=fail reason="signature verification failed" (2048-bit key; 
unprotected) header.d=posteo.ch header.i=@posteo.ch header.b="aOnoUCdm";
dkim-atps=neutral
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 + (UTC)
X-Original-To: kr...@list.krnet.org
Delivered-To: kr...@list.krnet.org
Received: from mout01.posteo.de (mout01.posteo.de [185.67.36.65])
 by sfo.mailmanlists.us (Postfix) with ESMTPS id A87C4451D4
 for ; Sat, 12 Mar 2022 04:11:21 + (UTC)
Received: from submission (posteo.de [185.67.36.169]) 
 by mout01.posteo.de (Postfix) with ESMTPS id A2D4C240026
 for ; Sat, 12 Mar 2022 05:11:19 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.ch; s=2017;
 t=1647058279; bh=uhsziU26DlE82aOodBuT5N/k3zqUF9gLxYr9j5Adduk=;
 h=Date:From:To:Subject:From;
 b=aOnoUCdmMpsz6xZo7olmCEYzDOzNVPw+G7ykfR0MOcALI+4LTpcLOkxJm5ILcN6Gj
 5v7dM9QGqV615jQ+z+lYR4nGmejN4Oqm36Ckcv6vl8mGeUs8nUx26tTFUDxPwo6Po6
 wYqPH+STSkGS/sBE22ZmCBLhta0FmjMdPjDe9sZ77dpATj4np/53EU8ObR0kyOrS3M
 OvsxbU8dFhsQq3ZugBUInkpFZuOiEKCjyDdb0HN9Wyqy9oyT931TDRAMXoawoy8YG8
 2b1HUIZkBc+2zSmTHpuFw6hRtAfIltddFkxbCTHDJhgYx5qnmJufUxYUHxpD3Z6/X/
 kXz56wcLSscnQ==
Received: from customer (localhost [127.0.0.1])
 by submission (posteo.de) with ESMTPSA id 4KFq9g0nhFz9rxK
 for ; Sat, 12 Mar 2022 05:11:18 +0100 (CET)
MIME-Version: 1.0
Date: Sat, 12 Mar 2022 04:11:18 +
To: 

[Mailman-Users] Re: Messages being delivered to administrators who are not subscribed.

[Mark Dale via Mailman-Users]

 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 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 of the 
>> post.
>>
>> Have I missed a setting, or have I screwed up the plumbing somewhere?


> 
> 
> What's in the Postfix mail.log for the delivery of the incoming message.
> 
> What are the aliases for this list?
> 
> Do the admin's messages come from Mailman?
> 

//

The issue is affecting only the one list on this server (all others are 
behaving correctly), which had me thinking it was a list-specific 
administration setting that I am not seeing.

The aliases for this list are as normal:

krnet:  "|/var/lib/mailman/mail/mailman post krnet"
krnet-admin:"|/var/lib/mailman/mail/mailman admin krnet"
krnet-bounces:  "|/var/lib/mailman/mail/mailman bounces krnet"
krnet-confirm:  "|/var/lib/mailman/mail/mailman confirm krnet"
krnet-join: "|/var/lib/mailman/mail/mailman join krnet"
krnet-leave:"|/var/lib/mailman/mail/mailman leave krnet"
krnet-owner:"|/var/lib/mailman/mail/mailman owner krnet"
krnet-request:  "|/var/lib/mailman/mail/mailman request krnet"
krnet-subscribe:"|/var/lib/mailman/mail/mailman subscribe krnet"
krnet-unsubscribe:  "|/var/lib/mailman/mail/mailman unsubscribe krnet"

.../bin/newaliases was run, and postfix reloaded.

/
/

SCENARIO 1.

m...@postmark.io = Administrator only (not a subscriber)

=

Test message posted to the list by a member at 04:11

Result: Message correctly delivered to all members, plus message delivered to 
Administrator (who is not a subscriber).  

=

Mailman server's Postfix log shows:

Mar 12 04:11:28 sfo postfix/smtp[1158]: 6B3E7452E0: to=, 
relay=svn.postmark.io[95.217.216.206]:25, delay=2.1, delays=0.05/0.19/1.4/0.41, 
dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 427CE3EE82)

=

Header of the received message shows the message as having come from the 
Mailman server, and identifies the list correctly.




/
/

SCENARIO 2

m...@postmark.io = Administrator and Subscriber


=

Test message posted to the list by a member at 04:21

Result: Message correctly delivered to all members, plus message delivered to 
Administrator. The Administrator is a subscriber, so received 2 copies of the 
message.

=

Mailman server's Postfix log shows:

Mar 12 04:21:16 sfo postfix/smtp[1513]: 08AA2452E1: to=, 
relay=svn.postmark.io[95.217.216.206]:25, delay=1.9, delays=0.05/0.16/1.3/0.42, 
dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as A0E743EE82)

Mar 12 04:21:25 sfo postfix/smtp[1519]: CD61B452DF: to=, 
relay=svn.postmark.io[95.217.216.206]:25, delay=12, delays=0.08/5.3/6.3/0.41, 
dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as A0E0E3EE82)

=

Headers of both the received messages show as having come from the Mailman 
server, and identify the list correctly.

/
/




--
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] Messages being delivered to administrators who are not subscribed.

[Mark Dale via Mailman-Users]

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 of the post.

Have I missed a setting, or have I screwed up the plumbing somewhere?

Nothing is leaping out at me from the logs. Any advice on where I should be 
looking would be much appreciated.

Thanks,
Mark

PS. Mailman 2.1.39 / Debian / Postfix
--
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: Digest on/off via email

[Mark Dale via Mailman-Users]

> 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 an email (The results of your email 
>> commands) but the digest mode does not get set to "Off".
>>
>>
>> 
>> 
>> The results of your email command are provided below. Attached is your
>> original message.
>>
>> - Results:
>>  Not authenticated 


==

> You have to authenticate before you can set any options. The part of the `set 
> help` you elided contains
> 
>     set authenticate  [address=]
>     To set any of your options, you must include this command first, along
>     with your membership password.  If you're posting from an address
>     other than your membership address, specify your membership address
>     with `address=' (no brackets around the email address, and no
>     quotes!).
> 
> 
> I.e. don't put the commands in the Subject:. In the body put
> 
> set authenticate 
> set digest off
> 
==

Many thanks once again Mark, that did the trick. 

I had indeed glossed over the "set help". It's the "bleedin' obvious" when it's 
pointed out. 


Best,
Mark

--
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] Digest on/off via email

[Mark Dale via Mailman-Users]

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




The results of your email command are provided below. Attached is your
original message.

- Results:
Not authenticated
Usage:

set help
Show this detailed help.

...

set digest plain
set digest mime
set digest off
When the `digest' option is turned off, you will receive postings
immediately when they are posted.  Use `set digest plain' if instead
you want to receive postings bundled into a plain text digest
(i.e. RFC 1153 digest).  Use `set digest mime' if instead you want to
receive postings bundled together into a MIME digest.




There isn't any info in the Mailman error log as to why the digest mode did not 
get turned off, and the only hint I've spotted so far is in the mail log where 
it says: "delivered to command: /var/lib/mailman/mail/mailman request LISTNAME"




Oct 20 21:28:04 sfo postfix/local[30957]: 0C59141796: 
to=<***LISTNAME@list.***DOMAIN>, relay=local, delay=0.44, 
delays=0.38/0.01/0/0.05, dsn=2.0.0, status=sent (delivered to command: 
/var/lib/mailman/mail/mailman request LISTNAME)


Oct 20 21:28:16 sfo postfix/smtp[30959]: 86BD141796: to=, 
relay=mx01.posteo.de[185.67.36.62]:25, delay=10, delays=0.01/0.01/9/1.3, 
dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 4HZNy74yvcz11SZ)




I note that sending a request email with the subject as "set show" returns an 
email with the expected result and the mail log also shows "delivered to 
command: /var/lib/mailman/mail/mailman request LISTNAME" -- so I'm guessing 
there isn't a file permissions issue with /var/lib/mailman/mail/mailman.




The results of your email command are provided below. Attached is your
original message.

- Results:
Your current option settings:
ack off
digest plain
delivery on
myposts on
hide off
duplicates off
reminders on

- Done.




Any clues on where I should be looking to get the Digest on/off working via 
email (or if I missed a setting in the list's Administration page) would be 
greatly appreciated.


Thanks,
Mark

--
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 + postfix automatically adding aliases

[Mark Dale via Mailman-Users]

 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. Am I supposed to create these 
> data/aliases files manually? Where are they supposed to go? There is no data/ 
> directory in /usr/lib/mailman and /var/lib/mailman has a data directory but 
> nothing inside named aliases
> 
> 
> [root@dhbmailman2 mailman]# bin/genaliases 
> To finish creating your mailing list, you must edit your /etc/aliases (or
> equivalent) file by adding the following lines, and possibly running the
> `newaliases' program:
> 
> ## newserver_test mailing list
> newserver_test:  "|/usr/lib/mailman/mail/mailman post 
> newserver_test"
> newserver_test-admin:"|/usr/lib/mailman/mail/mailman admin 
> newserver_test"
> newserver_test-bounces:  "|/usr/lib/mailman/mail/mailman bounces 
> newserver_test"
> newserver_test-confirm:  "|/usr/lib/mailman/mail/mailman confirm 
> newserver_test"
> newserver_test-join: "|/usr/lib/mailman/mail/mailman join 
> newserver_test"
> newserver_test-leave:"|/usr/lib/mailman/mail/mailman leave 
> newserver_test"
> newserver_test-owner:"|/usr/lib/mailman/mail/mailman owner 
> newserver_test"
> newserver_test-request:  "|/usr/lib/mailman/mail/mailman request 
> newserver_test"
> newserver_test-subscribe:"|/usr/lib/mailman/mail/mailman subscribe 
> newserver_test"
> newserver_test-unsubscribe:  "|/usr/lib/mailman/mail/mailman unsubscribe 
> newserver_test"
> 
> ## mailman mailing list
> mailman:  "|/usr/lib/mailman/mail/mailman post mailman"
> mailman-admin:"|/usr/lib/mailman/mail/mailman admin mailman"
> mailman-bounces:  "|/usr/lib/mailman/mail/mailman bounces mailman"
> mailman-confirm:  "|/usr/lib/mailman/mail/mailman confirm mailman"
> mailman-join: "|/usr/lib/mailman/mail/mailman join mailman"
> mailman-leave:"|/usr/lib/mailman/mail/mailman leave mailman"
> mailman-owner:"|/usr/lib/mailman/mail/mailman owner mailman"
> mailman-request:  "|/usr/lib/mailman/mail/mailman request mailman"
> mailman-subscribe:"|/usr/lib/mailman/mail/mailman subscribe mailman"
> mailman-unsubscribe:  "|/usr/lib/mailman/mail/mailman unsubscribe mailman"
> 
> 



The usual thing is to copy and paste that into the /etc/aliases file each time 
you create a list, then run "newaliases" and "postfix reload".

# nano /etc/aliases
# newaliases
# postfix reload


--
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: Non-ascii characters missing from Pipermail archive txt and gz downloads

[Mark Dale via Mailman-Users]

 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
> "hey, I know how to gunzip", the server will automatically gzip, the
> client gunzip, and you know nothing about it except that you have text
> onscreen.
> 
> It's unclear what the system will do if offered a .txt.gz file.  If
> the server is smart, it might say
> 
> Content-Type: text/plain; name=whatever.txt  <-- note: no .gz
> Content-Transfer-Encoding: gzip
> 
> and the end result is as above.  But it's not obviously a good idea
> for the server to second-guess the admin that way.
> 
> It's plausible that if the server just sends it as a binary, the
> client will say, "oh, they gzipped it on purpose, I should treat it as
> a file and save it", or it might say, "I know what a .txt is, and go
> ahead and transparently ungzip it.  Clients are reliably unreliable as
> a class -- some users want Do What I Mean, some what Do What I Say,
> and different clients will cater to different users.
> 
> Bottom line: if you're sure you want your .txt files treated as plain
> text and displayed as conveniently as possible, ungzip them!  Very
> likely you won't use any more bandwidth (and by the way, modern
> servers tend to cache that gzipped blob in case somebody asks for it
> again, so on-the-fly compression doesn't necessarily waste hours of
> CPU).
> 
> If for some reason you'd prefer that they be gzipped at both ends,
> that's probably more work to guarantee.


Thanks very much for this Steve. The learning from you guys never stops :-) 

And "unzip" was the pick at of the day.

Best,
Mark
--
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: Non-ascii characters missing from Pipermail archive txt and gz downloads

[Mark Dale via Mailman-Users]

 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 post is to point out that the .txt.gz files
> are an anachronism from the days when the bit of bandwidth saved by
> delivering a compressed version was important to more that a few ancient
> curmudgeons like me.
> 
> These days, the bandwidth savings is unimportant and is probably offset
> by the redundant storage and processing for the .txt.gz files.
> 
> If you want to get rid of these files, see
> .


Thank you Mark, that information is appreciated and I've made the change.


--
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: Non-ascii characters missing from Pipermail archive txt and gz downloads

[Mark Dale via Mailman-Users]

 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 characters.
> 
> How are you viewing the .txt file? The two bytes C3 A7 are the utf-8
> representation of the c-cedilla character. If you view that file as
> iso-8859-1 (latin-1 or western) encoding, you will see those two bytes
> as ç, but if you view it as uf-8 encoding, you will see the c-cedilla.
> 
> In short, the file contains just what it should, but there is a
> Content-Transfer-Encoding issue. If you are viewing it in a browser, the
> issue is the default content character set in your web server. For
> example with Apache something like
> 
> AddCharset utf-8 .txt
> 
> will do what you want, or perhaps your browser has a selection. E.g.,
> Firefox has a text encoding selection in the View menu and you want
> Unicode, not Western.
> 
> If you are actually downloading the file and viewing it with something
> else, the issue is with whatever you are viewing it with.
> 


... Uh-oh ...  ... you're right that the issue is what I'm 
viewing it with. 

Just to clarify: there are two .txt files ...

(A) an archive .txt.gz file before I made the change to the mm_cfg.py file; and 
(B) an archive .txt.gz file after I made the change.

I followed the txt.gz link on the Pipermail page and got the options to 
"Download" or "Open file".

FAIL -- On choosing the "Open file" with ArchiveManager/JEdit, File-A showed 
the c-cedilla replaced by the question-mark; and File-B showed it replaced by 
the ç characters.

SUCCESS -- However, choosing "Download", then gunzip and then open with JEdit I 
get a better result: File A showed the c-cedilla replaced by the question-mark 
as expected; but File-B shows the c-cedilla (happy days!). 


So in short, Mark Sapiro's recommended fix -- https://wiki.list.org/x/15958250 
-- has cracked this little chestnut.

Many thanks once again Mark.




--
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: Non-ascii characters missing from Pipermail archive txt and gz downloads

[Mark Dale via Mailman-Users]

 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 missing and displayed as "?".
> ...
>> Any advice on getting the non-ascii characters written into the archive .txt 
>> file would be gratefully received.
> 
> 
> The message is prepared for the .txt file by the Article.as_text()
> method in HyperArch.py
> <https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/view/head:/Mailman/Archiver/HyperArch.py#L563>.
> In order to do the email address obfuscation in the message body,
> whether or not ARCHIVER_OBSCURES_EMAILADDRS is True, the method first
> converts the body to unicode using the charset of the list's language
> and then after possible obfuscation, converts it back, again using the
> charset of the list's language. Both these conversions use
> `errors=replace` which replaces any characters not in the charset with,
> in the case of ascii, `?`.
> 
> One way to avoid this replacement would be to change the charset for
> English from ascii to utf-8. See <https://wiki.list.org/x/15958250>.
> 
> This isn't a complete solution in the case where the non-ascii
> characters are encoded other than `utf-8`, e.g., `iso-8859-1`, in the
> original message, but will probably handle most cases
> 
> 

Hi Mark,

Thank you for the comprehensive explanation of the process.

I haven't made any headway with the suggested solution of modifying the 
mm_cfg.py file. 

The author says: "The one known downside of doing this is that Python's email 
library which is used by Mailman will base64 encode charset=utf-8 message 
bodies which makes the raw message body impossible to read by eye or search 
with simple tools like grep." -- which, on reading, had me thinking I will be 
jumping from the frying pan into the fire.

However, in the spirit of things, I made the addition to the mm_cfg.py and ...

As a example, using a subscriber's name that appears in the archive.

François -- as seen in the mbox and Pipermail web archive: the cedille is 
displayed correctly.

Fran?ois -- as seen in the normal downloaded txt: the cedille is replaced by 
question mark (as expected).

François -- as seen in the mm_cfg modified download txt: the cedille replace 
by odd characters.


In short, no joy.

So I'm thinking that if the part of HyperArch.py that does the email address 
obfuscation (and back again) is removed, would that be a step in the direction 
I want to go?

My Python foo is way less than zero but I'm looking at lines 563 -- 600. Or is 
my thinking completely bonkers? 

Regards,
Mark




--
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] Non-ascii characters missing from Pipermail archive txt and gz downloads

[Mark Dale via Mailman-Users]

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 Sapiro's guide I've captured the incoming message to file.

 - https://www.mail-archive.com/mailman-users@python.org/msg73469.html

The message is received by Mailman with the non-ascii characters displaying 
correctly. 

The header of that message has:

User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.9.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Language: en-AU
Content-Transfer-Encoding: 8bit

In the list's mbox file and archive webpage, the message displays the non-ascii 
characters correctly.

In the archive's downloaded .txt (and also .gz) file, the non-ascii characters 
are missing and displayed as "?".

I've copied the message text in below, from both the correct one from the email 
and the erroneous .txt file. Hopefully they won't get scrambled up when I send 
this.

Any advice on getting the non-ascii characters written into the archive .txt 
file would be gratefully received.

Thanks,
Mark


=== Message text as okay in mbox and as shown on the archive webpage ===

If one goes by the definition of veḷippaṭai as given in the Tamil Lexicon that 
the meaning of an ambiguous word should be disambiguated by a qualifying word, 
then aruvi āmpal does not conform to that definition since in the case of aruvi 
āmpal in Patiṟṟuppattu 63, aruvi is really made up of aru+vi, a compound. 
Moreover, the expression aṭai aṭuppu aṟiyā is already there to clarify that 
āmpal is a number and not a flower. Thus, aruvi simply provides information in 
addition to aṭai aṭuppu aṟiyā that āmpal is not a flower. The modern 
commentator Aruḷampalavaṉār also does not call it veḷippaṭai.

=== 

=== Message text with missing characters in te archive's txt and gz downloads ==

If one goes by the definition of ve?ippa?ai as given in the Tamil Lexicon that 
the meaning of an ambiguous word should be disambiguated by a qualifying word, 
then aruvi ?mpal does not conform to that definition since in the case of aruvi 
?mpal in Pati??uppattu 63, aruvi is really made up of aru+vi, a compound. 
Moreover, the expression a?ai a?uppu a?iy? is already there to clarify that 
?mpal is a number and not a flower. Thus, aruvi simply provides information in 
addition to a?ai a?uppu a?iy? that ?mpal is not a flower. The modern 
commentator Aru?ampalava??r also does not call it ve?ippa?ai.

===
--
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: Pipermail scrubbing ascii txt to ksh attachment

[Mark Dale via Mailman-Users]

 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 patch
> Scrubber.py with this patch, you won't need to edit the mbox and rebuild
> the archive as that message won't get scrubbed.

Hi Mark. Your patch to Scrubber.py has solved the problem. Thank you.

A summary below: 



PROBLEM: Plain text emails being automatically posted to a list, via a Perl 
script, were displaying okay in subscribers' email clients, but in the archive 
-- the body of the message is scrubbed as "attachment.ksh".

CAUSE: The headers of the posts to the list contained the lines: 

Content-Disposition: inline
Content-Type: text/plain 

Mark wrote: "If the script that sends this mail can be altered to either 
include the charset= on the Content-Type: text/plain header or not include the
Content-Disposition: inline header or both, that would solve this." He then 
wrote a patch for Mailman/Handlers/Scrubber.py to do this (in the event that 
the script could not be modified).

=== modified file 'Mailman/Handlers/Scrubber.py'
--- Mailman/Handlers/Scrubber.py2020-06-21 18:45:30 +
+++ Mailman/Handlers/Scrubber.py2021-03-06 19:10:28 +
@@ -90,6 +90,9 @@
 if ctype.lower == 'application/octet-stream':
 # For this type, all[0] is '.obj'. '.bin' is better.
 return '.bin'
+if ctype.lower == 'text/plain':
+# For this type, all[0] is '.ksh'. '.txt' is better.
+return '.txt'
 return all and all[0]
 
 
@@ -196,8 +199,11 @@
 format = part.get_param('format')
 delsp = part.get_param('delsp')
 # TK: if part is attached then check charset and scrub if none
-if part.get('content-disposition') and \
-   not part.get_content_charset():
+# MAS: Content-Disposition is not a good test for 'attached'.
+# RFC 2183 sec. 2.10 allows Content-Disposition on the main body.
+# Make it specifically 'attachment'.
+if (part.get('content-disposition', '').lower() == 'attachment'
+and not part.get_content_charset()):
 omask = os.umask(002)
 try:
 url = save_attachment(mlist, part, dir)


IN ADDITION: The following script was run to tidy up the list's .mbox file.

#!/bin/bash
PATH=/usr/sbin:/usr/bin:/sbin:/bin
LISTNAME=your_list_name_goes_here
echo $LISTNAME archive rebuild started at $(date +%H:%M:%S)
sed -i '/Content-Disposition: inline/d' 
/var/lib/mailman/archives/private/$LISTNAME.mbox/$LISTNAME.mbox
sed -i 's/Content-Type: text\/plain/Content-Type: text\/plain; 
charset="us-ascii"/' 
/var/lib/mailman/archives/private/$LISTNAME.mbox/$LISTNAME.mbox
/usr/lib/mailman/bin/arch --wipe $LISTNAME
echo $LISTNAME archive rebuild completed at $(date +%H:%M:%S)
exit 0


 
--
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: Pipermail scrubbing ascii txt to ksh attachment

[Mark Dale via Mailman-Users]

 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 wrote:
>>
>> If it turns out that the the owner is unable to modify their Perl script, 
>> setting this shell script to run once a day may not be a problem as their 
>> list is auto-posted to at a scheduled time every day. It's a kludge of a 
>> "fix" I know, but it will limp it home.

> 
> The patch I posted previously was bad. This one is correct. If you patch
> Scrubber.py with this patch, you won't need to edit the mbox and rebuild
> the archive as that message won't get scrubbed.
> 

A -- when I looked (blindly) at the script earlier I was thinking that it 
would only write the attachment as a .txt rather than .ksh file. 

I've added your most recent patch. Now standing by to watch the next post get 
archived in glorious plain text.

Thank you once again Mark. 




--
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: Pipermail scrubbing ascii txt to ksh attachment

[Mark Dale via Mailman-Users]

 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 wrote:
>>
>>
>> I'll pass it on to the list owner to modify their script and see how we
>> get on.


> 
> 
> In case the script doesn't get modified, here's a patch I plan to commit
> to Scrubber.py which should help.
> 
> 
> --


Thanks again Mark. The list owner has indicated they can modify their Perl 
script (not done as yet), so I'll put your patch in place regardless.

I ran a script (below) against the mbox file to remove "Content-Disposition: 
inline" and change "Content-Type: text/plain" to include the charset and that 
has the archived messages now displaying nicely as plain text.

If it turns out that the the owner is unable to modify their Perl script, 
setting this shell script to run once a day may not be a problem as their list 
is auto-posted to at a scheduled time every day. It's a kludge of a "fix" I 
know, but it will limp it home.


#!/bin/bash
PATH=/usr/sbin:/usr/bin:/sbin:/bin
LISTNAME=redacted
echo $LISTNAME archive rebuild started at $(date +%H:%M:%S)
sed -i '/Content-Disposition: inline/d' 
/var/lib/mailman/archives/private/$LISTNAME.mbox/$LISTNAME.mbox
sed -i 's/Content-Type: text\/plain/Content-Type: text\/plain; 
charset="us-ascii"/' 
/var/lib/mailman/archives/private/$LISTNAME.mbox/$LISTNAME.mbox
/usr/lib/mailman/bin/arch --wipe $LISTNAME
echo $LISTNAME archive rebuild completed at $(date +%H:%M:%S)
exit 0
--
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: Pipermail scrubbing ascii txt to ksh attachment

[Mark Dale via Mailman-Users]

 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:
>>
>> Reading Steve's reply just now makes me look suspiciously at the Perl
>> X-Mailer: MIME::Lite that is sending the email to the list. My
>> understanding is the list owner has scheduled a Perl script to export
>> from a database and post the resulting export.
> 
> 
> I've looked at the code more carefully, and I see there are two
> conditions for the text/plain part to be scrubbed. One is the lack of a
> charset= parameter, but the other is that the part is not the only body
> part or maybe the first part of a multipart body.
> 
> However, the way the code determines if the part is the body vs. being
> an attachment is the presence of a Content-Disposition: header. Your
> message has a Content-Disposition: inline header and while this is
> explicitly allowed by RFC 2183, it is unusual for a single part
> text/plain message.
> 
> If the perl script that generates this message can not include that
> header, I don't thing the part will be scrubbed.
> 

Ahhh -- that's great intel Mark: thank you very much!!! Your diligence
and patience are mind blowing.

I'll pass it on to the list owner to modify their script and see how we
get on.

Content-Disposition: inline
Content-Type: text/plain
MIME-Version: 1.0
X-Mailer: MIME::Lite 3.031 (F2.85; T2.17; A2.21; B3.15; Q3.13)



--
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: Pipermail scrubbing ascii txt to ksh attachment

[Mark Dale via Mailman-Users]

 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:
>>
>> Thanks. I've implemented your script patch (LISTNAME needed to be in
>> quotes otherwise the server spat the dummy).
> 
> Sorry about that ...
> 
>> The next scheduled post to
>> the list will be in about 10 hours so I'll have a result to look at then.
> 
> 
> Cool.
> 
> 
>> Reading Steve's reply just now makes me look suspiciously at the Perl
>> X-Mailer: MIME::Lite that is sending the email to the list. My
>> understanding is the list owner has scheduled a Perl script to export
>> from a database and post the resulting export.
>>
>> Anyways, I'll see what the result gets written by scripts/post  in the
>> morning.
> 
> OK.
> 
> I'm just curious, but if the body is scrubbed as an attachment with a
> .txt extension instead of .ksh would that help?
> 


There is no problem opening the .ksh file but the owner of the list
would like to see the archive message display in the message body. The
Namazu text search engine that's incorporated into the list's
archive will then be of use. So having the attachment use .txt wont
really help.

Here is what the edited scripts/post wrote to file last night.

>From noreply@REDACTED  Fri Mar  5 12:03:30 2021
Return-Path: 
X-Original-To: REDACTED@lists.REDACTED
Delivered-To: REDACTED@lists.REDACTED
Received: from alln-iport-3.REDACTED (alln-iport-3.REDACTED [173.37.142.90])
by mailmanlists.network (Postfix) with ESMTPS id EC62F2029E
for ; Fri,  5 Mar 2021 12:03:29 + (UTC)
X-IPAS-Result: =?us-ascii?q?A0DxBADeHEJg/5tdJa1iHAEBAQEBAQcBARIBAQQEAQGCD?=
 =?us-ascii?q?wKCKYIGjXalKAsBAQEPNAQBAYUEgUUCJTkFDQIDAQEBAwIDAQEBAQUBAQECA?=
 =?us-ascii?q?QYEcYVuiTOFWq07AQEBgiaJNoEugTkBix6CIyYcgguBR407GgSTKwGRGJwCh?=
 =?us-ascii?q?EqGc41OhkWDdJ94C4YurF2EHIFsIoFXcIM6TxkNVZwwIwECZwIGCgEBAwmPJ?=
 =?us-ascii?q?gEB?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.81,224,1610409600";
   d="scan'208";a="656493238"
Received: from rcdn-core-4.REDACTED ([173.37.93.155])
  by alln-iport-3.REDACTED with ESMTP/TLS/DHE-RSA-SEED-SHA; 05 Mar 2021
12:03:28 +
Received: from mail.vrt.REDACTED ([10.83.44.69])
by rcdn-core-4.REDACTED (8.15.2/8.15.2) with SMTP id 125C3S2G009788
for ; Fri, 5 Mar 2021 12:03:28 GMT
Message-Id: <202103051203.125C3S2G009788@rcdn-core-4.REDACTED>
Received: from localhost.localdomain (sigmanager.vrt.REDACTED [10.7.89.25])
by mail.vrt.REDACTED (Postfix) with ESMTP id 44C1E463D6
for ; Fri,  5 Mar 2021 12:03:28 + (UTC)
Content-Disposition: inline
Content-Type: text/plain
MIME-Version: 1.0
X-Mailer: MIME::Lite 3.031 (F2.85; T2.17; A2.21; B3.15; Q3.13)
Date: Fri, 5 Mar 2021 07:03:28 -0500
From: noreply@REDACTED
To: REDACTED@lists.REDACTED
Subject: Signatures Published daily - 26099
Content-Transfer-Encoding: quoted-printable
X-Outbound-SMTP-Client: 10.83.44.69, [10.83.44.69]
X-Outbound-Node: rcdn-core-4.REDACTED


REDACTED Publishing Notice

Datefile:   daily
Version:26099
Publisher:  REDACTED
New Sigs:   139
Dropped Sigs:   0
Ignored Sigs:   75


New Detection Signatures:


* Win.Malware.Injects-9838834-0

* Win.Trojan.Generic-9838835-0

* Win.Packed.Razy-9838836-0

* Win.Packed.Razy-9838837-0


--
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: Pipermail scrubbing ascii txt to ksh attachment

[Mark Dale via Mailman-Users]

 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 the Mailman's group write permission on
> it. Then apply the following patch to Mailman's scripts/post
> 
>> === modified file 'scripts/post'
>> --- scripts/post 2018-06-17 23:47:34 +
>> +++ scripts/post 2021-03-05 01:16:56 +
>> @@ -58,8 +58,12 @@
>>  # some MTAs have a hard limit to the time a filter prog can run.  
>> Postfix
>>  # is a good example; if the limit is hit, the proc is SIGKILL'd giving 
>> us
>>  # no chance to save the message.
>> +content = sys.stdin.read()
>> +if listname == LISTNAME:
>> +with open('PATH_TO_FILE', 'a') as fp:
>> +fp.write(content)
>>  inq = get_switchboard(mm_cfg.INQUEUE_DIR)
>> -inq.enqueue(sys.stdin.read(),
>> +inq.enqueue(content,
>>  listname=listname,
>>  tolist=1, _plaintext=1)
>>  
>>
> 
> 
> where LISTNAME is the problem list's name and PATH_TO_FILE is the path
> to the file you created. This file will accumulate all the incoming
> messages posted to the list, exactly as they are received by Mailman.
> 
> Then we can at least know for sure what that message looks like.
> 
> Of course, once you have captured one such message, you can revert the
> patch.
> 

Thanks. I've implemented your script patch (LISTNAME needed to be in
quotes otherwise the server spat the dummy). The next scheduled post to
the list will be in about 10 hours so I'll have a result to look at then.

Reading Steve's reply just now makes me look suspiciously at the Perl
X-Mailer: MIME::Lite that is sending the email to the list. My
understanding is the list owner has scheduled a Perl script to export
from a database and post the resulting export.

Anyways, I'll see what the result gets written by scripts/post  in the
morning.

Cheers,
Mark
--
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: Pipermail scrubbing ascii txt to ksh attachment

[Mark Dale via Mailman-Users]

 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 
> 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:
>>> 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 renders each archived message as a ".ksh" attachment.
>>>
>>>
>>> *
>>>
>>> >From noreply at XXX.com  Wed Mar  3 12:06:05 2021
>>> From: noreply at XXX.com (noreply at XXX.com)
>>> Date: Wed, 3 Mar 2021 07:06:05 -0500
>>> Subject: [XXX] XXX Published daily - 26097
>>> Message-ID: <202103031206.123C662K015222@XXX>
>>>
>>> An embedded and charset-unspecified text was scrubbed...
>>> Name: not available
>>> URL:
>>> <https://XXX/pipermail/XXX/attachments/20210303/06a36d4b/attachment.ksh>
>>>
>>> *
>>>
>>> The message header contains:
>>>
>>> Content-Disposition: inline
>>> MIME-Version: 1.0
>>> X-Mailer: MIME::Lite 3.031 (F2.85; T2.17; A2.21; B3.15; Q3.13)
>>> ...
>>> Content-Type: text/plain; charset="us-ascii"
>>> Content-Transfer-Encoding: 7bit
>>>
>>>
>>> Could anyone point me in the right direction to get the archived
>>> messages to display their content as text in the message body instead of
>>> as an attachment?
>>
>> In order to help with this, I need to see the complete MIME structure of
>> the message. I.e. all the Content-Type: headers including the top level
>> and all the boundaries. This information for a message received from the
>> list is what I want to see as that's what Scrubber sees. Or the message
>> from the archives/private/listname.mbox/listname.mbox would do too.
>>
>> Scrubber should not be scrubbing the 'Content-Type: text/plain;
>> charset="us-ascii"' part with the message 'An embedded and
>> charset-unspecified text was scrubbed...'. Something else is going on here.
>>
>> The .ksh extension comes from the Python library
>> mime_types.guess_all_extensions, which returns the list
>>
>> ['.ksh', '.bat', '.h', '.txt', '.pl', '.c', '.asc', '.text', '.pot',
>> '.brf', '.srt']
>>
>> for text/plain and we arbitrarily pick the first one which is .ksh, but
>> we shouldn't be doing that with a text/plain part with a declared charset.
>>
> 
> ==
> 
> Thanks Mark. I've copied the message from mbox file and pasted below.
> (the client's info is marked as redacted).
> 
> Something I did notice: in the original received email headers I see:
> 
> Content-Disposition: inline
> Content-Type: text/plain; charset="us-ascii"
> Content-Transfer-Encoding: 7bit
> 
> And in the mbox file below (of the same message), I see:
> 
> Content-Disposition: inline
> Content-Type: text/plain
> Content-Transfer-Encoding: quoted-printable
> 
> 
> 
> 
>>From noreply@REDACTED  Thu Mar  4 12:04:42 2021
> Return-Path: 
> X-Original-To: REDACTED@lists.REDACTED
> Delivered-To: REDACTED@lists.REDACTED
> Received: from alln-iport-1.REDACTED (alln-iport-1.REDACTED [173.37.142.88])
>  by mailmanlists.network (Postfix) with ESMTPS id EDCEB1FFCA
>  for ; Thu,  4 Mar 2021 12:04:41 + (UTC)
> X-IPAS-Result: =?us-ascii?q?A0CcAgAZzEBgmJpdJa1iHgEBCxIMghGEL412pSQLAQEBD?=
>  =?us-ascii?q?zQEAQGFBIFFAiU5BQ0CAwEBAQMCAwEBAQEFAQEBAgEGBBQBAQEBAQEBAYZDi?=
>  =?us-ascii?q?TOCUoMIrWIBAQGCJok2gS2BOYsegiQmHIILgUQDgSiMExoEhVWNUAGREpt7h?=
>  =?us-ascii?q?EiGco1JhkWDcp9kC4YsrEqEGoFsIIFZcIM6TxkNVY1jjk0jAQJnAgYKAQEDC?=
>  =?us-ascii?q?YwTAQE?=
> X-IronPort-Anti-Spam-Filtered: true
> X-IronPort-AV: E=Sophos;i="5.81,222,1610409600"; d="scan'208";a="656725958"
> Received: from rcdn-core-3.REDACTED ([173.37.93.154])
>  by alln-iport-1.REDACTED with ESMTP/TLS/DHE-RSA-SEED-SHA;
>  04 Mar 2021 12:04:41 +
> Received:

[Mailman-Users] Re: Pipermail scrubbing ascii txt to ksh attachment

[Mark Dale via Mailman-Users]

 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:
>> 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 renders each archived message as a ".ksh" attachment.
>>
>>
>> *
>>
>> >From noreply at XXX.com  Wed Mar  3 12:06:05 2021
>> From: noreply at XXX.com (noreply at XXX.com)
>> Date: Wed, 3 Mar 2021 07:06:05 -0500
>> Subject: [XXX] XXX Published daily - 26097
>> Message-ID: <202103031206.123C662K015222@XXX>
>>
>> An embedded and charset-unspecified text was scrubbed...
>> Name: not available
>> URL:
>> <https://XXX/pipermail/XXX/attachments/20210303/06a36d4b/attachment.ksh>
>>
>> *
>>
>> The message header contains:
>>
>> Content-Disposition: inline
>> MIME-Version: 1.0
>> X-Mailer: MIME::Lite 3.031 (F2.85; T2.17; A2.21; B3.15; Q3.13)
>> ...
>> Content-Type: text/plain; charset="us-ascii"
>> Content-Transfer-Encoding: 7bit
>>
>>
>> Could anyone point me in the right direction to get the archived
>> messages to display their content as text in the message body instead of
>> as an attachment?
> 
> In order to help with this, I need to see the complete MIME structure of
> the message. I.e. all the Content-Type: headers including the top level
> and all the boundaries. This information for a message received from the
> list is what I want to see as that's what Scrubber sees. Or the message
> from the archives/private/listname.mbox/listname.mbox would do too.
> 
> Scrubber should not be scrubbing the 'Content-Type: text/plain;
> charset="us-ascii"' part with the message 'An embedded and
> charset-unspecified text was scrubbed...'. Something else is going on here.
> 
> The .ksh extension comes from the Python library
> mime_types.guess_all_extensions, which returns the list
> 
> ['.ksh', '.bat', '.h', '.txt', '.pl', '.c', '.asc', '.text', '.pot',
> '.brf', '.srt']
> 
> for text/plain and we arbitrarily pick the first one which is .ksh, but
> we shouldn't be doing that with a text/plain part with a declared charset.
> 

==

Thanks Mark. I've copied the message from mbox file and pasted below.
(the client's info is marked as redacted).

Something I did notice: in the original received email headers I see:

Content-Disposition: inline
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

And in the mbox file below (of the same message), I see:

Content-Disposition: inline
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable




>From noreply@REDACTED  Thu Mar  4 12:04:42 2021
Return-Path: 
X-Original-To: REDACTED@lists.REDACTED
Delivered-To: REDACTED@lists.REDACTED
Received: from alln-iport-1.REDACTED (alln-iport-1.REDACTED [173.37.142.88])
 by mailmanlists.network (Postfix) with ESMTPS id EDCEB1FFCA
 for ; Thu,  4 Mar 2021 12:04:41 + (UTC)
X-IPAS-Result: =?us-ascii?q?A0CcAgAZzEBgmJpdJa1iHgEBCxIMghGEL412pSQLAQEBD?=
 =?us-ascii?q?zQEAQGFBIFFAiU5BQ0CAwEBAQMCAwEBAQEFAQEBAgEGBBQBAQEBAQEBAYZDi?=
 =?us-ascii?q?TOCUoMIrWIBAQGCJok2gS2BOYsegiQmHIILgUQDgSiMExoEhVWNUAGREpt7h?=
 =?us-ascii?q?EiGco1JhkWDcp9kC4YsrEqEGoFsIIFZcIM6TxkNVY1jjk0jAQJnAgYKAQEDC?=
 =?us-ascii?q?YwTAQE?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.81,222,1610409600"; d="scan'208";a="656725958"
Received: from rcdn-core-3.REDACTED ([173.37.93.154])
 by alln-iport-1.REDACTED with ESMTP/TLS/DHE-RSA-SEED-SHA;
 04 Mar 2021 12:04:41 +
Received: from mail.vrt.REDACTED ([10.83.44.69])
 by rcdn-core-3.REDACTED (8.15.2/8.15.2) with SMTP id 124C4e83021704
 for ; Thu, 4 Mar 2021 12:04:40 GMT
Message-Id: <202103041204.124C4e83021704@rcdn-core-3.REDACTED>
Received: from localhost.localdomain (sigmanager.vrt.REDACTED
 [10.7.89.25])
 by mail.vrt.REDACTED (Postfix) with ESMTP id 7E95E424D5
 for ; Thu,  4 Mar 2021 12:04:40 + (UTC)
Content-Disposition: inline
Content-Type: text/plain
MIME-Version: 1.0
X-Mailer: MIME::Lite 3.031 (F2.85; T2.17; A2.21; B3.15; Q3.13)
Date: Thu, 4 Mar 2021 07:04:40 -0500
From: noreply@REDACTED
To: REDACTED@lists.REDACTED
Content-Transfer-Encoding: quoted-printable
X-Outbound-SMTP-Client: 10.83.44.69, [10.83.44.69]
X-Outbound-Node: rcdn-c

[Mailman-Users] Pipermail scrubbing ascii txt to ksh attachment

[Mark Dale via Mailman-Users]

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 renders each archived message as a ".ksh" attachment.


*

>From noreply at XXX.com  Wed Mar  3 12:06:05 2021
From: noreply at XXX.com (noreply at XXX.com)
Date: Wed, 3 Mar 2021 07:06:05 -0500
Subject: [XXX] XXX Published daily - 26097
Message-ID: <202103031206.123C662K015222@XXX>

An embedded and charset-unspecified text was scrubbed...
Name: not available
URL:


*

The message header contains:

Content-Disposition: inline
MIME-Version: 1.0
X-Mailer: MIME::Lite 3.031 (F2.85; T2.17; A2.21; B3.15; Q3.13)
...
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit


Could anyone point me in the right direction to get the archived
messages to display their content as text in the message body instead of
as an attachment?


Thanks,
Mark
--
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: Post log not being written

[Mark Dale]

==
> > The oddity was that with the check "/var/run/mailman/mailman.pid" -- the 
> > subscribe log was getting written but not the post. 
> > 
> > /var/log/mailman/subscribe /var/log/mailman/post {
> > ...
> > }
> 
==
> The subscribe log gets written often by the web CGIs. These are
> stand-alone, short lived processes, so they will always write to
> subscribe.log. However, if a qrunner writes to the subscribe log, it
> will continue to write to the rotated subscribe.log.1 even though the
> CGIs are writing to subscribe log. Thus you may find that while
> subscribe was being written, there were also new entries in subscribe.i
> written by CommandRunner when processing email commands.
> 
> Some logs including post, smtp and smtp-failure logs, are only written
> by Oby a qrunner so the new *.log won't get written until the runner is
> restarted or is SIGHUP'd either directly or by mailmanctl reopen.
==

Thanks Mark, that knowledge is very useful, and much appreciated.
--
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: Post log not being written

[Mark Dale]

> > 
> >>> Today that log file has rotated ("post.1) and the new post log file was
> >>> not being written to -- until I restarted the qrunner again. As said,
> >>> no problems with mail delivery, and the other logs.
> > 
> >> What does your logrotate script contain?
> >> Does it do
> >> bin/mailmanctl reopen
> >> after rotation?
> > 
> > 
> > Yes. It does "reopen" for "post". 
> > 
> > /var/log/mailman/subscribe /var/log/mailman/post {
> > su root list
> > daily
> > missingok
> > create 0664 list list
> > rotate 3
> > compress
> > delaycompress
> > sharedscripts
> > postrotate
> > [ -f '/var/run/mailman/mailman.pid' ] && 
> > /usr/lib/mailman/bin/mailmanctl -q reopen || exit 0
> > endscript
> > }
> 

> After rotation, do the post log messages get written to the prior
> (rotated) log or do they disappear?

Yes, after rotation the post log does get written to post.1 

> Does /var/run/mailman/mailman.pid exist and contain the master watcher's
> PID when Mailman is running?

No. /var/run/mailman/ is empty. 

> FWIW, I don't try to check if mailman is running in my postrotate
> script. I use
> 
> > postrotate
> > /usr/local/mailman/bin/mailmanctl reopen >/dev/null 2>&1 || true
> > endscript


Wonderful! I edited my postrotate the same and the post log got written to on 
schedule.

The oddity was that with the check "/var/run/mailman/mailman.pid" -- the 
subscribe log was getting written but not the post. 

/var/log/mailman/subscribe /var/log/mailman/post {
...
}

But I can sure live with that mystery and not look a gift horse in the mouth.

Thanks very much for your invaluable help Mark (yet again).
--
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: Post log not being written

[Mark Dale]

> >Today that log file has rotated ("post.1) and the new post log file was
> >not being written to -- until I restarted the qrunner again. As said,
> >no problems with mail delivery, and the other logs.

> What does your logrotate script contain?
> Does it do
> bin/mailmanctl reopen
> after rotation?


Yes. It does "reopen" for "post". 

/var/log/mailman/subscribe /var/log/mailman/post {
su root list
daily
missingok
create 0664 list list
rotate 3
compress
delaycompress
sharedscripts
postrotate
[ -f '/var/run/mailman/mailman.pid' ] && 
/usr/lib/mailman/bin/mailmanctl -q reopen || exit 0
endscript
}
--
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: extracting a lists's setting to move the list to a new domain

[Mark Dale]

> On 09/20/2020 8:35 PM Steven Jones  wrote:
> I cant find anything on extracting a list's settings, owners etc and then 
> using those to create a new list on a new domain.
> 
> Is there a simple operational command to extract and inject?


If you have privileged access you can run the following commands on your server 
to retrieve everything. Your file paths might be different so you'll need to 
adjust accordingly.

***
$ cd ~/
$ sudo -s
$ mkdir LISTNAME-files
$ cd LISTNAME-files
$ /usr/lib/mailman/bin/list_members -f  -r LISTNAME > LISTNAME.regular
$ /usr/lib/mailman/bin/list_members -f  -d LISTNAME > LISTNAME.digest
$ cp /var/lib/mailman/archives/private/LISTNAME.mbox/LISTNAME.mbox 
./LISTNAME.mbox
$ tar -czvf LISTNAME.attachments.tgz  
/var/lib/mailman/archives/private/LISTNAME/attachment
$ cp /var/lib/mailman/lists/LISTNAME/config.pck ./LISTNAME.pck
$ cd ../
$ tar -czvf LISTNAME-files.tgz LISTNAME-files
***
Copy LISTNAME-files.tgz to anywhere on the new server and unpack.
Create the new list.
***
Then for the new list, copy the config.pck into place, and also the ".mbox" and 
archive attachments.
***
Fix the URLs with: bin/withlist -l -r fix_url LISTAME -u DOMAINNAME

The lists settings and subscribers are in the config.pck so you shouldn't need 
to do any more.


/Mark
--
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: Post log not being written

[Mark Dale]

==
> > I've just noticed that the mailman/post log isn't being written to. 

==
> This is controlled by Defaults.py/mm_cfg.py settings SMTP_LOG_* which
> specify the log name and message format for these messages. The default
> settings that write to the post log are:
> 
> > # This will only be printed if there were no immediate smtp failures.
> > # Mutually exclusive with SMTP_LOG_REFUSED.
> > SMTP_LOG_SUCCESS = (
> > 'post',
> > 'post to %(listname)s from %(sender)s, size=%(size)d, 
> > message-id=%(msg_message-id)s, success')
> > 
> > # This will only be printed if there were any addresses which encountered an
> > # immediate smtp failure.  Mutually exclusive with SMTP_LOG_SUCCESS.
> > SMTP_LOG_REFUSED = (
> > 'post',
> > 'post to %(listname)s from %(sender)s, size=%(size)d, 
> > message-id=%(msg_message-id)s, %(#refused)d failures')
> 
==

I'm seeing the same in my Default.py (below) and nothing in the mm_cfg.py 
settings that would overide it.

After I posted my email to this list yesterday, I restarted the qrunner 
(mailman/bin/mailmanctl restart) and immediately the post log was getting 
written to.

Today that log file has rotated ("post.1) and the new post log file was not 
being written to -- until I restarted the qrunner again. As said, no problems 
with mail delivery, and the other logs.
 
SMTP_LOG_SUCCESS = (
'post',
'post to %(listname)s from %(sender)s, size=%(size)d, 
message-id=%(msg_message-id)s, success')

SMTP_LOG_REFUSED = (
'post',
'post to %(listname)s from %(sender)s, size=%(size)d, 
message-id=%(msg_message-id)s, %(#refused)d failures')
--
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] Post log not being written

[Mark Dale]

Hi,

I've just noticed that the mailman/post log isn't being written to. 

Mail is being delivered to the lists okay and the other log files (bounce, 
subscribe, etc) are being written okay.

The permissions and ownership look fine.

-rw-rw-r--  1 list list4297 Sep 19 09:00 bounce
-rw-rw-r--  1 list list6731 Sep 19 19:19 subscribe
-rw-rw-r--  1 list list   0 Sep 19 00:00 post

Mailman 2.1.34 (installed from source) on Debian 10/Postfix.

Any pointers on where I should be looking to fix this greatly appreciated.

/Mark
--
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: searchable private mailing lists in Mailman 2.1.20

[Mark Dale]

On 18/6/20 8:30 pm, Mark Sapiro wrote:

> There is also a FAQ article at  that
> discusses adding Namazu as a search engine for Mailman list archives.
> That doesn't cover adding a search function to the archive index pages,
> but it may provide ideas.

There's a comprehensive guide for installing Namazu (including adding
the search form to the Archive index page) at:

http://bakacsin.ki.iif.hu/~kissg/project/mailman+namazu/

"Language dependent HTML templates of Mailman. A search form is added as
done by Tom and Lindsay. Edit your templates manually as you need."
--
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/

Re: [Mailman-Users] Mailman version 2.1.16 -- Search of *private* archives?

[Mark Dale]

Hi,

It sounds like you now have it sorted with Namazu, but for what it's
worth there is an excellent guide to install Namazu "out of the box" on
Mailman 2.1.* at:

http://bakacsin.ki.iif.hu/~kissg/project/mailman+namazu/

And no issues with Private archives or incorrect URLs.

/Mark


On 25/8/19 8:07 am, Robert Heller wrote:
> At Sat, 24 Aug 2019 14:20:42 -0700 Mark Sapiro  wrote:
> 
>>
>> On 8/24/19 1:15 PM, Robert Heller wrote:
>>>
>>> OK, I have installed Namazu, which will do what I want, *BUT* pipermail.pl 
>>> is 
>>> missing from the tarball I downloaded from the Namazu website.  Where can I 
>>> get that file.  At this point, the search works, but the URI's are wrong 
>>> (local file name, not the proper mailman URL).
>>
>>
>> I can't answer directly, but see
>> .
>>
> 
> I figured out how to hack the Namazu code to incldue a "replacement" function 
> and passed it on to the re-index function.  I think that will work.  (Perl is 
> almost as bad as APL -- the only thing about Perl is that it uses "normal" 
> ASCII, but still is pretty much write-only code, like APL.)
> 
> 
--
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] archtoc and archtocnombox

[Mark Dale]

> On 4/24/19 3:15 PM, Mark Dale wrote:

>> Small archives seem to use "archtoc.html" which has the link to download
>> the full raw archive (mbox).
>>
>> Larger lists appear to use "archtocnombox.html" which is minus the link.
>>
>> Is there a threshold (filesize) somewhere that determines which gets
>> used? or am I barking up the wrong tree completely?


On 25/4/19 8:31 am, Mark Sapiro wrote:

> This is controlled by the mm_cfg setting PUBLIC_MBOX. If it is True, the
> list's index.html file is built with archtoc.html and if False, with
> archtocnombox.html.
> 
> If some lists have one and some the other it's because the PUBLIC_MBOX
> setting has been changed and those lists that reflect the prior setting
> haven't been posted to since the change.
> 

Many thanks for the clarity Mark.

/var/lib/mailman/Mailman/Defaults.py:478

# When the archive is public, should Mailman also make the raw Unix mbox
file publically available?
PUBLIC_MBOX = No
--
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] archtoc and archtocnombox

[Mark Dale]

Hi All,

Small archives seem to use "archtoc.html" which has the link to download
the full raw archive (mbox).

Larger lists appear to use "archtocnombox.html" which is minus the link.

Is there a threshold (filesize) somewhere that determines which gets
used? or am I barking up the wrong tree completely?


/etc/mailman/en/archtoc.html

You can get [more information about this list]
  or you can [download the full raw archive] ().

/etc/mailman/en/archtocnombox.html

You can get [more information about this list].

Thanks,
Mark
--
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] Restrict archives to Administrator

[Mark Dale]

> Mark Dale writes:

>  > I've posted some notes on restricting a list's archive to Administrators
>  > only. They may be of use to some folks.

From: Stephen J. Turnbull [mailto:turnbull.stephen...@u.tsukuba.ac.jp]

> Again, I'm not saying these are bad ideas, just that I want more
> information to decide if they are useful enough to add to Mailman 3.

Hi Steve,

We had a customer ask for their lists to have this option. Their lists
are used with some kind of automated entry/exit logging processes.

Once we had cobbled it together, posting the notes to the list was a
simply a case of "maybe someone else might also find this useful" - so
here it is. There's still some gas left in the tank of Mailman 2.

Mark


--
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] Restrict archives to Administrator

[Mark Dale]

Hi,

I've posted some notes on restricting a list's archive to Administrators
only. They may be of use to some folks.

It's a hack of Jim Popovitch's code which restricts archive access to
unmoderated subscribers.

Restrict archives to Administrator only (for Mailman 2.1.29)

https://www.postmark.io/mm2/archives_for_admin_only.html

Best,
Mark


--
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] Bogus mail to list from JavaMail.yahoo

[Mark Dale]

Hi All,

This may be a Postfix issue rather than a Mailman one, but the Mailman
post log (snip below) is showing some relevant info, so here goes.

This morning there was a legitimate post to a list from a subscriber
with a Gmail account.

Shortly after, there was a deluge of bogus posts (one every minute)
repeating the same email to the list purporting to come from the same
address.

The Mailman "post" logs below show the original at 13:43 with the
google.com ID, and the following bogus messages all with a yahoo.com ID

This appears to be happening to only the one list on the server.

If anyone could shed some light on this, or point me in the right
direction, it'd be much appreciated.

Regards,
Mark


Mar 06 13:43:12 2019 (21321) post to redacted-listname from
john.citi...@gmail.com, size=18763,
message-id=<0aa0c90583715...@google.com>, success

Mar 06 13:44:09 2019 (21321) post to redacted-listname from
john.citi...@gmail.com, size=16906,
message-id=<1951431589.1505.1551897769010.javamail.ya...@tardis008.cal.bf1.yahoo.com>,
success

Mar 06 13:45:09 2019 (21321) post to redacted-listname from
john.citi...@gmail.com, size=16896,
message-id=<1838256988.2441.1551897771539.javamail.ya...@tardis064.cal.bf1.yahoo.com>,
success

Mar 06 13:46:06 2019 (21321) post to redacted-listname from
john.citi...@gmail.com, size=16889,
message-id=<574641303.2211.1551897775604.javamail.ya...@tardis001.cal.bf1.yahoo.com>,
success

... and on and on ...
--
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] Spam Subscriptions

[Mark Dale]

> And what is the error in Mailman's error log.


GLOBAL_BAN_LIST = ['^[0-9a-z.]{6,}\+[0-9a-z]{4,}@gmail\.com$']

D'oh. My apologies. The error was not from the trailing '$' but 
from not having the quotes in place originally. All is now well 
(with the above).

Thanks,
Mark

2018/06/04 10:33:14 [error] 17956#17956: *4956 FastCGI sent in 
stderr: "[Mailman: low level unrecoverable exception]" while 
reading response header from upstream, client: 68.235.48.108, 
server: mailmanlists.sg, request: "GET /mailman/listinfo 
HTTP/1.1", upstream: 
"fastcgi://unix:///var/run/fcgiwrap.socket:", host: 
"www.mailmanlists.sg"
--
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] Spam Subscriptions

[Mark Dale]

> >> ^[0-9a-z.]{8,}\+[0-9a-z]{4,}@gmail\.com$
> > 
> > I'm getting errors with the above however it seems to do the job 
> > if I enclose it in quotes and remove the trailing $ - like so:
> > 
> > GLOBAL_BAN_LIST = ['^[0-9a-z.]{6,}\+[0-9a-z]{4,}@gmail\.com']

-
 
> What you have done is correct. I don't know why you would have needed to
> remove the '$'. Did you get an error and if so, what?.

I can't see why either, but with the '$' left in place, the 
Mailman Web UI displayed the error "Sorry, we hit a bug..."

-

> Also, it doesn't matter in this case because \+ and \. are not
> meaningful string metacharacters, but it never hurts to define them as
> raw strings like, e.g.,

Understood. Thanks.
 
> GLOBAL_BAN_LIST = [r'^[0-9a-z.]{8,}\+[0-9a-z]{4,}@gmail\.com$']

The 'r' that precedes the first quote - is that correct?

-

Cheers.
--
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] Spam Subscriptions

[Mark Dale]

> I use this regexp in the GLOBAL_BAN_LIST
> 
> ^[0-9a-z.]{8,}\+[0-9a-z]{4,}@gmail\.com$

I'm getting errors with the above however it seems to do the job 
if I enclose it in quotes and remove the trailing $ - like so:

GLOBAL_BAN_LIST = ['^[0-9a-z.]{6,}\+[0-9a-z]{4,}@gmail\.com']

Am I missing something?

Cheers,
Mark
--
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] Purging old archives over 7 years old

[Mark Dale]

Hi,

We've found this to be useful.

"Using Archivemail to pruning Mailman archives"

https://playingwithsid.blogspot.se/2014/03/using-archivemail-to-pruning-mailman.html


Best,
Mark

On 15/06/17 23:05, Julian H. Stacey wrote:
> Steven Jones wrote:
>> Hi,
>>
>>
>> I have a 12year old mailman server which is absorbing 650gb of expensive 
>> disk space. Is there any feature that would go through each list's archives 
>> and delete emails over say 7 years old?   (or maybe even only 3 as we do a 
>> yearly backup going back a decade).
> 
> I've no idea if mailman has own special tools for that,
> standard Unix tools can find tools that use the Unix find command, eg
>   echo "Learn find, dialects vary per Unix."
>   man find 
>   cd /usr/local/mailman/bin 
>   echo "Get an idea where to look:"
>   find . -type f | sort | xargs grep -l find | more
>   find . -type f | sort | xargs grep -l find \
>   | grep -v /archives/ \
>   | grep -v /lists/ \
>   | grep -v /logs/ \
>   | grep -v /messages/ \
>   | grep -v /templates/ \
>   | grep -v /tests/ \
>   | more
>   echo "Ignore ./cgi-bin/* binaries."
>   vi -c/find `find bin/* scripts/* -type f | xargs grep -l find`
>   echo "Also consider ./Mailman/*/*.py[c] files"
> 
> Or more simply:
> 
> cd /usr/local/mailman/archives
> find . -type f -name \*.html | more
>   ./private/pc532/index.html
>   ./private/pc532/2017q2/00.html
>   ./private/pc532/2017q2/date.html
>   ./private/pc532/2017q2/subject.html
>   ./private/pc532/2017q2/author.html
>   ./private/pc532/2017q2/thread.html
>   ./private/pc532/2017q2/01.html
>   ./private/pc532/2017q2/02.html
> 
> so eg
>   rm -rf ./private/pc532/2007*
> 
> find . -type f -name \*.html | xargs ls -l > ~/tmp/dates_to_browse
> find . -type f -name \[0-9\]\*.html
> find . -type d -name 2012q\* | more
> find . -type d -name 2012q\* | xargs rm -rf
> 
> Find is very powerful.  Read 
>   man find
> before you use find,
> use 
>   more
> before you use
>   rm
> Do a backup before anything. 
> 
> Cheers,
> Julian
> 
--
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] Looking for better servicess for mailing list

[Mark Dale]

Hi Amit,

If your group is a community service organisation (and a not-for-profit)
we'd be happy to host your lists for you at no charge.


Regards,
Mark



 MailmanLists - hosted discussion lists
 Canberra, Australia
 Tel: +61 .2 61003121
 http://www.mailmanlists.net
===

On 16/02/17 19:15, Amit Bhatt wrote:
> Hello all,
> 
> We are running two mailing lists with the host ultra.us for visually
> impaired people in India.
> Inicially ultra.us provided their support when we hired their services
> but they are not ready to respond even the tickets we have raised for
> the resolution now. Currently we are facing lot of problems and bugs
> but they are not fixing them.
> 
> I will appreciate if some other good and cost effective service
> provider can be suggested to me, so I can change the host and mailing
> list service provider for the smooth functioning of the mailing list.
> 
> Thanks,
> 
> Amit Bhatt
> --
> 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/mark%40mailmanlists.net
> 
> 
--
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] Searchable archive for mailman mailing-lists?

[Mark Dale]

Hi Fernando

For installing the Namazu search on Mailman 2.1.*, there is a good "how
to" (with a working example) at:

http://bakacsin.ki.iif.hu/~kissg/project/mailman+namazu/

We've had great success using the guide over the years. It might be
worth noting that on a recent installation on Debian Stretch I did have
to get the required Namazu packages from the Jessie repository.

Regards,
Mark





On 17/01/17 18:21, Fernando Gont wrote:
> Folks,
> 
> I was meaning to provide some option for searching our mailman mailing
> lists.
> 
> Two questions:
> 
> 1) Any open source recommendations for this?
> 
> 2) In the past, we were providing this feature by mirroring the
> mailing-lists with google-groups, and thus using the googlegroups
> interface for searching our lists. However, it seems such option is gone
> from googlegroups. Has anyone been able to do this recently?
> 
> Thanks!
> 
> Best regards,
> 
--
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] Mailman Hosting

[Mark Dale]

Thanks for the suggestion on the mailop list Jim.

Verizon began accepting mail again for lists on the European server 
about 6 hours ago.


No light was shed as to why or what changed their view. Not only Verizon 
but AT as well, at around the same time - a little puzzle that's 
probably best left alone.


It may be that their default position is to block all list mail 
regardless - until they get swamped with complaints.


I've subscribed to the mailop list as you suggest, and if I learn 
anything relevant to this issue I'll post it back here.


Thanks,
Mark




 MailmanLists - hosted discussion lists
 Canberra, Australia
 Tel: +61 .2 61003121
 http://www.mailmanlists.net
===

On 22/12/16 16:15, Jim Popovitch wrote:

On Wed, Dec 21, 2016 at 11:42 PM, Mark Dale <m...@mailmanlists.net> wrote:

...

All the DNS records (inc SPF, DKIM) are in place, the server is on no RBLs,
con-current connections to the recieving mail servers is set at 2 in
Postfix. In short, all the right boxes are ticked as far as we can see.

Point noted about the time needed to build a good IP reputation. In light of
that, we moved the list to our old established server in Europe. It has a
SenderScore of 99, and of course all the same boxes are ticked. Verizon
still rejected list mail.

...




A good place to start is on the mailop list, explain your company and
sign-up practices/filtering, etc.  Be open and ask for specific reps
to contact you offline if necessary.  You may get some awesome help,
although this close to the holidays your message may not hit the right
people until next year.

https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop


--
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] Mailman Hosting

[Mark Dale]

Hi Odhiambo and Steve,

I'm one of the co-owners of MailmanLists.net that is mentioned in this post.

As Odhiambo said, we've recently moved one of the servers that hosted 
Odhiambo's list. This involved a change of IP address, and at the same 
time the problem with Verizon kicked into play.


All the DNS records (inc SPF, DKIM) are in place, the server is on no 
RBLs, con-current connections to the recieving mail servers is set at 2 
in Postfix. In short, all the right boxes are ticked as far as we can see.


Point noted about the time needed to build a good IP reputation. In 
light of that, we moved the list to our old established server in 
Europe. It has a SenderScore of 99, and of course all the same boxes are 
ticked. Verizon still rejected list mail.


As they have been somewhat resistant to address the issue in any real 
way, I do agree with Steven that they may listen to loud complaints from 
their own customers. However, that doesn't help Odhiambo right now.


We haven't brushed Odhiambo off, but rather have worked with him on this 
problem trying to fix it. However, right now all our best intents are 
not helping - so any suggestions for a workaround on this would be truly 
appreciated.


His list has around 400 members, with 70 or so being Verizon customers.


Regards,
Mark


 MailmanLists - hosted discussion lists
 Canberra, Australia
 Tel: +61 .2 61003121
 http://www.mailmanlists.net
===

On 22/12/16 15:18, Stephen J. Turnbull wrote:

Odhiambo Washington writes:

 > mails, but majority of the subscribers are with Verizon/ATT and that has
 > really affected one list that I have so I need to change.

Do you have a reason to think a change will help?  As you say, they're
notorious for blocking list emails.  I doubt their criteria are so
heavily weighted toward which hosting service you use as to make a big
difference here.  Rather (as others have suggested) probably any
change that involves significant flows of duplicate message-ids from a
new source will get blocked.  Other than that negative effect,
reputation is something that you build over time.  Trying to buy it in
an instant is not a good bet.

The first thing would be to check that your IPs aren't on any of the
RBLs.  Seems unlikely since you don't have problems with other
providers, but Verizon may have poor taste in RBLs (as they do in so
many other ways).  If you're on one, you'll be better off if you can
get off rather than moving.

Do you know and conform to their acceptable use policies?  Have you
talked to their support staff?  They're the only ones who know what
criteria they actually use to decide what to block.  I wouldn't be
surprised if they just brush you off, but that's the second thing you
should try.

Can you get your subscribers to complain?  That often has more effect
than complaints from a third party.

Steve

--
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/mark%40mailmanlists.net



--
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] list_members when listname has a period

[Mark Dale]

Thanks Mark and Steve.

It is indeed as you said - the real listname was not the advertised 
listname.


The list has now been moved, named as it should be, and all is well.

Regards,
Mark





On 22/11/16 13:12, Mark Sapiro wrote:



$PATH/bin/list_members -f acme_widgets (works fine)

$PATH/bin/list_members -f acme.widgets (gets ignored)

Any clues from anyone would be greatly appreciated.



I just verified that it works for me.

As Steve suggests, if this is cPanel or possibly some other virtual
hosting patched Mailman, the name may include a domain.

I.e., if it's cPanel, the listname could be something like
acme.widgets_virt.domain.

What is the contents if the $PATH/lists/ directory?


--
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] list_members when listname has a period

[Mark Dale]

Hi,

I'm using version 2.1.23

Regards,
Mark

On 22/11/16 03:33, mailman-admin wrote:



Works for me.
Which version of mailman are you using?


Kind regards,
Christian Mack

--
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] list_members when listname has a period

[Mark Dale]

Hi,

If a list's name has a period in it, the "bin/list_members" doesn't seem 
to like it. For example:


$PATH/bin/list_members -f acme_widgets (works fine)

$PATH/bin/list_members -f acme.widgets (gets ignored)

I've tried escaping the period, wrapping the name in quotes, and I'm not 
seeing anything in the bin file - list_members - as an obvious place to 
hack.


Any clues from anyone would be greatly appreciated.

Thanks,
Mark



--
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] Attachment URL in the archive is mangled.

[Mark Dale]

Mark Sapiro wrote:

There is probably some incompatibility between the 2.1.9 Scrubber.py
and the rest of your installation that threw an exception on mail with
attachments. Check Mailman's error log and shunt queue.


Yes, it was a shot in the dark replacing 2.1.5 Srubber with a 2.1.9
There are a number of errors in the logfile  e.g.

Nov 23 03:05:27 2008 (1800) SHUNTING: 
1227409525.3357961+31e6f6226a3b5cbc4a8dadaf3f4dde064947822e


Nov 23 03:07:07 2008 (1800) uncaught archiver exception at filepos: 0

Nov 23 03:07:07 2008 (1800) Uncaught runner exception: 'module' object 
has no attribute 'SCRUBBER_USE_ATTACHMENT_FILENAME_EXTENSION'



I have been able to duplicate the problem with the 2.1.5 version of
Scrubber.py. I'll try to come up with a simple patch that you can
apply to fix it. 


That would be brilliant!


The issue is as I thought. The scrubbed message is quoted-printable
encoded, but the Content-Transfer-Encoding: header says 8bit and not
quoted-printable so the message is not properly decoded for the
archive.


Yes. Grant Taylor mentioned this. He made reference to format=flow being 
the go, rather that quoted=printable. I confess it's something I don't 
understand. I had thought f=f was something the email client decided.



In my case, I could see other symptoms of this besides just the URL of
the scrubbed attachment. For example, the --  separator before my
signature was rendered as -- = followed by a blank line.


Yes. I saw that also, I was pretending not to. ;-)

cheers
Mark Dale


--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

Re: [Mailman-Users] Attachment URL in the archive is mangled.

[Mark Dale]

Hi Mark

Your patch has worked a treat. Thank you very much for your patience and
generosity. Many of us would be a long way up the proverbial creek if it
weren't for your support.

In summary, for those interested:

Using Mailman 2.1.5 - in the Archives, the URL to attachments was being
malformed by it getting wrapped and an = sign inserted at the line break.

This was fixed (albeit lightly tested so far) by replacing, in the
Scrubber.py file, as follows:


OLD CODE

# Now join the text and set the payload
sep = _('-- next part --\n')
del msg['content-type']
msg.set_payload(sep.join(text), charset)
del msg['content-transfer-encoding']
msg.add_header('Content-Transfer-Encoding', '8bit')
return msg


NEW CODE

# Now join the text and set the payload
sep = _('-- next part --\n')
del msg['content-type']
del msg['content-transfer-encoding']
msg.set_payload(sep.join(text), charset)
return msg


cheers
Mark



Mark Sapiro wrote:
 Mark Sapiro wrote:
 I have been able to duplicate the problem with the 2.1.5 version of
 Scrubber.py. I'll try to come up with a simple patch that you can
 apply to fix it. It is fixed in recent Scrubber.py versions.
 
 
 I think you'd be better off upgrading your Mailman, but if you want to
 try a patch to the 2.1.5 Scrubber.py, I think this should do it. It is
 only lightly tested, but I think it's OK.
 
 --- Scrubber.py 2008-11-22 20:21:38.37500 -0800
 +++ Scrubberx.py2008-11-22 20:54:47.25000 -0800
 @@ -326,9 +326,8 @@
  # Now join the text and set the payload
  sep = _('-- next part --\n')
  del msg['content-type']
 -msg.set_payload(sep.join(text), charset)
  del msg['content-transfer-encoding']
 -msg.add_header('Content-Transfer-Encoding', '8bit')
 +msg.set_payload(sep.join(text), charset)
  return msg




--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

Re: [Mailman-Users] Attachment URL in the archive is mangled.

[Mark Dale]

Hi Mark
(Apologies for late reply, have been away)

Yes, I sure did. And also rebooted the server (and checked that the
qrunner was starting up on boot)
I also noticed that with the new Scrubber.py, emails with attachments
were neither delivered nor archived. Emails without attachments were okay.

Once I returned the original Scrubber.py and restarted, emails with
attachments got delivered and also sent to archive. (Broken link to
attachment still in archived message though).

Mark Dale



Mark Sapiro wrote:
 Did you remember to restart Mailman after replacing Scrubber.py?
 





--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

Re: [Mailman-Users] Attachment URL in the archive is mangled.

[Mark Dale]

 There have been many changes in Scrubber.py (the module which does
 this) since 2.1.5. I will look into it, but I don't know if I will be
 able to duplicate the problem.

For what it's worth Mark, I copied a Scrubber.py from a Version 2.19 on
the wild chance that it might do some good - but as was to be expected,
no magic occurred.

Here's hoping you do find a way to duplicate the problem. Upgrading this
installation would be like changing a flat tyre on a moving car.


 If it is a Word.doc that gets attached, no URL appears at all in the
 archive, not is there even a scrubbed message. Also, Word.doc files
 don't even arrive with the email.


 Because these attachments are removed by content filtering before the
 message is archived and delivered.

Understood. Thanks.



cheers
Mark Dale
-- 




--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

[Mailman-Users] Attachment URL in the archive is mangled.

[Mark Dale]

Hi All

In the archives, the URL to attachments is getting mangled.

Somehow an = gets inserted into the URL (see snippet below), and the
links returns Private archive file not found.

If I remove the = from the URL, all is well.

Can anyone shed any light on this, and how I might correct things so the
URL appears correctly (without the =) in the archive?

BTW. The attachments are travelling okay with the messages. It's just in
the archive that there is a problem.

cheers
Mark Dale


-- next part --
A non-text attachment was scrubbed...
Name: test.pdf
Type: application/pdf
Size: 5929 bytes
Desc: not available
Url :
http://myDomain.com/cgi-bin/mailman/private/myListname/attachments/200=
81119/d1fa80ed/test.pdf
-

But this works:

http://myDomain.com/cgi-bin/mailman/private/myListname/attachments/20081119/d1fa80ed/test.pdf








--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

Re: [Mailman-Users] Attachment URL in the archive is mangled.

[Mark Dale]

Hi Mark

In answer to your questions ...

I am using Mailman version: 2.1.5

Subscribers can choose digest if they want.

The link is broken in the digest messages, just like in the archive.

The broken link happens for every PDF file, even though the PDF arrives
with the email. (Doesn't arrive in the digest, just a broken link)

The link is almost okay, it's just the = sign that gets inserted that
messes things up.

If it is a Word.doc that gets attached, no URL appears at all in the
archive, not is there even a scrubbed message. Also, Word.doc files
don't even arrive with the email.

cheers

MArk Dale


Mark Sapiro wrote:
 Mark Dale wrote:
 In the archives, the URL to attachments is getting mangled.

 Somehow an = gets inserted into the URL (see snippet below), and the
 links returns Private archive file not found.

 If I remove the = from the URL, all is well.

 Can anyone shed any light on this, and how I might correct things so the
 URL appears correctly (without the =) in the archive?

 BTW. The attachments are travelling okay with the messages. It's just in
 the archive that there is a problem.

 cheers
 Mark Dale


 -- next part --
 A non-text attachment was scrubbed...
 Name: test.pdf
 Type: application/pdf
 Size: 5929 bytes
 Desc: not available
 Url :
 http://myDomain.com/cgi-bin/mailman/private/myListname/attachments/200=
 81119/d1fa80ed/test.pdf
 
 
 This appears to be a problem with encoding/decoding of quoted-printable.
 
 What Mailman version is this?
 
 If Mailman is recent enough to have it, is Non-digest options -
 scrub-nondigest Yes or No? (your The attachments are travelling okay
 with the messages implies no, but just checking.)
 
 Is your list digestable and if so, are the links in the plain digest
 OK or are they like the archive?
 
 Does this happen with every attachment, or only in some messages?
 

-- 


--
Mark Dale
GeniusMoon
Tel: 02 6100 3131
Fax: 02 6103 9130
Mob: 0403 831 748
email: [EMAIL PROTECTED]
http://www.geniusmoon.com.au
--



--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

[Mailman-Users] Bug reported when creating a new list from webpage

[Mark Dale]

Hi All

Can anyone shed any light on this error I get when creating a new list
from the webpage. (I can create lists okay from the newlist command)

*** Displayed on the webpage ***
-

Bug in Mailman version 2.1.9

We're sorry, we hit a bug!

Please inform the webmaster for this site of this problem. Printing of
traceback and other system information has been explicitly inhibited,
but the webmaster can find this information in the Mailman error logs.


*** extract from the error log ***
--

Jul 01 05:27:46 2008 (14663) command failed: /usr/sbin/postmap
/var/lib/mailman/data/virtual-mailman (status: 1, Operation not permitted)
Jul 01 05:27:46 2008 admin(14663):

admin(14663): [- Mailman Version: 2.1.9 -]
admin(14663): [- Traceback --]
admin(14663): Traceback (most recent call last):
admin(14663):   File /var/lib/mailman/scripts/driver, line 110, in
run_main
admin(14663): main()
admin(14663):   File /usr/lib/mailman/Mailman/Cgi/create.py, line 56,
in main
admin(14663): process_request(doc, cgidata)
admin(14663):   File /usr/lib/mailman/Mailman/Cgi/create.py, line 238,
in process_request
admin(14663): sys.modules[modname].create(mlist, cgi=1)
admin(14663):   File /usr/lib/mailman/Mailman/MTA/Postfix.py, line
232, in create
admin(14663): _update_maps()
admin(14663):   File /usr/lib/mailman/Mailman/MTA/Postfix.py, line 60,
in _update_maps
admin(14663): raise RuntimeError, msg % (vcmd, status, errstr)
admin(14663): RuntimeError: command failed: /usr/sbin/postmap
/var/lib/mailman/data/virtual-mailman (status: 1, Operation not permitted)
admin(14663): [- Python Information -]
admin(14663): sys.version =   2.5.2 (r252:60911, Apr 21 2008, 11:17:30)
[GCC 4.2.3 (Ubuntu 4.2.3-2ubuntu7)]
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

Re: [Mailman-Users] Bug reported when creating a new list from webpage

[Mark Dale]

That's great Mark, many thanks.

Just recapping for anyone else's interest.
--

After installing Mailman, when first attemping to create a new list
using the webpage - it returned a You don't have permission.

(Creating a new list from the terminal was working okay)

This was fixed by running: sudo mmsitepass -c myNewPassword
and restarting: sudo /etc/init.d/mailman restart

Then, when trying to create a new list from the webpage, it returned an
error Bug in Mailman ...

This was fixed by settig correct permissions and group/owner on the
files as Mark explained.


% /var/lib/mailman/data: ll
total 76
drwxrwsr-x 2 root list  4096 Jul  1 06:19 .
drwxrwsr-x 9 root list  4096 Jun 30 04:33 ..
-rw-rw 1 root list  1865 Jul  1 06:19 aliases
-rw-rw-r-- 1 list list 12288 Jul  1 06:19 aliases.db
-rw-rw 1 list list  4719 Jul  1 06:06 bounce-events-14733.pck
-rw-r- 1 root list41 Jul  1 05:26 creator.pw
-rw-rw-r-- 1 list list  1620 Jun 30 05:01 heldmsg-testlist-1.pck
-rw-rw-r-- 1 root list10 Jun 30 04:33 last_mailman_version
-rw-r--r-- 1 root list 14114 Mar  7 05:22 sitelist.cfg
-rw-rw 1 www-data list  1314 Jul  1 06:19 virtual-mailman
-rw-rw 1 list list 12288 Jul  1 06:19 virtual-mailman.db
% /var/lib/mailman/data: sudo /etc/init.d/mailman restart

--





Mark Sapiro wrote:
 Mark Dale wrote:
 Can anyone shed any light on this error I get when creating a new list
from the webpage. (I can create lists okay from the newlist command)
 *** extract from the error log ***
 --

 Jul 01 05:27:46 2008 (14663) command failed: /usr/sbin/postmap
 /var/lib/mailman/data/virtual-mailman (status: 1, Operation not permitted)
 Jul 01 05:27:46 2008 admin(14663):
 
 admin(14663): [- Mailman Version: 2.1.9 -]
 admin(14663): [- Traceback --]
 admin(14663): Traceback (most recent call last):
 admin(14663):   File /var/lib/mailman/scripts/driver, line 110, in
 run_main
 admin(14663): main()
 admin(14663):   File /usr/lib/mailman/Mailman/Cgi/create.py, line 56,
 in main
 admin(14663): process_request(doc, cgidata)
 admin(14663):   File /usr/lib/mailman/Mailman/Cgi/create.py, line 238,
 in process_request
 admin(14663): sys.modules[modname].create(mlist, cgi=1)
 admin(14663):   File /usr/lib/mailman/Mailman/MTA/Postfix.py, line
 232, in create
 admin(14663): _update_maps()
 admin(14663):   File /usr/lib/mailman/Mailman/MTA/Postfix.py, line 60,
 in _update_maps
 admin(14663): raise RuntimeError, msg % (vcmd, status, errstr)
 admin(14663): RuntimeError: command failed: /usr/sbin/postmap
 /var/lib/mailman/data/virtual-mailman (status: 1, Operation not permitted)
 
 
 The issue is with ownership and/or permissions of virtual-mailman*
 
 When running create from the web, the process is running as the web
 server user and the mailman group because the create wrapper is group
 mailman and SETGID.
 
 When this user:group runs postmap, it fails as above. Permissions and
 ownership of the aliases* and virtual-mailman* files should be
 
 -rw-rw 1 rootmailman6308 Jun 21 12:51 aliases
 -rw-rw 1 mailman mailman   12288 Jun 21 12:51 aliases.db
 -rw-rw 1 apache  mailman8051 Jun 21 12:51 virtual-mailman
 -rw-rw 1 mailman mailman   12288 Jun 21 12:51 virtual-mailman.db
 
 Note that all files are group writable and group mailman and the .db
 files (particularly aliases.db) are also owned by mailman. This latter
 controls the user (and that user's default group) that Postfix uses to
 run the pipes.
 
 The owner of aliases and virtual-mailman is not important. It may be
 root, apache or something else depending on who last created a list.
 
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

Re: [Mailman-Users] Incorrect link on empty archive page

[Mark Dale]

Yes, the %(listname)s bit is fine when there is something in the 
archive. It's weird that it gets malformed (i.e the missing slash) when 
the archive is empty.

I tried some edits on emptyarchive.html file and restarted Mailman, 
but these edits didn't show up - so does that mean the empty arhive page 
is coming from somewhere other than emptyarchive.html?

cheers
Mark Dale


Barry Finkel wrote:

  Mark Sapiro reponded recently to one of my postings that the archive
  page is static.  If you post something to the list, then the archive
  page will be rebuilt and will have the proper hyperlinks.  I followed
  Mark's advice, and my hyperlinks were corrected.  Why the hyperlink is
  bad I do not know.  In my cases, it was due to different
 
   DEFAULT_URL_PATTERN =
 
  values when I was initially installing Mailman on my test system.
  --
  Barry S. Finkel



 Mark Dale [EMAIL PROTECTED] wrote:
 
 On the Archives page, when the archives are empty, Mailman displays the 
 following message (which is correct).

 No messages have been posted to this list yet, so the archives are 
 currently empty. You can get more information about this list.


 However, there is an error with the more info link -  a slash is 
 missing between mailman and listinfo in the link, and of course I 
 get  a Not found reply.

 Not Found
 The requested URL .../cgi-bin/mailmanlistinfo/gen... was not found on 
 this server.

 I had a look at emptyarchive.html and it looks fine. The 
 %(listinfo)s works on other pages.


 --- snip from /etc/mailman/en/emptyarchive.html

 h1The %(listname)s Archives /h1
 p
 No messages have been posted to this list yet, so the archives are
 currently empty.  You can get a href=%(listinfo)smore information
 about this list/a.

 --- end snip






--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp

[Mailman-Users] Incorrect link on empty archive page

[Mark Dale]

On the Archives page, when the archives are empty, Mailman displays the 
following message (which is correct).

No messages have been posted to this list yet, so the archives are 
currently empty. You can get more information about this list.


However, there is an error with the more info link -  a slash is 
missing between mailman and listinfo in the link, and of course I 
get  a Not found reply.

Not Found
The requested URL .../cgi-bin/mailmanlistinfo/gen... was not found on 
this server.

I had a look at emptyarchive.html and it looks fine. The 
%(listinfo)s works on other pages.


--- snip from /etc/mailman/en/emptyarchive.html

h1The %(listname)s Archives /h1
p
No messages have been posted to this list yet, so the archives are
currently empty.  You can get a href=%(listinfo)smore information
about this list/a.

--- end snip




Any clues from anyone would be greatly appreciated.

cheers
Mark Dale





--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp

[Mailman-Users] Changing URLS in a py file

[Mark Dale]

Hello Mailman Users

In the email that gets sent to new subscribers, there is a message like 
the one below:

+-+

Welcome to the [EMAIL PROTECTED] mailing list!

General information about the mailing list is at:

http://geniusmoon.com.au/cgi-bin/mailman/listinfo/pcst

+-+

Is it possible to change those URLs in one of the .py files somewhere?

I'd like it to show http://pcst.geniusmoon.com.au;  instead, which 
would have a redirect (that I create manually) that sends the user to 
the above URL.

I'm thinking that it would be a matter of changing what wraps around the 
variables - domain and list name.

http://$DOMAIN/cgi-bin/mailman/listinfo/$LISTNAME
to
http://$LISTNAME.$DOMAIN


Any clues greatly appreciated.

regards
Mark Dale




  --
 Mark Dale

 phone: 02  6112 8632
mobile: 0403 831 748
 email: [EMAIL PROTECTED]

  --



--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp

Re: [Mailman-Users] Admin access for list creator

[Mark Dale]

Thanks. sudo mmsitepass did the trick.

regards
Mark Dale

Brad Knowles wrote:
 The site admin password gives you full web admin access, at least as far 
 as Mailman goes. You can access any list you want -- this is the Mailman 
 equivalent of root password, and should be treated with great care.
 
 --Brad Knowles [EMAIL PROTECTED]
 
 Sent from my iPhone
 
 On Aug 2, 2007, at 12:45 AM, Mark Dale [EMAIL PROTECTED] wrote:
 

 Hello Mailman Users

 Is there a way for a list-creator to access the admin section of
 different lists?

 My password allows me to create lists, but not access the admin section
 of various lists whose administrators have their own passwords.

 Thanks in advance for any clues.

 regards
 Mark Dale



  --
 Mark Dale

 phone: 02  6112 8632
mobile: 0403 831 748
 email: [EMAIL PROTECTED]

  --



 --
 Mailman-Users mailing list
 Mailman-Users@python.org
 http://mail.python.org/mailman/listinfo/mailman-users
 Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
 Searchable Archives: 
 http://www.mail-archive.com/mailman-users%40python.org/
 Unsubscribe: 
 http://mail.python.org/mailman/options/mailman-users/brad%40shub-internet.org
  


 Security Policy: 
 http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
 
 
 

-- 



  --
 Mark Dale

 phone: 02  6112 8632
mobile: 0403 831 748
 email: [EMAIL PROTECTED]

  --



--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp

[Mailman-Users] Admin access for list creator

[Mark Dale]

Hello Mailman Users

Is there a way for a list-creator to access the admin section of 
different lists?

My password allows me to create lists, but not access the admin section 
of various lists whose administrators have their own passwords.

Thanks in advance for any clues.

regards
Mark Dale



  --
 Mark Dale

 phone: 02  6112 8632
mobile: 0403 831 748
 email: [EMAIL PROTECTED]

  --



--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp