Re: [Mailman-Users] attachements question

[Brad Knowles]

At 2:03 PM +0900 2005-09-28, Stephen J. Turnbull wrote:

>  Why archivers don't use Message-Id for the URL, I don't know.

Because some MUAs generate message-ids that are likely to 
collide.  For some time now, I've been arguing that they should use a 
hash of the relevant information (maybe all the headers, maybe just 
selected headers, maybe the entire message, whatever is reasonable to 
assume will survive), making sure to at least include the value of 
the "Date:", "Message-ID:", and "Received:" headers as part of that 
input.

That hash would not change no matter how many times the archives 
are updated, and all published links could remain valid unless that 
particular message itself was deleted from the archives.

-- 
Brad Knowles, <[EMAIL PROTECTED]>

"Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety."

 -- Benjamin Franklin (1706-1790), reply of the Pennsylvania
 Assembly to the Governor, November 11, 1755

   SAGE member since 1995.  See  for more info.
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
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://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

[Mailman-Users] Changing the from header

[Jeremy Leonard]

We just changed from Majordomo to Mailman.

We use listserv for email announcements to members.

We need to be able to send messages from specific users.

We used to change the from header when we accepted messages in moderated 
lists.

Is there a way to do this with Mailman?

Scenario:

Joe the CEO wants a message to go to all the members of our 
organization. His secretary creates the message and sends it to the 
list. She is also the moderator of the list. In Majordomo she would 
reply to the moderate email with the moderator password in the header 
and change the From: header to the Joe CEO of company.

Is there a way to do a similar thing with Mailman?

Setting the from address to the Listserv name isn't an option.

Thanks,
Jeremy
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
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://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] Changing the from header

[Brad Knowles]

At 9:13 AM -0400 2005-09-28, Jeremy Leonard wrote:

>  Joe the CEO wants a message to go to all the members of our
>  organization. His secretary creates the message and sends it to the
>  list. She is also the moderator of the list. In Majordomo she would
>  reply to the moderate email with the moderator password in the header
>  and change the From: header to the Joe CEO of company.
>
>  Is there a way to do a similar thing with Mailman?

Nope.  At least, not without making source code modifications to 
Mailman.

This kind of thing falls under the general mail-merge/customer 
relationship management system stuff that is covered in 
.

-- 
Brad Knowles, <[EMAIL PROTECTED]>

"Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety."

 -- Benjamin Franklin (1706-1790), reply of the Pennsylvania
 Assembly to the Governor, November 11, 1755

   SAGE member since 1995.  See  for more info.
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
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://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] Changing the from header

[Christopher X. Candreva]

On Wed, 28 Sep 2005, Brad Knowles wrote:

> At 9:13 AM -0400 2005-09-28, Jeremy Leonard wrote:
> 
> >  Joe the CEO wants a message to go to all the members of our
> >  organization. His secretary creates the message and sends it to the
> >  list. She is also the moderator of the list. In Majordomo she would
> >  reply to the moderate email with the moderator password in the header
> >  and change the From: header to the Joe CEO of company.
> >
> >  Is there a way to do a similar thing with Mailman?

>   Nope.  At least, not without making source code modifications to 
> Mailman.

Wouldn't the obvious answer be to configure her mail program to send mail as 
the CEO in the first place ? This would work for not only MailMan, but any 
mailing list program, and in fact mail to individuals as well. :-)


==
Chris Candreva  -- [EMAIL PROTECTED] -- (914) 967-7816
WestNet Internet Services of Westchester
http://www.westnet.com/
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
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://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] attachements question

[John W. Baxter]

On 9/28/05 1:30 AM, "Brad Knowles" <[EMAIL PROTECTED]> wrote:

>>  Why archivers don't use Message-Id for the URL, I don't know.
> 
> Because some MUAs generate message-ids that are likely to
> collide.

In addition, the Message-Id values would have to be filtered, if used as is,
for URL-unfriendly characters (eg, Outlook Express tosses in a couple of $
characters).  Just another example of not trusting input from untrusted
sources.

The hash of Message-Id:, Date:, and Received: (all of the Received: headers)
would do, except for the case of an insane MTA--the one generating the "top"
Received: header--feeding the same message into Mailman multiple times.
Perhaps a representation of the computer's clock would help there.

There's also the small point that the presence of Message-Id: is a SHOULD,
not a MUST (some compromise in the musty past of the IETF, no doubt).

  --John


--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
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://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

[Mailman-Users] looking for information regarding the private archive session cookies

[michael dunston]

Can someone tell me where (in Mailman) the private archive session cookies are 
being set, or where I might find more information about the use of cookies for 
enforcing private archive access?  I am trying to add this level of protection 
to a swish-e search CGI.  Thanks in advance for any information or direction on 
where to look.
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
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://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] attachements question

