[Mailman-Users] Replacing the To:/Cc: fields?

2001-03-18 Thread Eva Isaksson

There was a functionality in majordomo that I've been missing
in mailman - the option to skip the To: and From: fields in the 
mail that is sent to the list, and to replace them with a 
standard To: header that only has the list's address in it.

I wonder whether it is at all possible to do this with mailman?
(Note: this is _not_ about setting the Reply-to field!)

In my majordomo installation, it went like this:
Instead of a generic resend script, each list would have its
own tailored resend script, resend.listname 
with these modifications:

  # skip these special headers
(...)
|| (/^to:/i)
|| (/^cc:/i)
(...)
   # add new header fields
   print OUT "To: Test Mailing List \n";

This made it possible to curb crossposting to other lists and
individuals, and to have 'cleaner' headers, from which the
list as a recipient was immediately clear. 

But mailman seems to keep any and all recipients as long as
there aren't more than are specified in max_num_recipients.

I've waded through documentation, but found no leads for this.

-- Eva
-------
 Eva Isaksson * [EMAIL PROTECTED] * [EMAIL PROTECTED]
 http://www.helsinki.fi/~eisaksso/

--
Mailman-Users maillist  -  [EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users



[Mailman-Users] UTF-8 question

2008-01-09 Thread Eva Isaksson

Recently, I was asked to set our mailman installation to utf-8.
Our server is running the debian 2.1.9 mailman package.
I did this, and it "works" -- but I have a question anyway.

I started with the current settings: default language Finnish, 
charset iso-8859-1. 

The changes made for utf-8 included:
- changing the template files and the Finnish translation file
into utf-8 with iconv.
- fixing the mm_cfg.py by making DEFAULT_CHARSET = 'UTF-8'
and copying the relevant litany of LC_DESCRIPTIONS from
Defaults.py into mm_cfg.py and setting Finnish into utf-8.

Now, the problem that keeps puzzling me:

1. Before the change, mails with charset=iso-8859-1 and
charset=utf-8 were being distributed with the charset
untouched. I figured out as this is how it should be - right?

2. As our server hosts a lot of lists (almost 400 of them)
I decided to try utf-8 out on a smaller scale first, on an 
Ubuntu server, running only a couple of lists with its standard 
mailman package, version 2.1.5. The utf-8 change was a success. 
The webpages and archive were all okay, and the charset of 
mails was untouched too.

3. As things looked promising, I decided to proceed with our
real list server. The result: 
Web pages, archive, all okay, now in utf-8.
Mails... all of them in utf-8. And I mean ALL mails.

My question: was this to be expected? Is everything meant
to be in utf-8 from now on, including the forcing of
charset=utf-8 into all list mail headers? And why didn't this 
happen neither with the iso-8859-1 settings, nor with the
Ubuntu server?


- Eva
-- 
 Eva Isaksson * [EMAIL PROTECTED] * [EMAIL PROTECTED]
 http://www.helsinki.fi/~eisaksso/
--
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] UTF-8 question

2008-01-10 Thread Eva Isaksson
Mark Sapiro:
> I'm not certain about all of this, but there are places including
> Scrubber (removing attachments and flattening a message to plain text)
> and adding msg_header and msg_footer where the character set of a
> message can be coerced.

Yes, this seems to be the case. Our lists typically have umlaut
characters in their descriptions. Here's an example:

List-Id: =?utf-8?q?Vihreiden_vaikuttajien_sis=C3=A4inen_keskustelulista?=

Using a test list, I was able to find out that a list that has
only us-ascii in its headers and msg_footer will keep the original
charset untouched. As soon as any of those has any utf-8 stuff
in it, it causes a forced charset=utf-8.

I had spent more than a week trying to figure this out, 
so it's good to find out why this happens.

- Eva
-- 
 Eva Isaksson * [EMAIL PROTECTED] * [EMAIL PROTECTED]
 http://www.helsinki.fi/~eisaksso/
--
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] Encoding problem with 2.15 to 2.18 upgrade with Finnish

2015-12-14 Thread Eva Isaksson
Hi,

I have a charset encoding problem that I'm unable to solve. I've been
reading FAQs and list archives with little success.

Our lists are in Finnish. The setup: our mailman installation uses its own
translation file that is different from the Finnish translation that comes
with the release. Because of that, mailman is on hold, and gets upgraded
manually so that we can msfmt our own mailman.po.

We have been running 2.15, on Debian, but because of the DMARC situation
it's time to upgrade to 2.18..

Our upgrades have been rather routine so far, but this time we ran into
problems. Suddenly, the character encoding was producing quite unreadable
interfaces.

Believing that the translation file was now supposed to be in utf-8 instead
of iso-8859-1 I  tried to re-encode all relevant files and change the
mm_cfg.py values accordingly. This did not help at all.

I've tried to check whether there have been any changes to mailman that
could explain this, but no luck.

- Eva Isaksson
--
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] Encoding problem with 2.15 to 2.18 upgrade with Finnish

2016-01-07 Thread Eva Isaksson
I tried to approach this problem by getting the source package from the
debian repository.
We are still running wheezy, so we need to stick to 2.1.18 for now.

When I built the package, the resulting mailman.mo file for Finnish ends up
utf-8 encoded
(which I deduced by converting it back to a .po file by msgunfmt.
The encoding seems to happen in debian/patches/91_utf8.patch
which does have a list of correct encodings, but this is what seems to
happen:
(not only to Finnish, but to all listed languages):

msgconv -t utf-8 fi/LC_MESSAGES/mailman.po | tee
fi/LC_MESSAGES/mailman.po.utf-8 | msgfmt -o fi/LC_MESSAGES/mailman.mo -

Also:
http://sources.debian.net/patches/patch/mailman/1:2.1.18-2/91_utf8.patch/
<https://mail.google.com/>

If this means that debian is forcing everything to utf-8, what should I do,
if every package comes with this forced utf-8 encoding?

Here is the trackback we got in October:

Oct 28 10:04:28 2015 (22144) Uncaught runner exception: 'utf8' codec
can't decode byte 0xe4 in position 11: invalid continuation byt
e
Oct 28 10:04:28 2015 (22144) Traceback (most recent call last):
  File "/var/lib/mailman/Mailman/Queue/Runner.py", line 119, in _oneloop
self._onefile(msg, msgdata)
  File "/var/lib/mailman/Mailman/Queue/Runner.py", line 190, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
  File "/var/lib/mailman/Mailman/Queue/IncomingRunner.py", line 130, in
_dispose
more = self._dopipeline(mlist, msg, msgdata, pipeline)
  File "/var/lib/mailman/Mailman/Queue/IncomingRunner.py", line 153, in
_dopipeline
sys.modules[modname].process(mlist, msg, msgdata)
  File "/var/lib/mailman/Mailman/Handlers/CookHeaders.py", line 239, in
process
i18ndesc = uheader(mlist, mlist.description, 'List-Id', maxlinelen=998)
  File "/var/lib/mailman/Mailman/Handlers/CookHeaders.py", line 65, in
uheader
return Header(s, charset, maxlinelen, header_name, continuation_ws)
  File "/usr/lib/python2.7/email/header.py", line 183, in __init__
self.append(s, charset, errors)
  File "/usr/lib/python2.7/email/header.py", line 267, in append
ustr = unicode(s, incodec, errors)
UnicodeDecodeError: 'utf8' codec can't decode byte 0xe4 in position 11:
invalid continuation byte


- Eva Isaksson




2016-01-05 21:29 GMT+02:00 Mark Sapiro :

> On 01/05/2016 10:42 AM, Mark Sapiro wrote:
> > On 01/05/2016 04:43 AM, Eva Isaksson wrote:
> >>
> >> This is what we see after installing the .deb:
> >>
> >> ```Uncaught runner exception: 'utf8' codec can't decode byte 0xe4 in
> >> position 11: invalid continuation byte```
> >
> >
> > Please post the entire traceback from Mailman's error log.
> >
> > Please keep this thread on the list.
>
>
> Although I can't say for sure without seeing the traceback, this may be
> similar to the situation described at
> <https://bugs.launchpad.net/mailman/+bug/1462755>.
>
> --
> 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] Encoding problem with 2.15 to 2.18 upgrade with Finnish

2016-01-07 Thread Eva Isaksson
2016-01-07 22:12 GMT+02:00 Mark Sapiro :
On 01/07/2016 11:44 AM, Mark Sapiro wrote:

> I think simply re-entering the description and saving changes will fix
> this, but you should probably go through the entire web admin UI and do
> the same for any other non-ascii strings.

Am I right in thinking that this option would mean choosing the debian utf-8
alternative? We have some 750 lists, so checking all of them would have to
happen outside the web admin UI, i.e. from command line.

