Re: [Mailman-Users] changing Digest formatting

[Mark Sapiro]

[EMAIL PROTECTED] wrote:
>
>Is there any way to remove/re-arrange the "header" that is printed with every
>digest?
>
>Send Change_Notification mailing list submissions to
> [EMAIL PROTECTED]
>
>To subscribe or unsubscribe via the World Wide Web, visit
> http://list.example.com/mailman/listinfo/list
>or, via email, send a message with subject or body 'help' to
> [EMAIL PROTECTED]
>
>You can reach the person managing the list at
> [EMAIL PROTECTED]
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of List digest..."
>
>...
>
>We're using digests for announcements and we'd rather not send all that
>information to the recipients, at least at the beginning of the message.  We
>wouldn't want them to miss the meat of the message.
>
>We'd like to get the message started with "Today's Topics".


The information you quote above is built from the masthead.txt
template. See .

If you make an empty version of that template for your list, that part
of the digest will be empty. For the plain digest, there will be no
manifest. For the MIME digest, there will still be a MIME part for the
manifest, but it will be empty.

Actually rearranging the parts so the manifest comes after "Today's
Topics" would require changes to the send_i18n_digests() function
definition in Mailman/Handlers/ToDigest.py. The manifest would still
have to come before the first message to maintain RFC 1153 compliance
of the plain digest.

-- 
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://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] Rejection notice substitution variables (member_moderation_notice)

[Rodriguez Gomez Pedro]

Hi there!,

I'm using Mailman 2.1.11 and in the context of defining the rejection
notice for moderated members (member_moderation_notice) am trying to use
substitution variables like:

%(real_name)s 
%(web_page_url)s
%(cgiext)s
%(_internal_name)s

or even if possible at all in that context :

%(user_optionsurl)s

As far as I see this is not an option now. Not being shy of modifying
the code, can anybody point me in the right direction?

Thanks,

Pedro Rodriguez Gomez



This e-mail has been scanned for all known viruses by EMEA.

--
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] Archiving is broken

[Mark Heer]

Hello,

I just noticed that archivin is no longer working on any list. last archive 
message was received last Aug 12 and I can's seem to find a reason for it.  I 
am using external archiver as can be seen in the mmcfg.py fiile and it worked 
just fine for about a month. (we just started using mailman)
 
I don't know all the info you might need but I'll include the mmcfg.py and 
whatever els I can think of.. Your help is greatly appreciated..   

I only get the following error for a few lists but in each case the ownership 
is mailman:mailman
I noted an error re: ownership problems - but mailman user and group do indeed 
own the dirs/files so that message is confusing : 
sr/local/mailman/archives/public/wan-data-transfers'
Aug 20 09:31:06 2008 (27219) Traceback (most recent call last):
  File "/usr/local/mailman/Mailman/Queue/Runner.py", line 114, in _oneloop
self._onefile(msg, msgdata)
  File "/usr/local/mailman/Mailman/Queue/Runner.py", line 185, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
  File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 133, in 
_dispose
mlist.Save()
  File "/usr/local/mailman/Mailman/MailList.py", line 568, in Save
self.CheckHTMLArchiveDir()
  File "/usr/local/mailman/Mailman/Archiver/Archiver.py", line 236, in 
CheckHTMLArchiveDir
breaklink(pubdir)
  File "/usr/local/mailman/Mailman/Archiver/Archiver.py", line 56, in breaklink
os.unlink(link)
OSError: [Errno 1] Not owner: 
'/usr/local/mailman/archives/public/wan-data-transfers'

Aug 20 09:31:06 2008 (27219) SHUNTING: 
1219249865.3392961+47525c120442e9f4bd836c09cd41c46b6feb351e



mmcfg.py:

###
# Here's where we get the distributed defaults.

from Defaults import *

##
# Put YOUR site-specific settings below this line.
MTA = 'Postfix'
POSTFIX_ALIAS_CMD = '/usr/local/postfix/sbin/postalias'
POSTFIX_MAP_CMD = '/usr/local/postfix/sbin/postmap'
ARCHIVE_TO_MBOX = 2
PUBLIC_EXTERNAL_ARCHIVER = 'ssh -e none -i $HOME/.ssh/archkey [EMAIL PROTECTED] 
%(listname)s'
PRIVATE_EXTERNAL_ARCHIVER = 'ssh  -e none -i $HOME/.ssh/archkey [EMAIL 
PROTECTED] %(listname)s'
SUBSCRIBE_POLICY = 3
VIRTUAL_HOSTS.clear()
add_virtualhost('mailman.nersc.gov','nersc.gov')
DEFAULT_EMAIL_HOST = 'nersc.gov'
DEFAULT_URL_HOST   = 'mailman.nersc.gov'

--
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] more details on broken archiving...

[Mark Heer]

I should mention that I already ran check_perms -f and the trouble remains

It appears that the archiver is not honoring the mmcfg entry:
PUBLIC_EXTERNAL_ARCHIVER = 'ssh -e none -i $HOME/.ssh/archkey [EMAIL PROTECTED] 
%(listname)s'

is there a way to manually test this routine.  The last thing done before 
archiver stopped working was to change a list archive from monthly to yearly - 
then I re-created the archive with arch --wipe.  All the old stuff is there but 
nothing new.

The shunting messages still appear in the log after the check_perms was run. I 
sent to a test list which is configured fror public archive.  It gets delivered 
to the members, not shunted aand not in the archives, and no error messages.

Thanks,

Mark
--
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] Rejection notice substitution variables(member_moderation_notice)

[Mark Sapiro]

Rodriguez Gomez Pedro wrote:
>
>I'm using Mailman 2.1.11 and in the context of defining the rejection
>notice for moderated members (member_moderation_notice) am trying to use
>substitution variables like:
>
>%(real_name)s 
>%(web_page_url)s
>%(cgiext)s
>%(_internal_name)s
>
>or even if possible at all in that context :
>
>%(user_optionsurl)s
>
>As far as I see this is not an option now. Not being shy of modifying
>the code, can anybody point me in the right direction?


You are correct that it is not currently an option because no variable
interpolation whatsoever is done on member_moderation_notice.

If you want to implement it, look at the process() function in
Mailman/Handlers/Moderate.py. You will see the following:

elif mlist.member_moderation_action == 1:
# Reject
text = mlist.member_moderation_notice
if text:
text = Utils.wrap(text)
else:
# Use the default RejectMessage notice string
text = None
raise Errors.RejectMessage, text

You can modify this to add interpolation by doing something like

elif mlist.member_moderation_action == 1:
# Reject
text = mlist.member_moderation_notice
if text:
text = Utils.wrap(text)
d = {'real_name': mlist.real_name,
 'web_page_url': mlist.web_page_url,
 'cgiext': mm_cfg.CGIEXT,
 '_internal_name': mlist.internal_name(),
 'options_url': mlist.GetOptionsURL(sender,
absolute=True),
 }
text = text % d
else:
# Use the default RejectMessage notice string
text = None
raise Errors.RejectMessage, text

Note at least one (options_url) of the above lines is wrapped by my MUA
and shouldn't be wrapped.

You can look at modules like Mailman/Handlers/Decorate.py for examples
of how this is done elsewhere.

-- 
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://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] Archiving is broken

[Mark Sapiro]

Mark Heer wrote:
>
>I only get the following error for a few lists but in each case the ownership 
>is mailman:mailman
>I noted an error re: ownership problems - but mailman user and group do indeed 
>own the dirs/files so that message is confusing : 
>sr/local/mailman/archives/public/wan-data-transfers'
>Aug 20 09:31:06 2008 (27219) Traceback (most recent call last):
>  File "/usr/local/mailman/Mailman/Queue/Runner.py", line 114, in _oneloop
>self._onefile(msg, msgdata)
>  File "/usr/local/mailman/Mailman/Queue/Runner.py", line 185, in _onefile
>keepqueued = self._dispose(mlist, msg, msgdata)
>  File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 133, in 
> _dispose
>mlist.Save()
>  File "/usr/local/mailman/Mailman/MailList.py", line 568, in Save
>self.CheckHTMLArchiveDir()
>  File "/usr/local/mailman/Mailman/Archiver/Archiver.py", line 236, in 
> CheckHTMLArchiveDir
>breaklink(pubdir)
>  File "/usr/local/mailman/Mailman/Archiver/Archiver.py", line 56, in breaklink
>os.unlink(link)
>OSError: [Errno 1] Not owner: 
>'/usr/local/mailman/archives/public/wan-data-transfers'
>
>Aug 20 09:31:06 2008 (27219) SHUNTING: 
>1219249865.3392961+47525c120442e9f4bd836c09cd41c46b6feb351e


It appears that at some point, the archive of this list
(wan-data-transfers) was changed from public to private and now
mailman is trying to remove the symlink from
/usr/local/mailman/archives/public/wan-data-transfers to
/usr/local/mailman/archives/prvate/wan-data-transfers. It is being
denied by the OS when it tries to do this.

This may be a permissions issue not checked by check_perms or it may be
a SELinux or other security policy manager issue or it may be that
IncomingRunner was not started properly (i.e. by 'mailmanctl start'
run by root) and is not running as the correct user:group.

-- 
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://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] more details on broken archiving...

[Mark Sapiro]

Mark Heer wrote:
>
>It appears that the archiver is not honoring the mmcfg entry:
>PUBLIC_EXTERNAL_ARCHIVER = 'ssh -e none -i $HOME/.ssh/archkey [EMAIL 
>PROTECTED] %(listname)s'
>
>is there a way to manually test this routine.

What do you expect it to do. What it says is login via ssh using the
specified key as user mailman to host nim.nersc.gov and pipe the
message to be archived to the command whose name is the name of the
list. Is that what you want?

You can test it with

su mailman -c 'ssh -e none -i $HOME/.ssh/archkey [EMAIL PROTECTED]
list_name < file/containing/an/email/message'

This assumes that ArchRunner which will actually be running this
command is running as user mailman as it should be.


>The last thing done before archiver stopped working was to change a list 
>archive from monthly to yearly - then I re-created the archive with arch 
>--wipe.  All the old stuff is there but nothing new.


bin/arch only works with the pipermail archive, not with external
archivers. If you rebuild a pipermail archive with bin/arch --wipe, it
will be built with all the messages currently in the archive mbox
file, but new messages will not be added to the pipermail archive
because you have an external archiver.

If you have an external archiver, the pipermail HTML archive will not
be written. It's an either/or choice. Either pipermail or external.


>The shunting messages still appear in the log after the check_perms was run.


See my reply to your prior post.


>I sent to a test list which is configured fror public archive.  It gets 
>delivered to the members, not shunted aand not in the archives, and no error 
>messages.


Not in which archive. Not in the pipermail archive is expected because
you have a specified PUBLIC_EXTERNAL_ARCHIVER. Not in the external
archive is an issue for your external archiver.

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