[Mailman-Users] Mailman 3 The Definitive Mailman Suite - Download error

[Henrik Rasmussen]

Is this list the correct place for Mailman 3 questions?

I was in the progress of installing the Mailman3-bundler as it got obsolete. As 
a consequence the old Mailman-bundler documentation was changed to refer to 
http://docs.mailman3.org/en/latest/devsetup.html "The Definitive Mailman Suite 
Development Setup Guide". I am now starting over.

Both in the Mailman Suite Setup Guide section "Set up and run Mailman Core" 
http://docs.mailman3.org/en/latest/devsetup.html#set-up-and-run-mailman-core , 
and the Mailman Core doc at 
http://mailman.readthedocs.io/en/release-3.0/src/mailman/docs/WebUIin5.html#gnu-mailman-3
 the code is supposed to be downloaded using the command "git clone 
g...@gitlab.com:mailman/mailman.git", but I get a Permission Denied

  (venv-3.5) [mailman@lstapp01pl ~]$ git clone 
g...@gitlab.com:mailman/mailman.git
  Cloning into 'mailman'...
  The authenticity of host 'gitlab.com ()' can't 
be established.
  RSA key fingerprint is b6:03:0e:39:97:9e:d0:e7:24:ce:a3:77:3e:01:42:09.
  No matching host key fingerprint found in DNS.
  Are you sure you want to continue connecting (yes/no)? yes
  Warning: Permanently added 'gitlab.com' (RSA) to the list of known hosts.
  Permission denied (publickey).
  fatal: Could not read from remote repository.
  
  Please make sure you have the correct access rights
  and the repository exists.

How should I download the Mailman core?

Henrik Rasmussen
--
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] Understanding the flow of outgoing mails

[Henrik Rasmussen]

> On 10/14/2016 05:05 PM, Mark Sapiro wrote:
> So these are messages that were originally held (as administrivia or ?) and 
> "approved" by a moderator.

Correct. Moderator mistake.

Regarding Mailman keep posting messages to the MTA despite the out directory 
had been emptied, it appeared that the qrunner was still active even after 
running mailmanctl stop (and mailmanctl -s stop). Killing the qrunner by kill 
-9 only spawned a new qrunner. I had to kill -9 the mailmanctl process too, to 
make Mailman stop posting mails to the MTA.

Problem solved. Now I just have to find the "Unsubscribe!" mails, before 
re-moving the others back into the out directory.

Thank you for the explaination.

Henrik
--
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] Understanding the flow of outgoing mails

[Henrik Rasmussen]

I am trying to understand the Mailman mailflow and I am aware that stopping a 
mail from being distributed is not a trivial task. I've looked around and found 
this*) ,but it doesn't really explain the problem I am facing.

By accident, a list admin released a bunch of mail-replies to the list-address 
from people wanting to unsubscribe. The list contains 9000+ members.

To quickly work around the problem, I set a filter in Postfix rejecting all 
mails containing the particular subject and moved all outgoing mails from 
/var/spool/mailman/out to out.org, and thought I was home safe, but it seems 
that the list keeps putting mails with subject Unsubscribe in the out directory.

Does Mailman have another queue that I need to empty or filter out?

*) https://mail.python.org/pipermail/mailman-users/2014-September/077857.html

Henrik Rasmussen
--
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] Personalised mails, content very depending on mail client

[Henrik Rasmussen]

Thank you. 

According to the article paragraph "Patching Mailman to solve this problem", a 
user found a solution to the problem in version 2.1.5, but would Mailman 3 
handle this in a better way to work around the problem with some MUAs? Would 
upgrading be a better option to solve this?

Med venlig hilsen
 
Henrik Rasmussen
Systemadministrator, Core Services
 
KØBENHAVNS UNIVERSITET
Koncern-it, Drift & Support, Infrastruktur
Nørregade 10, postboks 2177
1017 København K

Tel: 35322626
Dir 35322704
Fax 35322707
Email: h...@adm.ku.dk
Web: it.ku.dk



Har du brug for hjælp eller har spørgsmål af enten faglig og teknisk karakter, 
er du velkommen til at hendende dig til Servicedesk ved at oprette en sag i 
KUnet’s selvbetjeningssystem: "KUnet → Selvbetjening → It-service → Min 
Servicedesk → Opret Sag", eller ringe til Servicedesk på telefon 35 32 27 00. 
Du er også velkommen til at sende en mail til it-serv...@adm.ku.dk. KUnet’s 
selvbetjening findes på adressen http://sd.ku.dk.

 



-Oprindelig meddelelse-
Fra: Mailman-Users [mailto:mailman-users-bounces+her=adm.ku...@python.org] På 
vegne af Mark Sapiro
Sendt: 5. oktober 2016 06:19
Til: mailman-users@python.org
Emne: Re: [Mailman-Users] Personalised mails, content very depending on mail 
client

On 10/03/2016 07:06 AM, Henrik Rasmussen wrote:
> 
> Is there something I, as site admin, or the list-admins can do, to get 
> personalized HTML mails, even to Outlook users?


You can set Non-digest options -> personalize to Full Personalization
which will cause delivered non-digest messages to be addressed To: the
recipient, and not try to use msg_header for this purpose.

As far as brain dead MUAs not properly rendering multipart messages with
msg_header and or msg_footer added, see <https://wiki.list.org/x/4030707>.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/her%40adm.ku.dk
--
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] Personalised mails, content very depending on mail client

[Henrik Rasmussen]

As I am testing personalized mails from Mailman (2.1.12) I was wondering why 
various email clients display the content different.


* If I send an HTML mail containing only text, both Gmail and Outlook 
includes personalization in msg_header "Hello %(user_name)s . This is a test"

* If I send an HTML mail containing an image, Gmail shows "Hello 
[member's name]. This is a test" on top and the rest of the mail, including 
image, but Outlook only show the e-mail (including the image), NOT the 
msg_header not msg_footer.

* If I use Outlook to email received on Gmail, using IMAP connection, 
"Hello [member's name]. This is a test" is displayed at the top of the received 
mail, but the content from the sender and the image is attached.

My content filtering -> pass_mime_types are
multipart/mixed
multipart/alternative
text/plain
text/html

but pass_mime_types shouldn't affect the mail as content filtering -> 
filter_content if off. Also collapse_alternatives or convert_html_to_plaintext 
doesn't change a thing (as content filtering -> filter_content if off).

Is there something I, as site admin, or the list-admins can do, to get 
personalized HTML mails, even to Outlook users?

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

[Mailman-Users] What is the difference between welcome.msg and subscribeack.txt

[Henrik Rasmussen]

The welcome message that is sent to new subscribers (provided that "General 
Options -> Send_welcome_msg" is set to Yes) comes from the text file 
/var/lib/mailman/lists/LISTNAME/en/subscribeack.txt. If this file includes 
%(welcome)s, the information from the field "General Options -> welcome_msg" is 
also included.

Both can be edited by the list admin from the admin webinterface in General 
Options -> welcome_msg and "HTML Page Editing" -> "Welcome email text file", 
respectively.

What is the difference between the welcome_msg text box and the 
subscribeack.txt and why would you, as list admin, edit one over the other?

Yours faithfully

Henrik Rasmussen
--
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] No confirmation e-mails even “Receive acknowledgement mail when you send mail to the list?” has been set to “Yes”

[Henrik Rasmussen]

A list administrator asked me whether it is possible for the sender to receive 
an email confirmation when he’s mail has been approved by the list 
administrator or moderator.

I found some documentation on how to achieve 
this<http://www.list.org/mailman-member/node24.html>*) and I tried it on my 
test list, which have two members: My corporate mail and my private Gmail 
account. My corporate e-mail is owner if the list, both are subscribed to the 
list as moderated member, and both members have set “Receive acknowledgement 
mail when you send mail to the list?” to “Yes” at 
http://mailman.foo/roster/mylist.

But I do not seem to receive any confirmation e-mails to any of the e-mail 
addresses, once I have approved the mails and they have been sent to the 
members, neither last Friday nor today.

I am using Mailman 2.1.12

This is logs from today:

vette
Feb 15 09:12:19 2016 (2440) Mylist post from corporatem...@example.com held, 
message-id=<6DCC3E5DA06FE346B4DE4876C4F2713D01668845EA@mymailser...@foo.bar>: 
Post to moderated list
Feb 15 09:17:01 2016 (26733) held message approved, message-id: 
<6DCC3E5DA06FE346B4DE4876C4F2713D01668845EA@mymailser...@foo.bar>
Feb 15 09:20:40 2016 (2440) Mylist post from privatem...@gmail.com held, 
message-id=:
 Post to moderated list
Feb 15 09:23:07 2016 (27926) held message approved, message-id: 
CAGfPFBwYO-fE-fB8S4nCoAF1j6ztAS9vbcu9-UbO131dsmsu=g...@mail.gmail.com<mailto:CAGfPFBwYO-fE-fB8S4nCoAF1j6ztAS9vbcu9-UbO131dsmsu=g...@mail.gmail.com>

smtp
Feb 15 09:12:21 2016 (2442)  
smtp to mylist for 1 recips, completed in 0.093 seconds
Feb 15 09:12:22 2016 (2442)  
smtp to mylist for 1 recips, completed in 0.089 seconds
Feb 15 09:17:02 2016 (2442) 
<6DCC3E5DA06FE346B4DE4876C4F2713D01668845EA@mymailser...@foo.bar> smtp to 
mylist for 1 recips, completed in 0.113 seconds
Feb 15 09:20:41 2016 (2442)  
smtp to mylist for 1 recips, completed in 0.089 seconds
Feb 15 09:20:41 2016 (2442)  
smtp to mylist for 1 recips, completed in 0.091 seconds
Feb 15 09:20:42 2016 (2442)  
smtp to mylist for 1 recips, completed in 0.089 seconds
Feb 15 09:23:09 2016 (2442) 
 smtp to 
mylist for 1 recips, completed in 0.108 seconds

post
Feb 15 09:17:02 2016 (2440) post to mylist from Henrik Rasmussen 
 anonymized
Feb 15 09:17:02 2016 (2442) post to mylist from myl...@mailman.foo, size=12028, 
message-id=<6DCC3E5DA06FE346B4DE4876C4F2713D01668845EA@mymailser...@foo.bar>, 
success
Feb 15 09:23:08 2016 (2440) post to mylist from Henrik Rasmussen 
 anonymized
Feb 15 09:23:09 2016 (2442) post to mylist from myl...@mailman.foo, size=4122, 
message-id=,
 success

*) http://www.list.org/mailman-member/node24.html

What may I have missed?

/Henrik Rasmussen

--
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] Part of moderated mails postponed to later digests

[Henrik Rasmussen]

> This is the first time (I think) you mentioned 'posted to the list'
This may be something with lost in translation. What I meant by "posted to the 
list" is "forwarded to the members" after approval. 

> Are the messages missing from the digest not posted to the list at all until 
> the next week? I.e. are they not in the list archives and not delivered to 
> any non-digest members?
There are only a few non-digest members and the list admin is not aware whether 
they receive the mails or not.

> If in fact the missing messages don't appear in the archive until the next 
> week, this is a different issue which has nothing to do with digests per se.
I will look closely at that, and get info from the list admin on when he 
approves mails.

>> if you don't want digests triggered on size
> The list admin doesn't need digests sent according to size so a 
> digest_size_threshhold = 1 should be fine. The moderator wants to have 
> the mails included in a digest the next noon after approving the mails.

> Are the messages which are sent, sent in an immediate digest at the time of 
> approval or just the next noon?
> If the former, that digest is triggered on size. If the latter, those are the 
> only messages that actually got approved at that time.
Next noon.

> What does the vette log say about the messages that don't appear in a digest 
> until the following week? Do they show as approved at the same time as the 
> others that are in the first digest or not until later.
I am still trying to figure that out, as I still need to know exactly when the 
list admin has approved messages. The vette log shows a lot of  Refused posting 
labeled with the list name, but all the held message approved messages does not 
contain information on which list the message was approved, so I can't use the 
vette log to determine when messages on the list was approved.

But I wonder why the smtp log contains so many entries postings to exactly 1209 
recipients on the list, even the list has 1222 normal members and 6493 digest 
members. Why only 6 times 1209. And are the 1209 digest members while the 6 
recips could be regular members or something?

   /var/log/mailman/smtp Nov 09 09 06 44 2015 (16804) 
 smtp to LISTNAME for 1 
recips, completed in 0.098 seconds
   /var/log/mailman/smtp Nov 09 09 06 45 2015 (16804) 
 smtp to LISTNAME for 6 
recips, completed in 0.200 seconds
   /var/log/mailman/smtp Nov 09 09 06 45 2015 (16804) 
 smtp to LISTNAME for 6 
recips, completed in 0.200 seconds
   /var/log/mailman/smtp Nov 09 09 06 45 2015 (16804) 
 smtp to LISTNAME for 6 
recips, completed in 0.200 seconds
   /var/log/mailman/smtp Nov 09 09 06 45 2015 (16804) 
 smtp to LISTNAME for 6 
recips, completed in 0.200 seconds
   /var/log/mailman/smtp Nov 09 09 06 45 2015 (16804) 
 smtp to LISTNAME for 6 
recips, completed in 0.200 seconds
   /var/log/mailman/smtp Nov 09 09 06 45 2015 (16804) 
 smtp to LISTNAME for 6 
recips, completed in 0.200 seconds
   /var/log/mailman/smtp Nov 09 13 28 33 2015 (16804) 
<6f7a7eb8e5e442668ea1a864e84c2...@pobox.engr.local> smtp to LISTNAME for 1209 
recips, completed in 110.189 seconds
   /var/log/mailman/smtp Nov 09 13 28 33 2015 (16804) 
<6f7a7eb8e5e442668ea1a864e84c2...@pobox.engr.local> smtp to LISTNAME for 1209 
recips, completed in 110.189 seconds
   /var/log/mailman/smtp Nov 09 13 28 33 2015 (16804) 
<6f7a7eb8e5e442668ea1a864e84c2...@pobox.engr.local> smtp to LISTNAME for 1209 
recips, completed in 110.189 seconds
   /var/log/mailman/smtp Nov 09 13 28 33 2015 (16804) 
<6f7a7eb8e5e442668ea1a864e84c2...@pobox.engr.local> smtp to LISTNAME for 1209 
recips, completed in 110.189 seconds
   /var/log/mailman/smtp Nov 09 13 28 33 2015 (16804) 
<6f7a7eb8e5e442668ea1a864e84c2...@pobox.engr.local> smtp to LISTNAME for 1209 
recips, completed in 110.189 seconds
   /var/log/mailman/smtp Nov 09 13 28 33 2015 (16804) 
<6f7a7eb8e5e442668ea1a864e84c2...@pobox.engr.local> smtp to LISTNAME for 1209 
recips, completed in 110.189 seconds
   /var/log/mailman/post Nov 09 13 28 33 2015 (16804) post to LISTNAME from 
some...@example.com, size=5675, 
message-id=<6f7a7eb8e5e442668ea1a864e84c2...@pobox.engr.local>, success

Where can I see which messages was contained in which digests and when? My 
problem is that I don't seem to be able to tell whether the list admin is right 
or not. Not that I doubt his statement, but I really like to be able to tell 
when what happens.

Regards, Henrik Rasmussen
--
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] Part of moderated mails postponed to later digests

[Henrik Rasmussen]

Sorry for the late reply.

> Mark Sapiro [mailto:m...@msapiro.net]
> Sent: 4. november 2015 17:07

> Anyway, I understood your OP to say digests were being sent only weekly when 
> batches of held messages are approved.
That was an example of the frequency, held mails is being approved by the 
moderator. When the moderator approves a bunch of mails in one week, the list 
admin claims that only some of the mails are posted to the list, but that some 
of the mails will not be sent in a digest until the next moderation a week 
later (example).

> if you don't want digests triggered on size
The list admin doesn't need digests sent according to size so a 
digest_size_threshhold = 1 should be fine. The moderator wants to have the 
mails included in a digest the next noon after approving the mails.

> and your mailman is older than 2.1.16
I run Mailman 2.1.12 which is the latest available for yum update on RHEL6. I 
think the last Mailman version on RHEL7 is 2.1.15, but we're not there yet.

I just confirmed that senddigest is run every noon:
   /var/log/cron:Nov  8 12:00:01 p1kitlst01l CROND[18196]: (mailman) CMD 
(/usr/lib/mailman/cron/senddigests)
   /var/log/cron:Nov  9 12:00:01 p1kitlst01l CROND[27052]: (mailman) CMD 
(/usr/lib/mailman/cron/senddigests)

> If this is not the case, either cron/senddigests is not running every noon or 
> it is somehow skipping this list or encountering errors with this list. Is 
> there anything in Mailman's error log?

The error log doesn't show anything in association with the list in question. 

According to the vette log, some are discarded by moderator actions, :
   Oct 25 10:20:42 2015 (16801) Precedence: bulk message discarded by: 
listname-requ...@list.example.com
And of cause a lot of "Reason: Non-members" and spam-like messages "Reason: 
Your message was deemed inappropriate by the moderator.".

Regards, Henrik Rasmussen

-Oprindelig meddelelse-
Fra: Mark Sapiro [mailto:m...@msapiro.net] 
Sendt: 4. november 2015 17:07
Til: Henrik Rasmussen; mailman-users@python.org
Emne: Re: SV: [Mailman-Users] Part of moderated mails postponed to later digests

On 11/04/2015 02:09 AM, Henrik Rasmussen wrote:
>> My best guess is you are triggering digests on size (Digest options -> 
>> digest_size_threshold) and either not periodically (digest_send_periodic = 
>> No) or cron/senddigests runs only weekly.
> 
> To clarify, he has set digest_size_threshold to 1 and 
> digest_send_periodic =Yes. /usr/lib/mailman/cron/senddigests is run by cron 
> every day at noon.
> 
> Other digest settings is
> 
> nondigestable = True
> scrub_nondigest = False
> digestable = True
> digest_is_default = 1
> mime_is_default_digest = 0
> digest_size_threshhold = 1
> digest_send_periodic = 1
> digest_volume_frequency = 3
> discard_these_nonmembers = (241 members)
> ban_list = (188 members)
> 
> The digest_size_threshhold = 1 may likely course the problem, but is 
> necessary as a digest containing a single mail is sent each time a mail is 
> sent to the list-address as suggested by 
> https://mail.python.org/pipermail/mailman-users/2014-August/077622.html.


That's a bug <https://bugs.launchpad.net/mailman/+bug/558274> which was
fixed in MM 2.1.16, but in any case, if you don't want digests triggered
on size and your mailman is older than 2.1.16, setting
digest_size_threshhold = 1 (KB = 10 MB) should stop digests being
triggered on size unless your list has a lot of large graphics attached
to posts. I.e. 10MB / 100 posts is still 100KB per post.


