Re: [Mailman-Users] Problem with mailman install

[LuKreme]

On 17-May-2009, at 19:29, Mark Sapiro wrote:

  status 4: "/usr/local/mailman/mail/mailman post listname". Command
output:
  No such file or directory


status 4 means the execve that runs python returned. The "no such file
or directory" can refer to either /usr/local/mailman/mail/mailman or
to the path to Python that the mail wrapper is using.


Very odd, the path was there, the executable was there, permissions  
where right, and python appeared to be running. I certainly didn't do  
anything to change python's settings either before or after.



See the FAQ at  to understand more about
this error.


My confusion about the error is that mailman has ALWAYS been setu for  
uid/gid mailman, and has been for years and years.



If you have a file named last_mailman_version in Mailman's data/
directory, it probably has contents

0x2010bf0

If so, change the contents to

0x20109f0


That file has the right info, it's just the ports DB that is off since  
I replaced the install from backups 'behind its back'.


--
What are you, Ghouls? There are no dead students here. This week.

--
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] Installation On Separate Server Plausible?

[Mark Sapiro]

James Reid wrote:
>
>Is this something that would become *easier* if it were done using the
>MYSQL plugin that is floating around?


If by "MYSQL plugin", you mean a MySQL Member Adaptor, then no. That
has only to do with list membership. It has nothing to do with
delivery of mail to 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
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] emails are not being sent

[Mark Sapiro]

Khalil Abbas wrote:
>
>I have a list of 15000 subscribers .. and everything was working fine till 
>like 2 weeks ago, when sending to the list and checking the mail statistics.. 
>I find out that the outgoing emails are only 9000!! I used to check the logs 
>and all the 15000 were being sent successfully .. but now it's 9000 only and 
>people has been complaining that they are not recieving my messages..


Assuming that

bin/list_members -n LISTNAME | wc -l

reports zero, and

bin/list_members -d LISTNAME | wc -l

reports zero, and

bin/list_members -r LISTNAME | wc -l

reports 15,000

and Mailman's smtp log reports something like

May 17 13:00:37 2009 (7605)  smtp to LISTNAME for 9000
recips, completed in xx.xxx seconds

check Mailman's smtp-failure 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
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] Installation On Separate Server Plausible?

[Stephen J. Turnbull]

Brad Knowles writes:

 > You can certainly configure Mailman to use your new mail-only server as 
 > the external mail interface to the world, but I think you're going to 
 > need to have some sort of mail server running on the web server machine, 
 > 
 > The only other solution I can see is to have your mail server and web 
 > server both mount and share the same file storage,
 > 
 > However, neither of these is an easy configuration to set up or 
 > maintain, at least not relative to the typical method.

Setting up a webhost MTA to talk only to the mail server host is much
easier than setting up a networked filesystem, and far more robust in
my experience.  Even if you already have networked file systems in
place, the requirements placed by mail servers, webservers, and local
users on the networked file system are rather different, and unless
you're already managing all of those on the networked file system,
trying to tune and maintain the networked file system is going to cost
way more in admin time and system down time than the internal-only MTA
on the webhost.  (But listen to Brad and Mark, not me, if they say
something different.)

--
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] mailman mali list already created

[Mark Sapiro]

Noah wrote:
>
>I am migrating my old mailman system.   mailman thinks the mailman mail 
>list is not created although it is as identified correctly by the 
>newlist program.  What is going on here?


What is/are the settings for MAILMAN_SITE_LIST in Defaults.py/mm_cfg.py?

The Defaults.py setting should be

MAILMAN_SITE_LIST = 'mailman'

Is it changed or overridden in mm_cfg.py?

-- 
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
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] Problem with mailman install

[Mark Sapiro]

LuKreme wrote:
>
>A few days ago, I tried to post a message to a list I host and got:
>
>Command died with
>status 4: "/usr/local/mailman/mail/mailman post listname". Command  
>output:
>No such file or directory


status 4 means the execve that runs python returned. The "no such file
or directory" can refer to either /usr/local/mailman/mail/mailman or
to the path to Python that the mail wrapper is using.


