Re: [Mailman-Users] DEFAULT_SUBSCRIBE_POLICY

kalin mintchev wrote: >> in the mm_cfg.py it says: >> >> from Defaults import * >> >> so that should take care of it if i change it in Defaults.py?!? Do not ever under any circumstances change Defaults.py as explained at . --

Re: [Mailman-Users] flowed.text

Jojo Almario wrote: >I had found a fix for inserted line breaks in Mailman on source fourge >( > and one of Mark Sapiro's posts), >but I don't have any idea how to apply it? I am not the admin for the >mai

Re: [Mailman-Users] Support for Cpanel users?

| For Plesk, they use an ancient version of Python, and an ancient | version of all the Python libraries, but if you know what you're | doing and you hold your mouth right while doing the correct dance | while waving a dead chicken, you can jury-rig things so that you can | actually replace th

Re: [Mailman-Users] Support for Cpanel users?

At 11:41 PM -0400 4/16/07, Michael Kabot wrote: > It might be a thought to create a FAQ on how to upgrade Cpanel/Plesk to the > latest version of Mailman and keep it up to date. I'm not familiar with > Cpanel. CPanel has made source-code level changes to the version of Mailman they ship,

Re: [Mailman-Users] DEFAULT_SUBSCRIBE_POLICY

nevermind... sorry... figured it out... thanks... > hi all... > > i'm really tired of clients batching over the subscription confirmation: > "but why?", "nobody will do it and we goanna lose people?", "it's to > difficult", "can we do it without it?!", "our list is special..", etc, > etc...

Re: [Mailman-Users] Support for Cpanel users?

[EMAIL PROTECTED] writes: > is it possible for a Server Provider to dump the cPanel version of > MM and do a source install that would work similar to the > pre-package version?? Depends on what you mean by "work similarly", of course. There are four points of view: list user, list admin, sit

Re: [Mailman-Users] Support for Cpanel users?

Ed, | Now to "stir the pot" -:), is it possible for a Server | Provider (bluehost.com is THE BEST with the BEST | "bang-for-the-buck" and the MOST responsive Tech group I have | EVER been exposed to!!) to dump the cPanel version of MM and | do a source install that would work similar to the

[Mailman-Users] DEFAULT_SUBSCRIBE_POLICY

hi all... i'm really tired of clients batching over the subscription confirmation: "but why?", "nobody will do it and we goanna lose people?", "it's to difficult", "can we do it without it?!", "our list is special..", etc, etc... so i did change the settings in Defaults.py but it's still asking f

Re: [Mailman-Users] Support for Cpanel users?

<> As a "captive" of cPanel, I feel the need to add my .02 here. Dragon is 100% correct. Even tho I don't have command access I have learned a LOT about MailMan via THIS List for which I am very grateful!! Now to "stir the pot" -:), is it possible for a Server Provider (bluehost.com is THE BE

[Mailman-Users] flowed.text