> You could install Mailman from source. See the FAQ at
> <http://wiki.list.org/x/17891606> for info.

Does this allow for keeping all the settings and passwords from the old
package
installation intact? The number of lists is so big that I want to be on the
safe
side.

- Eva Isaksson
--
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] Encoding problem with 2.15 to 2.18 upgrade with Finnish

2016-01-16 Thread Eva Isaksson
I did the 2.1.18 upgrade this weekend, after some weighing of the options.
In the long run, using the Debian package is less work intensive, so
in the end my choice was the utf-8 conversion.

> The script is at <https://www.msapiro.net/scripts/recode_list> (mirrored
> at <http://fog.ccsf.edu/~msapiro/scripts/recode_list>)

To cut the long story short, the script worked without any problems.
Taking backups took more time than running the script and doing the
package upgrade.

Such a relief - thank you.

- Eva Isaksson



2016-01-08 2:55 GMT+02:00 Mark Sapiro :

> On 01/07/2016 01:20 PM, Mark Sapiro wrote:
> >
> > You can keep the Debian package with it's utf-8 character sets and
> > programmatically change all your lists so they work. In MM 2.1.19 I
> > changed the character sets for Russian and Romanian from koi8-r and
> > iso-8859-2 respectively to utf-8 because I was convinced that the former
> > character sets were not appropriate for those languages. In so doing, I
> > augmented Mailman's version updater to identify strings in list
> > attributes that were not valid utf-8 and convert them from the former
> > character set.
> >
> > This is an imperfect process. It does guarantee that all the strings in
> > list attributes are valid utf-8 encodings, but not necessarily that they
> > are 'correct'.
> >
> > I am working on a stand-alone script to do this. I will post it later
> today.
>
>
> There is now a first cut at this script. The functions that do the
> recoding are lifted straight from Mailman/versions.py so they have been
> fairly well exercised. I didn't just import them because I wanted the
> caller to know if they had changed anything and that required a minor
> addition to the top level function to return a flag.
>
> The script is at <https://www.msapiro.net/scripts/recode_list> (mirrored
> at <http://fog.ccsf.edu/~msapiro/scripts/recode_list>)
>
> Install the script in Mailman's bin/ directory and run it with the -h
> option for full info. It uses Python's argparse function and as such
> requires python 2.7.
>
> In your case, to convert all Finnish preferred_language lists strings
> from iso-8859-1 encoding to utf-8
>
> recode_list --language=fi
>
> would suffice. There are options to specify other than iso-8859-1 to
> utf-8 and to produce output about skipped or unchanged lists, but the
> defaults should be good for you and will report which lists were
> changed. In no case does it report the actual changes, just what lists
> were changed.
>
> I recommend making backups of your lists/*/config.pck files before
> running this in case something goes wrong.
>
> --
> 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


[Mailman-Users] genaliases not generating aliases

2020-12-07 Thread Eva Isaksson
I've been running mailman on an old Ubuntu server that will become defunct
in a couple of weeks. Besides of having a new cloud based server  (with
Ubuntu 20.04.1 LTS), I also need to switch from Sendmail to Postfix.

Now, setting up Postfix was not too big a problem, but getting it to work
with mailman has been challenging. Particularly, genaliases gives me a
traceback like this:

root@ardbeg:~# /var/lib/mailman/bin/genaliases
Traceback (most recent call last):
  File "/var/lib/mailman/bin/genaliases", line 124, in 
main()
  File "/var/lib/mailman/bin/genaliases", line 118, in main
MTA.create(None, quiet=True)
  File "/var/lib/mailman/Mailman/MTA/Postfix.py", line 336, in create
_do_create(mlist, ALIASFILE, _addlist)
  File "/var/lib/mailman/Mailman/MTA/Postfix.py", line 320, in _do_create
func(mlist, fp)
  File "/var/lib/mailman/Mailman/MTA/Postfix.py", line 113, in _addlist
loopaddr = Utils.ParseEmail(Utils.get_site_email(extra='loop'))[0]
  File "/var/lib/mailman/Mailman/Utils.py", line 799, in get_site_email
hostname = mm_cfg.VIRTUAL_HOSTS.get(get_domain(), get_domain())
  File "/var/lib/mailman/Mailman/Utils.py", line 794, in get_domain
return hostname.lower()
AttributeError: 'NoneType' object has no attribute 'lower'

I'm getting no alias files in the /var/lib/mailman/data/ directory, and my
list addresses are not working:

<"|/var/lib/mailman/mail/mailman post test-list"@ardbeg.xx.net>
(expanded
from ): unknown user:
"|/var/lib/mailman/mail/mailman post test-list"

I've spent quite some time checking what might be wrong with my Postfix
configuration, and trying to search for previous, similar sounding cases,
but I've reached the point of feeling quite clueless. Any help would be
really appreciated.


- Eva Isaksson

--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/


[Mailman-Users] Re: genaliases not generating aliases

2020-12-07 Thread Eva Isaksson
Thanks - part of my problem was fixed:
> DEFAULT_URL and DEFAULT_URL_HOST (set in mm_cfg.py) are also None.

Setting  DEFAULT_URL_HOST seems to have solved the genaliases
part of my problems, as I can now run the command and it generates
the files it should.


However, mailman aliases are still user unknown with
<"|/var/lib/mailman/mail/mailman post test-list"@ardbeg.xx.net>

> The alias apparently contains quotation marks, but it should not.  I
> don't know whether some program is generating them that way, or if you
> put them in.

Those are defined in the usual way as:

## test-list mailing list
test-list:  "|/var/lib/mailman/mail/mailman post test-list"

(etc.)

so I think some program is generating them, but which one?

- Eva

ma 7. jouluk. 2020 klo 16.44 Stephen J. Turnbull (
turnbull.stephen...@u.tsukuba.ac.jp) kirjoitti:

> Eva Isaksson writes:
>
>  > Now, setting up Postfix was not too big a problem, but getting it to
> work
>  > with mailman has been challenging. Particularly, genaliases gives me a
>  > traceback like this:
>
> [traceback trimmed]
>
>  >   File "/var/lib/mailman/Mailman/Utils.py", line 799, in get_site_email
>  > hostname = mm_cfg.VIRTUAL_HOSTS.get(get_domain(), get_domain())
>  >   File "/var/lib/mailman/Mailman/Utils.py", line 794, in get_domain
>  > return hostname.lower()
>  > AttributeError: 'NoneType' object has no attribute 'lower'
>
> get_domain is returning None, which means that the OS environment
> variables HTTP_HOST and SERVER_NAME are not set (this is normal) and
> DEFAULT_URL and DEFAULT_URL_HOST (set in mm_cfg.py) are also None.
> DEFAULT_URL is obsolete and normally is None, DEFAULT_URL_HOST should
> be a string (enclosed in quotes), and defaults to 'localhost'.  You
> should check what these variables are in mm_cfg.py, and if neither is
> present in mm_cfg.py, what they are in Defaults.py (you should never
> edit Defaults.py because it will get overwritten on upgrade).
>
>  > I'm getting no alias files in the /var/lib/mailman/data/ directory, and
> my
>  > list addresses are not working:
>  >
>  > <"|/var/lib/mailman/mail/mailman post test-list"@ardbeg.xx.net>
>  > (expanded
>  > from ): unknown user:
>  > "|/var/lib/mailman/mail/mailman post test-list"
>
> I'm not very familiar with Postfix configuration (Exim user), but
> pretty clearly the aliases are getting written somehow.
>
> The alias apparently contains quotation marks, but it should not.  I
> don't know whether some program is generating them that way, or if you
> put them in.
>
> It's perfectly acceptable to us for you to post your Postfix
> configuration files and mm_cfg.py, but you may consider some of the
> information (including but not limited to domain names and list names)
> sensitive.  If so, you should redact sensitive information by
> substituting fake names, or if necessary, Mark and I accept private
> mail.  (The technical conversation will continue on list; private mail
> is just a way to keep private information out of the public archives.)
>
> Regards,
> Steve
>
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/


[Mailman-Users] List URL problem

2025-03-05 Thread Eva Isaksson via Mailman-Users
Our site (which I call below ourdomain.com) has some 400 lists.
mm_cfg.py has these definitions:

DEFAULT_EMAIL_HOST = 'ourdomain.net'
DEFAULT_URL_HOST = 'lists.ourdomain.net'

All other lists behave as they should, but one of our listownes reported a
strange URL change when accessing held messages.
instead of
https://lists.ourdomain.net/cgi-bin/mailman/admindb/listname?msgid=1
the mailman interface gives
https://ourdomain.net/cgi-bin/mailman/admindb/listname?msgid=1

Also the list archive seems to have lost the "lists" part of the URL.

After trying to refresh the configuration of this list, the problem
persists. How to fix this?

- Eva
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/
Member address: arch...@jab.org