>I went in and tried to look at the install, but everything appeared to  
>be fine. So I tried to reinstall via portupgrade mailman.
>
>After the upgrade completed, I got this error:
>
>  Command died with
>status 2: "/usr/local/mailman/mail/mailman post gfamily". Command  
>output:
>Group mismatch error.  Mailman expected the mail wrapper script to  
>be
>executed as group "mailman", but the system's mail server executed  
>the mail
>script as group "nobody".
>
>This is odd since my current install of mailman has permissions like  
>this:


See the FAQ at  to understand more about
this error.


>So I tried
>$ export MM_USERNAME=nobody
>$ export MM_GROUPNAME=nobody
>$ export MM_USERID=65534
>
>and made sure that in pkgtools.conf I had
>
>'mail/mailman' => 'WITH_MAIL_GID=nobody',
>
>and ran the port install again, only to get the same error. At each  
>step I ran bin/check_perms and nothing was wrong.


I can't help you much with all this package specific stuff. You might
be better off asking for help using resources specific to the package
you are installing.

My guess is that the 'WITH_MAIL_GID=nobody' change should have fixed
the group mismatch problem, particularly if the prior setting was
'WITH_MAIL_GID=mailman'. Possibly the environment changes messed this
up somehow.


>Finally I just went into my backups and restored /usr/local/mailman  
>with a cp -rp and now everything works (except ports thinks I have  
>version 2.1.11)
>
>So, for future reference, what SHOULD I have done?  And does anyone  
>know how to tell ports I have 2.1.9 instead of 2.1.11?


If you have a file named last_mailman_version in Mailman's data/
directory, it probably has contents

0x2010bf0

If so, change the contents to

0x20109f0

I don't know what you SHOULD have done to fix the original problem,
since I don't know what the underlying cause was.

-- 
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
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] Installation On Separate Server Plausible?

[James Reid]

Hi Brad,

Is this something that would become *easier* if it were done using the
MYSQL plugin that is floating around?

Thanks!
James.

> on 5/14/09 8:45 PM, Carlos Williams said:
>
>> I am being told that my Postfix email server can no longer run Apache
>> on the same physical server. The management has decided for specific
>> reasons that Apache can only be installed and configured on the web
>> server, not the mail server. The mail server will simply run Postfix /
>> Dovecot.
>
> You can certainly configure Mailman to use your new mail-only server as
> the external mail interface to the world, but I think you're going to
> need to have some sort of mail server running on the web server machine,
> even if that mail server is not otherwise externally accessible.  The
> reason is because of the way that messages are handed off to Mailman --
> via e-mail.
>
> The only other solution I can see is to have your mail server and web
> server both mount and share the same file storage, so that the mail
> server can provide the message input to Mailman (as well as the
> archiving, mailing the messages back out to the subscribers, etc...),
> and the web server can provide the WebUI for interacting with Mailman.
>
>
> However, neither of these is an easy configuration to set up or
> maintain, at least not relative to the typical method.  I think we've
> got some pointers on doing this kind of thing in the FAQ and in the
> archives of this list, but there may be some details which are not clear
> to you and will need further clarification.
>
>> This will force me to move web mail (RoundCube) & MailMan to my web
>> server! My question is can I have MailMan function from scratch (no
>> data needs to be migrated to the new install) from my web server and
>> work?
>
> You still need access to the data.  You can't just install a web server
> on another machine and expect it to magically have all the data.  And
> you still need to provide some way to update that data, and you still
> need some way to provide e-mail input and output to that system.
>
> There are a few ways to solve these issues, but each has a different set
> of trade-offs, etc
>
> --
> Brad Knowles
> If you like Jazz/R&B guitar, check out
> LinkedIn Profile: my friend bigsbytracks on YouTube at
> http://preview.tinyurl.com/bigsbytracks
> --
> 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/james%40thereidsonline.com
>
> Security Policy: http://wiki.list.org/x/QIA9
>


--
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] mailman mali list already created

[Noah]

Hi there,

I am migrating my old mailman system.   mailman thinks the mailman mail 
list is not created although it is as identified correctly by the 
newlist program.  What is going on here?


r...@enabled:/usr/local/mailman# /etc/init.d/mailman start
 * Site list for mailman (usually named mailman) missing.
 * Please create it; until then, mailman will refuse to start.
r...@enabled:/usr/local/mailman# bin/newlist mailman
Create a new, unpopulated mailing list.

