Re: [Mailman-Users] language encoding for archives

kristina clair wrote: >On 4/27/06, Mark Sapiro <[EMAIL PROTECTED]> wrote: >> >> It depends which archive pages you're talking about. The table of >> contents is rebuilt with every message and should be OK. The periodic >> (monthly) index pages are only rebuilt when a post is added so old >> period

Re: [Mailman-Users] Sender field

At 10:40 AM -0500 2006-04-27, Neal Groothuis wrote: > I would like to request that a feature be added in the next version of > Mailman to allow a list administrator to disable rewriting of the > "Sender:" header, or (better) for this behavior to be eliminated from > Mailman altogether.

Re: [Mailman-Users] language encoding for archives

On 4/27/06, Mark Sapiro <[EMAIL PROTECTED]> wrote: > kristina clair wrote: > > > >I've noticed that changing the language preference for a list will > >change the character set for the list pages, but not for the archives. > > Do I need to modify the archive templates in order to have the > >archiv

Re: [Mailman-Users] Sender field

Neal Groothuis wrote: > >I would like to request that a feature be added in the next version of >Mailman to allow a list administrator to disable rewriting of the >"Sender:" header, or (better) for this behavior to be eliminated from >Mailman altogether. The best place to make this kind of reques

Re: [Mailman-Users] language encoding for archives

kristina clair wrote: > >I've noticed that changing the language preference for a list will >change the character set for the list pages, but not for the archives. > Do I need to modify the archive templates in order to have the >archive pages use the same character set? Or is there another way?

Re: [Mailman-Users] "-owner" works, "-admin" doesn't...

Mark Sapiro wrote: > Bottom line - external messages to -owner are different from internally > crafted notices to the owner. The former have envelope sender of > -bounces@ and the latter have > envelope sender of -bounces@. > > Nothing has changed in the way these messages from Mailman have been >

Re: [Mailman-Users] the to and from addresses are the same

Gary Hall wrote: > >I would like the "To" address to that of the person receiving the notice. > >I bet it is in the FAQ's but I can't find it. It's . What did you look for that didn't find it? (So we can make it more findable.

Re: [Mailman-Users] "-owner" works, "-admin" doesn't...

Kris Wilk wrote: > >1) -owner has worked all along. Looking at the message, the Return-Path: >is "[EMAIL PROTECTED]". cheiron is the name of the shared >server my site is on. I suspect SMTP is configured to allow >"[EMAIL PROTECTED]" as a sender. > >2) My test yesterday showed that "[EMAIL PROTE

[Mailman-Users] the to and from addresses are the same

We are currently using Mailman to just send out notices to our customers. There is no way they can post at this time and that is fine. The problem we are experiencing is that the from address is correct BUT the "To" address is the same as the "From" address. I would like the "To" address to that

Re: [Mailman-Users] setting options for a list of users?

On 4/27/06, Dewhirst, Rob <[EMAIL PROTECTED]> wrote: > Is there a way I can automate setting nomail and norepro for a bunch of > users at once? add_members lets me set digest but not the other > options. Certainly, bin/withlist can accomplish this. I don't know if there's an easier way. -- - Pa

[Mailman-Users] setting options for a list of users?

Is there a way I can automate setting nomail and norepro for a bunch of users at once? add_members lets me set digest but not the other options. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailma

Re: [Mailman-Users] Message Footer

On 4/27/06, Robert Haack <[EMAIL PROTECTED]> wrote: > appear at the bottom of the message but not as an attachment. Is there > anyway to prevent this from happening? I can't be certain, but it may be that it's being sent as part of a MIME multi-part message, and your mail client happens to render

Re: [Mailman-Users] Can mm_cfg.py use includes?

> You can't just put an add_virtualhost('a','b') line in a file and > import it into mm_cfg.py, because 'add_virtualhost' is undefined in > the file you're importing. Makes sense. I was able to get it working by simply adding "from Defaults import add_virtualhost" to the top of my vmail_cfg.

Re: [Mailman-Users] delivery off

Manlio Perillo wrote: > >As a response to the "set show" command, I obtain: > >delivery off (a causa degli errori il Wed, 12 Apr 2006 01:21:46 -) > cause of errors on > > >I've tried to send a "delivery on" command, but this seems not to work. >What's the problem? Did you include

[Mailman-Users] Message Footer

We've just recently noticed that on messages that come through the mailing list that the message footer is appended to the end of the message and also as an attachment in the message. I want the footer to appear at the bottom of the message but not as an attachment. Is there anyway to prevent

Re: [Mailman-Users] "-owner" works, "-admin" doesn't...

