Re: [Mailman-Users] shunted messages + not delivering to list members

[Mollatt Ntini]

On 31/03/2011 02:59, Mark Sapiro wrote:

[/snip]
The lists/LISTNAME/config.pck file for the affected list is corrupted
in some way. The stored list object in this file has no msg_footer
attribute. This is an "impossible" error unless you maybe deleted it
with bin/withlist.

Can you access the web list admin interface for this list? If you can,
try to go to the Non-digest options Section and put something in
msg_footer and Submit. If this works, you can try running bin/unshunt
to process the shunted messages. Or view the messages in qfiles/shunt
with bin/show_qfiles and rm the ones you don't want and then run
bin/unshunt. This may fix the list or get you to the next error.

If the above doesn't work, you can try

bin/withlist -l LISTNAME

and then at the python>>>  prompts enter exactly


m.msg_footer = ''
m.Save()
^D


This did the trick and I am so thrilled.

The last is control-D, end of file, not the two characters ^ and D.


If you can't access the list from the web admin or run bin/withlist,
you'll have to restore the lists/LISTNAME/config.pck file from the
last good backup before this started.


Many thanks Mark, have a beautiful day ahead.

Molla.

--
A government that robs Peter to pay Paul can always depend on the 
support of Paul.

¬ George Bernard Shaw

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

Re: [Mailman-Users] Question about Mailman domain and OS X serverset-up.

[Larry Stone]

On 3/30/11 7:36 PM, Brad Knowles at b...@shub-internet.org wrote:

> I don't mean to sound pessimistic or to rain on your parade, but in both
> cases, the solution was to blow away the stuff that Apple ships, and to
> install the "real deal" code as downloaded from list.org.

I'll add that there are a number of here who run Mailman on OS X "Client".
Searching the archives, you will find full step-by-step directions for
installing it. Blowing away the Apple provided Mailman (or just ignoring it)
and installing a clean unmodified version from source will give you, on OS X
Server, the same as those of on "Client" have.

-- 
Larry Stone
lston...@stonejongleux.com
http://www.stonejongleux.com/


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

Re: [Mailman-Users] shunted messages + not delivering to list members

[Mark Sapiro]

Mollatt Ntini wrote:
>
>I have been having a rather queer problem.  I am running several lists 
>on my list server but having a problem with only one list.
[...]
>and an extract from the error log:
>
>=
>Mar 30 16:56:41 2011 (31246) SHUNTING: 
>1301496673.9261229+2fab5f43dddedddbe043032cebf1eb3a442d88a0
>Mar 30 17:01:08 2011 (31246) Uncaught runner exception: msg_footer
>Mar 30 17:01:08 2011 (31246) Traceback (most recent call last):
>   File "/usr/local/mailman/Mailman/Queue/Runner.py", line 120, in _oneloop
> self._onefile(msg, msgdata)
>   File "/usr/local/mailman/Mailman/Queue/Runner.py", line 191, in _onefile
> keepqueued = self._dispose(mlist, msg, msgdata)
>   File "/usr/local/mailman/Mailman/Queue/OutgoingRunner.py", line 74, 
>in _dispose
> self._func(mlist, msg, msgdata)
>   File "/usr/local/mailman/Mailman/Handlers/SMTPDirect.py", line 132, 
>in process
> Decorate.process(mlist, msg, msgdata)
>   File "/usr/local/mailman/Mailman/Handlers/Decorate.py", line 70, in 
>process
> footer = decorate(mlist, mlist.msg_footer, 'non-digest footer', d)
>   File "/usr/local/mailman/Mailman/MailList.py", line 146, in __getattr__
> raise AttributeError, name
>AttributeError: msg_footer
>=


The lists/LISTNAME/config.pck file for the affected list is corrupted
in some way. The stored list object in this file has no msg_footer
attribute. This is an "impossible" error unless you maybe deleted it
with bin/withlist.

Can you access the web list admin interface for this list? If you can,
try to go to the Non-digest options Section and put something in
msg_footer and Submit. If this works, you can try running bin/unshunt
to process the shunted messages. Or view the messages in qfiles/shunt
with bin/show_qfiles and rm the ones you don't want and then run
bin/unshunt. This may fix the list or get you to the next error.