Usage: bin/newlist [options] [listname [listadmin-addr [admin-password]]]

Options:

-l language
--language=language
Make the list's preferred language `language', which must be a two
letter language code.

-u urlhost
--urlhost=urlhost
Gives the list's web interface host name.

-e emailhost
--emailhost=emailhost
Gives the list's email domain name.

-q/--quiet
Normally the administrator is notified by email (after a 
prompt) that

their list has been created.  This option suppresses the prompt and
notification.

-h/--help
Print this help text and exit.

You can specify as many of the arguments as you want on the command line:
you will be prompted for the missing ones.

Every Mailman list has two parameters which define the default host name for
outgoing email, and the default URL for all web interfaces.  When you
configured Mailman, certain defaults were calculated, but if you are running
multiple virtual Mailman sites, then the defaults may not be appropriate for
the list you are creating.

You also specify the domain to create your new list in by typing the command
like so:

newlist --urlhost=www.mydom.ain mylist

where `www.mydom.ain' should be the base hostname for the URL to this 
virtual

hosts's lists.  E.g. with this setting people will view the general list
overviews at http://www.mydom.ain/mailman/listinfo.  Also, www.mydom.ain
should be a key in the VIRTUAL_HOSTS mapping in mm_cfg.py/Defaults.py if
the email hostname to be automatically determined.

If you want the email hostname to be different from the one looked up by the
VIRTUAL_HOSTS or if urlhost is not registered in VIRTUAL_HOSTS, you can 
specify

`emailhost' like so:

newlist --urlhost=www.mydom.ain --emailhost=mydom.ain mylist

where `mydom.ain' is the mail domain name. If you don't specify 
emailhost but

urlhost is not in the virtual host list, then mm_cfg.DEFAULT_EMAIL_HOST will
be used for the email interface.

For backward compatibility, you can also specify the domain to create your
new list in by spelling the listname like so:

myl...@www.mydom.ain

where www.mydom.ain is used for `urlhost' but it will also be used for
`emailhost' if it is not found in the virtual host table. Note that
'--urlhost' and '--emailhost' have precedence to this notation.

If you spell the list name as just `mylist', then the email hostname will be
taken from DEFAULT_EMAIL_HOST and the url will be taken from DEFAULT_URL (as
defined in your Defaults.py file or overridden by settings in mm_cfg.py).

Note that listnames are forced to lowercase.

List already exists: mailman

--
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] emails are not being sent

[Khalil Abbas]

Hi fellas ..

I have a list of 15000 subscribers .. and everything was working fine till like 
2 weeks ago, when sending to the list and checking the mail statistics.. I find 
out that the outgoing emails are only 9000!! I used to check the logs and all 
the 15000 were being sent successfully .. but now it's 9000 only and people has 
been complaining that they are not recieving my messages..

the list has no members with "no mail" option .. and no one has been 
automatically removed due to the bounce options..

what could be the problem?

Thanks ..

_
Show them the way! Add maps and directions to your party invites. 
http://www.microsoft.com/windows/windowslive/products/events.aspx
--
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] shunting after "decoding Unicode is notsupported"

[David Newman]

On 5/17/09 5:49 PM, Mark Sapiro wrote:
> David Newman wrote:
> 
>> On 5/13/09 10:06 PM, David Newman wrote:
>>> Mailman 2.1.12
>>>
>>> Had a server crash. Built a new server, compiled MM 2.1.12 from source
>>> and restored the lists, data, and archives from a backup.
>>>
>>> Messages are going to the list but most aren't getting archived, with
>>> errors like the one pasted below.
>>>
>>> This has come up before:
>>>
>>> http://mail.python.org/pipermail/mailman-users/2007-May/057100.html
>>>
>>> I'm wary about screwing up the digests, so two questions:
> 
> 
> The above issue is the same exception, but it's a totally different
> cause.
> 
> 
>>> 1. Is there any way of clearing this error without renaming/moving the
>>> digest?
>>>
>>> 2. If I do move the digest, will the messages that didn't get archived
>>> then make it into the archive? Or will archiving work only for those
>>> messages from that point forward?
> 
> 
> This one has to be fixed in a different way. It has nothing to do with
> digests.
> 
> 
>> Sorry for replying to my own email, but I've noticed it's only HTML
>> email that produces this error, and doesn't go into the archives.
>>
>> How to remedy (without clobbering the digest, that is)?
> 
> 
> This is a known incompatibility between Mailman 2.1.12 and the Python
> email 3.0.2 package. email 3.0.2 is part of Python 2.4.4 through
> 2.4.6, and these are the only Python versions that have this problem
> with Mailman 2.1.12.
> 
> There is a long thread about this in the bug report at
>  which also contains a
> patch to (in your case) /usr/local/lib/python2.4/email/Charset.py.
> 
> There is also an Update - March 2009: about this near the bottom of the
> FAQ at  which contains a direct link to
> the Charset.py patch.
> 
> You could upgrade Python to 2.5.x or 2.6.x to fix this, but the easiest
> fix is to apply the patch to /usr/local/lib/python2.4/email/Charset.py
> and restart Mailman. Then you can run bin/unshunt to process the
> shunted messages to the archive.

Thanks, Mark. Upgrading Python and running unshunt (which previously I
didn't know about) appears to have made this archive whole. Thanks again.

dn



> 

--
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] Installation On Separate Server Plausible?

[Mark Sapiro]

Brad Knowles wrote:

>on 5/14/09 8:45 PM, Carlos Williams said:
>
>> I am being told that my Postfix email server can no longer run Apache
>> on the same physical server. The management has decided for specific
>> reasons that Apache can only be installed and configured on the web
>> server, not the mail server. The mail server will simply run Postfix /
>> Dovecot.
>
>You can certainly configure Mailman to use your new mail-only server as 
>the external mail interface to the world, but I think you're going to 
>need to have some sort of mail server running on the web server machine, 
>even if that mail server is not otherwise externally accessible.  The 
>reason is because of the way that messages are handed off to Mailman -- 
>via e-mail.


This is the best solution. I.e., run Postfix (or another MTA) on the
new Mailman/webserver and use aliases or whatever on the primary MX to
relay list mail to Mailman.

You can also do this step by having list mail delivered to mailboxes on
the primary MX and then moving the mail via pop3/imap from the
mailboxes to Mailman with fetchmail or similar, although that may be
more difficult to configure.

-- 
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
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] shunting after "decoding Unicode is notsupported"

[Mark Sapiro]

David Newman wrote:

>On 5/13/09 10:06 PM, David Newman wrote:
>> Mailman 2.1.12
>> 
>> Had a server crash. Built a new server, compiled MM 2.1.12 from source
>> and restored the lists, data, and archives from a backup.
>> 
>> Messages are going to the list but most aren't getting archived, with
>> errors like the one pasted below.
>> 
>> This has come up before:
>> 
>> http://mail.python.org/pipermail/mailman-users/2007-May/057100.html
>> 
>> I'm wary about screwing up the digests, so two questions:


The above issue is the same exception, but it's a totally different
cause.


>> 1. Is there any way of clearing this error without renaming/moving the
>> digest?
>> 
>> 2. If I do move the digest, will the messages that didn't get archived
>> then make it into the archive? Or will archiving work only for those
>> messages from that point forward?


This one has to be fixed in a different way. It has nothing to do with
digests.


>Sorry for replying to my own email, but I've noticed it's only HTML
>email that produces this error, and doesn't go into the archives.
>
>How to remedy (without clobbering the digest, that is)?


This is a known incompatibility between Mailman 2.1.12 and the Python
email 3.0.2 package. email 3.0.2 is part of Python 2.4.4 through
2.4.6, and these are the only Python versions that have this problem
with Mailman 2.1.12.

There is a long thread about this in the bug report at
 which also contains a
patch to (in your case) /usr/local/lib/python2.4/email/Charset.py.

There is also an Update - March 2009: about this near the bottom of the
FAQ at  which contains a direct link to
the Charset.py patch.

You could upgrade Python to 2.5.x or 2.6.x to fix this, but the easiest
fix is to apply the patch to /usr/local/lib/python2.4/email/Charset.py
and restart Mailman. Then you can run bin/unshunt to process the
shunted messages to the archive.

-- 
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
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] Installation On Separate Server Plausible?

[Adam McGreggor]

