Patches item #820723, was opened at 2003-10-09 16:19
Message generated for change (Comment added) made by ppsys
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=820723&group_i…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Pipermail
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Richard Barrett (ppsys)
Assigned to: Nobody/Anonymous (nobody)
Summary: Mailman/pipermail/MHonArc integration patch
Initial Comment:
This patch tightly integrates the MHonArc mail-to-HTML
convertor with Mailman and its internal pipermail
archiving code.
The purpose of the patch is to produce a fusion of
(hopefully) the best features of pipermail and MHonArc
for handling Mailman mailing list archives.
For more detail see patch content or
http://www.openinfo.co.uk/mailman/patches/mhonarc/index.html
----------------------------------------------------------------------
>Comment By: Richard Barrett (ppsys)
Date: 2006-03-02 21:17
Message:
Logged In: YES
user_id=75166
mhonarc-2.1.6-0.3.patch.gz corrects a long standing omission in the code of
Mailman/Cgi/create.py which fails to get the initial setup of lists created
through the web quite right. This leads to spurious errors being logged on
message archiving until bin/arch --wipe is run for such a list affected. Lists
created with bin/newlist did not have this problem.
----------------------------------------------------------------------
Comment By: Richard Barrett (ppsys)
Date: 2005-09-23 21:45
Message:
Logged In: YES
user_id=75166
mhonarc-2.1.6-0.2.patch.gz corrects an error in the modified code of
$prefix/bin/arch introduced by the mhonarc-2.1.6-0.1.patch.gz - the
problem was not present in patches for previous MM versions. In some
circumstances, after running $prefix/bin/arch --wipe, subsequent post to a
list my be generated using the wrong archiver. Examining index pages in
the archives of a list will show if this problem has affected that list.
Reinstallation with this revised patch and rerunning $prefix/bin/arch --wipe
should resolve the problem.
----------------------------------------------------------------------
Comment By: Richard Barrett (ppsys)
Date: 2005-08-23 17:43
Message:
Logged In: YES
user_id=75166
mhonarc-2.1.6-0.1.patch.gz is a MM 2.1.6 compatible version of the patch
----------------------------------------------------------------------
Comment By: dfragos (dfragos)
Date: 2005-07-21 15:24
Message:
Logged In: YES
user_id=1310569
what about MM 2.1.6?
----------------------------------------------------------------------
Comment By: Richard Barrett (ppsys)
Date: 2004-08-03 10:04
Message:
Logged In: YES
user_id=75166
mhonarc-2.1.5-0.1.patch.gz is a MM 2.1.5 compatible version of the
patch
----------------------------------------------------------------------
Comment By: Martin Mokrejs (mmokrejs)
Date: 2004-04-19 23:53
Message:
Logged In: YES
user_id=696559
I've applied this patch(mhonarc-2.1.4-0.1.patch.gz) and it
works great for me. Would someone apply to offcial cvs tree?
Thanks.
----------------------------------------------------------------------
Comment By: Richard Barrett (ppsys)
Date: 2004-01-02 15:32
Message:
Logged In: YES
user_id=75166
mhonarc-2.1.4-0.1.patch is a MM 2.1.4 compatible version of
this patch
----------------------------------------------------------------------
Comment By: Richard Barrett (ppsys)
Date: 2003-10-22 14:32
Message:
Logged In: YES
user_id=75166
mhonarc-2.1.3-0.6.patch better supports the use of MHonArc
-saveresources option. Also fixes minor HTML syntax error in
mhonarc.mrc and author.mrc that affected generated date and
author index pages.
----------------------------------------------------------------------
Comment By: Richard Barrett (ppsys)
Date: 2003-10-14 05:49
Message:
Logged In: YES
user_id=75166
With mhonarc-2.1.3-0.4.patch, the default path to MHonArc itself
defined in Defaults.py is the empty string and, until this is
changed, the option to select MHonArc instead of pipermail for
per-list archiving is not offered on the web admin GUI.
----------------------------------------------------------------------
Comment By: Richard Barrett (ppsys)
Date: 2003-10-10 17:51
Message:
Logged In: YES
user_id=75166
Under some circumstances, when a single message is passed to
MHonArc for archiving via a pipe, MHonArc may finish its
processing and exit, closing its STDIN before the Mailman
process that invoked it has finished output of the message
to the pipe. Mistakenly, the patched pipermail code treated
this as an error. mhonarc-2.1.3-0.3.patch corrects this mistake.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=820723&group_i…
Patches item #1442025, was opened at 2006-03-02 20:32
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1442025&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: mail delivery
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Richard Barrett (ppsys)
Assigned to: Nobody/Anonymous (nobody)
Summary: List Specialisation for Support Groups
Initial Comment:
This patch modifies Mailman to address the following scenario:
1. A Mailman list to be used as the means by which a closed set of list
subcribers (support staff) can provide responses to requests for
support made by non-subscribers (customers) posting messages to the
list.
2. Requirement that the incoming posts from customers (both original
and follow up) and consequential responses from support staff should
be entirely list-centric:
a. The customer should see the response to a posting to the list as
coming from the list, not the support person that responded.
b. Any subsequent reply by the customer to a message from the list
should go back to the list.
c. Replies to customers by support staff should automatically be
distributed to the the list.
d. This should all happen by use of the basic features of typical
MUAs by both support staff and customers; use of the MUA GUI's
"Reply" button should do all that is necessary.
e. Using the list in the way described should require no or minimal
explanation to support staff and absolutely no explanation to
customers.
f. The e-mail addresses of support staff should remain hidden
behind the list address.
For more detail of implementation see:
http://www.openinfo.co.uk/mm/patches/supportlist/index.html
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1442025&group_…
Feature Requests item #1441723, was opened at 2006-03-03 00:48
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1441723&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: dmvianna (dmvianna)
Assigned to: Nobody/Anonymous (nobody)
Summary: privacy hole in password reminder
Initial Comment:
Mailman sends me password reminders in plain text. I
can disable this feature, but other users can manually
make it send a reminder just as if I had forgot the
password, with no other question being asked. If smart
enough to intercept that message, the attacker could:
1) Get my password;
2) get my IP in the mail header.
Possible solutions:
1) Some sites and programs use a "secret question"
which right answer would give the user the chance to
get a password reminder.
2) The password could be prompted in a secure html
page. I find this safer, as compared to plain text mails.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1441723&group_…