[Brad Knowles]

At 8:50 AM -0700 2005-09-28, John W. Baxter wrote:

>  The hash of Message-Id:, Date:, and Received: (all of the Received: headers)
>  would do, except for the case of an insane MTA--the one generating the "top"
>  Received: header--feeding the same message into Mailman multiple times.
>  Perhaps a representation of the computer's clock would help there.

The top "Received:" header is added by the Mailman mailing list 
server MTA itself, and that should include the local date/time stamp 
as of the time of receipt of the message.

-- 
Brad Knowles, <[EMAIL PROTECTED]>

"Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety."

 -- Benjamin Franklin (1706-1790), reply of the Pennsylvania
 Assembly to the Governor, November 11, 1755

   SAGE member since 1995.  See  for more info.
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
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://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

[Mailman-Users] Host name problem

[Gregg Leslie]

I've recently set up mailman under SuSE Linux 9.3. When I was testing the
new machine, I had its host name set to "linux.reporterscommittee.org". Now
that it's ready (more or less) for prime time, I've changed the host name to
www.reporterscommittee.org. But all the lists still want to use the linux
address instead of the new "www" one.

When I log in to admin pages, for instance, I get redirected to the linux
address, and the page heading says "linux.reporterscommittee.org Mailing
Lists".
And all the list information sent to subscribers includes the linux address.

I've confirmed that the word linux does not appear anywhere in the mm_cfg.py
file or the sysconfig/mailman file, and it doesn't seem to be a problem with
postfix (and all the other servers running), which works fine under the
renamed setup.

Am I missing something obvious? Or do I have to kill all the lists and start
over?

Gregg 

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
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://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] 3 questions

[Mark Sapiro]

Victor Komarov wrote:
>
>I would like to do better working my Mailman 2.1.4 list.
>
>1. Is it possible to save messages with attachment in archives?


Normally, messages are processed by the 'scrubber' which saves
attachments in separate files and replaces them in the archives with
links to the files. Is this not happening in your case?


>2. My list is russian speaking. 
>So, archive page
>http://schooner.coastlandtech.com/pipermail/speleo-info
>is in KOI-8R Character Coding. 
>But each times they appear in brouser in ISO-8859-1 and user must handly to 
>change in brouser encoding to KOI-8R.
>
>Do you know the way to solve this problem?


This appears to be a problem with your web server configuration. The
archive index page contains the tag

  

but browsers don't appear to honor it. I think this is because the web
server is providing its own

 Content-Type: text/html; charset=ISO-8859-1

header which is overriding it.


>3. When I try to get the help file, I can't to get it by email...
>Come back message like this, without help file. 
>
>- Original Message - 
>From: "Victor Komarov" <>
>To: <[EMAIL PROTECTED]>
>Sent: Monday, September 26, 2005 2:33 AM
>Subject: help
>
>Do you know the way to solve this problem?


The response from the help command comes back as a multipart/mixed
message with a text/plain part containing the actual help text and a
message/rfc822 part containing the original mail to the -request
address.

I sent a message to <[EMAIL PROTECTED]> with subject
help and no message body and I got back two replies. One reply was
from [EMAIL PROTECTED] with subject (in english)
"Auto-response for your message to the "Speleo-info" mailing list" and
no message body.

The other reply was also from [EMAIL PROTECTED] and
had subject "? ? ? ??" which I guess is the
russian translation of "The results of your email commands". This
message was multipart/mixed. The first subpart was

Content-Type: text/plain; charset="koi8-r"
Content-Transfer-Encoding: base64

and was the help text - mostly in russian, but with the text for
confirm, password and who in english.

The second subpart was

Content-Type: message/rfc822

and was a copy of my original message.

If all you are seeing in the response is your original message, this
appears to be a problem with your MUA (e-mail client).


--
Mark Sapiro <[EMAIL PROTECTED]>   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://www.python.org/cgi-bin/faqw-mm.py
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://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] Host name problem

[Mark Sapiro]

Gregg Leslie wrote:

>I've changed the host name to
>www.reporterscommittee.org. But all the lists still want to use the linux
>address instead of the new "www" one.


See
>Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
article 4.29 "Existing versus new lists".


--
Mark Sapiro <[EMAIL PROTECTED]>   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://www.python.org/cgi-bin/faqw-mm.py
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://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] Customize an Auto-Respond Message

[Mark Sapiro]

Felipe wrote:

>I've searched the archives but I can't find my solution.
>I want to customize the unsubscribe message which is automatically sent.
>The text now reads:
>You have been unsubscribed. --
>
>What I want is in carets below:
> has been unsubscribed.
>---
>
>I cannot figure out how to get the name and address into the message, nor
>can I get the text to break.  Is this possible?  TIA, felipe.