On Thu, May 14, 2009 at 09:45:33PM -0400, Carlos Williams wrote:
> I am being told that my Postfix email server can no longer run Apache
> on the same physical server. The management has decided for specific
> reasons that Apache can only be installed and configured on the web
> server, not the mail server. The mail server will simply run Postfix /
> Dovecot.

*tongue in cheek* use another httpd/web-server?
--
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] Installation On Separate Server Plausible?

[Brad Knowles]

on 5/14/09 8:45 PM, Carlos Williams said:


I am being told that my Postfix email server can no longer run Apache
on the same physical server. The management has decided for specific
reasons that Apache can only be installed and configured on the web
server, not the mail server. The mail server will simply run Postfix /
Dovecot.


You can certainly configure Mailman to use your new mail-only server as 
the external mail interface to the world, but I think you're going to 
need to have some sort of mail server running on the web server machine, 
even if that mail server is not otherwise externally accessible.  The 
reason is because of the way that messages are handed off to Mailman -- 
via e-mail.


The only other solution I can see is to have your mail server and web 
server both mount and share the same file storage, so that the mail 
server can provide the message input to Mailman (as well as the 
archiving, mailing the messages back out to the subscribers, etc...), 
and the web server can provide the WebUI for interacting with Mailman.



However, neither of these is an easy configuration to set up or 
maintain, at least not relative to the typical method.  I think we've 
got some pointers on doing this kind of thing in the FAQ and in the 
archives of this list, but there may be some details which are not clear 
to you and will need further clarification.



This will force me to move web mail (RoundCube) & MailMan to my web
server! My question is can I have MailMan function from scratch (no
data needs to be migrated to the new install) from my web server and
work?


You still need access to the data.  You can't just install a web server 
on another machine and expect it to magically have all the data.  And 
you still need to provide some way to update that data, and you still 
need some way to provide e-mail input and output to that system.


There are a few ways to solve these issues, but each has a different set 
of trade-offs, etc


--
Brad Knowles
If you like Jazz/R&B guitar, check out
LinkedIn Profile: my friend bigsbytracks on YouTube at
http://preview.tinyurl.com/bigsbytracks
--
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] Problem with mailman install

[LuKreme]

[oops, left something out]

This is odd since my current install of mailman has permissions like  
this:


 8 -rwxr-xr-x  1 rootmailman   7622 Jun  8  2007 add_members
 6 -rwxr-xr-x  1 rootmailman   6008 Jun  8  2007 arch
 4 -rwxr-xr-x  1 rootmailman   2569 Jun  8  2007 b4b5-archfix

mailman was compiled on my system with GID mailman, but trying to  
setup 2.1.11 with the same build options fails, so assuming I upgrade  
at some point, how do I get this to work?


--
Do not meddle in the affairs of Dragons for you are crunchy and
taste good with ketchup

--
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] Problem with mailman install

[LuKreme]

I have had mailman running for many years now, and have updated it  
semi regularly over the years (currently 2.1.9).


A few days ago, I tried to post a message to a list I host and got:

Command died with
   status 4: "/usr/local/mailman/mail/mailman post listname". Command  
output:

   No such file or directory

I went in and tried to look at the install, but everything appeared to  
be fine. So I tried to reinstall via portupgrade mailman.


After the upgrade completed, I got this error:

 Command died with
   status 2: "/usr/local/mailman/mail/mailman post gfamily". Command  
output:
   Group mismatch error.  Mailman expected the mail wrapper script to  
be
   executed as group "mailman", but the system's mail server executed  
the mail

   script as group "nobody".

This is odd since my current install of mailman has permissions like  
this:



So I tried
$ export MM_USERNAME=nobody
$ export MM_GROUPNAME=nobody
$ export MM_USERID=65534

and made sure that in pkgtools.conf I had

'mail/mailman' => 'WITH_MAIL_GID=nobody',

and ran the port install again, only to get the same error. At each  
step I ran bin/check_perms and nothing was wrong.


Finally I just went into my backups and restored /usr/local/mailman  
with a cp -rp and now everything works (except ports thinks I have  
version 2.1.11)


So, for future reference, what SHOULD I have done?  And does anyone  
know how to tell ports I have 2.1.9 instead of 2.1.11?


--
Do not meddle in the affairs of Dragons for you are crunchy and
taste good with ketchup

--
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] Mailing list + message filter problem