If the above doesn't work, you can try

bin/withlist -l LISTNAME

and then at the python >>> prompts enter exactly

>>> m.msg_footer = ''
>>> m.Save()
>>> ^D

The last is control-D, end of file, not the two characters ^ and D.


If you can't access the list from the web admin or run bin/withlist,
you'll have to restore the lists/LISTNAME/config.pck file from the
last good backup before this started.

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

Re: [Mailman-Users] bug adding user, and archiving gets "shunted"

[Mark Sapiro]

Lucio Chiappetti wrote:

>On Wed, 30 Mar 2011, Lucio Chiappetti wrote in thread starting at
>http://mail.python.org/pipermail/mailman-users/2011-March/071332.html
>
>> and ran bin/withlist -l -a -r fix_url
>
>> I still have some problems when subscribing a new user, and concerning 
>> message archiving. I will post a separate request for clarity.
>
>After I fixed the problems described in the thread quoted above, I had
>the following problems.
>
>  - when subscribing an user (myself) to the "mailman" list via the web
>interface I get the message on the screen
>
>Bug in Mailman version 2.1.11
>We're sorry, we hit a bug!
>
>Please inform the webmaster for this site of this problem. Printing of 
>traceback and other system information has been explicitly inhibited, but 
>the webmaster can find this information in the Mailman error logs.
>
> after a while *root* (not me as "mailman-owner" !!) receives a message
> to visit the list control page to accept the subscription request,
> but such page has no pending requests
>
>  - when subscribing an user (myself) to any other list via the web
>interface I get the same "bug" message, but after a while I receive
>the confirmation message, and if I confirm the welcome message,
>and are subscribed
>
>  - I removed ALL lists, because "mailman" was created with newlist
>before I ran fix_url. When I recreate it with newlist, also mailman
>behaves as any other list i.e.
>
> - "bug message" on the screen
> - nevertheless confirmation e-mail
> - and regular welcome if I confirm
>
>what stuff in /var/lib/mailman/logs/error is relevant ?



Potentially all of it from one such error, but most problems can be
diagnosed with just the python traceback from the error. In some
cases, the web server information is helpful for errors in CGIs.


>The other question is that if I send a message to a list, the member
>receive it, but the message is NOT archived.
>
>I see that a file appears in qfiles/shunt/


Here again, there will be an error and a python traceback associated
with the shunted message. Archiving issues are often permission
problems. Have you run Mailman's bin/check_perms? In any case, the
traceback is needed to say more.


>Note that I did not install any crontab (since my machine is just a test 
>arrangement). Are crontabs necessary for the archiver ?


No. None of the cron jobs are required for Mailman's basic operation.
There should be a crontab.in file in Mailman's cron/ directory that
has more detail as to what the individual crons do.


>Is there any FAQ or doc which describes what is in logs and qfiles, and 
>how to interpret and dispose of it ?


There's probably some, but not collected in one place :(

See the mmdsr script in the contrib/ directory for a daily log analysis
program.


>In particular how do I get rid of all old stuff there (other than doing it 
>manually), so that I'll have only errors after a fresh restart ?


There should be no "old stuff" other than logs which are normally
handled by logrotate.

On my test/development system, I have a shell script to copy /dev/null
to all the logs, but you can simply rm them as they will be
automatically created when written.

There is a cron job called cull_bad_shunt if your MM is recent enough.
See the documentation for BAD_SHUNT_* settings in Defaults.py.


>What material from logs/error or qfiles/shunt should be posted to this 
>list for diagnostics (if any) ?


Most likely nothing from qfiles/shunt. These are the messages that
couldn't be completely processed due to some exception. After the
underlying issue is fixed, you can finish processing the message by
running bin/unshunt. If you run bin/unshunt before fixing the
underlying issue, the message will be shunted again. To view the files
use bin/show_qfiles or bin/dumpdb. show_qfiles displays only the
message and accepts multiple file arguments. dumpdb only accepts a
single file, but also dumps the metadata associated with the queue
entry.

For logs/error, for a shunted message, post the python exception and
the entire traceback. For a CGI error, it's safest to post everything
with the timestamp of the error, but if there is sensitive information
in the web server or python configuration sections, it is OK to mung
it as long as the munging is obvious. You don't have to post more than
one traceback if they are the same.

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

Re: [Mailman-Users] Question about Mailman domain and OS X serverset-up.

[Brad Knowles]

On Mar 30, 2011, at 6:15 PM, JRC Groups wrote:

> Is there anyone on the list who is familiar with both OS X Server and
> Mailman to help with this problem ? I am willing to pay a consultation fee
> to someone who can connect to my server remotely and help solve this issue.

I've been an Apple consultant, at least part-time.  I came within a hairs 
breadth of doing that job full-time for a local Apple VAR.  I've got all the 
PDF versions of all the official Apple documentation on Mac OS X and Mac OS X 
Server, as well as PDF versions of the good 3rd party books on the subject.  
And I've been a professional Unix system administrator and consultant for over 
twenty years.

The guy who used to run lists.apple.com was involved in the development and 
support of Mailman long before I came along, and has more experience in the 
business than I do.

I don't mean to sound pessimistic or to rain on your parade, but in both cases, 
the solution was to blow away the stuff that Apple ships, and to install the 
"real deal" code as downloaded from list.org.


The Mailman project is freely available open source (under a GNU license, no 
less), and the support we provide is best effort.  There is no commercial 
version of Mailman that we sell or officially support.  Anyone else that 
includes Mailman as part of a commercial product or service that they sell, 
should include with that a full after-sales support staff.


Note that there isn't going to be a separate "Server" edition of Mac OS X 
"Lion".

No one seems to know if this means that all the stuff that the "Server" edition 
used to include will now be available to everyone, and that all the people who 
developed the "Server" edition of Mac OS X have been transitioned over to the 
mainline code development team, or if that means that a lot of products and 
services will get thrown out the door as Apple re-focuses exclusively on the 
retail/home user market.

But that is certainly something that you should keep in mind as you look 
towards solutions in this space.

--
Brad Knowles 
LinkedIn Profile: 

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

Re: [Mailman-Users] cannot add user or create mailing list

[Mark Sapiro]

Lucio Chiappetti wrote:

>Please advise if preferred policy on this list is reply to all or reply to 
>list, and excuse if I did wrong.


There is no policy per se. I prefer reply to all, and it seems to me,
although I haven't actually counted in any rigorous way, that most
long time members of this list do too. My reasons for preferring reply
to all are:

1) Tt keeps digest subscribers who post up to date on replies to their
posts and can facilitate their replying to replies.

2) Although the list policy is that posting is restricted to list
members, non-member posts are sometimes accepted, and reply to all
includes the non-member poster.

3) It is not a burden for most list members as they have set their
duplicate avoidance appropriately for their preference.


>On Tue, 29 Mar 2011, Mark Sapiro wrote:
>> Lucio Chiappetti wrote:
>
[...]
>
>>> (QUESTION 5)
>>> The arrangement on the target system will be more complicated.
>
>because our aliases are mantained on the NIS master server. The master and 
>slave servers are also the domain main and backup MX.
>
>However the web server is on a third machine. A configuration like the one 
>I use on my test machine (local sendmail aliases inherited from local 
>mailman aliases, which "pipe" into local mailman executables) is likely 
>to work there ...
>
>... but we'd have to expose somehow this machine name in the e-mail 
>address (we currently mask all behind the domain) or replicate all mailman 
>aliases in the NIS maps as
>
>x: x@mailmanhost
>
>but I do understand we cannot use a CNAME for mailmanhost ?


There is no Mailman restriction per se, but there is an email standard
(RFC 1123, STD 3) that is clear that the names in MX records must have
A records, not CNAME. See the FAQ at  for
some of the consequences.

I don't think I actually understand the configuration or what the
problem is.

Ultimately, mail to a list must be delivered to the Mailman machine,
but I don't understand why the existing MXs can't relay it there or
can they?

-- 
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
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] shunted messages + not delivering to list members

[Mollatt Ntini]

Dear List,

