|
Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
| Summary: | Update mail system: Add procmail functionality. | ||
|---|---|---|---|
| Product: | Infrastructure | Reporter: | dcarrera <daniel.carrera> |
| Component: | Website general issues | Assignee: | Unknown <non-migrated> |
| Status: | CLOSED DUPLICATE | QA Contact: | issues@www <issues> |
| Severity: | Trivial | ||
| Priority: | P3 | CC: | issues-openoffice.org, issues |
| Version: | current | Keywords: | oooqa |
| Target Milestone: | --- | ||
| Hardware: | Sun | ||
| OS: | All | ||
| Issue Type: | ENHANCEMENT | Latest Confirmation in: | --- |
| Developer Difficulty: | --- | ||
Hi Routing to support for evaluation. Support, please add this to the stack of suggestions relating to mail in SourceCast. thanks Louis *** Issue 26449 has been confirmed by votes. *** Issue 18731 was already created for the Reply-to part. Please be aware that users of gmane.org usually do not reply (SMTP) but post a
follow-up (NNTP).
All this should not require any user intervention at all and should be handled
at server level (the server does the cc, not the user). This is how I think it
should be done.
1) to-be-moderated mail comes in
2) CollabNET server adds [MOD: $ID] to the subject
3) CollabNET servers extracts senders address and stores the $ID-$Sender
relation in some database.
4) response comes in to ML address
5) CollabNET server checks whether the headers have a matching line for
{^Subject\ :\[MOD\:\ $REGEXP_FOR_$ID\]} returning the value for
$REGEXP_FOR_$ID.
6) CollabNET server looks in its database for the matching $Sender.
7) CollabNET server sends mail both to the list and to $Sender.
Doing it this way has some very significant advantages:
a) The user (and possibly new contributors) does not have to worry about
all this, as it should be.
b) The person asking for help receives ALL answers, not just direct
responses.
Closing this as duplicate of issue 18731. *** This issue has been marked as a duplicate of 18731 *** For technical reasons we have to move the issue to another subcomponent tan 'www'. Sorry for bothering you with this generated notification message. There is no need for any action from yor side. Thanks for your understanding, Stefan The Issue you raised has been marked as 'Resolved' and not updated within the last 1 year+. I am therefore setting this issue to 'Verified' as the first step towards Closing it. If you feel this is incorrect, please re-open the issue and add any comments. Many thanks, Andrew Cleaning-up and Closing old Issues ~ The Grand Bug Squash, pre v3 ~ http://marketing.openoffice.org/3.0/announcementbeta.html As per previous posting: Verified -> Closed. A Closed Issue is a Happy Issue (TM). Regards, Andrew |
The current mail system is inadequate for the users list. The users list serves as the community-based support system. We are currently overwhelmed with emails from users who are not subscribed to the list. As a consequence, whenever one of the list members replies to the email, the reply only reaches the list. It never reaches the original poster who needed help. What a lot of list members have had to do is manually read the headers of in-comming emails to see which ones have been moderated. This significantly adds to our workload. I think that the mail system should be updated to include procmail. With procmail we could alter moderated emails like this: * Prepend the text '[moderated]' to the subject line. * Add the user's email to the Reply-To field, so that the when a list member hits "reply", the original poster actually receives the response. As OpenOffice grows in popularity, the number of messages we receive at the users list is only going to increase. We are already barely managing the current volume. Making these changes to the mail system are imperative for the long-term viability of this commuity-based support list. Cheers, Daniel. OpenOffice.org users-list member.