I had found a fix for inserted line breaks in Mailman on source fourge ( &aid=1495122&gro

Re: [Mailman-Users] Support for Cpanel users?

There may be some install/config specific issues for Cpanel & Plesk. At the same time, I would guess these users also have a lot of common mailman questions that have nothing to do with Cpanel/Plesk as well I'm for keeping 1 list. As I stated earlier, I'll stay on to assist with Plesk use

Re: [Mailman-Users] Support for Cpanel users?

Brad Knowles writes: > Of course, if there isn't any other resource, then CPanel users are > welcome to try to help each other through this list. +1 Such help might even leak into the FAQ occasionally. > Maybe it's also time we set up a separate mailman-cpanel-users list, > as well as a m

Re: [Mailman-Users] Support for Cpanel users?

Brad Knowles sent the message below at 12:06 4/16/2007: >Maybe it's also time we set up a separate mailman-cpanel-users list, >as well as a mailman-plesk-users list. End original message. - I see the problem with that idea being that there won't be many subsc

Re: [Mailman-Users] Support for Cpanel users?

At 7:40 PM -0500 4/15/07, Tracey McCartney wrote: > I understand from reading the archives that this is not the best place > for people to get support if they are simply administering Mailman lists > on remote hosts through Cpanel. We don't have or use CPanel ourselves, and they provide a modi

Re: [Mailman-Users] HTML causing list-wide bounce?

At 2:51 PM -0400 4/16/07, Michael Kabot wrote: > You & Paul helped me greatly, simply by suggesting it was an MTA filter - > which caused me to take a more detailed look at my system and find the Qmail > logs - which then pointed to the issue, my hosting provider's relay server > rejecting the

Re: [Mailman-Users] customizing list info pages

Dennis Morgan wrote: >After searching the archives differently I found references to >"HTMLFormater.py" and the section GetmailmanFooter > >The statement/line/what ever you call it that seems to apply reads: >innertext = _('%(listinfo_link)s list run by %(owner_link)s') > >Can I just comment that

Re: [Mailman-Users] customizing list info pages

Dennis Morgan wrote: >I have what is most likely a silly question. At the bottom of every list >info page you something like this: > run by mailuser at host.com > >Where mailuser at host.com is a mailto link to the [EMAIL PROTECTED] mailuser at host.com is the value of the list's owner attribut

Re: [Mailman-Users] customizing list info pages

After searching the archives differently I found references to "HTMLFormater.py" and the section GetmailmanFooter The statement/line/what ever you call it that seems to apply reads: innertext = _('%(listinfo_link)s list run by %(owner_link)s') Can I just comment that out with a hash? # innertext

[Mailman-Users] customizing list info pages

I have what is most likely a silly question. At the bottom of every list info page you something like this: run by mailuser at host.com Where mailuser at host.com is a mailto link to the [EMAIL PROTECTED] I would like to remove that mailto and substitute a throw away email address - one that b

Re: [Mailman-Users] HTML causing list-wide bounce?

Brad, Thanks for the pointer. I have Mailman running successfully under Plesk 8.1 including - an upgraded to the 2.1.8 release last year - mailman serving lists for virtual domains through an integration with Plesk & Qmail You & Paul helped me greatly, simply by suggesting it was an MTA fil

Re: [Mailman-Users] message archiving problem

At 9:35 PM -0400 4/15/07, Rick Pasotto wrote: > What should happen and what *does* happen evidently are not the same. You report what you see, but the description you give in your report may have little to do with what is actually happening under the hood. We need to figure out if there's anyt

Re: [Mailman-Users] HTML causing list-wide bounce?

At 4:56 PM -0400 4/15/07, Michael Kabot wrote: > I am not fluent in Qmail. Finally found the logs for Qmail which was not in > the /var/log location, but rather deep under a Plesk directory. Ahh. Plesk. See FAQ 6.15. -- Brad Knowles <[EMAIL PROTECTED]>, Consultant & Author LinkedIn Profile

Re: [Mailman-Users] Relative path rather than absolute???

David Southwell wrote: > Difficulty with list creation procedures. If I understand what follows, the problem is not with list creation, but rather it is with the icon images on all Mailman web pages. > version 2.1.9 > > > Each of the above referrer lines for the img_src are sho

Re: [Mailman-Users] message archiving problem

Stephen J. Turnbull wrote: >Mark Sapiro writes: > > > I said in my first reply > > > > A single post should be archived as one message unless it containes > > lines beginning with "From " (*nix mbox separators), but I think the > > current archiver escapes extraneous "From " lines, so even the

[Mailman-Users] Relative path rather than absolute???

Difficulty with list creation procedures. My webserver is intended to host a number of sites each one of which will provide, among other things,maillists. The primary site is www.vizion200.net. Access to www.vizion2000.net/mailman/create responds with the result that the mailing list has been cr

Re: [Mailman-Users] Can someone help me?

Calvin Muller wrote: >I'm trying to use Mailman on an Ubuntu 6.10 system with Postfix but when I >send mails it gets sent to the shunt folder, and if I try run the unshunt >command I get the following error in the /var/log/mailman/error > >Apr 15 00:42:40 2007 (21596) send_digests() failed: us-asc

Re: [Mailman-Users] Help: Digests not working after upgrade

Yasean Khan wrote: > Mark Sapiro <[EMAIL PROTECTED]> 15 April 2007 4:42 AM >>> > >Then assuming cron/sendigests is pointing at the right Mailman, a >digest should be sent or there should be some error reported in >Mailman's error log. >===> How does one check that senddigests is pointing to th

[Mailman-Users] Can someone help me?

I’m trying to use Mailman on an Ubuntu 6.10 system with Postfix but when I send mails it gets sent to the shunt folder, and if I try run the unshunt command I get the following error in the /var/log/mailman/error Apr 15 00:42:40 2007 (21596) send_digests() failed: us-ascii Apr 15 00:42:41 2007 (21

Re: [Mailman-Users] list of disabled address?

Gerardo Herzig wrote: >Hi all. I would like to know if there is some way to view all the >accounts who has been disabled (p.e. due for a bounce threshold limit >reached) for a mailman list. If you have command line access to your Mailman installation, use bin/list_members for this. See 'bin/li

[Mailman-Users] list of disabled address?

Hi all. I would like to know if there is some way to view all the accounts who has been disabled (p.e. due for a bounce threshold limit reached) for a mailman list. Thanks! Gerardo -- Mailman-Users mailing list Mailman-Users@python.org http://m

Re: [Mailman-Users] Help: Digests not working after upgrade

>>> Mark Sapiro <[EMAIL PROTECTED]> 15 April 2007 4:42 AM >>> Yasean Khan wrote: >> >>Senddigests when executed does nothing.. nothing gets written to the >>log either. > > >Is there a lists//digest.mbox file? Is the list's >digest_send_periodic attribute set to Yes? >> yes to both Then a

Re: [Mailman-Users] message archiving problem

Mark Sapiro wrote: > > What happens if you do > > bin/withlist -i > > and then at the Python (>>>) prompts type > import email email.__version__ > > It should print 2.5.8 for Mailman 2.1.9. (Type a control-D to a >>> > prompt to quit.) On my Debian "Stable" (aka "etch") system, it