I have been having a rather queer problem.  I am running several lists 
on my list server but having a problem with only one list. I have gone 
through my server and tried to compare configs and have done check_perms 
but have found no clue as to why it is failing to deliver to list 
members and yet it is archiving properly. Looking through the logs i 
have seen that the messages are being shunted. Being a newbie would 
someone please point me in the right direction. Below is my list server 
information:



FreeBSD 8.0
Exim 4.69
Python 2.6.2
Mailman 2.1.2


and an extract from the error log:

=
Mar 30 16:56:41 2011 (31246) SHUNTING: 
1301496673.9261229+2fab5f43dddedddbe043032cebf1eb3a442d88a0

Mar 30 17:01:08 2011 (31246) Uncaught runner exception: msg_footer
Mar 30 17:01:08 2011 (31246) Traceback (most recent call last):
  File "/usr/local/mailman/Mailman/Queue/Runner.py", line 120, in _oneloop
self._onefile(msg, msgdata)
  File "/usr/local/mailman/Mailman/Queue/Runner.py", line 191, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
  File "/usr/local/mailman/Mailman/Queue/OutgoingRunner.py", line 74, 
in _dispose

self._func(mlist, msg, msgdata)
  File "/usr/local/mailman/Mailman/Handlers/SMTPDirect.py", line 132, 
in process

Decorate.process(mlist, msg, msgdata)
  File "/usr/local/mailman/Mailman/Handlers/Decorate.py", line 70, in 
process

footer = decorate(mlist, mlist.msg_footer, 'non-digest footer', d)
  File "/usr/local/mailman/Mailman/MailList.py", line 146, in __getattr__
raise AttributeError, name
AttributeError: msg_footer
=

Best regards,

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

Re: [Mailman-Users] Question about Mailman domain and OS Xserverset-up.

[Mark Sapiro]

JRC Groups wrote:
>
>The problem that keeps throwing me off is the problem we discussed here
>before. The list info page keeps reverting back to the name of the server
>instead of the name of the domain. I have, as you suggested, edited the
>mailman configuration file several times and every time I do it the info
>page changes to displaying the domain name associated with the list on the
>page. But as soon as I do anything in OS X Server's System Administration
>tool it reverts back to the server's name.


This is some Apple thing. I can't help you with it, but perhaps someone
else on this list can.


>I've been told it could be related to way I have OS X Server set-up. Based
>on a discussion I have had with another Apple Consultant I have even
>considered downloading Mailman and doing a fresh install to use this version
>instead of the one that Apple bundles with OS X. However I am afraid that
>(1) this could cause some type of conflict and (2) if the problem is related
>to some of my settings in OS X Server it may not work just as the bundled
>version doesn't.


I can't answer number 2 one way or the other, but for number 1, see the
FAQ at .

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

Re: [Mailman-Users] Question about Mailman domain and OS X serverset-up.

[JRC Groups]

Thank you Mark and Brad for your replies.

>From what I can tell rDNS seems to be working properly. I've created some
lists and they also seem to be working well. I used some test e-mails
(e-mail accounts I have) and received welcome e-mail from the lists after
subscribing.

The problem that keeps throwing me off is the problem we discussed here
before. The list info page keeps reverting back to the name of the server
instead of the name of the domain. I have, as you suggested, edited the
mailman configuration file several times and every time I do it the info
page changes to displaying the domain name associated with the list on the
page. But as soon as I do anything in OS X Server's System Administration
tool it reverts back to the server's name.

I've been told it could be related to way I have OS X Server set-up. Based
on a discussion I have had with another Apple Consultant I have even
considered downloading Mailman and doing a fresh install to use this version
instead of the one that Apple bundles with OS X. However I am afraid that
(1) this could cause some type of conflict and (2) if the problem is related
to some of my settings in OS X Server it may not work just as the bundled
version doesn't.

Is there anyone on the list who is familiar with both OS X Server and
Mailman to help with this problem ? I am willing to pay a consultation fee
to someone who can connect to my server remotely and help solve this issue.

Thank you in advance,

Joe




On 3/28/11 1:27 PM, "Mark Sapiro"  wrote:

> JRC Groups wrote:
>> 
>> While discussing some possible DNS set-up issues I might need to resolve on
>> my server a certain IT professional mentioned to me that Mailman shouldn't
>> be run using a virtual domain. I am not sure if this professional was
>> referring to virtual domains in general or only those running on Mac OS X
>> Server.
> 
> 
> Just a quick addendum to Brad's response. From the point of view of the
> mail server rather than Mailman, There should be full circle DNS.
> I.e., an rDNS lookup of the server's IP address should give a
> host/domain name and a lookup of that name should return an A record
> (not a CNAME) with the same IP. Also, when sending mail, the server
> should identify itself in HELO with the same name.
> 
> These things should be true for any mail server regardless of Mailman.
> 
> Now if a mailman list is in a virtual domain, the envelope sender of
> messages from that list will be the virtual domain. This is fine, but
> if the virtual domain publishes an SPF record, it needs to specify the
> server's name as a permitted sender.


--
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] bug adding user, and archiving gets "shunted"

[Lucio Chiappetti]

On Wed, 30 Mar 2011, Lucio Chiappetti wrote in thread starting at
http://mail.python.org/pipermail/mailman-users/2011-March/071332.html


and ran bin/withlist -l -a -r fix_url


I still have some problems when subscribing a new user, and concerning 
message archiving. I will post a separate request for clarity.


After I fixed the problems described in the thread quoted above, I had
the following problems.

 - when subscribing an user (myself) to the "mailman" list via the web
   interface I get the message on the screen

Bug in Mailman version 2.1.11
We're sorry, we hit a bug!

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


after a while *root* (not me as "mailman-owner" !!) receives a message
to visit the list control page to accept the subscription request,
but such page has no pending requests

 - when subscribing an user (myself) to any other list via the web
   interface I get the same "bug" message, but after a while I receive
   the confirmation message, and if I confirm the welcome message,
   and are subscribed

 - I removed ALL lists, because "mailman" was created with newlist
   before I ran fix_url. When I recreate it with newlist, also mailman
   behaves as any other list i.e.

- "bug message" on the screen
- nevertheless confirmation e-mail
- and regular welcome if I confirm

   what stuff in /var/lib/mailman/logs/error is relevant ?

The other question is that if I send a message to a list, the member
receive it, but the message is NOT archived.

   I see that a file appears in qfiles/shunt/

Note that I did not install any crontab (since my machine is just a test 
arrangement). Are crontabs necessary for the archiver ?



Is there any FAQ or doc which describes what is in logs and qfiles, and 
how to interpret and dispose of it ?


In particular how do I get rid of all old stuff there (other than doing it 
manually), so that I'll have only errors after a fresh restart ?


What material from logs/error or qfiles/shunt should be posted to this 
list for diagnostics (if any) ?


--

Lucio Chiappetti - INAF/IASF - via Bassini 15 - I-20133 Milano (Italy)

L'Italia ripudia la guerra [...] Italy repudiates war [...]
come mezzo di risoluzione delle   as a way of resolution of
controversie internazionali international controversies
 [Art. 11 Constitution of the Italian Republic]

For more info : http://www.iasf-milano.inaf.it/~lucio/personal.html

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

Re: [Mailman-Users] cannot add user or create mailing list

[Lucio Chiappetti]

Please advise if preferred policy on this list is reply to all or reply to 
list, and excuse if I did wrong.



On Tue, 29 Mar 2011, Mark Sapiro wrote:

Lucio Chiappetti wrote:



Recently I decided to make an experiment, so I installed mailman 2.1.11
via the suse 11.3 distribution on my machine.



When you install a downstream packaged Mailman, it is best to refer
first to any documentation the packager provides.


yes thanks, that will be file /usr/share/doc/packages/mailman/README.SuSE
(somewhat hidden and unannounced, but it is there)


APACHE_SERVER_FLAGS in /etc/sysconfig/apache2, but I have no documentation
for it, and it seems that the site can be accessed ok

(QUESTION 1)
Any Suse user can confirm this is unnecessary ?


De facto I found out that this flag is documented in README.SuSE. A 
command a2enflag (NOT applied during yast installation) applies all 
necessary changes to apache .conf files. They are equivalent to what I 
did, but simpler to use. So I reset things and did it, and will recommend 
that for our final installation.


--> question 1 solved



--

Concerning sendmail, I followed the "method 2" (WITHOUT mm_handler)