Mark Sapiro wrote: > Yes. Your analysis seems correct. Mailman generated messages are always > sent from [EMAIL PROTECTED] > > The only thing that puzzles me is that should also be true for the > relay of the messages you sent to -owner so why did they go through? > If you send a message to -owner

[Mailman-Users] delivery off

Hi. As a response to the "set show" command, I obtain: delivery off (a causa degli errori il Wed, 12 Apr 2006 01:21:46 -) cause of errors on I've tried to send a "delivery on" command, but this seems not to work. What's the problem? Only the administrator can fix this? Than

[Mailman-Users] language encoding for archives

Hello, I've noticed that changing the language preference for a list will change the character set for the list pages, but not for the archives. Do I need to modify the archive templates in order to have the archive pages use the same character set? Or is there another way? Thanks, Kristina ---

[Mailman-Users] Sender field

To reopen an old discussion: I would like to request that a feature be added in the next version of Mailman to allow a list administrator to disable rewriting of the "Sender:" header, or (better) for this behavior to be eliminated from Mailman altogether. Rationale: - Outlook treats the Sender

Re: [Mailman-Users] [Mailman-cabal] Cannot update Mailman FAQ

On 27 Apr 2006, at 16:26, Barry Warsaw wrote: > On Thu, 2006-04-27 at 16:04 +0100, Richard Barrett wrote: >> And your point is? >> >> Of course I be deluded and imagining the error response I got back >> but then again 17 days is a long time in the life of a file's >> permissions. > > Indeed. Aft

Re: [Mailman-Users] upgrading from 2.1.5 -> 2.1.8

kristina clair wrote: > >In the UPGRADING file in the tarball for mailman 2.1.8, there are no >notes for upgrading to 2.1.8. Is that because there is nothing to >look out for? I'm upgrading from 2.1.5. There are no specific caveats for upgrading from 2.1.5 to a later release (through 2.1.8). Ba

Re: [Mailman-Users] [Mailman-cabal] Cannot update Mailman FAQ

And your point is? Of course I be deluded and imagining the error response I got back but then again 17 days is a long time in the life of a file's permissions. Richard btw: I think I have seen comments about the same problem in recent postings to the recent mailman-user archives by other

[Mailman-Users] upgrading from 2.1.5 -> 2.1.8

Hi - just a quick question: In the UPGRADING file in the tarball for mailman 2.1.8, there are no notes for upgrading to 2.1.8. Is that because there is nothing to look out for? I'm upgrading from 2.1.5. Thanks! Kristina -- Mailman-Users mailin

[Mailman-Users] Permission problem updating Mailman FAQ

To: [EMAIL PROTECTED] During the past month or so, there have been at least two periods of a few days or more each during which any attempts to commit changes to the Mailman FAQ have produced errors like the following: Sorry, an error occurred Can't writ

Re: [Mailman-Users] Cannot update Mailman FAQ

Barry Warsaw wrote: > >The only thing I can recommend is to contact the Python webmasters >([EMAIL PROTECTED]) to see if they're aware of any problems. I'm not >sure if there are logs or anything that they can check. Maybe it's a >problem with the specific issue (as opposed to a general problem).

Re: [Mailman-Users] [Mailman-cabal] Cannot update Mailman FAQ

On Thu, 2006-04-27 at 16:04 +0100, Richard Barrett wrote: > And your point is? > > Of course I be deluded and imagining the error response I got back > but then again 17 days is a long time in the life of a file's > permissions. Indeed. After I sent my response, I noticed that your original

Re: [Mailman-Users] Mailing list protection

Alan wrote: >Is there a way to protect the list in a way that ONLY admin can send >mails to the list. >Maybe with password in Subject or in some other way. See the FAQ >Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Articles 3.11 and 3.34 -- Mark Sapiro <[EMAIL PROTECTED]> The h

Re: [Mailman-Users] "-owner" works, "-admin" doesn't...

Kris Wilk wrote: > >B-I-N-G-O (I think)! The smtp-failure log has entries like: > >Seems like SMTP is rejecting mail that is supposed to have come from >"[EMAIL PROTECTED]". That address does not - and never did - >exist as a real account as far as I know. In the past (when all was >working) the

[Mailman-Users] Charset problem. cmd_confirm assumes ascii code.

Hello We have problem with confirm mail when mail body contains characters out of ascii code (range(128)). Mailman version is 2.1.5 . I think Mailman could leave the body unread when Subject contains the confirm code or at least it should stop to "end" line. If Mailman wants to check through the

[Mailman-Users] Mailing list protection

Hi, Is there a way to protect the list in a way that ONLY admin can send mails to the list. Maybe with password in Subject or in some other way. Regards Alan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/l