[Filipe Zanluca Darós]

I had set myself as a member. I thought you meant otherwise.

I receive mails sent directly to the list, but not when messages get redirected 
by the filter.


> Date: Wed, 13 May 2009 17:33:51 -0700
> From: m...@msapiro.net
> To: fzanl...@hotmail.com; mailman-users@python.org
> Subject: RE: [Mailman-Users]  Mailing list + message filter problem
> 
> Filipe Zanluca Darós wrote:
> >
> >The address t...@test.com is not a list. It is just a pop3 email account.
> >
> >They do appear in the archives at l...@test.com!
> >
> >> Does 'l...@test.com' have any eligible recipients (non-digest members
> >> with delivery enabled and in some cases not an explicit addressee and
> >> not the poster).
> >
> >Did not understand what you mean by that. But since I did not add any 
> >addresses I am guessing no.
> 
> 
> So there is no problem. The post was delivered to the list, accepted,
> archived and resent to all zero of the list members. Once there are
> some members, they will get it too.
> 
> If your confusion is that you think the list owner should have received
> something, that is an incorrect thought. The list owner is not a list
> member unless explicitly added as a member and therefore does not
> receive copies of normal posts just by being the owner.
> 
> -- 
> Mark Sapiro The highway is for gamblers,
> San Francisco Bay Area, Californiabetter use your sense - B. Dylan
> 

_
Emoticons e Winks super diferentes para o Messenger. Baixe agora, é grátis!
http://specials.br.msn.com/ilovemessenger/pacotes.aspx
--
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] Mailing list + message filter problem

[Filipe Zanluca Darós]

The address t...@test.com is not a list. It is just a pop3 email account.

They do appear in the archives at l...@test.com!

> Does 'l...@test.com' have any eligible recipients (non-digest members
> with delivery enabled and in some cases not an explicit addressee and
> not the poster).

Did not understand what you mean by that. But since I did not add any addresses 
I am guessing no.

> What's in Mailman's vette log.

I have no access to shell in server. I was not the one who installed Mailman. 
The administrator of that shell account does not know how to solve my problem 
so I looked for help myself.


Thank you!

Filipe.

> Date: Wed, 13 May 2009 08:40:28 -0700
> From: m...@msapiro.net
> To: fzanl...@hotmail.com; mailman-users@python.org
> Subject: Re: [Mailman-Users]  Mailing list + message filter problem
> 
> Filipe Daros wrote:
> >
> >For example: My main e-mail address is t...@test.com and I created a list:
> >l...@test.com. I also created a message filter that forwards any e-mail sent
> >to t...@test.com and has the word "hello" on it's subject to the list
> >l...@test.com. 
> >
> >I tried changing generic_nonmember_action to accept but it still would hold
> >the emails sent with that subject and the messages get held with the reason:
> >"Message has implicit destination".
> >
> >So again I tried changing require_explicit_destination to NO. But now when I
> >send emails with that specific word on it's subject the e-mails seem to
> >disappear.
> 
> 
> If I understand correctly, the problem is with the 'l...@test.com' list
> and the 't...@test.com' list works as expected.
> 
> Also, if I understand, you have a process external to Mailman the sees
> a post to 't...@test.com' with 'hello' in the subject and forwards it
> to 'l...@test.com', and these posts were being held for "implicit
> destination" by the 'l...@test.com' list. You then set
> require_explicit_destination to NO on 'l...@test.com' which is one way
> to avoid the "implicit destination" hold, and now the posts forwarded
> to 'l...@test.com' just "disappear".
> 
> Do they appear in the archives of 'l...@test.com'?
> 
> Does 'l...@test.com' have any eligible recipients (non-digest members
> with delivery enabled and in some cases not an explicit addressee and
> not the poster).
> 
> What's in Mailman's vette log.
> 
> See items 7, 8 and 9 in the FAQ at  for
> other possibilities.
> 
> -- 
> Mark Sapiro The highway is for gamblers,
> San Francisco Bay Area, Californiabetter use your sense - B. Dylan
> 

_
Conheça os novos produtos Windows Live! Clique aqui.
http://www.windowslive.com.br
--
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] Fetchmail with Mailman

[Bryan Humphreys]

--
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] shunting after "decoding Unicode is not supported"

[David Newman]

