[Mailman-Users] Umbrella lists && approvals
I have a mild inconvenience here, and was wondering if there's a simple way around it. For our department, I have setup lists for each class of users (undergraduates, grad students, faculty, etc), and an umbrella list to cover all the users. There are some mails that are sent out to the all users list by 3rd parties (ie, a calendar of upcoming talks in different departments and such), and usually those mails are sent out with each recipient in the BCC field so we never see any recipients; sometimes, however, the person sends them out with each user in the To: field, and the mails get held because of too many recipients. Now, this wouldn't be too big of a deal, except that approving the mail through the web interface on the umbrella list causes 7 mails to come to me and the other list admin, each for the same message but in a different list which is subscribed to the all users list. So I have to approve the same mail 8 times. The web interface doesn't seem to have any decent way around this, but I was wondering if there's some trick I can do? Put the "Approved" header in the mail twice, so it's removed the first time and used the second time for the sub lists? Maybe adding a check box to the admin database pages that says "Approve this mail for sub-lists" or something, which might require some extra hacking so that the Approved: header isn't accidentally sent out to a user. Yes, I could be a BOFH and bounce the mails right back to the sender, but I'd rather not be that harsh. The sender is aware of the issue, but everybody makes mistakes now and then :> -- Steve Huston - Unix Systems Admin, Dept. of Astrophysical Sciences Princeton University | ICBM Address: 40.346525 -74.651285 126 Peyton Hall |"On my ship, the Rocinante, wheeling through Princeton, NJ 08544 | the galaxies; headed for the heart of Cygnus, (609) 258-7375 | headlong into mystery." -Rush, 'Cygnus X-1' -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] HTDIG patches! Arghh!
On Monday, Jun 2, 2003, at 19:57 US/Eastern, Mark Dadgar wrote: Richard Barrett at [EMAIL PROTECTED] wrote: I am kicking. I have been publishing and maintaining patches to integrate htdig search with MM since MM 2.0.6 and none of the MM support lists use the facility. When I asked thru this list how many people used the patches I got 3 replies; so obviously not many sites need searchable Mailman archives. All users please note that MM 2.1.3 is the last version of MM for which I shall be publishing revisions of the #444884 patch. I will make one last effort to publish a generic version of the htdig integration patch which provides a framework for integrating other search engiones. Then I give up. Life is too short to continue pushing this particular rope uphill. Ai! No! Say it isn't so! These patches are critical for me. Sigh. They are for me too; while we don't have a lot of lists, one of the major points that was brought up by the users here is that the software has to have searchable archives, and these patches were one of the reasons I chose Mailman over any other package (very little work to get a full install with the htdig interaction running). Had I seen a mail asking about how many people use the patches I would've certainly raised a hand. I've said it before (recently) and I'll say it again - these patches should be integrated into the main Mailman tree. They are That Good. I'll second (or by now third or fourth) this motion as well. I'm not sure of the reason why they're not included, but considering your excellent work in keeping up with the patches I haven't seen it as a problem. If you're moving away from them, this will be a problem (unless I don't find any need to upgrade the system until someone else picks up the torch). Thank you, Richard, for maintaining them as long as you have. Definitely. Now, is there any way we can talk you into continuing? :) ...if you can keep your sanity in the process. I know what it's like when you just want to get away from something you wrote before (google for "megahal eggdrop"... I still can't escape that one, and haven't even been on IRC in over 4 years :P) I can understand if you want to walk away from the patches because you're just tired of maintaining them, just know that there are a lot of people who love them and use them, so don't throw in the towel because you think they're not appreciated. -- Steve Huston - Unix Systems Admin, Dept. of Astrophysical Sciences Princeton University | ICBM Address: 40.346525 -74.651285 126 Peyton Hall |"On my ship, the Rocinante, wheeling through Princeton, NJ 08544 | the galaxies; headed for the heart of Cygnus, (609) 258-7375 | headlong into mystery." -Rush, 'Cygnus X-1' -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Thank you all.
(Please reply privately for the sanity of the other lists, if you feel a reply is needed; or at least trim out the lists you're not a member of) I just wanted to drop a line to all the developers of the programs I setup recently for our mailserver, and thank you all. Sometimes the people who work hard to bring the good programs to us don't get the recognition they deserve (especially when reading lists like these where you usually only hear of the problems people have). Everything's working very well, was painless to install, heck even the users here like it. So again, thanks for all your work. It is not unappreciated :> -- Steve Huston - Unix Systems Admin, Dept. of Astrophysical Sciences Princeton University | ICBM Address: 40.346525 -74.651285 126 Peyton Hall |"On my ship, the Rocinante, wheeling through Princeton, NJ 08544 | the galaxies; headed for the heart of Cygnus, (609) 258-7375 | headlong into mystery." -Rush, 'Cygnus X-1' -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Mailman on RH 8
On Tuesday, Mar 25, 2003, at 20:44 US/Eastern, George Cohn wrote: Is their anyone using Mailman on RH 8 with Postfix? I am, plus amavisd-new with spamassassin 2.50 (been up now 77 hours and am just about to pass the 1000th spam blocked. What a feeling :>) I loaded their RPM but it looks like it's intended for RH 7.3 and I have some permission problems. Who's RPM? And for which program, Mailman or Postfix? I can create lists but when I try to post to them, I get the following errors: IOError: [Errno 13] Permission denied: '/var/spool/mailman/qfiles/f3fc338508d6ec557e19843b6d1b3e54b549b9b3.db' Check that the permissions on the wrapper program are correct, and the permissions on the /var/spool/mailman directory. The trouble with RPMs that aren't made by the distributor is that sometimes little things snag you, such as whomever made the mailman RPM might have tailored it more for a Sendmail installation, while Postfix uses different users for its setup. I ended up installing Mailman by hand (which isn't too difficult, and also allowed me to easily add the ht://Dig patches), installing Postfix via the SRPM from Simon Mudd, amavisd-new by hand (big deal, it's a single Perl script and a config file) and Cyrus IMAPD by hand as well since I wanted to make sure certain authentication methods were disabled. So the only RPM'd packages on the server are Postfix and Apache, and since the others are simple to install and/or don't require upgrades often, it shouldn't be a maintenance nightmare. You may want to consider the same or a similar approach; even if you use a SRPM, you can at least tailor the package more to your own site that way, still have the ease of later saying 'rpm -Uvh foo', but not get "trapped" by whatever the package maintainer decided to do for his own setup. Good maintainers will make either multiple packages for varying setups, or if possible one which encompasses most/all variables. When you're talking about the delicate interactions between multiple programs (especially since Postfix is quite particular about its environment), sometimes the ease of RPM isn't worth it. -- Steve Huston - Unix Systems Admin, Dept. of Astrophysical Sciences Princeton University | ICBM Address: 40.346525 -74.651285 126 Peyton Hall |"On my ship, the Rocinante, wheeling through Princeton, NJ 08544 | the galaxies; headed for the heart of Cygnus, (609) 258-7375 | headlong into mystery." -Rush, 'Cygnus X-1' -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] New mail server setup
I'm setting up a new mail server, and Mailman is one of the softwares installed.Currently I have the defaults set for DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST to be the actual hostname of the machine (mercury), but when it goes online there will be an alias which should be used instead (mail). The email_host should actually then point to the domain, not the hostname (ie, astro.princeton.edu instead of mercury.astro or mail.astro). As I've created lists to replace old alias exploders, I've forced the "preferred hostname for this list" to be astro.princeton.edu, so that mails it sends out say you should send mail to [EMAIL PROTECTED], which is how it should look when it goes live. Currently the webpage information points to the actual hostname and not mail, which is fine since mail is another server which knows nothing about Mailman. Am I correct that, once it goes live, I should run: bin/withlist -l -a -r bin/fix_url ...and that will clean up the URLs appropriately (so they now read mail.astro)? Of course I first would have to first change DEFAULT_URL_HOST in mm_cfg.py. Is there anything that needs doing to change the DEFAULT_EMAIL_HOST? Or is that only used when the list is created for setting the initial value for the "host name this list prefers for email"? If that's the case I might just set it now so I don't forget later while creating lists on the box. TIA --- Steve Huston - Unix Systems Admin, Dept. of Astrophysical Sciences Princeton University | ICBM Address: 40.346525 -74.651285 126 Peyton Hall |"On my ship, the Rocinante, wheeling through Princeton, NJ 08544 | the galaxies; headed for the heart of Cygnus, (609) 258-7375 | headlong into mystery." -Rush, 'Cygnus X-1' -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Ending a list..
On Friday, Feb 28, 2003, at 11:48 US/Eastern, Todd wrote: Jon Carnes wrote: That would work. I would also delete the aliases and with the web-admin mark the list as private. Wouldn't doing so prevent access to the archives? I read Carl's message to mean that he wanted the list archives to remain accessible. If the archives are public, this is really simple with rmlist. If they're private, I'm curious how that'll work, as I can't recall ever having done it. But, what happens if at some other time you do a bin/arch --wipe ? Are the .mbox files kept around to rebuild the web archives from, or would they also go with a rmlist? If they're wiped, then the first suggestion (remove all users, require authorization to join list), plus removing the aliases, would probably be best. --- Steve Huston - Unix Systems Admin, Dept. of Astrophysical Sciences Princeton University | ICBM Address: 40.346525 -74.651285 126 Peyton Hall |"On my ship, the Rocinante, wheeling through Princeton, NJ 08544 | the galaxies; headed for the heart of Cygnus, (609) 258-7375 | headlong into mystery." -Rush, 'Cygnus X-1' -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Bundle Htdig with Pipermail? -was- How to deletemessages from private archives
[Trimming CCs down to just the list] On Mon, 27 Jan 2003, Matthew Davis wrote: > * Jon Carnes ([EMAIL PROTECTED]) wrote: > > Is there a reason you wouldn't want to simply include Htdig as part of > > the "out of the box" install? > My concern is the size of the package. > Thats a good chunk, and adding htdig (tarball for 3.1.6 is 2 meg) would up > the package size to roughly 7-8 meg. Considering I'm just a lowly dial-up > 56k constant connection server (theres no plans of broadband where I live, > way too far in the NC sticks), puts me as a minority I know. Just a > concern. Yes, but look at just the size of Mailman, plus the "htdig" patches on Sourceforge. That's not too big, and simply means you'd have to install htdig separately. Or even change the patches around (if necessary, don't recall now) so that they can be applied, but htdig isn't required for things to run. Yes, you'd still have to download and install it if you wanted the functionality, however it comes with RedHat at least so you could install it from your distribution's media. While I can agree with large package sizes (have had my DSL dropped twice when companies went under, and had to go back to good old dial-up), I doubt a couple patches to Mailman would change the size that much. Plus, it already requires Python, and last I checked that was pretty big :> -- Steve Huston - Unix Systems Administrator, Dept. of Astrophysical Sciences Princeton University | ICBM Address: 40.346525 -74.651285 126 Peyton Hall |"On my ship, the Rocinante, wheeling through Princeton, NJ 08544 | the galaxies; headed for the heart of Cygnus, (609) 258-7375 | headlong into mystery." -Rush, 'Cygnus X-1' -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] post_id in messages and archives
On Fri, 24 Jan 2003, Steve Huston wrote: > Checking the patches on Sourceforge, I found where someone sent in a patch > that adds the mlist.post_id number to the subject if it contains '%d'. While > this may be the easiest way to do this, since it would also be searchable that > way in the archives, I'd prefer to keep the information in the footer and/or > message headers. > If/when I get this nicely cleaned up and presentable I'll submit the patch to > SF. Well, a few hours later, I did just that: http://sourceforge.net/tracker/index.php?func=detail&aid=674433&group_id=103&atid=300103 Please, if a couple people better at Python than I am could look this over, and see if you notice any glaring mistakes, I'd appreciate it. Thanks. -- Steve Huston - Unix Systems Administrator, Dept. of Astrophysical Sciences Princeton University | ICBM Address: 40.346525 -74.651285 126 Peyton Hall |"On my ship, the Rocinante, wheeling through Princeton, NJ 08544 | the galaxies; headed for the heart of Cygnus, (609) 258-7375 | headlong into mystery." -Rush, 'Cygnus X-1' -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] post_id in messages and archives
In trying to migrate some old mailing lists to Mailman on our new server, one
thing was mentioned to me. The old list software kept track of messages by a
unique sequential number (first message is 1, second is 2, etc). This was
mostly done for the archives of the list, but apparently the list users have
grown accustomed to referring to messages by their number, since it is also
mentioned in the footer of the mail ("This is message number 2348 in the
archive").
Checking the patches on Sourceforge, I found where someone sent in a patch
that adds the mlist.post_id number to the subject if it contains '%d'. While
this may be the easiest way to do this, since it would also be searchable that
way in the archives, I'd prefer to keep the information in the footer and/or
message headers.
So far, I have patched the Digest.py code and Decorate.py to make available
"post_id" as a variable in the footer (though it's not really pertinent in
digests, and I don't know what'll happen if it shows up in one, but I can't
use it in PERSONALIZED_ALLOWEDS in NonDigest.py since the list doesn't need
personalization or the overhead of processing it that way), and an X-Post-ID
header in CookHeaders.py, and though I haven't tested the header part yet
everything seems to work fine.
My two questions:
1) Where would I go about adding a config option to set the post_id? Ideally
this is something which should only be set once, since you don't want someone
mucking about with the number, and if you know there's 2850 messages in the
old archive it's safe to make this one 3000 for those that might come in while
you're migrating, and not worry about repeating numbers. So I would think it
would be somewhere when creating the list you'd want to do this; or, an option
that only allows inflation of the number (new_post_id > post_id || error).
2) How do I get this information to pass into the archives? The headers seem
to be stripped somewhere, and footers are not archived. I'd like people to be
able to search for the number and find that article. This could even be
pretty-printed from the header, so instead of "X-Post-ID: 1234" it would say
somewhere "This is article # 1234". Since the search engine is ht://Dig, it
would pick it up either way; I imagine it could even be in the html source and
not displayed (META tag?) and htdig would get it, but I'd rather it be
viewable somehow.
If/when I get this nicely cleaned up and presentable I'll submit the patch to
SF.
--
Steve Huston - Unix Systems Administrator, Dept. of Astrophysical Sciences
Princeton University | ICBM Address: 40.346525 -74.651285
126 Peyton Hall |"On my ship, the Rocinante, wheeling through
Princeton, NJ 08544 | the galaxies; headed for the heart of Cygnus,
(609) 258-7375 | headlong into mystery." -Rush, 'Cygnus X-1'
--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/
This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] htdig integration patches
On Wed, 22 Jan 2003, Richard Barrett wrote: > In response to your input I have posted a revised version of patch #444884 > for MM 2.1 on sourceforge as file htdig-2.1-0.3.patch > Thanks for your heads up on the problem and your observation. Sorry for the > errors. Your suggested change was not quite right; good try but no cigar.:) Tried it today, works like a champ. Thanks! > At 23:41 21/01/2003, Steve Huston wrote: > >Lastly, I'm a little confused by one way things fit together. Granted, it > >works, but... Why does the htdig script make its results point to itself? > One of the objectives of this patch was to preserve private archive privacy > and make changing an archive from private to public or vice-versa a > non-event from the archive search standpoint. I later read a mail to the same effect in the archives, and understood why it works this way. Makes sense, any of the tests I've done so far were on publicly viewable archives, never thought about private ones. -- Steve Huston - Unix Systems Administrator, Dept. of Astrophysical Sciences Princeton University | ICBM Address: 40.346525 -74.651285 126 Peyton Hall |"On my ship, the Rocinante, wheeling through Princeton, NJ 08544 | the galaxies; headed for the heart of Cygnus, (609) 258-7375 | headlong into mystery." -Rush, 'Cygnus X-1' -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] htdig integration patches
I've applied the patches, but have had a few problems. I emailed Richard Barrett through sourceforge, and don't know if you got it, so I'll start with what I've figured out since then. Should line 1485 of htdig-2.1-0.2.patch read "if (not ctype) or cencode:" instead of reading "if not (ctype and cencode):"? Because with the way it was, when I clicked on a found item from a search, it tried to download the file as type application/octet-stream, but changing it to (not ctype) or cencode lets it come properly as text/html. That one took a bit to figure :> Another thing I noticed is that it seems there are quite a few references in the code to "DEFAULT_URL", but I believe that changed to "DEFAULT_URL_HOST"; setting DEFAULT_URL to the same thing made some of the error messages I'd received actually work instead of dumping Python (somewhere in make_inserts). Lastly, I'm a little confused by one way things fit together. Granted, it works, but... Why does the htdig script make its results point to itself? For example, if I search for 'foo', and find an instance, the URL that the result points to is "http://host/mailman/htdig/listname/2003-January/06.html";. I tried setting HTDIG_ARCHIVE_URL to "/pipermail/" instead to get it to output the links as "http://host/pipermail/listname/2003-January/06.html";, but this seemed to have no effect. Perhaps this works differently than I'm thinking, but it seems more resource-effective to have the link point right to the file instead of going through another cgi, when we know the location of the file we're trying to get. Please, call me an idiot, and explain why :> -- Steve Huston - Unix Systems Administrator, Dept. of Astrophysical Sciences Princeton University | ICBM Address: 40.346525 -74.651285 126 Peyton Hall |"On my ship, the Rocinante, wheeling through Princeton, NJ 08544 | the galaxies; headed for the heart of Cygnus, (609) 258-7375 | headlong into mystery." -Rush, 'Cygnus X-1' -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