Anyway, I understood your OP to say digests were being sent only weekly
when batches of held messages are approved. If as you say,
digest_send_periodic =Yes and /usr/lib/mailman/cron/senddigests is run
by cron every day at noon, even if 50 messages are approved and 30 of
them are sent immediately in a digest (triggered on size), the other 20
should be sent in a digest the next noon.

If this is not the case, either cron/senddigests is not running every
noon or it is somehow skipping this list or encountering errors with
this list. Is there anything in Mailman's error log?

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Part of moderated mails postponed to later digests

[Henrik Rasmussen]

> My best guess is you are triggering digests on size (Digest options -> 
> digest_size_threshold) and either not periodically (digest_send_periodic = 
> No) or cron/senddigests runs only weekly.

To clarify, he has set digest_size_threshold to 1 and digest_send_periodic 
=Yes. /usr/lib/mailman/cron/senddigests is run by cron every day at noon.

Other digest settings is

nondigestable = True
scrub_nondigest = False
digestable = True
digest_is_default = 1
mime_is_default_digest = 0
digest_size_threshhold = 1
digest_send_periodic = 1
digest_volume_frequency = 3
discard_these_nonmembers = (241 members)
ban_list = (188 members)

The digest_size_threshhold = 1 may likely course the problem, but is 
necessary as a digest containing a single mail is sent each time a mail is sent 
to the list-address as suggested by 
https://mail.python.org/pipermail/mailman-users/2014-August/077622.html.

Regards Henrik
--
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] Part of moderated mails postponed to later digests

[Henrik Rasmussen]

One of my list administrators complains that digest mails now seems to be sent 
in fragmented chunks and instead of sending all moderated mails in a digest the 
same day, only some of the mails will be sent with a digest the same day, and 
the rest will be sent in a digest with the next moderated mails, half a week 
later. For instance, when moderating say 50 mails in week 1 and 50 mails in 
week 2, the digest mail in week 1 will contain say 30 mails in a digest, while 
the digest in week 2 will contain like 20 mails from week 1 and like 10 mails 
from week 2.

There is no information about when the admin discovered the problem, but on 
August 20th 2015 Mailman has been upgraded from 3:2.1.12-18.el6 to 
3:2.1.12-25.el6 and I wonder if the DMARC implementation in 3:2.1.12-22.el6 has 
something to do with it, as this is the only changes I can think of having any 
effect on the mail behavior.

dmarc_quarantine_moderation_action is set to Yes on the list in particular and 
according to some discussions on the Internet, this strict action has been 
coursing bounces, so I suggested him to set this to No.

But even being strict, I don't see why this would course parts of the digest 
being held half a week, so something else must interfere.

Regards
Henrik Rasmussen
--
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] Some subscriber's e-mail adresses contains linebreak unicode character ​

[Henrik Rasmussen]

Sorry, my bad. Output from list_members LISTNAME shows email addresses 
containing ​ like m...@example.com​, but without semicolon (;) used 
in HTML.

All the affected members seems to have been added by mass subscribtion from an 
admin so maybe the Mailman web interface form have been altered somewhere. I 
wonder why it's random though.

Thank you for the command. I will look further in to the problem.

Yours faithfully
 
Henrik Rasmussen
Systemadministrator, Core Services






> -Oprindelig meddelelse-
> Fra: Mailman-Users [mailto:mailman-users-
> bounces+her=adm.ku...@python.org] På vegne af Mark Sapiro
> Sendt: 21. oktober 2015 05:59
> Til: mailman-users@python.org
> Emne: Re: [Mailman-Users] Some subscriber's e-mail adresses contains
> linebreak unicode character 
> 
> On 10/20/2015 01:52 AM, Henrik Rasmussen wrote:
> > In some occasions, a few subscribers of different lists contains the
> character ​ in the mail-address, like
> m...@example.com​<mailto:m...@example.com​;> preventing
> them from receiving any mails from Mailman. The Unicode is always the
> same on affected subscribers.
> 
> 
> I am confused. Are you saying the addresses end with an actual Unicode zero
> width space character or that they end with the ascii string '​'. If the
> latter, I don't see how this can happen. In no version of Mailman 2.1 back to
> pre 2.1.1 has a ';' been allowed in an email address. If the former, an 
> address
> with '\u200B' (the python escape for that character) in the domain would not
> have been allowed since Mailman 2.1.15, but may have been allowed before
> that.
> 
> 
> > As what I've read it is a zero space line break unicode character. So far 
> > the
> only think I found was about HTML pages containing the character and a
> single post explains something about the character being added to a page
> through the Office 365 Public Website editor. But since subscribing to a
> Mailman list does not involve an editor, I assume that the character could
> have been added by a webbased mail client.
> 
> 
> That is probably correct, but gmail's web mail in particular (which I once
> thought was good about stuff like this) and probably others when composing
> in 'rich text' and creating a multipart/alternative message, sometimes creates
> a text/plain alternative littered with these characters.
> 
> Thus, if one composes an email in Gmail's web client to the list-request
> address with a body line
> 
> subscribe m...@example.com
> 
> It is possible the text/plain alternative will have a zero width space 
> appended
> to the address.
> 
> 
> > I don't know whether the subscribers have subscribed through mail or
> through the Mailman web interface, but since the problem is random, I
> assume that the Mailman web interface is not associated. I guess that it must
> be some kind of common web based MUA they have used, like Gmail or
> Hotmail or similar.
> 
> 
> Have you looked at Mailman's subscribe log?
> 
> 
> > What could course this and how can I prevent it?
> 
> 
> Conjecture on cause above. Prevention - upgrade Mailman to >= 2.1.15
> 
> --
> Mark Sapiro The highway is for gamblers,
> San Francisco Bay Area, Californiabetter use your sense - B. Dylan
> --
> Mailman-Users mailing list Mailman-Users@python.org
> https://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy:
> http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-
> archive.com/mailman-users%40python.org/
> Unsubscribe: https://mail.python.org/mailman/options/mailman-
> users/her%40adm.ku.dk
--
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] Some subscriber's e-mail adresses contains line break unicode character ​

[Henrik Rasmussen]

In some occasions, a few subscribers of different lists contains the character 
​ in the mail-address, like 
m...@example.com​<mailto:m...@example.com​;> preventing them from 
receiving any mails from Mailman. The Unicode is always the same on affected 
subscribers.

As what I've read it is a zero space line break unicode character. So far the 
only think I found was about HTML pages containing the character and a single 
post explains something about the character being added to a page through the 
Office 365 Public Website editor. But since subscribing to a Mailman list does 
not involve an editor, I assume that the character could have been added by a 
webbased mail client.

>From what I've learned, the issue is associated with a random number of 
>subscribers on different lists, having different admins in most cases - I 
>currently have the issue on two lists having the same admin though, but two 
>different subscribers.

I don't know whether the subscribers have subscribed through mail or through 
the Mailman web interface, but since the problem is random, I assume that the 
Mailman web interface is not associated. I guess that it must be some kind of 
common web based MUA they have used, like Gmail or Hotmail or similar.

What could course this and how can I prevent it?

Yours faithfully

Henrik Rasmussen
--
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] Custom contact address, not site admin

[Henrik Rasmussen]

On 11/29/2014 02:33 AM, Mark Sapiro wrote:

> On 11/28/2014 04:16 AM, Henrik Rasmussen wrote:
> > I found this, so it seems that there is no single way to change the
> > site admin contact address, as messages seems to be associate with the
> > list admin, according to the %(owneraddr)s in the bounce.txt
> 
> 
> The %(owneraddr)s in templates/LC/bounce.txt is replaced by the site email,
> not the list owner email.

Since disabled.txt and probe.txt contains

you can contact the list owner at
%(owneraddr)s

I figured that %(owneraddr)s would be the list admin address, not the site 
admin address.

Why does disabled.txt and probe.txt refer %(owneraddr)s as List owner address 
when bounce.txt refer it as Site admin address?

Henrik Rasmussen
--
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] Custom contact address, not site admin

[Henrik Rasmussen]

Some standard mails from Mailman, like "bounce action notice", urges the user 
to contact the Mailman site-list address*). While I still want system mails, 
meant for the site admin, to go to the site admin address, I would like to 
customize the contact address displayed in mails and on the web GUI, to show 
our helpdesk e-mail address instead.

Normally I would edit the file 
/usr/lib/mailman/messages/uk/LC_MESSAGES/mailman.po and run 
/usr/lib/mailman/bin/msgfmt.py 
/usr/lib/mailman/messages/da/LC_MESSAGES/mailman.po, but not all messages can 
be customized this way.

What is the best way to customize the site admin contact address in each e-mail 
and web-gui page, to display our helpdesk contact address?

*) Example of standard mail from Mailman: "Questions? Contact the Mailman site 
administrator at mail...@list.example.com<mailto:mail...@list.example.com>."

Henrik Rasmussen
--
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] Custom contact address, not site admin

[Henrik Rasmussen]

I found this, so it seems that there is no single way to change the site admin 
contact address, as messages seems to be associate with the list admin, 
according to the %(owneraddr)s in the bounce.txt

[2] https://mail.python.org/pipermail/mailman-users/2012-September/074141.html

Henrik Rasmussen

Fra: Henrik Rasmussen
Sendt: 28. november 2014 12:55
Til: mailman-users@python.org
Emne: Custom contact address, not site admin

Some standard mails from Mailman, like "bounce action notice", urges the user 
to contact the Mailman site-list address*). While I still want system mails, 
meant for the site admin, to go to the site admin address, I would like to 
customize the contact address displayed in mails and on the web GUI, to show 
our helpdesk e-mail address instead.

Normally I would edit the file 
/usr/lib/mailman/messages/uk/LC_MESSAGES/mailman.po and run 
/usr/lib/mailman/bin/msgfmt.py 
/usr/lib/mailman/messages/da/LC_MESSAGES/mailman.po, but not all messages can 
be customized this way.

What is the best way to customize the site admin contact address in each e-mail 
and web-gui page, to display our helpdesk contact address?

*) Example of standard mail from Mailman: "Questions? Contact the Mailman site 
administrator at mail...@list.example.com<mailto:mail...@list.example.com>."

Henrik Rasmussen
--
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 digest issues

[Henrik Rasmussen]

On 08/12/2014 6:56 PM, Mark Sapiro wrote:

>> I am still confused, even after reading section 2.6 in 
>> http://www.gnu.org/software/mailman/mailman-admin.pdf. In my understanding, 
>> (and I know I'm wrong here) if the volume number is >>changed weekly, but 
>> digest mails are sent daily, all digests will contain the same volume number 
>> all week long. What is the difference between volume number and issue 
>> number, and when do >>Mailman send what?

>A volume is a set of issues. The very first digest is Volume 1, Issue 1.
>The next is Volume 1, Issue 2 and so on. After digest_volume_frequency 
>elapses, the next digest is Volume 2, Issue 1, and so on.
>
>Most print periodicals work the same way.

What is the purpose of using both Volumes and issues? I mean, wouldn't a single 
counter (like Issue) be sufficient? I ask simply to understand the nature, and 
relations between Digest options (where exist).

>> No errors in the error log. Cron/senddigests -l LISTNAME. However, 
>> shows
>> 
>>   [r...@mailman.example.com]# /usr/lib/mailman/cron/senddigests -l 
>> Sci-diku-imageworld
>>   Traceback (most recent call last):
>> File "/usr/lib/mailman/cron/senddigests", line 106, in 
>>   main()
>> File "/usr/lib/mailman/cron/senddigests", line 84, in main
>>   mlist = MailList.MailList(listname, lock=0)
>> File "/usr/lib/mailman/Mailman/MailList.py", line 130, in __init__
>>   self.Load()
>> File "/usr/lib/mailman/Mailman/MailList.py", line 626, in Load
>>   raise Errors.MMUnknownListError
>>   Mailman.Errors.MMUnknownListError
>
>
>Does LISTNAME (all lower case) exist? Does the file lists/listname/config.pck 
>exist in Mailman's file system?

Yes, the list (lower case except for the first character, as list_lists display 
them) do exist, and the lists/sci-diku-imageworld/config.pck too.

> This is a bug <https://bugs.launchpad.net/mailman/+bug/558274>. It was fixed 
> in 2.1.16. Prior to that, setting digest_size_threshhold = 0 would produce 
> the behavior you see.
>
>If you want no digests based on size in older versions, set 
>digest_size_threshhold =  a very large number.

No Digest mails was sent at all when digest_size_threshhold = 1000.

>I don't understand this question. With emergency = Yes, all posts will be held 
>and if approved by the list admin/moderator will be delivered to the list and 
>accumulated for the digest (which with >digest_size_threshhold = 0 pre 2.1.16 
>will be sent immediately, one digest per post).

Thanks, that's what I meant and figured.

Henrik Rasmussen
--
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 digest issues

[Henrik Rasmussen]

Further info on the problem is that the list admin just released 47 mails 30 
minutes ago (please note that the digest_size_threshhold is now = 0, was 
previously 1000). Until now the list have sent 22 digest-mails with a single 
mail in each digest mail, all named Volume 20, but with increasing Issue number 
from 1 to 22. The numbering is expected, but the mails should've been send as a 
collection, not as individual mails.

Right now the settings are

nondigestable = True
scrub_nondigest = False
digestable = True
digest_is_default = 1
mime_is_default_digest = 0
digest_size_threshhold = 0
digest_send_periodic = 1
digest_header = ''
digest_volume_frequency = 3

There is no /var/lib/mailman/lists/LISTNAME/digest.mbox for the list in 
question, or any other list. Though I don't know which other lists do send 
digest mails.

The list admin now have Emergency-moderated the list. I guess this is just to 
stop all incoming traffic from being sent out, and have no effect on what the 
list admin do release, right?

Henrik Rasmussen


-Oprindelig meddelelse-
Fra: Henrik Rasmussen 
Sendt: 12. august 2014 09:32
Til: Mark Sapiro; mailman-users@python.org
Emne: SV: [Mailman-Users] Mailman digest issues

On 08/12/2014 03:00 AM, Mark Sapiro wrote:

>On 08/11/2014 06:15 AM, Henrik Rasmussen wrote:
>> I am using Mailman version 2.1.12.
>> 
>> But he also complains that no digest mails are being sent when he set 
>> _send_digest_now to Yes.
>Did he press "Submit Your Changes" after setting _send_digest_now to Yes? If 
>so, and if there were digested messages and digest members with delivery 
>enabled, something else is wrong.

Yes he did. I did too, afterwards.

>What response did he get when pressing "Submit Your Changes" after setting 
>_send_digest_now to Yes? What's in Mailman's error log.

I got the message "There was no digest to send". No messages regarding this 
list in /var/log/mailman/error (or any other log in this directory for that 
matter).

The smtp log show that the list do send message (to normal-members I guess), 
but I can't verify if messages are sent to digest-members. The list admin say 
no mails are sent to digest-members.

>> He also set digest_send_periodic to Yes.
> >
>> We're confused that the digest_send_periodic  text is saying "Should a 
>> digest be dispatched daily when the size threshold isn't reached?" as he 
>> wants the digest to be sent weekly as set in digest_volume_frequency.
>digest_volume_frequency has nothing to do with how often periodic digests are 
>sent. It only controls how often the vvv is incremented and ii is reset in the 
>"List_name Digest, Vol vvv, Issue ii" >Subject: header of the digest.

I am still confused, even after reading section 2.6 in 
http://www.gnu.org/software/mailman/mailman-admin.pdf. In my understanding, 
(and I know I'm wrong here) if the volume number is changed weekly, but digest 
mails are sent daily, all digests will contain the same volume number all week 
long. What is the difference between volume number and issue number, and when 
do Mailman send what?

>> 1)  Where can I see if digest mails are in fact being sent out?
>Your MTA logs and Mailman's smtp log. Also, digest messages are accumulated in 
>lists/list_name/digest.mbox, and when a digest is sent, this file is removed.

How can I tell normal from digest? Will the digest mails mention Digest I the 
SMTP log. If so, no digests have been sent.

>> 2)  Where will Mailman log digest issues?
>Mailman's error log and in the output from cron/senddigests (for periodic 
>digests.

No errors in the error log. Cron/senddigests -l LISTNAME. However, shows

  [r...@mailman.example.com]# /usr/lib/mailman/cron/senddigests -l 
Sci-diku-imageworld
  Traceback (most recent call last):
File "/usr/lib/mailman/cron/senddigests", line 106, in 
  main()
File "/usr/lib/mailman/cron/senddigests", line 84, in main
  mlist = MailList.MailList(listname, lock=0)
File "/usr/lib/mailman/Mailman/MailList.py", line 130, in __init__
  self.Load()
File "/usr/lib/mailman/Mailman/MailList.py", line 626, in Load
  raise Errors.MMUnknownListError
  Mailman.Errors.MMUnknownListError


>Note, that often the output, if any, from Mailman's cron jobs is mailed to the 
>'mailman' user which happens to be the site list. If the site list is not 
>configured to accept non-member posts, and the >site admin is not a member of 
>the site list, this output is often lost.
>You can either set the site list as above or add a MAILTO= directive with a 
>deliverable address to Mailman's crontab.

Thanks.

>-- 
>Mark Sapiro The highway is for gamblers,

Henrik Rasmussen

--

Re: [Mailman-Users] Mailman digest issues

[Henrik Rasmussen]

On 08/12/2014 03:00 AM, Mark Sapiro wrote:

>On 08/11/2014 06:15 AM, Henrik Rasmussen wrote:
>> I am using Mailman version 2.1.12.
>> 
>> But he also complains that no digest mails are being sent when he set 
>> _send_digest_now to Yes.
>Did he press "Submit Your Changes" after setting _send_digest_now to Yes? If 
>so, and if there were digested messages and digest members with delivery 
>enabled, something else is wrong.

Yes he did. I did too, afterwards.

>What response did he get when pressing "Submit Your Changes" after setting 
>_send_digest_now to Yes? What's in Mailman's error log.

I got the message "There was no digest to send". No messages regarding this 
list in /var/log/mailman/error (or any other log in this directory for that 
matter).

The smtp log show that the list do send message (to normal-members I guess), 
but I can't verify if messages are sent to digest-members. The list admin say 
no mails are sent to digest-members.

>> He also set digest_send_periodic to Yes.
> >
>> We're confused that the digest_send_periodic  text is saying "Should a 
>> digest be dispatched daily when the size threshold isn't reached?" as he 
>> wants the digest to be sent weekly as set in digest_volume_frequency.
>digest_volume_frequency has nothing to do with how often periodic digests are 
>sent. It only controls how often the vvv is incremented and ii is reset in the 
>"List_name Digest, Vol vvv, Issue ii" >Subject: header of the digest.

I am still confused, even after reading section 2.6 in 
http://www.gnu.org/software/mailman/mailman-admin.pdf. In my understanding, 
(and I know I'm wrong here) if the volume number is changed weekly, but digest 
mails are sent daily, all digests will contain the same volume number all week 
long. What is the difference between volume number and issue number, and when 
do Mailman send what?

>> 1)  Where can I see if digest mails are in fact being sent out?
>Your MTA logs and Mailman's smtp log. Also, digest messages are accumulated in 
>lists/list_name/digest.mbox, and when a digest is sent, this file is removed.

How can I tell normal from digest? Will the digest mails mention Digest I the 
SMTP log. If so, no digests have been sent.

>> 2)  Where will Mailman log digest issues?
>Mailman's error log and in the output from cron/senddigests (for periodic 
>digests.

No errors in the error log. Cron/senddigests -l LISTNAME. However, shows

  [r...@mailman.example.com]# /usr/lib/mailman/cron/senddigests -l 
Sci-diku-imageworld
  Traceback (most recent call last):
File "/usr/lib/mailman/cron/senddigests", line 106, in 
  main()
File "/usr/lib/mailman/cron/senddigests", line 84, in main
  mlist = MailList.MailList(listname, lock=0)
File "/usr/lib/mailman/Mailman/MailList.py", line 130, in __init__
  self.Load()
File "/usr/lib/mailman/Mailman/MailList.py", line 626, in Load
  raise Errors.MMUnknownListError
  Mailman.Errors.MMUnknownListError


>Note, that often the output, if any, from Mailman's cron jobs is mailed to the 
>'mailman' user which happens to be the site list. If the site list is not 
>configured to accept non-member posts, and the >site admin is not a member of 
>the site list, this output is often lost.
>You can either set the site list as above or add a MAILTO= directive with a 
>deliverable address to Mailman's crontab.

Thanks.

>-- 
>Mark Sapiro The highway is for gamblers,

Henrik Rasmussen

--
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] Mailman digest issues

[Henrik Rasmussen]

I am using Mailman version 2.1.12.

One of my list admins have complained that he's list does not send out digest 
mails, which is most likely because he set digest_size_threshhold to 1000.

But he also complains that no digest mails are being sent when he set 
_send_digest_now to Yes.

He also set digest_send_periodic to Yes.

We're confused that the digest_send_periodic  text is saying "Should a digest 
be dispatched daily when the size threshold isn't reached?" as he wants the 
digest to be sent weekly as set in digest_volume_frequency.

The /var/log/cron shows that the /usr/lib/mailman/cron/senddigests is being run 
daily at noon.


1)  Where can I see if digest mails are in fact being sent out?

2)  Where will Mailman log digest issues?

3)  Does the digest_send_periodic daily affect the digest_volume_frequency 
weekly?


Yours faithfully

Henrik Rasmussen
Systemadministrator, Core Services

UNIVERSITY OF COPENHAGEN
Corporate IT, Operation & Support
Nørregade 10, P.O. Box 2177
DK1017 Copenhagen K

Tel: +45 35322626
Dir: +45 35322704
Fax: +45 35322707
Email: h...@adm.ku.dk<mailto:h...@adm.ku.dk>
Web: it.ku.dk<http://it.ku.dk/>

[KU-logo_UK]


--
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] Password in clear text

[Henrik Rasmussen]

I know this has been asked before, but I haven't found anything about whether 
or not this will be a future change or how to work around it.

The passwords in Mailman, are stored unencrypted. The web connection can be 
encrypted by SSL to avoid man in the middle, but passwords are sent in clear 
text in password reminders.

Is there any plans of a future change so passwords will be stored encrypted, 
and some kind of one-time link to change the password, instead of sending 
reminders, or some kind of challenge will be implemented, to avoid revealing 
the password to third party?

Otherwise I will request such a change.

Henrik Rasmussen
--
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] Changes to archive templates have no effect

[Henrik Rasmussen]

I am running Mailman version 2.1.12.

When I change my templates in /usr/lib/mailman/templates/site/da/ (like 
admlogin.html) I see the changes taking effect (immediately, even though I 
didn't restart Mailman), but any changes I make to the Archive templates 
located in the same directory doesn't seem to have any effect.

According to /usr/lib/mailman/Mailman/Archiver/HyperArch.py line 799 Mailman 
uses archtoc.html in case of a Private list or archtocnombox.html in case of a 
public list. The changes doesn't take effect regardless of whether the list is 
private or public. But I'm not sure if this the decision is made from the 
default (PUBLIC_MBOX) variable in the mm_cfg.py or Default.py files since the 
HyperArch.py file refers to the mm_cfg.

To debug, I tried make a change in the default /usr/lib/mailman/templates/da/ 
archtoc.html file, but this does not have any effect either.

Changing the archliststart.html, archlistend.html, archtocentry.html, 
archidxfoot.html, archidxhead.html have no effect either.

I did remember to restart Mailman both (just in case) using "service mailman 
restart" and "mailmanctl restart".

Henrik Rasmussen 
--
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] Which file are Mailman's webpages build from?

[Henrik Rasmussen]

I am running Mailman version 2.1.12. I have not been able to find a list of 
pages where the different HTML templates are used.

Having copied the HTML-templates, listed below, from 
/usr/lib/mailman/templates/da/  to /usr/lib/mailman/templates/site/da/ I would 
like to change the design of the web-pages. So far I am doing good a few 
templates, but I am not able to locate on which pages the second list of files 
are used Also some of the web-pages gets there information from various spurces 
such as the template-files, the messages file etc.

Is there an overview of which files different pages are build from?

admlogin.html
listinfo.html
emptyarchive.html
private.html
admindbdetails.html
subscribe.html
roster.html
options.html
headfoot.html
article.html
archtocnombox.html
archtoc.html
archtocentry.html
archliststart.html
archidxhead.html
archidxfoot.html
admindbsummary.html
admindbpreamble.html


Med venlig hilsen

Henrik Rasmussen
Systemadministrator, Core Services

KØBENHAVNS UNIVERSITET
Koncern-it, Drift & Support
Nørregade 10, postboks 2177
1017 København K

Tel: 35322626
Dir 35322704
Fax 35322707
Email: h...@adm.ku.dk<mailto:h...@adm.ku.dk>
Web: it.ku.dk<http://it.ku.dk/>

[KU_logo]

Spørgsmål af både faglig og teknisk karakter skal indrapporteres i KUnet's 
selvbetjeningssystem: "KUnet --> Selvbetjening --> It-service --> Min 
Servicedesk --> Opret Sag" eller via mail til 
it-serv...@adm.ku.dk<mailto:it-serv...@adm.ku.dk>. KUnet's selvbetjening findes 
på http://sd.ku.dkhttp://sd.ku.dk/>.


--
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] Moderator page similar to the admin page

[Henrik Rasmussen]

I am running Mailman version 2.1.12.

How to I present a moderator-page similar to the /admin/ page, containing a 
list of Maillists to moderate? Or does moderators only have the option of 
entering the URL as mentioned at 
https://mail.python.org/pipermail/mailman-users/2004-December/041411.html


Yours faithfully

Henrik Rasmussen
--
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] Automatic update of list members while making it possible to (un)subscribe manually

[Henrik Rasmussen]

Before I start making my own script, I was wondering whether the feature I need 
is already available. I run Mailman version: 2.1.5.

I have two types of Mailman lists
* some of which members are allowed to subscribe or unsubscribe as desired 
(though some list administrators still need to approve subscriptions)
* and some lists, which members of a certain group must be subscribed to, as 
long as they are part of the group.

The group-members e-mail addresses are extracted from the group and pushed to 
the list using " add_members -wn -r /tmp/group_members.lst mailman-list". 
Likewise are those, no longer part of the group, removed from the list using 
"remove_members -n -N -f /tmp/group_exmembers.lst mailman-list".

Now I want to combine those features, having lists that are updated 
automatically using above method, but at the same time making sure that group 
members, who have manually opted-out from the mailinglist, won't be subscribed 
to the mailinglist automatically again, and also making sure that people, who 
are not part of the group, have the ability to opt-in to the mailinglist 
without being removed by automatic procedure.

Is there a neat way of accomplish this already?

Henrik Rasmussen

--
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] Changing "Send questions and comments" mail-address without changing MAILMAN_OWNER

[Henrik Rasmussen]

I am running a Mailman version 2.1.5 installation. I need to change the e-mail 
address that users are requested to send questions and comments to
(messages/uk/LC_MESSAGES/mailman.po: msgid "(Send questions and comments to "

I still need other mails like non-handled bounces to be sent to the original 
MAILMAN_OWNER site admin address mail...@my-server.example.com

Is there a better way to achieve this than to change the line 280 in the 
Mailman/Cgi/admin.py file?

* Line 280: Link('mailto:%s' % mailman_owner, mailman_owner)

Henrik Rasmussen
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Danish characters - in "result of your commands" and in Mail archive

[Henrik Rasmussen]

 
I have found quite a few descriptions about this, but none of them seems to be 
able to solve the problem.

I am using:

* Mailman 2.1.5
* Python-2.3.4-14.4.el4_6.1
* Redhat-release-4AS-7
* postfix-2.2.10-1.1.el4


I have a few cases of Danish characters not beind displayed correctly.

1) "Result of you commands" e-mail contains Quoted Printable
2) The E-mail archive is displayed in UTF-8



