I'm getting a number of errors from cron scripts similar to this:-
File /Users/mailman/cron/nightly_gzip, line 154, in ?
main()
File /Users/mailman/cron/nightly_gzip, line 110, in main
mlist = MailList.MailList(name, lock=0)
File /Users/mailman/Mailman/MailList.py, line 130, in
On Feb 11, 2007, at 6:12 PM, Mark Sapiro wrote:
Actually, I meant unsubscribe_policy, but that isn't it anyway..
There is an issue with subscribe_policy, but it doesn't impact your
present issue. It seems the policy is likely set to None, but the
mm_cfg option ALLOW_OPEN_SUBSCRIBE is set
Bill Bedford wrote:
I'm getting a number of errors from cron scripts similar to this:-
File /Users/mailman/cron/nightly_gzip, line 154, in ?
main()
File /Users/mailman/cron/nightly_gzip, line 110, in main
mlist = MailList.MailList(name, lock=0)
File
Thanks for any help on this.
We have a mailman list set-up as a newsletter type list.
We'd like to send basic html formatted email.
This seems to work seamlessly for regular subscribers - they receive the
html email that was sent.
However, digest subscribers get a message about the html being
At 8:58 AM -0800 2/13/07, Jeff Pflueger wrote:
So I'd like to resolve this problem by either
1 - Disabling the digest option (easy) and then changing all the
digest subscribers to regular subscribers (this appears to be
difficult - doing it by hand would be impossible - big list) How does
I am having a problem with Mailman. I have two test machines.
On one (Sun Solaris 10) I installed Mailman 2.1.8 and then upgraded
to 2.1.9. On the other (Ubuntu dapper), I installed the Mailman
2.1.5 package. Both installations worked after some simple fixups.
As the Ubuntu Mailman package is
Brad Knowles wrote:
At 8:58 AM -0800 2/13/07, Jeff Pflueger wrote:
2 - Somehow prevent the digests from scrubbing html
That's not really feasible. The problem is that the process of
creating the digest does all sorts of things to the message which is
not compatible with HTML. So, while
Barry Finkel wrote:
I decided to build a Ubuntu/Debian package using the Mailman 2.1.9
source. After a few problems I built a package.
I installed the package on Ubuntu, replacing the 2.1.5. When I sent
mail to one of my test lists, I got this message:
Diagnostic-Code: X-Postfix; Command died
The esteemed Brad Knowles has said:
Use the latest version of 2.4.x. As you've demonstrated, the 2.5
stuff is not yet fully baked, and Mailman 2.1.8 and earlier are not
compatible with it. $DEITY-only-knows what else they're going to
break in the process of trying to fix 2.5.
I'll
I have mailman 2.19 installed with postfix and apache2.
Almost everything is perfect except for the archives.
I have 3 test list, only one with a couple messages.
If you click on the link to go look at the archives for a list, instead of
getting the archive list, you get a files listing (ie no
Joe Comeau wrote:
Almost everything is perfect except for the archives.
I have 3 test list, only one with a couple messages.
If you click on the link to go look at the archives for a list, instead of
getting the archive list, you get a files listing (ie no index file for
apache) of the public
11 matches
Mail list logo