On 5/13/09 10:06 PM, David Newman wrote:
> Mailman 2.1.12
> 
> Had a server crash. Built a new server, compiled MM 2.1.12 from source
> and restored the lists, data, and archives from a backup.
> 
> Messages are going to the list but most aren't getting archived, with
> errors like the one pasted below.
> 
> This has come up before:
> 
> http://mail.python.org/pipermail/mailman-users/2007-May/057100.html
> 
> I'm wary about screwing up the digests, so two questions:
> 
> 1. Is there any way of clearing this error without renaming/moving the
> digest?
> 
> 2. If I do move the digest, will the messages that didn't get archived
> then make it into the archive? Or will archiving work only for those
> messages from that point forward?
> 
> Many thanks

Sorry for replying to my own email, but I've noticed it's only HTML
email that produces this error, and doesn't go into the archives.

How to remedy (without clobbering the digest, that is)?

Thanks again

dn


> 
> dn
> 
> 
> 
> 
> May 13 21:37:17 2009 (16245) Uncaught runner exception: decoding Unicode
> is not
> supported
> May 13 21:37:17 2009 (16245) 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/ArchRunner.py", line 73, in
> _dispose
> mlist.ArchiveMail(msg)
>   File "/usr/local/mailman/Mailman/Archiver/Archiver.py", line 216, in
> ArchiveMa
> il
> h.processUnixMailbox(f)
>   File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 578, in
> processU
> nixMailbox
> a = self._makeArticle(m, self.sequence)
>   File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 684, in
> _makeArt
> icle
> mlist=self.maillist)
>   File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 308, in
> __init__
> charset = message.get_content_charset(cset_out)
>   File "/usr/local/lib/python2.4/email/Message.py", line 800, in
> get_content_cha
> rset
> charset = unicode(charset, 'us-ascii').encode('us-ascii')
> TypeError: decoding Unicode is not supported
> 
> May 13 21:37:17 2009 (16245) SHUNTING:
> 1242275836.745697+2fd3997d48268b501123514
> 
> 

--
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] Installation On Separate Server Plausible?

[Carlos Williams]

I am being told that my Postfix email server can no longer run Apache
on the same physical server. The management has decided for specific
reasons that Apache can only be installed and configured on the web
server, not the mail server. The mail server will simply run Postfix /
Dovecot.

This will force me to move web mail (RoundCube) & MailMan to my web
server! My question is can I have MailMan function from scratch (no
data needs to be migrated to the new install) from my web server and
work?

My mail and web server are on the same LAN and same network/subnet,
just separate servers. They don't want IT to manage several instances
of the same application on different servers, in this case Apache.

Thanks for any input!

- Carlos
--
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] shunting after "decoding Unicode is not supported"

[David Newman]

Mailman 2.1.12

Had a server crash. Built a new server, compiled MM 2.1.12 from source
and restored the lists, data, and archives from a backup.

Messages are going to the list but most aren't getting archived, with
errors like the one pasted below.

This has come up before:

http://mail.python.org/pipermail/mailman-users/2007-May/057100.html

I'm wary about screwing up the digests, so two questions:

1. Is there any way of clearing this error without renaming/moving the
digest?

2. If I do move the digest, will the messages that didn't get archived
then make it into the archive? Or will archiving work only for those
messages from that point forward?

Many thanks

dn




May 13 21:37:17 2009 (16245) Uncaught runner exception: decoding Unicode
is not
supported
May 13 21:37:17 2009 (16245) 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/ArchRunner.py", line 73, in
_dispose
mlist.ArchiveMail(msg)
  File "/usr/local/mailman/Mailman/Archiver/Archiver.py", line 216, in
ArchiveMa
il
h.processUnixMailbox(f)
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 578, in
processU
nixMailbox
a = self._makeArticle(m, self.sequence)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 684, in
_makeArt
icle
mlist=self.maillist)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 308, in
__init__
charset = message.get_content_charset(cset_out)
  File "/usr/local/lib/python2.4/email/Message.py", line 800, in
get_content_cha
rset
charset = unicode(charset, 'us-ascii').encode('us-ascii')
TypeError: decoding Unicode is not supported

May 13 21:37:17 2009 (16245) SHUNTING:
1242275836.745697+2fd3997d48268b501123514

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