I'm not sure I understand all of what you want, but the message I think
you are referring to has subject "You have been unsubscribed from the
 mailing list" (in the member's language). This is hard
coded and cannot be changed without changing the code.

The body of the message contains the text from the list's goodbye_msg
attribute (on the General Options page). This text is filled and
wrapped. You can force a paragraph break by inserting an empty line,
and you can prevent filling of a line by beginning the line with white
space.

There is no way to insert the members name or address or any other
variable info without changing code.

--
Mark Sapiro <[EMAIL PROTECTED]>   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://www.python.org/cgi-bin/faqw-mm.py
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://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] attachements question

[Stephen J. Turnbull]

> "Brad" == Brad Knowles <[EMAIL PROTECTED]> writes:

Brad> At 2:03 PM +0900 2005-09-28, Stephen J. Turnbull wrote:

>> Why archivers don't use Message-Id for the URL, I don't know.

Brad>   Because some MUAs generate message-ids that are likely
Brad> to collide.

Can we stop pandering to the broken mailers, please?  Are we not
hackers?  We know how to handle collisions.  Here's the algorithm:

1)  Look for a unique ID in the (X-)List-Archive-Message-ID field.  If
not found:
a)  Generate a unique ID according to the usual algorithm as if
the post were about to be sent from the archive host.
b)  Add it to the header in the (X-)List-Archive-Message-ID field.

2)  Extract the message ID from the message.  If none, set the program
variable equal to the ID generated in 1, and (optionally) add it as
Message-ID to the message's header.

4)  Generate the URL for the archived message based on *Message-ID*.

5)  Check for collision.

6)  If there is a collision, make a directory (could be a file-system
directory, could be just an HTML file, could be a digest message)
with the URL generated in 4.  Generate URLs for the colliding
messages based on Message-ID plus List-Archive-Message-ID, and
include them in the directory.  Conforming implementations MAY also
extract MUA information and make nasty comments about the broken
MUAs, their implementers, and their users to go with the directory.

If Message-ID == List-Archive-Message-ID, go to 1a.  At this point
a conforming implementation MAY mail /vmunix to its implementer,
who obvious snafu'ed.

7) PUT the colliding messages at those URLs.

Rationale:

1.  You could actually derive an URN from this:
archived-message://list-archive.your.org/MESSAGE-ID.

2.  The URL is unique and will persist across regeneration of the
archive as long is the message is present.

3.  People who use conformant software implemented competently should
be given precedence.

4.  Users who don't subscribe to the archiver's client but somehow get
their hands on a message ID can use Google to find it (and the
rest of the thread).

5.  People who use software that doesn't conform will suffer.

Brad> For some time now, I've been arguing that they should use a
Brad> hash of the relevant information (maybe all the headers,
Brad> maybe just selected headers, maybe the entire message,
Brad> whatever is reasonable to assume will survive), making sure
Brad> to at least include the value of the "Date:", "Message-ID:",
Brad> and "Received:" headers as part of that input.

This gives 1 and 2, but not 3, 4, and 5.  (No, you can't generate a
Google search item from knowledge of the algorithm because you don't
necessarily have the Received headers.)  Seems like overkill for Step
1 of the algorithm, too.


-- 
School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp
University of TsukubaTennodai 1-1-1 Tsukuba 305-8573 JAPAN
   Ask not how you can "do" free software business;
  ask what your business can "do for" free software.
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
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://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] attachements question

[Stephen J. Turnbull]

> "John" == John W Baxter <[EMAIL PROTECTED]> writes:

John> In addition, the Message-Id values would have to be
John> filtered, if used as is, for URL-unfriendly characters

I don't think so.  AFAIK, that was fixed about 2000 RFCs ago.  When
used as URLs, conforming agents will URL-encode them.  How the archive
chooses to implement identifying a storage location from the decoded
URL is up to it.  The URL-encoded string as filename is an obvious
choice, but database-based archives might just use the raw Message-ID.

BTW, I just realized that Google probably does index Message-IDs
already (as long as the archived message includes that header), so
Googleability is _not_ an advantage of my scheme over the header
digest approach.  The ability to algorithmically construct URNs and
URLs however still is.

John> There's also the small point that the presence of
John> Message-Id: is a SHOULD, not a MUST (some compromise in the
John> musty past of the IETF, no doubt).

I would guess that's for the convenience of folks who use "telnet HOST
25" as their MTA.  Humans are notoriously bad at generating unique
anything.  Anyway, my algorithm just treats such messages as a
collision with all the others that don't have Message-IDs.


-- 
School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp
University of TsukubaTennodai 1-1-1 Tsukuba 305-8573 JAPAN
   Ask not how you can "do" free software business;
  ask what your business can "do for" free software.
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
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://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp