Mailman 3 March 2006 - Mailman-coders

[ mailman-Patches-1459897 ] New Arabic translation
by SourceForge.net March 28, 2006

March 28, 2006

Patches item #1459897, was opened at 2006-03-28 13:04 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=1459897&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: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Munzir Taha (munzirtaha) Assigned to: Nobody/Anonymous (nobody) Summary: New Arabic translation Initial Comment: Attached is an Arabic translation of mailman. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1459897&group_…

1 0

[ mailman-Patches-1459818 ] New Arabic translation
by SourceForge.net March 28, 2006

March 28, 2006

Patches item #1459818, was opened at 2006-03-28 10:38 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=1459818&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: internationalization Group: None Status: Open Resolution: None Priority: 5 Submitted By: Munzir Taha (munzirtaha) Assigned to: Nobody/Anonymous (nobody) Summary: New Arabic translation Initial Comment: Attached is an Arabic translation of mailman. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1459818&group_…

1 0

[ mailman-Bugs-1459022 ] Postfix.py and aliases (#CREATED:xxx)
by SourceForge.net March 27, 2006

March 27, 2006

Bugs item #1459022, was opened at 2006-03-26 18:30 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1459022&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: configuring/installing Group: 2.1 alpha Status: Open Resolution: None Priority: 5 Submitted By: Bob Holden (eawf) Assigned to: Nobody/Anonymous (nobody) Summary: Postfix.py and aliases (#CREATED:xxx) Initial Comment: CentOS4.2 Installed Mailman2.1.5 via YUM. Postfix Configured Automatic aliases file creation. When creating list from ./newlist, no problems. When creating list from web, got bug page, and discovered an alias entry, "#CREATED:...". While not being a Python programmer, glancing through the Postfix.py file, it looks like when looping through the STANZA section to create the aliases file, the commented #CREATED: line isn't ignored, causing the record to be created. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2006-03-26 18:59 Message: Logged In: YES user_id=1123998 Both bin/newlist and the Cgi create script invoke the exact same Mailman/MTA/Postfix.py module to update the aliases. The only difference is the user/group under which it runs. Thus, this is most likely a problem with the 'mailman' group not having write permission on data/aliases*. Both data/aliases and data/aliases.db should be group owned by the 'mailman' group and be group writable. This may be FAQ 6.9 - http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq06.009.htp If this is not a permissions issue, please post the traceback from the "bug" from Mailman's error log. Note that the "#CREATED:" line in the aliases file is a comment and is intended to be there. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1459022&group_…

1 0

[ mailman-Bugs-1459022 ] Postfix.py and aliases (#CREATED:xxx)
by SourceForge.net March 27, 2006

March 27, 2006

Bugs item #1459022, was opened at 2006-03-26 18:30 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=1459022&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: configuring/installing Group: 2.1 alpha Status: Open Resolution: None Priority: 5 Submitted By: Bob Holden (eawf) Assigned to: Nobody/Anonymous (nobody) Summary: Postfix.py and aliases (#CREATED:xxx) Initial Comment: CentOS4.2 Installed Mailman2.1.5 via YUM. Postfix Configured Automatic aliases file creation. When creating list from ./newlist, no problems. When creating list from web, got bug page, and discovered an alias entry, "#CREATED:...". While not being a Python programmer, glancing through the Postfix.py file, it looks like when looping through the STANZA section to create the aliases file, the commented #CREATED: line isn't ignored, causing the record to be created. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1459022&group_…

1 0

[ mailman-Feature Requests-403066 ] Auto Approval of subscriptions for certain domains
by SourceForge.net March 26, 2006

March 26, 2006

Feature Requests item #403066, was opened at 01/01/01 06:27 Message generated for change (Settings changed) made by sf-robot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=403066&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: Closed Resolution: Accepted Priority: 3 Submitted By: Mark Tearle (mtearle) Assigned to: Mark Sapiro (msapiro) Summary: Auto Approval of subscriptions for certain domains Initial Comment: A patch to enable automatic approval for certain domains, eg people in the example.com are automatically approved all others have to wait for the moderator ---------------------------------------------------------------------- >Comment By: SourceForge Robot (sf-robot) Date: 03/25/06 19:21 Message: Logged In: YES user_id=1312539 This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker). ---------------------------------------------------------------------- Comment By: Jim Popovitch (jimpop) Date: 03/12/06 19:12 Message: Logged In: YES user_id=3142 I've successfully applied this against a v2.1.8 system and it works well. Thanks!! ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 03/11/06 10:36 Message: Logged In: YES user_id=1123998 The attached patch is against a 2.1.8a1 installed base (installed because it patches Defaults.py and not Defaults.py.in). It is a modification and extension of the original patch. It implements a new list attribute 'subscribe_auto_approval' which is a list of email addresses and regular expressions matching email addresses whose subscriptions are exempt from admin approval. It implements the original intent if one just uses regexps that match domains. This will go in Mailman 2.2, but it would be nice to get some feedback from people who are interested in this feature and are willing to try the patch. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 03/11/03 05:31 Message: Logged In: YES user_id=34209 Is this still necessary with Mailman 2.1, which has more 'automatic' options (as well as 'memberadaptors') ? In any case, the patch is likely heavily out of date by now, I'm moving this to Feature Requests for now. Feel free to respond if you (still) have a need. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=403066&group_i…

1 0

[ mailman-Patches-1455262 ] A workaround for treating long address splitted into lines
by SourceForge.net March 21, 2006

March 21, 2006

Patches item #1455262, was opened at 2006-03-21 19:12 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=1455262&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: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Naoki Fukuta (naoki-fukuta) Assigned to: Nobody/Anonymous (nobody) Summary: A workaround for treating long address splitted into lines Initial Comment: ---Summary:--- Following is a workaround for a problem when processing very long email address field that is splitted into two or more lines. I tested it on Mailman 2.1.8. Please evaluate this patch and feedback to the latest build. I appreciate if this is a duplicate of already reported one. ---Problem Description:--- The mail address parser program (pythonlib/email/_parseaddr.py) has a problem when the field is splitted into two or more lines by using continuations(eg. "\r\n " or "\r\n\t"). For example, following "Cc:" field can be splitted into lines when the mail is sent to the server. Cc: =?ISO-2022-JP?B?IktCU0UbJEI4JjVmMnEbKEIgGyRCNDQ7dkNEGyhC?= =?ISO-2022-JP?B?Ig==?= <fukutax(a)example.org>, =?ISO-2022-JP?B?IhskQkVFO1I+cEpzREw/LjNYMnEbKEIgGyRCOCY1ZhsoQg==?= =?ISO-2022-JP?B?GyRCMnFIL0k9Pz05fiU3JTklRiVgGyhCIg==?= <fukutax(a)example2.org> The main problem is there are no actual email address at line 1 and 3. Current code in _parseaddr.py expects there is at least one valid email address in a line. So what will happen? See below. When posting the mail to members, two addresses are newly made, with a default domain name (@mailman.example3.org). Cc: =?ISO-2022-JP?B?Ig==?= <fukutax(a)example.org>, =?ISO-2022-JP?B?IktCU0UbJEI4JjVmMnEbKEIgGyRCNDQ7dkNEGyhC?=(a)mailman.example3.org, =?ISO-2022-JP?B?IhskQkVFO1I+cEpzREw/LjNYMnEbKEIgGyRCOCY1ZhsoQg==?=(a)mailman.example3.org, =?ISO-2022-JP?B?GyRCMnFIL0k9Pz05fiU3JTklRiVgGyhCIg==?= <fukutax(a)example2.org> ---Patch--- I made a workaroud patch by adding a darty code into getphraselist() method. ---------------------------------------------------- def getphraselist(self): """Parse a sequence of RFC 2822 phrases. A phrase is a sequence of words, which are in turn either RFC 2822 atoms or quoted-strings. Phrases are canonicalized by squeezing all runs of continuous whitespace into one space. """ plist = [] while self.pos < len(self.field): if self.field[self.pos] in self.LWS: self.pos += 1 elif self.field[self.pos] == '"': plist.append(self.getquote()) elif self.field[self.pos] == '(': self.commentlist.append(self.getcomment()) + elif (self.pos + 4) < len(self.field) and self.field[self.pos] in '\r' and self.field[self.pos+1] in '\n' and self.field[self.pos+2] in '\t': + self.pos += 3 + elif (self.pos + 4) < len(self.field) and self.field[self.pos] in '\r' and self.field[self.pos+1] in '\n' and self.field[self.pos+2] in ' ': + self.pos += 3 + elif (self.pos + 4) < len(self.field) and self.field[self.pos] in '\n' and self.field[self.pos+1] in '\t': + self.pos += 2 + elif (self.pos + 4) < len(self.field) and self.field[self.pos] in '\n' and self.field[self.pos+1] in ' ': + self.pos += 2 + elif (self.pos + 4) < len(self.field) and self.field[self.pos] in '\r' and self.field[self.pos+1] in '\t': + self.pos += 2 elif self.field[self.pos] in self.phraseends: break else: plist.append(self.getatom(self.phraseends)) return plist ---------------------------------------- ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1455262&group_…

1 0

[ mailman-Bugs-1453049 ] Typos in the Mailman 2.1.8a PO file
by SourceForge.net March 18, 2006

March 18, 2006

Bugs item #1453049, was opened at 2006-03-18 18:54 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=1453049&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: Clytie Siddall (clytie) Assigned to: Nobody/Anonymous (nobody) Summary: Typos in the Mailman 2.1.8a PO file Initial Comment: 1. po:670 reference: â¤ Mailman/Gui/ContentFilter.py:130 Original: â0 One of these actions is take when the message matches one of\n the content filtering rules, <snip> - is take + is taken 2. po:717 reference: â¤ Mailman/Gui/General.py:143 Original: â0 This text will be prepended to subject lines of messages \n posted to the list, to distinguish mailing list messages in in\n mailbox summaries. Brevity is premium here, it's ok to shorten\n long mailing list names to something more concise, as long as it\n still identifies the mailing list.\n You can also add a sequencial number <snip> - messages in in mailbox summaries + messages in mailbox summaries - sequencial + sequential 3. po:785 reference: â¤ Mailman/Gui/NonDigest.py:129 Original: â0 Text prepended to the top of every immediately-delivery \n message. - immediately-delivery + immediate-delivery (OR + immediately-delivered) Also in this string: .po:787 reference: â¤ Mailman/Gui/NonDigest.py:134 Original: â0 Text appended to the bottom of every immediately- delivery\n message. 4. po:789 reference: â¤ Mailman/Gui/NonDigest.py:141 Original: â0 When you scrub attachments, they are stored in archive\n area and links are made in the message so that the member can\n access via web browser. If you want the attachments totally\n disappear, you can use content filter options. + When you scrub attachments, they are stored in the archive and accessible to the member via web-browser links in the message. If you want to get rid of attachments completely, you can use the content filter options. 5. po:828 reference: â¤ Mailman/Gui/Privacy.py:244 Original: â0 Postings from any of these non-members will be automatically\n accepted with no further moderation applied. Add member\n addresses one per line; start the line with a ^ character to\n designate a regular expression match. In several strings about "non-members", the sentence beginning "Add member addresses one per line" still occurs. It should probably be changed, in those strings, to "Add non-member addresses one per line". The other strings are: .po:830 reference: â¤ Mailman/Gui/Privacy.py:253 Original: â0 Postings from any of these non-members will be immediately\n and automatically held for moderation by the list moderators. \n The sender will receive a notification message which will allow\n them to cancel their held message. Add member addresses one per\n line; start the line with a ^ character to designate a regular\n expression match. .po:832 reference: â¤ Mailman/Gui/Privacy.py:264 Original: â0 Postings from any of these non-members will be automatically\n rejected. In other words, their messages will be bounced back to\n the sender with a notification of automatic rejection. This\n option is not appropriate for known spam senders; their messages\n should be\n <a href=\"?VARHELP=privacy/sender/ discard_these_nonmembers\"\n >automatically discarded</a>.\n \n Add member addresses one per line; start the line with a ^\n character to designate a regular expression match. po:834 reference: â¤ Mailman/Gui/Privacy.py:279 Original: â0 Postings from any of these non-members will be automatically\n discarded. That is, the message will be thrown away with no\n further processing or notification. The sender will not receive\n a notification or a bounce, however the list moderators can\n optionally <a href=\"?VARHELP=privacy/sender/ forward_auto_discards\"\n >receive copies of auto-discarded messages.</a>.\n \n Add member addresses one per line; start the line with a ^\n character to designate a regular expression match. 6. Here you create two strings to show plural forms: po:892 reference: â¤ Mailman/HTMLFormatter.py:80 Original: â0 (1 private member not shown) .po:893 reference: â¤ Mailman/HTMLFormatter.py:82 Original: â0 (%(num_concealed)d private members not shown) but this is not effective for translation. The gettext plurals feature makes it possible for translators to input the correct number of plurals for their language. English may need two forms, singular and plural, but my language is one of several which have _no_ plural forms in this sense, and there are European languages which have more than two forms. If you don't use the gettext plurals feature, we can't translate those strings effectively. Gettext will output the correct number of plurals fields for each language, by parsing the plurals string in the PO file header. In my case, that will avoid me inputting the same translation twice in several places in this file. In the case of languages with more plural forms than English, it will avoid incomplete translations or translations that simply don't make sense. Please see the gettext manual for further information: http://www.gnu.org/software/gettext/manual/html_mono/ gettext.html#SEC150 7. po:906 reference: â¤ Mailman/HTMLFormatter.py:195 Mailman/ HTMLFormatter.py:202 Original: â0 also po:908 reference: â¤ Mailman/HTMLFormatter.py:206 Original: â0 This is %(also)sa private list, which means that the\n list of members is not available to non-members. This is likely to cause errors in translation. Although it means translating six strings instead of three, we can cut and paste most of the string, and we can be sure, that way, of correct translations. Please don't take short-cuts on translation, unless you are sure they will not affect the quality of the translation. 8. Original: â0 Rebuild a list's archive.\n \n <snip> -e M\n --end=M\n End indexing at article M. This script is not very efficient with\n respect to memory management, and for large archives, it may not be\n possible to index the mbox entirely. For that reason, you can specify\n the start and end article numbers.\n \n Where <mbox> is the path to a list's complete mbox archive. Usually this will\n There seems to be something missing here, between "the start and end article numbers" and "Where <mbox> is the path", because "where" in this context is a conjunction, joining a previous statement to this one. However, there is a full stop and two line breaks in between, indicating a statement well and truly finished. What is missing here? 9. po:1069 reference: â¤ bin/b4b5-archfix:19 Original: â0 Fix the MM2.1b4 archives.\n \n Usage: %(PROGRAM)s [options] file ...\n \n Where options are:\n -h / --help\n Print this help message and exit.\n \n Only use this to `fix' some archive database files that may have gotten \n written in Mailman 2.1b4 with some bogus data. Use like this from your\n $PREFIX directory\n<snip> - Use like this + Use it like this OR + Use the command like this (Syntax error: transitive verb must have object.) 10. po:1111 reference: â¤ bin/clone_member:19 Original: â0 Clone a member address.\n <snip> Usage:\n clone_member [options] fromoldaddr tonewaddr\n \n Where:\n \n --listname=listname\n -l listname\n <snip> - Where + Options Also occurs in these strings: po:1149 reference: â¤ bin/find_member:19 Original: â0 Find all lists that a member's address is on.\n \n Usage:\n find_member [options] regex [regex [...]]\n \n Where:\n --listname=listname\n -l listname\n .po:1161 reference: â¤ bin/list_admins:19 Original: â0 List all the owners of a mailing list.\n \n Usage: %(program)s [options] listname ...\n \n Where:\n \n --all-vhost=vhost\n -v=vhost\n po:1163 reference: â¤ bin/list_lists:19 Original: â0 List all mailing lists.\n \n Usage: %(program)s [options]\n \n Where:\n \n -a / --advertised\n List only those mailing lists that are publically advertised\n .po:1166 reference: â¤ bin/list_members:19 Original: â0 List all the members of a mailing list.\n \n Usage: %(PROGRAM)s [options] listname\n \n Where:\n \n --output file\n -o file\n po:1220 reference: â¤ bin/rmlist:19 Original: â0 Remove the components of a mailing list with impunity - beware!\n \n This removes (almost) all traces of a mailing list. By default, the lists\n archives are not removed, which is very handy for retiring old lists.\n \n Usage:\n rmlist [-a] [-h] listname\n \n Where:\n --archives\n -a\n po:1254 reference: â¤ bin/unshunt:19 Original: â0 Move a message from the shunt queue to the original queue.\n \n Usage: %(PROGRAM)s [options] [directory]\n \n Where:\n \n -h / --help\n Print help and exit.\n 11. po:1142 reference: â¤ bin/dumpdb:19 Original: â0 Dump the contents of any Mailman `database' file.\n \n Usage: %(PROGRAM)s [options] filename\n \n Options:\n \n --marshal/-m\n Assume the file contains a Python marshal, overridding any automatic\n guessing.\n<snip> - overridding + overriding 12. (Also from the above string...) The interaction between -l and -x is as follows. If any -l option is given\n then only the named list will be included in the search. If any -x option is\n given but no -l option is given, then all lists will be search except those \n specifically excluded.\n - all lists will be search + all lists will be searched 13. .po:1166 reference: â¤ bin/list_members:19 Original: â0 List all the members of a mailing list.\n <snip> Print the members that have delivery disabled. Optional argument can\n be \"byadmin\", \"byuser\", \"bybounce\", or \"unknown\" which prints just the\n users who have delivery disabled for that reason. It can also be\n \"enabled\" which prints just those member for whom delivery is \n enabled.\n<snip> - the members that have delivery disabled + the members who have delivery disabled - which prints just those member + which prints just those members 14. po:1170 reference: â¤ bin/list_owners:19 Original: â0 List the owners of a mailing list, or all mailing lists.\n \n Usage: %(PROGRAM)s [options] [listname ...]\n Options:\n \n -w / --with-listnames\n Group the owners by list names and include the list names in the \n output. Otherwise, the owners will be sorted and uniquified based on\n the email address.\n - uniquified + identified There is no such word "uniquify" in common usage. Identification within a group is based on unique qualities, so "identified" is appropriate. 15. .po:1171 reference: â¤ bin/mailmanctl:19 Original: â0 Primary start-up and shutdown script for Mailman's qrunner daemon.\n \n<snip> Note though, that if you run with -u and are not in the mailman group,\n you may have permission problems, such as begin unable to delete a\n list's archives through the web. Tough luck!\n<snip> - such as begin unable to + such as being unable to 16. po:1200 reference: â¤ bin/newlist:19 Original: â0 Create a new, unpopulated mailing list.\n \n Usage: %(PROGRAM)s [options] [listname [listadmin-addr [admin- password]]]\n \n<snip> E.g. with this setting people will view the general list\n overviews at http://www.mydom.ain/mailman/listinfo. Also, www.mydom.ain\n should be a key in the VIRTUAL_HOSTS mapping in mm_cfg.py/ Defaults.py if\n the email hostname to be automatically determined.\n - if the email hostname to be automatically determined.\n + if the email hostname is to be automatically determined.\n 17. Options:\n \n -r runner[:slice:range]\n --runner=runner[:slice:range]\n Run the named qrunner, which must be one of the strings returned by\n the -l option. Optional slice:range if given, is used to assign\n multiple qrunner processes to a queue. range is the total number of\n qrunners for this queue while slice is the number of this qrunner from\n [0..range).\n \n If using the slice:range form, you better make sure that each qrunner\n for the queue is given the same range value. If slice:runner is not\n given, then 1:1 is used.\n - If slice:runner is not given + If slice:range is not given 18. po:1283 reference: â¤ bin/update:585 Original: â0 Ignoring bad pended data: %(key)s: %(val)s - pended data + pending data OR + appended data OR (prepended/suspended etc.) 19. po:1300 reference: â¤ bin/withlist:19 Original: â0 General framework for interacting with a mailing list object.\n <snip l-o-n-g string in between> Now, from the command line you can print the list's posting address by running\n the following from the command line:\n - Now, from the command line you can print the list's posting address by running\n the following from the command line:\n + Now, you can print the list's posting address by running\n the following from the command line:\n (you've repeated "from the command-line" in this string) from Clytie, Vietnamese translator (I'm about to add the Vietnamese translation) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1453049&group_…

1 0

[ mailman-Patches-943827 ] true virtual hosting patch for 2.1
by SourceForge.net March 17, 2006

March 17, 2006

Patches item #943827, was opened at 2004-04-28 18:57 Message generated for change (Comment added) made by minfrin You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=943827&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: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: The Anarcat (anarcat) Assigned to: Nobody/Anonymous (nobody) Summary: true virtual hosting patch for 2.1 Initial Comment: [copy of the mail sent to -developpers@] We developped a reliable solution for running lists with the same name on different domains on the same Mailman installation. I implemented that on top of the Mailman 2.1.1-5.1 Debian stable package. All that is needed is to patch 2 files (bin/newlist, Mailman/MailList.py) in the mailman install, and here is the patch: http://bugs.koumbit.net/file_download.php?file_id=3&type=bug There's only one caveat right now: Mailman/Cgi/create.py might need to get patched too, but I haven't got around looking at it yet, and it "just works", for now. I don't know what's the current status of virtual hosting support on Mailman, but this patch is a simple hack that should bring joy in the homes of all Mailman admins around the world. :) I got my inspiration and part of the code from: http://mithrandr.moria.org/blog/139.html All it does is to add the domain to the internal_name() of a list. The real_name is kept as is, and the getListAddress() does the Right Thing. This makes Mailman generate aliases like: list-example.com: "|/var/lib/mailman/mail/mailman post list-example.com" Care will have to be taken on the MTA side to map those list-example.com to list(a)example.com. We are using alternc.org to manage our server, so we are using LDAP, so everything went pretty smoothly. :) But I guess it will require some magic on the Postfix side or something... Cheers, A. PS: for those wanting to see more, you can come to our Wiki: http://koumbit.net/wiki/VirtualMailman You'll probably have a little trouble finding your way if you don't read french though. :) Babelfish might help, haven't tried. ---------------------------------------------------------------------- Comment By: Graham Leggett (minfrin) Date: 2006-03-17 21:39 Message: Logged In: YES user_id=129704 I tried the patch at http://al.blog.free.fr/mailman/mailman-vh-2.1.5.patch and it applied cleanly to mailman as provided by RHEL4. I tried to create a list called "list(a)domain1.com", but this failed with the error "Error: List name must not include "@"". Does this patch have any sort of instructions anywhere? ---------------------------------------------------------------------- Comment By: Arnaud Lavrard (arnaudlavrard) Date: 2005-07-20 15:52 Message: Logged In: YES user_id=1315788 I ported the patch to mailman 2.1.5 : http://al.blog.free.fr/mailman/mailman-vh-2.1.5.patch ---------------------------------------------------------------------- Comment By: The Anarcat (anarcat) Date: 2005-03-16 21:40 Message: Logged In: YES user_id=246797 I have ported the patch to 2.1.4, no news on 2.1.5 yet. I have also put the patch in a seperate CVS server. Fetch all the goods there: http://cvs.koumbit.net/cgi-bin/cvsweb/koumbit-maint/patches/mailman-true-vi… http://cvs.koumbit.net/cgi-bin/cvsweb/koumbit-maint/patches/mailman-true-vi… I've also updated the 2.1.1 patch to fix the list-id, so I delete the attachment, fetch the patch straight from our CVS for the latest fixes. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=943827&group_i…

1 0

[ mailman-Patches-1451544 ] Addition of canonical list name
by SourceForge.net March 16, 2006

March 16, 2006

Patches item #1451544, was opened at 2006-03-16 18:42 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=1451544&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: configure/install Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Andrew D. Clark (beshwa) Assigned to: Nobody/Anonymous (nobody) Summary: Addition of canonical list name Initial Comment: This patch adds MM-List-Name-Canonical to HTMLFormatter.py This is the lower-case list name, provided by the lower() function. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1451544&group_…

1 0

[ mailman-Bugs-1445630 ] /templates/de/verify.txt: encoding of special chars(umlaute)
by SourceForge.net March 14, 2006

March 14, 2006

Bugs item #1445630, was opened at 2006-03-08 14:06 Message generated for change (Comment added) made by chris-taylor You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1445630&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: Closed Resolution: Fixed Priority: 5 Submitted By: chris-taylor (chris-taylor) Assigned to: Nobody/Anonymous (nobody) Summary: /templates/de/verify.txt: encoding of special chars(umlaute) Initial Comment: In the last stable release of mailman-2.1.7 the encoding of the special german characters (umlaute: Ã¤Ã¶Ã¼ÃÃÃ) in the file /templates/de/verify.txt is wrong. When a confirm message is sent the recipient gets strange characters for the german umlaute (e.g. ÃÂ¼ instead of Ã¼). I inserted the right characters in the file, now everything seems fine. See attached file... Regards Christian ---------------------------------------------------------------------- >Comment By: chris-taylor (chris-taylor) Date: 2006-03-14 10:53 Message: Logged In: YES user_id=994602 Hello, I looked through all the german template-files and as far as I can say /templates/de/verify.txt is the only file which was encoded in UTF-8.... Additional comment: Thank you very much for this great piece of software !!! ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-03-10 20:13 Message: Logged In: YES user_id=1123998 The template has been properly iso-8859-1 encoded for 2.1.8a1. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-03-08 16:50 Message: Logged In: YES user_id=1123998 It looks like the /templates/de/verify.txt template we're distributing is UTF-8 encoded. Is this the only one? I looked at a couple of others and they appear to be iso-8859-1 as they should be since that is Mailman's character set for german language. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1445630&group_…

1 0