So all this seems to be working.


  yes. After I posted to mailman-users I also verified that creation of
  another list, adding members, removing members or lists via the
  linemode commands in mailman/bin also do work

  problems below appl(ied) only to the web interface


(QUESTION 2)
I hope the fact I always use the same test password is not a problem



unless you have ALLOW_SITE_ADMIN_COOKIES = Yes in
mm_cfg.py, this probably doesn't matter.


  thanks


--

At this point I entered the admin web page of such a list [...]
If I try to subscribe via the mailman/listinfo/mailman page, I get instead
an error "you must supply a valid e-mail address"

(QUESTION 3)
Why does that happen ? see also question 4



--

(QUESTION 4)

I tried also to create a new mailing list via the web interface (this
requires supplying the site password as well)

this gives me instead an error
"Unknown virtual host: sax.iasf-milano.inaf.it "



You are accessing the create CGI via a URL with host
sax.iasf-milano.inaf.it, but the only host known to Mailman is
poseidon.lambrate.inaf.it.


I have read the FAQ entries. I changed mm_cfg.py first from


DEFAULT_EMAIL_HOST = 'poseidon.lambrate.inaf.it'
DEFAULT_URL_HOST = 'poseidon.lambrate.inaf.it'


to

DEFAULT_URL_HOST = 'sax.iasf-milano.inaf.it'
DEFAULT_EMAIL_HOST = 'lambrate.inaf.it'

and ran bin/withlist -l -a -r fix_url

and finally to

DEFAULT_URL_HOST = 'sax.iasf-milano.inaf.it'
DEFAULT_EMAIL_HOST = 'poseidon.lambrate.inaf.it'

and did the same.

The first case (sax/lambrate) is similar to what we wish on the target 
system (a web server name, and the domain name as mail host)


The second case (sax/poseidon) is necessary in the test arrangement
to create valid e-mail addresses.