1)

When users subscribe or unsubscribe to a list with a mail containing Danish 
characters æøåÆØÅ, they receive a mail with the result of their commands. This 
mail includes the 2 standard sections "Results" and "Not handled" (translated 
from Danish, so they might have other names). In the section of Not handled, 
the text is displayed in Quoted Printable "=20" or "=E6=F8=E5=C6=D8=C5".

I've read somewhere that I am suppose to put DEFAULT_CHARSET into mm_cfg.py, 
but as I understand the comments in the Defaults.py file, this is only when 
using Pipermail. Anyway, it doesn't change anything when I set it to 
['iso-8859-1'].

Sending the mail as plain text, UTF-8, the resulting mail contains

æøåÆØÅ
w6bDuMOlw4bDmMOFDQo=

How am I support to make the result mails human readable?



2)

The list's mail archive in mailserver.domain.tld/mailman/private/mylist/ 
contains Thread, Title, Author and Dato in Danish (Marts 2008: [ Tr d ] [ Titel 
] [ Forfatter ] [ Dato ]  [ Tekst 765 bytes ]). The webpage source contains the 
the word "Tråd" (instead of Tråd) and since the page is displayed in 
UTF-8, the word is displayed as "Tr d" with a square instead of the danish 
character.

I have tried changing the å in /usr/lib/mailman/templates/da/archtocentry.html 
to Tråd (and restarting Mailman), but this doesn't change anything. 
Changing the DEFAULT_CHARSET in mm_cfg.py doesn't make any chances either.

When changing the character set for the displayed webpage in the browser, to 
"West european (Windows)", the character displayed correct.

How can I change the archive to use ISO8859-1 instead of UTF-8?

Regards Henrik
--
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=show&file=faq01.027.htp

Re: [Mailman-Users] No subscription is made despite confirmation

[Henrik Rasmussen]

 
Stephen J. Turnbull wrote:
> Henrik Rasmussen writes:
> Of course it's possible that the MUA is just inserting those headers
> but it's a lie (the MUA thinks that's enough to let it get away with
> just putting UTF-8 *anywhere*).  But note that 0xF8 is illegal in
> UTF-8 (for several reasons), so most likely that is intended as an ISO
> 8-bit character.
> Do you agree that the interpretation of 0xF8 as "ø" is likely here?

I'm not sure. The mail body contains a signature "Nørregaard" in the plain text 
section and "N=C3=B8rregaard" in the HTML section, but there is no "ø" in the 
header (and thus nor the e-mail address of the subscriber).

But even so, the fact that Mailman issued a 'new' command, the user should have 
been put on the list (i'm just speculating here, I'm not that familiar with 
e-mail handeling and especially not Mailman nor Python).

>  > >The only reasonable solution is to get your users to stop 
> doing that.
>  > >This may require them to subscribe that address from a 
> different MUA.
>  > 
>  > This would not be a practicable solution, since we have subscribers
>  > from around the world.
> 
> The alternative is far worse, though:  to ask "Søren" to spell his
> name as "Soren".  :-(

Haha yes, that would not be easy.
--
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=show&file=faq01.027.htp

Re: [Mailman-Users] No subscription is made despite confirmation

[Henrik Rasmussen]

Stephen J. Turnbull wrote: 

>Henrik Rasmussen writes:
>
> > UnicodeDecodeError: 'ascii' codec can't decode byte 0xf8 in
> > position 5: ordinal not in range(128) 
>
>Your user is sending mail with raw 8-bit characters (in this case
>probably meaning "ø") in the headers.  This is forbidden by RFC 2822.
>The universally accepted way to do this is by using MIME encoded words.

That's plausible. The mailheader of the confirmation reply contains "This is a 
MIME message", but the message seems to be multipart MIME, containing both

Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

and 

Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Description: HTML

>The only reasonable solution is to get your users to stop doing that.
>This may require them to subscribe that address from a different MUA.

This would not be a practicable solution, since we have subscribers from around 
the world.

Henrik
--
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=show&file=faq01.027.htp

Re: [Mailman-Users] No subscription is made despite confirmation

[Henrik Rasmussen]

Mark Sapiro wrote:

>>One of my list administrators have celled me regarding some users not being 
>>subscribed to a list. Mailman have sent the users in question a confirmation 
>>ticket, and the subscribe log shows that the users have been put in pending 
>>mode.
>> 
>>Jan 31 13:09:33 2008 (2223) listname: pending [EMAIL PROTECTED] 
>><mailto:[EMAIL PROTECTED]>   [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> 
>> 
>>When the users returned the mail, Mailman issued a New command
>> 
>>Jan 31 13:11:29 2008 (2223) listname: new "[EMAIL PROTECTED] <mailto:[EMAIL 
>>PROTECTED]> " <>, via email confirmation
>
>
>And this user is successfully subscribed. The only things left to do
>after the "new" log entry is written are
>
> - Send the welcome to the user if the list's send_welcome_msg is Yes.
>
> - Send the notice to the admin if the list's admin_notify_mchanges is
>   Yes.
>
>Were these messages received?

Both send_welcome_msg and admin_notify_mchanges has been set to No. The 
subscriber currently have vacation so whether she received a "Result of your 
commands" mail is unknown. I've tried subscribing to the list from my external 
mail account and (as the subscriber) received the "Result of your commands" 
reply. Though I am actually subscribed to the list.

>>but still the users wasn't subscribed (list_members listname still did not 
>>show the user as member of the list).
>
>
>I don't know why this would be the case. Does subscribe and confirm by
>email work for other lists?

Yes this works (for me anyway), I haven't consultet the user about this yet.

>For other users on this list?

For me, by subscribing an external address (a spamcop.net address) to the 
particular list works too.

>What if the user confirms by web?

In general, the users have no knowledge about the web-interface nor the use of 
it. Only the list administrators have.


>>A few days later one of the users retried subscribing, and the same happened. 
>>The log does not show any signs that the user have tried unsubscribing 
>>(deleted).
>> 
>>According to the error log at the particular time, Mailman seems to have 
>>failed subscribing the user.

>These errors have nothing to do with the problem.
>Jan 31 11:36:09 2008 (2223) SHUNTING: 
>1201775768.8376081+629ed6771846a9304e6eca2178f2047980aa8630
>
>This is from a shunted message at 11:36:09. The error that caused the
>shunting is the traceback with the same timestamp that precedes the
>above message in the log.
>
>
>>Jan 31 13:10:06 2008 (2223) Uncaught runner exception: 'ascii' codec can't 
>>decode byte 0xf8 in position 5: ordinal not in range(128)
>>Jan 31 13:10:06 2008 (2223) Traceback (most recent call last):
>>  File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop
>>self._onefile(msg, msgdata)
>>  File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 167, in _onefile
>>keepqueued = self._dispose(mlist, msg, msgdata)
>>  File "/usr/lib/mailman/Mailman/Queue/CommandRunner.py", line 237, in 
>> _dispose
>>res.process()
>>  File "/usr/lib/mailman/Mailman/Queue/CommandRunner.py", line 110, in process
>>stop = self.do_command(cmd, args)
>>  File "/usr/lib/mailman/Mailman/Queue/CommandRunner.py", line 135, in 
>> do_command
>>return self.do_command(cmd, args)
>>  File "/usr/lib/mailman/Mailman/Queue/CommandRunner.py", line 137, in 
>> do_command
>>return handler.process(self, args)
>>  File "/usr/lib/mailman/Mailman/Commands/cmd_confirm.py", line 86, in process
>>if line.lstrip() == match:
>>UnicodeDecodeError: 'ascii' codec can't decode byte 0xf8 in position 5: 
>>ordinal not in range(128)
>
>
>And this traceback is probably followed by another 'shunting' entry for
>the message that caused it.

That's correct.

