Feature Requests item #1182014, was opened at 2005-04-12 22:40
Message generated for change (Comment added) made by mapopa
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1182014&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: mariuz (mapopa)
Assigned to: Nobody/Anonymous (nobody)
Summary: forum like interface to mailman
Initial Comment:
one long term item would be creating an forum like
interface for
archives / mail
The idea came to me after some users on mono list
requested a forum for mono
http://lists.ximian.com/mailman/listinfo/mono-list
the basic forum interface (there are many others)
http://www.gotmono.com/cgi-bin/yabb/YaBB.pl?board=ASPX
----------------------------------------------------------------------
>Comment By: mariuz (mapopa)
Date: 2005-08-30 00:24
Message:
Logged In: YES
user_id=85089
On ubuntuforums.org they have two way between mailman and
vbulletin
Here is the example
http://ubuntuforums.org/showthread.php?t=60843
----------------------------------------------------------------------
Comment By: Fred H Olson (fholson)
Date: 2005-08-24 00:57
Message:
Logged In: YES
user_id=1334022
There is an open source development project similar to this:
GroupServer is a GPL open source collaboration server. It
supports many-to-many interaction in groups and communities
via email and an integrated web forum interface.
See http://groupserver.org/
How much do mailman and groupserver developers communicate?
Has collaboration of some sort been considered?
Fred Olson http://justcomm.org
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1182014&group_…
Bugs item #1275856, was opened at 2005-08-29 10:26
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1275856&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: Web/CGI
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Mark Sapiro (msapiro)
Assigned to: Nobody/Anonymous (nobody)
Summary: Utils.get_domain() wrong if VIRTUAL_HOST_OVERVIEW off
Initial Comment:
Part of the code in get_domain() in Utils.py is:
if mm_cfg.VIRTUAL_HOST_OVERVIEW and host:
return host.lower()
else:
# See the note in Defaults.py concerning
DEFAULT_HOST_NAME
# vs. DEFAULT_EMAIL_HOST.
hostname = mm_cfg.DEFAULT_HOST_NAME or
mm_cfg.DEFAULT_EMAIL_HOST
return hostname.lower()
It is clear that get_domain() should return the web
host, not the e-mail host. This code should be:
if mm_cfg.VIRTUAL_HOST_OVERVIEW and host:
return host.lower()
else:
# See the note in Defaults.py concerning
DEFAULT_URL
# vs. DEFAULT_URL_HOST.
hostname = mm_cfg.DEFAULT_URL or
mm_cfg.DEFAULT_URL_HOST
return hostname.lower()
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1275856&group_…
Bugs item #1269067, was opened at 2005-08-24 20:09
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1269067&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: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Daniel (doolyo)
Assigned to: Nobody/Anonymous (nobody)
Summary: e-mail command confirmations should be optional
Initial Comment:
When we send an e-mail to change the member's
options with a command (e.g. to subscribe/unsubscribe
members), the confirmation of the commands should be
optionnal.
This is useful particularly if we do a php script that
sends the commands automatically from a post field.
Then the member doesn't need to see all those e-mail
commands.
This should be an optional command that would disable
these confirmations for the whole list and all commands.
www.Sympa.org mailing list does this very well.
Thank you.
Daniel
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1269067&group_…
Bugs item #1269025, was opened at 2005-08-24 19:55
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1269025&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: (un)subscribing
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Daniel (doolyo)
Assigned to: Nobody/Anonymous (nobody)
Summary: unsubscribe removal confirmation should be optional
Initial Comment:
We should be able to choose if we want the members
that unsubscribe by e-mail to receive a 'removal
confirmation' e-mail. I need the user to not receive this
notice and just remove him without him knowing it.
However, we should still be able to sent him the
good_bye message when he left if we want it, like it's
the case currently.
The removal notice is not really necessary if people
receive an e-mail telling that they have been removed.
They can submit again if they want and report the abuse.
This option should just be an added tag that would be
valid for the whole list.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1269025&group_…
Bugs item #1268939, was opened at 2005-08-24 19:11
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1268939&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: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Daniel (doolyo)
Assigned to: Nobody/Anonymous (nobody)
Summary: host_name tag doesn't allow IP addresses
Initial Comment:
Hello.
I have realised that we cannot put an IP address in
the 'host_name' tag. Normally, we can send an e-mail
from a client to a server that doesn't have a domain
name by just putting it's IP address into square
brackets like this:
john(a)[142.56.2.72]
This works, especially if you have put the same IP
address on the destination server in your /etc/mail/local-
host-names file on one line (for Sendmail):
[142.56.2.72]
Now the problem is that if we specify the IP address
into square brackets in the 'host_name' tag, then the
resolved hostname is returned in the e-mail address
instead of this square brackets IP address.
I have tried several backslashes like '', [], "", %5B and %
5D but nothing does.
Square brackets are still correct to the standard, so I
think that this is a bug.
Regards,
Daniel
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1268939&group_…
Feature Requests item #1182014, was opened at 2005-04-13 01:40
Message generated for change (Comment added) made by fholson
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1182014&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: mariuz (mapopa)
Assigned to: Nobody/Anonymous (nobody)
Summary: forum like interface to mailman
Initial Comment:
one long term item would be creating an forum like
interface for
archives / mail
The idea came to me after some users on mono list
requested a forum for mono
http://lists.ximian.com/mailman/listinfo/mono-list
the basic forum interface (there are many others)
http://www.gotmono.com/cgi-bin/yabb/YaBB.pl?board=ASPX
----------------------------------------------------------------------
Comment By: Fred H Olson (fholson)
Date: 2005-08-24 03:57
Message:
Logged In: YES
user_id=1334022
There is an open source development project similar to this:
GroupServer is a GPL open source collaboration server. It
supports many-to-many interaction in groups and communities
via email and an integrated web forum interface.
See http://groupserver.org/
How much do mailman and groupserver developers communicate?
Has collaboration of some sort been considered?
Fred Olson http://justcomm.org
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1182014&group_…
Feature Requests item #1198375, was opened at 2005-05-09 11:01
Message generated for change (Comment added) made by fholson
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1198375&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: rst (r_st)
Assigned to: Nobody/Anonymous (nobody)
Summary: edit moderated messages directly on admindb page
Initial Comment:
When viewing held messages on the administrative
database page, owners/moderators should be able to edit
those messages without having to forward the messages
to themselves. This will allow for easy editing as
well as maintaining the original headers.
----------------------------------------------------------------------
Comment By: Fred H Olson (fholson)
Date: 2005-08-24 03:50
Message:
Logged In: YES
user_id=1334022
I agree this would be useful tho I suppose some indicator
that a message
has been edited should be added.
It would be nice to be able to edit subject lines at least.
All those "digest reply" subject lines.
And deleting all the excessive quoting - particularly on
"top replies"
Some options for doing the latter automatically would be great.
Fred H Olson http://justcomm.org
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1198375&group_…
Feature Requests item #1267807, was opened at 2005-08-24 03:36
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=1267807&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: Fred H Olson (fholson)
Assigned to: Nobody/Anonymous (nobody)
Summary: Digest header / masthead.txt changes
Initial Comment:
Mailman digests get (potentially) two blocks of text at
the top:
The contents of a file called masthead.txt
currently about 13 lines which I summarize as:
Send ... submissions to ...
To subscribe or unsubscribe ...
You can reach the person managing the list at ....
When replying, please edit your Subject line ...
In addition list admins can add a digest_header
(which defaults to nothing) that follows the masthead.
Two other requests suggest allowing the the masthead
be moved to the bottom of the list because a
significant number of people in my estimation find this
repetitive block of text rather verbose and a nuisance.
See feature requests:
1220821 Option to move "cruft" ("boilerplate") to
bottom of digest
1059834 daily digest new setting: mail body change
Note that the masthead.txt does not seem to change for
announcement lists for which the "submissions" and
"when replying" portions are inappropriate.
REQUEST: Allow "masthead" text to be changeable by
listowners
I would like to see the text supplied currently by
masthead
be changeable by list owners. It seems like this could
be done similar to footers - with default contents
(preferably smarter) to the digest_header form which
already exists.
Fred H Olson who manages lists as http://justcomm.org
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1267807&group_…
Feature Requests item #791928, was opened at 2003-08-20 09:10
Message generated for change (Comment added) made by fholson
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=791928&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: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: JC Dill (jcdill)
Assigned to: Nobody/Anonymous (nobody)
Summary: digest filter options
Initial Comment:
Add an option on the *digest* settings page to
automatically discard, bounce to the sender (with an
explanatory message), or hold for moderator approval
all messages with a subject that matches the
list-created subject used on the outgoing digest. That
way when you setup your digest options, you can easily
select from several common methods of how listmanagers
often want their list to handle replies from digest
subscribers.
Link to this setting from the page that has the other
incoming message filtering options, so that when you
are looking at your incoming message filtering options
you notice/remember that you also have special filters
relating to digests.
----------------------------------------------------------------------
Comment By: Fred H Olson (fholson)
Date: 2005-08-24 03:08
Message:
Logged In: YES
user_id=1334022
This is a feature that I and others have long desired. On
one list I currently have a low size limit (8K) to catch
quoted digests which typically accompany "digest replies"
... It helps.
Fred http://justcomm.org
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=791928&group_i…
Patches item #644797, was opened at 2002-11-27 15:56
Message generated for change (Comment added) made by ppsys
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644797&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: mail delivery
Group: Mailman 2.2 / 3.0
Status: Open
Resolution: None
Priority: 5
Submitted By: Richard Barrett (ppsys)
Assigned to: Nobody/Anonymous (nobody)
Summary: Revised mailer exit status
Initial Comment:
This patch modifies the Python scripts in $prefix/scripts/
that are used by the MTA to deliver incoming mail to
Mailman.
The exit statuses now returned are drawn from the mail
related values defined in /usr/include/sysexits.h
This allows the MTA to return more meaningful
responses to the sender when rejecting mail. It also
allows a more sympathetic treatment of mail in the event
that the Python script suffers an unexpected exception
when handling incoming email.
Such exceptions are now logged to MM's
$prefix/logs/erro in all but the most extreme error cases
and the internal information about the Python exception
is not passed into the response to the sender.
There are two patch versions; one for MM 2.0.13 and the
other for MM 2.1b5
in the MM build directory say:
patch -p1 < patch-filename
----------------------------------------------------------------------
>Comment By: Richard Barrett (ppsys)
Date: 2005-08-23 17:46
Message:
Logged In: YES
user_id=75166
exitstatus-2.1.6-0.1.patch.gz is a MM 2.1.6 compatible version of the
patch
----------------------------------------------------------------------
Comment By: Richard Barrett (ppsys)
Date: 2004-08-03 09:56
Message:
Logged In: YES
user_id=75166
exitstatus-2.1.5-0.1.patch.gz is a MM 2.1.5 compatible version of the
patch
----------------------------------------------------------------------
Comment By: Richard Barrett (ppsys)
Date: 2004-01-02 15:14
Message:
Logged In: YES
user_id=75166
exitstatus-2.1.3-0.1.patch can be used with MM 2.1.4
----------------------------------------------------------------------
Comment By: Richard Barrett (ppsys)
Date: 2003-09-30 20:39
Message:
Logged In: YES
user_id=75166
exitstatus-2.1.3-0.1.patch is a MM 2.1.3 compatible version of the
patch
----------------------------------------------------------------------
Comment By: Richard Barrett (ppsys)
Date: 2003-04-28 14:40
Message:
Logged In: YES
user_id=75166
exitstatus-2.1.2-0.1.patch is a revision of the patch for MM
2.1.2 compatibility
----------------------------------------------------------------------
Comment By: Richard Barrett (ppsys)
Date: 2003-02-10 11:42
Message:
Logged In: YES
user_id=75166
exitstatus-2.1-0.1.patch is alos applicable to MM release
2.1.1
----------------------------------------------------------------------
Comment By: Richard Barrett (ppsys)
Date: 2003-01-02 16:30
Message:
Logged In: YES
user_id=75166
exitstatus-2.1-0.1.patch is a revision of the patch for MM 2.1
compatibility
----------------------------------------------------------------------
Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-24 03:29
Message:
Logged In: YES
user_id=12800
Sorry Richard, I have to defer this one. It's too much for
me to think about for MM2.1.
----------------------------------------------------------------------
Comment By: Richard Barrett (ppsys)
Date: 2002-12-11 11:58
Message:
Logged In: YES
user_id=75166
exitstatus-2.1b6-0.1.patch is a revision of the patch for MM
2.1b6 compatibility
----------------------------------------------------------------------
Comment By: Richard Barrett (ppsys)
Date: 2002-11-27 15:58
Message:
Logged In: YES
user_id=75166
version for MM 2.1b5
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644797&group_i…