Both *mostly* work (if I use a list@poseidon type address for posting)
in the sense that the web interface works (so URL_HOST is what solves
questions 3 and 4.

I still have some problems when subscribing a new user, and concerning 
message archiving. I will post a separate request for clarity.




(QUESTION 5)
The arrangement on the target system will be more complicated.


because our aliases are mantained on the NIS master server. The master and 
slave servers are also the domain main and backup MX.


However the web server is on a third machine. A configuration like the one 
I use on my test machine (local sendmail aliases inherited from local 
mailman aliases, which "pipe" into local mailman executables) is likely 
to work there ...


... but we'd have to expose somehow this machine name in the e-mail 
address (we currently mask all behind the domain) or replicate all mailman 
aliases in the NIS maps as


x: x@mailmanhost

but I do understand we cannot use a CNAME for mailmanhost ?


--

Lucio Chiappetti - INAF/IASF - via Bassini 15 - I-20133 Milano (Italy)

L'Italia ripudia la guerra [...] Italy repudiates war [...]
come mezzo di risoluzione delle   as a way of resolution of
controversie internazionali ? international controversies ?
 [Art. 11 Constitution of the Italian Republic]

For more info : http://www.iasf-milano.inaf.it/~lucio/personal.html

--
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%40pytho

Re: [Mailman-Users] Installing latest Mailman updates via automaticbash script file possible?

[Adam McGreggor]

On Wed, Mar 30, 2011 at 08:19:46AM -0700, Mark Sapiro wrote:
> René Linke wrote:
> >In one of a short news of the upcoming Ubuntu 11.04 is the latest
> >Mailman version available then. My provider don't accept any Kernel
> >upgrades.
> 
> This is really a Debian/Ubuntu question and not a mailman question, but
> how about
> 
> apt-get update mailman

Or find a PPA (there are a couple out there), and whack the necessary
lines in sources.list(5), then

apt-get update && apt-get (upgrade|install) mailman

 -- you may need to check pinning (see 'man apt_preferences')

Those with a more cavalier streak may find grabbing the .deb for a
newer (base) version and thence 'dpkg -i''ing the .deb works, ( a
drawback is you won't necessarily get security updates), or indeed,
looking in backports.

YMMV.


-- 
"Of course we are not patronising women. We are just going to explain to
  them, in words of one syllable, what it is all about."
-- Olga Maitland
--
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

Re: [Mailman-Users] Installing latest Mailman updates via automatic bash script file possible?

[Mark Sapiro]

Michael Capelle wrote:

>I also would like to know this to, and if someone can, please give me
>step-by-step on how to update mailman, that would be great.


If you have a packaged Mailman, you use the pacgage tool (apt-get, yum,
etc.) appropriate for your distribution/package.

If your mailman is installed from source, the steps are:

1. Obtain the source you want. Download and unpack a tarball or run a
"bzr export" to get the source directly from lp:mailman/2.1.

2. Go to the directory containing the Mailman source.

3. Read the NEWS file for information about changes.

3.5 If you have any local patches that are still applicable, install
them now.

4. Run ./configure with exactly the same options as when you initially
coffigured and installed Mailman.

5. Stop Mailman. Some people will also advocate stopping the MTA and
web server at this point, but the window in which the MTA could be
affected is extremely short and even if the MTA tried to execute the
mail wrapper just as it was being updated, it would probably result in
a retryable SMTP error. Likewise, unless you have heavy Mailman web
traffic, the likelyhood of a problem due to Mailman being updated
while a CGI was being executed is small. I don't stop either the MTA
or web server.

6. Run make install

7. Start Mailman

I put steps 5, 6 and 7 in a shell script to minimize the time Mailman
is not running. I also review Mailman's logs after step 7 to make sure
there are no immediate problems.

This process should be all that's required for upgrading from any 2.1.x
version to a later 2.1.x version, but if your current version is 2.1.4
or older, see the UPGRADING file in the source directory.

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

Re: [Mailman-Users] Installing latest Mailman updates via automaticbash script file possible?

[Mark Sapiro]

René Linke wrote:
>
>I'm a new here on this list and new on the Linux world. :-)
>
>Using for a web project a virtual server with Ubuntu 10.04.2 LTS, and
>installed is from the Ubuntu package sources Mailman version 2.1.13.
>
>In one of a short news of the upcoming Ubuntu 11.04 is the latest
>Mailman version available then. My provider don't accept any Kernel
>upgrades.
>
>My question: It's possible with a bash script to update largely and to
>minimize the administration process automatically?
>
>For the beginners in this area, it seems the English documentation is
>not really easy to use it manually.
>
>Thanks for tips and tricks.


This is really a Debian/Ubuntu question and not a mailman question, but
how about

apt-get update mailman

?

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

Re: [Mailman-Users] Installing latest Mailman updates via automatic bash script file possible?

[Michael Capelle]

I also would like to know this to, and if someone can, please give me 
step-by-step on how to update mailman, that would be great.
- Original Message - 
From: "René Linke" 

To: "Mailman Users List" 
Sent: Tuesday, March 29, 2011 4:33 AM
Subject: [Mailman-Users] Installing latest Mailman updates via automatic 
bash script file possible?



Hi all,

I'm a new here on this list and new on the Linux world. :-)

Using for a web project a virtual server with Ubuntu 10.04.2 LTS, and
installed is from the Ubuntu package sources Mailman version 2.1.13.

In one of a short news of the upcoming Ubuntu 11.04 is the latest
Mailman version available then. My provider don't accept any Kernel
upgrades.

My question: It's possible with a bash script to update largely and to
minimize the administration process automatically?

For the beginners in this area, it seems the English documentation is
not really easy to use it manually.

Thanks for tips and tricks.

--
Best regards,
René

--
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/michael.capelle%40charter.net 


--
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] Installing latest Mailman updates via automatic bash script file possible?

[René Linke]

Hi all,

I'm a new here on this list and new on the Linux world. :-)

Using for a web project a virtual server with Ubuntu 10.04.2 LTS, and
installed is from the Ubuntu package sources Mailman version 2.1.13.

In one of a short news of the upcoming Ubuntu 11.04 is the latest
Mailman version available then. My provider don't accept any Kernel
upgrades.

My question: It's possible with a bash script to update largely and to
minimize the administration process automatically?

For the beginners in this area, it seems the English documentation is
not really easy to use it manually.

Thanks for tips and tricks.

-- 
Best regards,
René

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