>
>These error log entries are from messages (most likely spam) with
>unencoded non-ascii characters in headers such as Subject: or From:.
>
>You can see these messages in the shunt queue and determine what they
>are.
>
>  bin/show_qfiles qfiles/shunt/*
>
>It is possible that the traceback at 13:10:06 is from this user's
>confirm attempt, but even if this is the case, the confirm was
>successfully retried by the user, because if it hadn't been, there
>would be no 'new' entry in the subscribe log.

The thunted message is the particular confirmation reply from the user. The 
reply contains HTML, however, as you point out, this wasn

[Mailman-Users] No subscription is made despite confirmation

[Henrik Rasmussen]

One of my list administrators have celled me regarding some users not being 
subscribed to a list. Mailman have sent the users in question a confirmation 
ticket, and the subscribe log shows that the users have been put in pending 
mode.
 
Jan 31 13:09:33 2008 (2223) listname: pending [EMAIL PROTECTED]    [EMAIL PROTECTED]  
 
When the users returned the mail, Mailman issued a New command
 
Jan 31 13:11:29 2008 (2223) listname: new "[EMAIL PROTECTED]  " <>, via email confirmation

 
but still the users wasn't subscribed (list_members listname still did not show 
the user as member of the list). A few days later one of the users retried 
subscribing, and the same happened. The log does not show any signs that the 
user have tried unsubscribing (deleted).
 
According to the error log at the particular time, Mailman seems to have failed 
subscribing the user.
 
Jan 31 11:36:09 2008 (2223) SHUNTING: 
1201775768.8376081+629ed6771846a9304e6eca2178f2047980aa8630
Jan 31 13:10:06 2008 (2223) Uncaught runner exception: 'ascii' codec can't 
decode byte 0xf8 in position 5: ordinal not in range(128)
Jan 31 13:10:06 2008 (2223) Traceback (most recent call last):
  File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop
self._onefile(msg, msgdata)
  File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 167, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
  File "/usr/lib/mailman/Mailman/Queue/CommandRunner.py", line 237, in _dispose
res.process()
  File "/usr/lib/mailman/Mailman/Queue/CommandRunner.py", line 110, in process
stop = self.do_command(cmd, args)
  File "/usr/lib/mailman/Mailman/Queue/CommandRunner.py", line 135, in 
do_command
return self.do_command(cmd, args)
  File "/usr/lib/mailman/Mailman/Queue/CommandRunner.py", line 137, in 
do_command
return handler.process(self, args)
  File "/usr/lib/mailman/Mailman/Commands/cmd_confirm.py", line 86, in process
if line.lstrip() == match:
UnicodeDecodeError: 'ascii' codec can't decode byte 0xf8 in position 5: ordinal 
not in range(128)
 
>From the log entries above, can some of you explain to me what might be wrong?
 
Henrik
--
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=show&file=faq01.027.htp

Re: [Mailman-Users] Mailman 2.1.5 - Local customizations is beingignored

[Henrik Rasmussen]

Hi Mark

It seems that we had put the copy in /usr/lib/mailman/lists//da
instead of /var/lib/mailman/lists//da/ where the config.pck is.
Thanks.

Henrik 

-Oprindelig meddelelse-
Fra: Mark Sapiro [mailto:[EMAIL PROTECTED] 
Sendt: 12. marts 2007 18:32
Til: Henrik Rasmussen; Mailman Users
Emne: Re: [Mailman-Users] Mailman 2.1.5 - Local customizations is
beingignored

Henrik Rasmussen wrote:
>
>I've read*) that to avoid customize the original templates, it is
>adviced to 
>
>"Create a directory lists//en (assuming English :) and copy
>  templates/subscribeack.txt to this directory.  Then edit this file 
>  for your specific wording.  Mailman will use this specialized 
>  template for the English welcome messages."


See
<http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.048.htp>
(which you might have found if you'd searched the FAQ for 'template'
instead of 'customize').


>I assume this does not require a OWNERS_CAN_ENABLE_PERSONALIZATION = 1 


Correct.


>However, even I copy the file templates/da/verify.txt to
>lists//da/ (and check the directory and file permissions
>according to the originals) and restart the mailman server using
>mailmanctl restart, Mailman still uses the original template
>templates/da/verify.txt
>
>Do I have to change something in the Mailman configuration to use
>customized templates?

No. The only requirement is that the template be in one of the places
discussed in the above referenced FAQ, and that it be readable by the
mailman group.

Is the lists// directory the existing directory that contains
the list's config.pck file?

Is the lists//da/verify.txt file you created readable by the
mailman group (i.e. group mailman and group readable or world
readable)?

-- 
Mark Sapiro <[EMAIL PROTECTED]>   The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
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=show&file=faq01.027.htp

[Mailman-Users] Mailman 2.1.5 - Local customizations is being ignored

[Henrik Rasmussen]

I'm using Mailman 2.1.5.

I've read*) that to avoid customize the original templates, it is
adviced to 

"Create a directory lists//en (assuming English :) and copy
  templates/subscribeack.txt to this directory.  Then edit this file 
  for your specific wording.  Mailman will use this specialized 
  template for the English welcome messages."

I assume this does not require a OWNERS_CAN_ENABLE_PERSONALIZATION = 1 

However, even I copy the file templates/da/verify.txt to
lists//da/ (and check the directory and file permissions
according to the originals) and restart the mailman server using
mailmanctl restart, Mailman still uses the original template
templates/da/verify.txt

Do I have to change something in the Mailman configuration to use
customized templates?

*)
http://www.python.org/cgi-bin/faqw-mm.py?query=customize&querytype=simpl
e&casefold=yes&req=search

Henrik
--
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=show&file=faq01.027.htp

Re: [Mailman-Users] Mailman's root path or where to place images

[Henrik Rasmussen]

Thank you Mark. According to my colleague, our Mailman installation is
installed by clicking a checkbox when installing RedHat Linux and it
seems that it somehow doesn't make use of the httpd.conf file (which I
don't understand) since the Script Alias is 

ScriptAlias /cgi-bin/ "/var/www/cgi-bin/".

(which is an empty directory) and Mailman's CGI-scripts is contained in
/usr/lib/mailman/cgi-bin/ though you are right about the conflict using

Alias /mailman/  /usr/lib/mailman/

so somehow it must be using httpd.conf anyway. I am totally new to both
Mailman and Apache so I don't yet know how they work.

For now I think i'll scrub the proxy thing, but it would be nice to know
how Mailman corresponds with httpd.conf in the default Redhat
installation.

Henrik

-Oprindelig meddelelse-
Fra: Mark Sapiro [mailto:[EMAIL PROTECTED] 
Sendt: 16. januar 2007 19:35
Til: Henrik Rasmussen; mailman-users@python.org
Emne: Re: [Mailman-Users] Mailman's root path or where to place images

Henrik Rasmussen wrote:
>
>I currently have my mailman icons in an /icons directory relative to
>Apache's root directory.
> 
>Example:
> 
>Icons is in /var/www/icons/ and the source http path to the icons is
>http://server.xxx.yyy.zz/icons/
> 
>In order to put the server behind a proxy server, I need to change the
>directory to http://server.xxx.yyy.zz/mailman/icons/

If it really has to be http://server.xxx.yyy.zz/mailman/icons/ and
http://server.xxx.yyy.zz/something_else/ won't do, I think you have
only one choice. See below.

 
>By changing the variable IMAGE_LOGOS = '/icons/' to IMAGE_LOGOS =
>'icons/' in the file /usr/lib/mailman/Mailman/mm_cfg.py the http path
is
>seemly relative to Mailman's root
>http://server.xxx.yyy.zz/mailman/icons/


Actually, it is just a relative path in the HTML to which your browser
prepends the current location.


>which I suppose should be
>/usr/lib/mailman/icons/ ,but moving the image file
>/usr/lib/mailman/icons/ still results in a missing image.
> 
>My question is, where Mailman's root directory is suppose to be, or
>rather which directory on the server correspond to
>http://server.xxx.yyy.zz/mailman/icons/?

You have something like

ScriptAlias /mailman/   /usr/lib/mailman/cgi-bin/

in your httpd.conf, so http://server.xxx.yyy.zz/mailman/icons/
corresponds to the CGI named icons in the directory
/usr/lib/mailman/cgi-bin/.

Ideally, you could alias it in your Apache httpd.conf with something
like

Alias /mailman/  /usr/lib/mailman/

except this won't work because of the conflict with the ScriptAlias.

If you really need the URL for the icons to be
http://example.com/mailman/icons/, I think you need to create an
'icons' CGI and put it in /usr/lib/mailman/cgi-bin/. This would be a
simple CGI that would just parse the name following
http://example.com/mailman/icons/ in the URL and locate and serve that
file.

There may be some other way to address this in the Apache
configuration, but that's an Apache question that I don't know the
answer to.

-- 
Mark Sapiro <[EMAIL PROTECTED]>   The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
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=show&file=faq01.027.htp

[Mailman-Users] Mailman's root path or where to place images

[Henrik Rasmussen]

I currently have my mailman icons in an /icons directory relative to
Apache's root directory.
 
Example:
 
Icons is in /var/www/icons/ and the source http path to the icons is
http://server.xxx.yyy.zz/icons/
 
In order to put the server behind a proxy server, I need to change the
directory to http://server.xxx.yyy.zz/mailman/icons/
 
By changing the variable IMAGE_LOGOS = '/icons/' to IMAGE_LOGOS =
'icons/' in the file /usr/lib/mailman/Mailman/mm_cfg.py the http path is
seemly relative to Mailman's root
http://server.xxx.yyy.zz/mailman/icons/ which I suppose should be
/usr/lib/mailman/icons/ ,but moving the image file
/usr/lib/mailman/icons/ still results in a missing image.
 
My question is, where Mailman's root directory is suppose to be, or
rather which directory on the server correspond to
http://server.xxx.yyy.zz/mailman/icons/?
 
Henrik


--
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=show&file=faq01.027.htp

Re: [Mailman-Users] Hit a but & use of VERP

[Henrik Rasmussen]

It seems that the only files containing something like %(..)p is

[EMAIL PROTECTED] lib]# find /usr/lib/mailman -name "*.py" -exec grep -H
")p" {} \; 

/usr/lib/mailman/tests/test_handlers.py:mlist.msg_header =
'%(real_name)p header\n'
/usr/lib/mailman/tests/test_handlers.py:mlist.msg_footer =
'%(real_name)p footer'
/usr/lib/mailman/tests/test_handlers.py:%(real_name)p header
/usr/lib/mailman/tests/test_handlers.py:%(real_name)p footer""")

I most likely read the error message wrong, but according to the error
message to me it seems it is line 105 in the file i18n.py that would
contain the unexpected format character 'p', but it doesn not contain
anything with )p

However, changing "your %(extra)smembership" to "your %(extra)s
membership" in the file /usr/lib/mailman/Mailman/Cgi/options.py have
solved the problem. Se I guess it must have been the p in smembership
that it was referring to.

Thanks for pointing out where to look.

Henrik

-Oprindelig meddelelse-
Fra: Mark Sapiro [mailto:[EMAIL PROTECTED] 
Sendt: 8. november 2006 16:44
Til: Henrik Rasmussen; mailman-users@python.org
Emne: Re: [Mailman-Users] Hit a but & use of VERP

Henrik Rasmussen wrote:
> 
>Problem 2) When calling
>[mailmanserver]/mailman/options/nyhedsbrev/[EMAIL PROTECTED]
><mailto:mailserver/mailman/options/nyhedsbrev/[EMAIL PROTECTED]>  and
>other addresses, I get the message
> 
>We're sorry, we hit a bug!
> 
>This is described a lot of places, but not exactly my problem (maybe I
>just didn't find it yet).
> 
>The error log shows:
>admin(1354): [- Traceback --]
>admin(1354): Traceback (most recent call last):
>admin(1354):   File "/usr/lib/mailman/scripts/driver", line 101, in
>run_main
>admin(1354): main()
>admin(1354):   File "/usr/lib/mailman/Mailman/Cgi/options.py", line
239,
>in main
>admin(1354): loginpage(mlist, doc, user, language)
>admin(1354):   File "/usr/lib/mailman/Mailman/Cgi/options.py", line
813,
>in loginpage
>admin(1354): table.AddRow([_("""In order to change your membership
>option, you must
>admin(1354):   File "/usr/lib/mailman/Mailman/i18n.py", line 89, in _
>admin(1354): return tns % dict
>admin(1354): ValueError: unsupported format character 'p' (0x70) at
>index 105

The code at line 813 in options.py in the 2.1.5 base is (with some
lisnes wrapped)

table.AddRow([_("""In order to change your membership option, you
must
first log in by giving your %(extra)smembership password in the
section
below.  If you don't remember your membership password, you can
have it
emailed to you by clicking on the button below.  If you just want to
unsubscribe from this list, click on the Unsubscribe
button and a
confirmation message will be sent to you.

Important: From this point on, you
must have
cookies enabled in your browser, otherwise none of your changes
will take
effect.
""")])

It appears that this has been edited in the area of
"%(extra)smembership password" creating something like %(..)p

The "%(extra)s" is a substitution that receives either "email address
and " or nothing depending on context. It can be deleted, but it can't
be changed.

-- 
Mark Sapiro <[EMAIL PROTECTED]>   The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
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=show&file=faq01.027.htp

Re: [Mailman-Users] Hit a but & use of VERP

[Henrik Rasmussen]

Thanks to both.

The trick with VERP_DELIVERY_INTERVAL = 1 did it. I thought that this
variable was for another purpose.

Henrik

-Oprindelig meddelelse-
Fra: Mark Sapiro [mailto:[EMAIL PROTECTED] 
Sendt: 8. november 2006 16:30
Til: Larry Stone; Henrik Rasmussen
Cc: mailman-users@python.org
Emne: Re: [Mailman-Users] Hit a but & use of VERP

Larry Stone wrote:

>On Wed, 8 Nov 2006, Henrik Rasmussen wrote:
>
>> I am new to Mailman. I currently have two problems.
>>
>> I am using Mailman version 2.1.5 with Postfix. I am able to send
mails
>> to the list and the mails are sent to the subscribers. According to
the
>> mail headers in the mails received from Mailman, Mailman actually
uses
>> Postfix.
>>
>> Problem 1) I would like to use VERP. I have read a number of
>> documents[1] describing how to set this up, but so far Mailman is
still
>> not using VERP, that is, the mails I receive from the list does not
seem
>> to contain any VERPed headers.
>>
>> [1]http://www.exim.org/howto/mailman21.html
>> http://www.postfix.org/VERP_README.html
>>
>> Etc. Some describes to set VERP_CONFIRMATIONS = 1 (etc.) and other
>> documents explains to set VERP_CONFIRMATIONS = Yes ,but I have tried
>> both in ~mailman/Mailman/mm_cfg.py, without luck. I have also tried
to
>> set it directly in Default.py (shame on me) but also no luck.
>
>I'm not an "expert" but I believe VERP_CONFIRMATIONS only controls
>confirmation messages like the parameter name implies.


Actually, in 2.1.5 VERP_CONFIRMATIONS only affects mass subscribe
invitations by putting the confirm token in the reply address and
creating a friendlier Subject:.


>Controlling VERPing
>of list messages is done by 1) turning on Personalization (non-digest
>options in the interface; not sure how it's done for digests) which
firt
>requires OWNERS_CAN_ENABLE_PERSONALIZATION to be set in mm_cfg.py and
2)
>setting the variables VERP_PERSONALIZED_DELIVERIES and
>VERP_DELIVERY_INTERVAL in mm_cfg.py.



You don't need to personalize the list in order to use VERP. Set

VERP_DELIVERY_INTERVAL = 1

to VERP all regular deliveries, personalized or not.

Read the VERP section in Defaults.py for more information.

-- 
Mark Sapiro <[EMAIL PROTECTED]>   The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
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=show&file=faq01.027.htp

[Mailman-Users] Hit a but & use of VERP

[Henrik Rasmussen]

I am new to Mailman. I currently have two problems.
 
I am using Mailman version 2.1.5 with Postfix. I am able to send mails
to the list and the mails are sent to the subscribers. According to the
mail headers in the mails received from Mailman, Mailman actually uses
Postfix.
 
Problem 1) I would like to use VERP. I have read a number of
documents[1] describing how to set this up, but so far Mailman is still
not using VERP, that is, the mails I receive from the list does not seem
to contain any VERPed headers.
 
[1]http://www.exim.org/howto/mailman21.html
http://www.postfix.org/VERP_README.html
 
http://mail.python.org/pipermail/mailman-users/2004-April/036006.html
http://www.python.org/cgi-bin/faqw-mm.py?req=all
/usr/share/doc/postfix-2.2.10/README_FILES/VERP_READM

Etc. Some describes to set VERP_CONFIRMATIONS = 1 (etc.) and other
documents explains to set VERP_CONFIRMATIONS = Yes ,but I have tried
both in ~mailman/Mailman/mm_cfg.py, without luck. I have also tried to
set it directly in Default.py (shame on me) but also no luck.
 
In postfix, I have tried to follow
/usr/share/doc/postfix-2.2.10/README_FILES/VERP_READM ,but I am not sure
where exactly to set up sendmail -V. I suppose it is mailman I should
set up to use sendmail -V, but I am not sure where. I figured it would
be in mm_cfg.py where I set SENDMAIL_CMD = '/usr/sbin/sendmail -V', but
this didn't do any difference. The default (in Defaults.py) is
SENDMAIL_CMD = '/usr/lib/sendmail' and I have tried this one with
SENDMAIL_CMD = '/usr/lib/sendmail -V' also. Still no luck.
 
I recall something about that VERP should have been set up at
installation, but isn't there any way to do it afterwards?
 
 
Problem 2) When calling
[mailmanserver]/mailman/options/nyhedsbrev/[EMAIL PROTECTED]
  and
other addresses, I get the message
 
We're sorry, we hit a bug!
 
This is described a lot of places, but not exactly my problem (maybe I
just didn't find it yet).
 
The error log shows:
admin(1354): [- Traceback --]
admin(1354): Traceback (most recent call last):
admin(1354):   File "/usr/lib/mailman/scripts/driver", line 101, in
run_main
admin(1354): main()
admin(1354):   File "/usr/lib/mailman/Mailman/Cgi/options.py", line 239,
in main
admin(1354): loginpage(mlist, doc, user, language)
admin(1354):   File "/usr/lib/mailman/Mailman/Cgi/options.py", line 813,
in loginpage
admin(1354): table.AddRow([_("""In order to change your membership
option, you must
admin(1354):   File "/usr/lib/mailman/Mailman/i18n.py", line 89, in _
admin(1354): return tns % dict
admin(1354): ValueError: unsupported format character 'p' (0x70) at
index 105
admin(1354): [- Python Information -]
admin(1354): sys.version =   2.3.4 (#1, Feb  6 2006, 10:38:46)
[GCC 3.4.5 20051201 (Red Hat 3.4.5-2)]
admin(1354): sys.executable  =   /usr/bin/python
admin(1354): sys.prefix  =   /usr
admin(1354): sys.exec_prefix =   /usr
admin(1354): sys.path=   /usr
admin(1354): sys.platform=   linux2

What do I do wrong?
 
Henrik
--
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=show&file=faq01.027.htp

[Mailman-Users] Changing the From field displayed to the user

[Henrik Rasmussen]

My Mailman list server is currently called
mailman.fullqualified.domain.name and this is reflected by the From
field in the mails sendt by the listsserver (From: root
[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> ). Instead I want to change the
displayed host name to list.fullqualified.domain.name in the e-mail
From: field and the webinterface.
 
Changing myhostname in the /etc/postfix/main.cf (and restarting the
Postfix server) does not work.
Changing mydomain in the /etc/postfix/main.cf (and restarting the
Postfix server) does not work.
myorigin is already set to $myhostname, so changing this would probably
not change anything either.
 
My colleague and I have read several documents, but until now we have't
found out anything usefull (in means of changing the From field).
 
Also I am uncertain whether I am suppose to make changes to the Mailman
configuration or the Postfix configuration in order to change the From
field, and there in which configuration file the changes should be made.
 
How can I set this up so the server appear as
list.fullqualified.domain.name?
 
Regards Henrik Rasmussen
--
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=show&file=faq01.027.htp