Re: [Mailman-Users] Rather perplexing set of problems with a new 2.1.14vhost install on a DirectAdmin box -- and I'm new to Mailman

Christopher Woods (CustomMade) wrote: > Wondering if part of the problems are due to the OS (CentOS)... This > VPS came specced with it, and I went along with the choice. Little > was I aware of the development approach with regards to new and > shiny... (this is your cue to all have a chuckle at m

Re: [Mailman-Users] Cannot set digest mode via URL

Stephen J. Turnbull wrote: > Under the GPL, you don't have any grounds for anything except the > kind of campaign that might open you up to a libel suit as long as > they're distributing source with the binary versions. The GPL > doesn't require that version numbers be munged by downstream, and I

Re: [Mailman-Users] Cannot set digest mode via URL

Brad Knowles wrote: > If they are now shipping something and calling it 2.1.13 and it's > not exactly the same code that we provide from > , then I think it's time we had > the PSF and/or FSF lawyers give them a call -- and speaking as a > member of the Mailman Ca

Re: [Mailman-Users] Fake Email

Barry Warsaw wrote: > On Oct 31, 2009, at 1:28 AM, Stephen J. Turnbull wrote: > >>A better way to do this would be to set up the MTA on Mailman's host >>to only deliver to the list address (ie, Mailman) if the sender has >>been authenticated (eg, with TLS). > > Or to use digital signatures for send

Re: [Mailman-Users] MM-2.1.12 Bug (non critical)

Barry Warsaw wrote: > I tend to agree that "normal" users think of globs instead of > regexps. Unfortunately, there's no good non-filesystem glob module > in Python that I know of. Ideally, there'd be a module that > translates globs to regexps. That might not be too hard. Would fnmatch.transla

Re: [Mailman-Users] Centos + Blue Quartz question - virtual site issue.

Mark Sapiro wrote: > Based on your off-list reply to Brad, it appears that you're using a > CentOS/RedHat Mailman package. My understanding of this package, > which may be incorrect, is it integrates aliases with Postfix as the > MTA. The Red Hat / CentOS mailman packages don't create any default

Re: [Mailman-Users] welcome message

Henry Hartley wrote: > Joe Damico wrote: >> >> We would like to make some slight modification to the Mailman >> welcome message for new subscribers at our location. Where is this >> message located and if it is in Python code, how do we go about >> changing the text? > > If you just want to change

Re: [Mailman-Users] "create a new list" web interface

[EMAIL PROTECTED] wrote: > By diabling SELinux altogether it worked. If you don't want to keep SELinux disabled, it should be possible to make mailman work without too much trouble. I do know that the Red Hat packages install mailman in locations that are more FHS compliant to help ease the writi

Re: [Mailman-Users] selinux postfix + mailman

Dony Tata wrote: > how to configure selinux on centos 5 , i use postfix and mailman,if > selinux set enabled, i have got error in /var/log/mailman/error > "command failed: /usr/sbin/postalias /etc/mailman/aliases (status: > 1, Operation not permitted)", if selinux set disabled, it's work > fine. Bu

Re: [Mailman-Users] converting an ezmlm archive

Brandon Sussman wrote: > A 15 minute attempt to find doc on how to convert an ezmlm archive > to mailman is not showing much promise. > > Without me personally writing a converter, is there any recent > wisdom on doing this? You should just need to convert the exmlm archive to mbox, then import i

Re: [Mailman-Users] getting python errorss with check_perms

Rob Tanner wrote: > I think the bug URL you gave me is a wrong URL. Bug 132495 is a > Japanese encoding bug and its status is closed (which I presume > means fixed). That doesn't sound like the problem I'm seeing. The bug summary may not sound like what you're seeing, but the patch that was appl

Re: [Mailman-Users] getting python errorss with check_perms

Rob Tanner wrote: > Running this as root so that it can fix any perm problems, but I'm > getting what I assume to be python errors: > > [EMAIL PROTECTED] mailman]# bin/check_perms -f > Traceback (most recent call last): > File "bin/check_perms", line 382, in > checkarchives() > File "bin/check

Re: [Mailman-Users] After Installing Virtual Hosts with mailman, regular aliases quit working.

audit wrote: > Here's my output from postconf -n > > alias_database = hash:/usr/local/etc/postfix/aliases > alias_maps = hash:/usr/local/mailman/data/aliases [...] > Problem is, anything that I had in my /usr/local/etc/postfix/aliases > file that wasn't the standard root, bin, postmaster, etc won

Re: [Mailman-Users] mass subscribe

Khalil Abbas wrote: > I have a dedicated server with cent-OS .. I access my mailman using: > > http://www.mydoman.com/mailman/admin/listname > > based on the message below, a nice fellow answered my questions by: > path-to-mailman/bin/ > > now I browsed my server using SSH but couldn't find

Re: [Mailman-Users] Adding the list aliases

mattias wrote: > But after i have created a list with newlist Wil the aliases be > displayed? I believe so (but it's been a long time since I created a list without using the nice Postfix integration that handles this automatically, so I could be wrong). > And wil all this commands work iven if i

Re: [Mailman-Users] a few questions about the NNTP gateway

Brad Knowles wrote: > There's no way we can possibly track down every single developer on > every single platform that is creating localized patches for Mailman > on their platform. The only way this process can possibly work is > if they use our mechanisms to send their patches to us. FWIW, I wa

Re: [Mailman-Users] a few questions about the NNTP gateway

(Disclaimer: I'm not a Debian maintainer or user) Brad Knowles wrote: > On 8/25/07, Manlio Perillo wrote: > >> Do the debian maintainer of Mailman frequent this mailing list? > > Not so far as I know. > > Improved contact between our project and the other projects which > take our code and cr

Re: [Mailman-Users] Subscribing by email?

Brad Knowles wrote: >> Also does mailman 2.1.3 support the sending of a blank email to >> [EMAIL PROTECTED] ? (or some similar address) instead >> of the subscribe email via request? > > Sure. Just set up your aliases to support that. Mailman doesn't > actually see anything of the addresses t

Re: [Mailman-Users] Error - can't open aliases.db

Hydro John wrote: > Frustraiting! No aliases file in /var/lib/mailman/data/... it must > be that the file in /etc/mailmain/ is the one (or at least it looks > like the one) that the service should be using... It sounds like you're using a Red Hat or Fedora packaged mailman. In those distros, mai

Re: [Mailman-Users] Error when sending from an unsubscribed address

Brad Knowles wrote: > On 7/10/07, Simon Helson wrote: > >> I'm trying to send email to a mailman list from an address that >> isn't subscribed to the list, The expected behaviour (or the >> configured at least) would be for this message to be held for >> moderation, however it's not, and I'm g

Re: [Mailman-Users] Low level smtp error: Server not connected

Brad Knowles wrote: > On 5/29/07, Leonard Jacobs wrote: > >> It is strange that a pretty vanilla installation, CentOS and >> Postfix with the latest Mailman version of 2.1.9 is so hard to >> configure and use. > > Can you share with us the relevant portions of your mm_cfg.py file, > and your p

Re: [Mailman-Users] Looking for professional help

James Dinkel wrote: > Why does there need to be a patch to mailman? Could you just setup > htdig and have it index the pipermail web pages? That doesn't provide the per-list integration that Brian wants. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp

Re: [Mailman-Users] Looking for professional help

Brian Carpenter wrote: > My installation of mailman is on a Linux box running cPanel/WHM. The > os is CentOS 4.4. It is not an apple machine. It seems to me that > the patch is looking for a Defaults.py.in file, which I don't have. > I could be wrong however in interpreting the error message. I do

Re: [Mailman-Users] us-ascii problem with new install in Ubuntu(SOLVED)

Mark Sapiro wrote: > Some additional information: > > This is mailman 2.1.8-2ubuntu2. > > The reference to the 'bug fix' is at > > in which is found > > * Make sure we don't ship /var/lib/mailman/pyt

Re: [Mailman-Users] FW: Wrong group

Ralph, Also, you should check out the Mailman install manual, at least the section on integrating Postfix. http://www.list.org/mailman-install/node13.html And of course, peruse the Mailman FAQ if you haven't already done so. If the package you are using has omitted some of these steps you may n

Re: [Mailman-Users] FW: Wrong group

Ralph Utbult wrote: > Installed package via X (Gnome). Version 2.1.9. What distro and distro version? > Since I'm not a regular Un*x administrator (fix some simple mail > problem once a month) I tend to like GUI over CMD ;-) Fair enough. Though mailman provides no GUI method of installing, so

Re: [Mailman-Users] Wrong group

Ralph Utbult wrote: > I run mailman with Postfix. Have MTA='Postfix' and have run > check_perm a number of times, with -f > How do I tweak the mail server (a.k..a Postfix) to run the script as > group "mail"? What are the permissions and owner/group for the mailman aliases file? Postfix will execu

Re: [Mailman-Users] Mailman on Mac OS X Server 10.3: Outgoingmessagesstuck in qrunner/in folder

Stephen J. Turnbull wrote: > Todd Zullinger writes: > > > Nothing wrong with that. It's why open source is so nice. I have > > the choice to find vendors and projects that share more of my > > values than others may. If FHS compliance is really important to >

Re: [Mailman-Users] Mailman on Mac OS X Server 10.3: Outgoingmessagesstuck in qrunner/in folder

Brad Knowles wrote: > At 10:20 PM -0500 12/14/06, Todd Zullinger wrote: > >> But what value would MacOSX specific integrations be to the >> Mailman project? > > Well, if they fed their changes back to us, that would allow us to > incorporate that into future vers

Re: [Mailman-Users] Mailman on Mac OS X Server 10.3: Outgoingmessagesstuck in qrunner/in folder

Brad Knowles wrote: > Even if they have made the source code available for everything > they've done with regards to Mailman (which includes all their > proprietary management tools), this is not the same thing as > contributing that code back to the Mailman project. But what value would MacOSX

Re: [Mailman-Users] Mailman on Mac OS X Server 10.3: Outgoingmessagesstuck in qrunner/in folder

Brad Knowles wrote: > We can tell you what the Mailman-standard was is to start them, but > Apple has created their own code to manage this aspect of Mailman > operations and they haven't shared that with us. Apple does provide the source code for their mailman packages. You can browse it here:

Re: [Mailman-Users] A scrubber issue

I wrote: > Tokio Kikuchi wrote: [...] >> But as to the default charset is 'us-ascii' problem, if we put the >> part together the parts, some language text (like japanese) become >> irreversibly unreadable. It is safe to keep it in a separate file >> if you can't archive the whole message in multip

Re: [Mailman-Users] A scrubber issue

Tokio Kikuchi wrote: > Folks, > > I'm OK with changing the recomposing part in Scrubber.py: > > if not part or part.is_multipart(): > continue > > to > > if part.is_multipart(): > continue > > It looks like the email package is more robust than it was when the > bug report was issued

Re: [Mailman-Users] A scrubber issue

Mark Sapiro wrote: > Todd Zullinger wrote: [...] >>Poking in the email package (on python 2.4.4) shows: >> >>def get_content_charset(self, failobj=None): >>"""Return the charset parameter of the Content-Type header. >> >>Th

Re: [Mailman-Users] A scrubber issue

Mark Sapiro wrote: > In another reply, I suggested a simpler change Yeah, I should have just waited a little longer before posting a half-baked diff. :-) > In order to fix the bug we really only need to skip parts with payload > = None so if we want to keep the 'empty' part, the fix should be >

Re: [Mailman-Users] A scrubber issue

Related to the second part of Werner's message being scrubbed with the message: An embedded and charset-unspecified text was scrubbed... Poking in the email package (on python 2.4.4) shows: def get_content_charset(self, failobj=None): """Return the charset parameter of the Conten

Re: [Mailman-Users] A scrubber issue

Tokio Kikuchi wrote: > It looks like the problem is something to do with email package > behavior. Here is a test code to reproduce the problem: That's neat. I like how you can do if not p: print p and it'll print out "A message without header". :) Would an (ugly, amateurish) work-around

Re: [Mailman-Users] A scrubber issue

Mark Sapiro wrote: > It shouldn't be a content filtering issue. If a part is missing a > Content-Type: header, the message methods get_content_type() and > get_content_maintype() which are used by MimeDel.py (content > filtering) return the default types which are text/plain and text > except for s

Re: [Mailman-Users] A scrubber issue

Hi Mark, Mark Sapiro wrote: > There seems to be another issue in that there is no 'link' to the > scrubbed part, just a relative URL which doesn't work. Yes, there are other issues with the configuration there. Click on the list info link and then follow that to the archives. You get into the t

[Mailman-Users] A scrubber issue

In honor of recent discussions on pipermail, I think I've found another issue with archiving, though this seems to be in Mailman.Scrubber. In a few recent posts to the GnuPG lists, Werner Koch sent along some signed patches fixing issues in the gpg code. Unfortunately, the archives ate his posts[

Re: [Mailman-Users] Mailman archive messages(not rm, but install!)

Paul Tomblin wrote: > Oh right, now I get it. I told you I didn't know Python, but I > should have been able to figure that > def __init__(self, outfp, mangle_from_=True, maxheaderlen=78): > meant that it defaulted to True in Generator.py so didn't need to be > changed in Mailman. :-) I actu

Re: [Mailman-Users] Mailman archive messages(not rm, but install!)

Mark Sapiro wrote: > Paul Tomblin wrote: > >>Quoting Barry Warsaw ([EMAIL PROTECTED]): >>> >>> It already does escape From lines in the body of the message. It >>> does this by way of the email package's Generator class, which is >>> instantiated with mangle_from_=True. >> >>Must be a newer vers

Re: [Mailman-Users] change thread list most recent to top

Barry R Cisna wrote: > Thanks for the response. Want I m wanting to do is show recent > threads,,the same as the other mailman list lines up most recent > posts at the top such as here: > > http://www.mail-archive.com/mailman-users%40python.org/ I don't think that mail-archive.com uses pipermail

Re: [Mailman-Users] Mailman archive messages

Paul Tomblin wrote: > Quoting Mark Sapiro ([EMAIL PROTECTED]): [...] >> You can remove all messages from a list's pipermail archive by >> >> bin/arch --wipe listname /dev/null > > What, "rm -rf" not good enough for you? :-) You do have to know the location of the list archives with rm whereas w

Re: [Mailman-Users] invalid checksum while doing portinstall

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Zbigniew Szalbot wrote: > Hello, > > I have a problem installing mailman under FreeBSD 6.1. When I go to ports > to install mailman, it gives me an error message about invalid checksum. > > Distinfo file shows the following): > > MD5 (mailman/mailm

Re: [Mailman-Users] a few details

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Matt Herzog wrote: > When I try try to accept an invitation to a group I get this bounce message: > > <[EMAIL PROTECTED]>: Command died with status 2: > "/usr/pkg/lib/mailman/mail/mailman request mung". Command > output: Group mismatch error.

Re: [Mailman-Users] Hijacking threads and netiquette (was: e: Obscure addresses problem)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Dyer-Bennet wrote: > If you want to take a rules-lawyer approach and use it to resist any > suggestion of change, be my guest. So far as I know, what's at > issue here is the question of interoperability in an area where > there are no formal st

Re: [Mailman-Users] Hijacking threads and netiquette (was: e: Obscure addresses problem)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Dyer-Bennet wrote: > It's an issue in the interaction of browsers and Mailman. It could > almost certainly be fixed by either side. If you want to start a > finger-pointing contest and say "not my problem" that's your > privilege of course, but

Re: [Mailman-Users] Hijacking threads and netiquette (was: e: Obscure addresses problem)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Dyer-Bennet wrote: > On 9/5/06, Todd Zullinger <[EMAIL PROTECTED]> wrote: > If firefox has profiles, they're not in the menu and not in the help > (under that name). I don't know the various ways to change the profile

Re: [Mailman-Users] Hijacking threads and netiquette (was: e: Obscure addresses problem)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Dyer-Bennet wrote: > I'm not convinced there's anything about this in the FAQ. > > 4.65 is not about the issue I'm raising; that's about cookie issues, > whereas my case is that the password field isn't recognized in the > first place. I've tes

Re: [Mailman-Users] Postfix Question

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jason [WeatherServer] wrote: > Thank you for the reply. At least some people are able to answer > questions rather then replying with more then just read the FAQ's You ask an off-topic question here and then you have the nerve to make a remark like th

Re: [Mailman-Users] Some basic how-to questions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ken Winter wrote: > My host administrator says I have the privileges I need. Indeed, I can get > to /usr/local/mailman/ through a SSH shell. Excellent. > But, see, I'm more-or-less UNIX / LINUX ignorant, so I can't seem to > get anything to happen f

Re: [Mailman-Users] Some basic how-to questions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ken Winter wrote: > Using the Mailman web admin interface, can I / how can I: > > 1.Delete an entire mailing list? By default you can't do this from the web interface. If the site admin puts OWNERS_CAN_DELETE_THEIR_OWN_LISTS = yes into mm_cfg.p

Re: [Mailman-Users] query re "message has implicitdestination"(devils advocate!)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brad Knowles wrote: > Looking at > , > > it looks like they got up to version 2.1.5, but again I'm still > trying to figure out what parts may have been modified by A

Re: [Mailman-Users] query re "message has implicit destination"(devils advocate!)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] wrote: > I'm just concerned that sharing might not be the intention of the > system owner. No problem. Sharing this source code is perfectly fine with the system owner. I know him well enough to know that implicitly. - -- Todd

Re: [Mailman-Users] query re "message has implicit destination"(devils advocate!)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] wrote: > You have to actually receive a distribution to have GPL rights. > Merely having access to somebody else's copy is not enough. The system owner most certainly allows me to access and use the source that he was provided as par

Re: [Mailman-Users] query re "message has implicit destination"(devils advocate!)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] wrote: > If you actually do have the right to do so, yes, please. I do, AFAIK. Mailman is GPL'd and I have legitimate root access on that system so I have access to the source code. AIUI, the GPL doesn't permit them to restrict wha

Re: [Mailman-Users] query re "message has implicit destination"(devils advocate!)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] wrote: > Has anybody at Mailman asked CPanel, Plesk, or Apple for source and > been refused? Or one of their customers, and been refused because > they were under NDA? If we haven't asked, how can we bitch? I asked cPanel a few yea

Re: [Mailman-Users] Contemplating new installation

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brad Knowles wrote: > At 7:21 PM + 2006-07-26, Jon Loose wrote: [...] >> Second, my previous install of mailman was 2.1.x running under >> /usr/local/mailman. I note that the fedora installation already >> seems to have mailman files distribute

Re: [Mailman-Users] GID mismatch with Postfix on Fedora Core 5 install of mailman RPM

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chris Lawson wrote: > Please excuse what may well be an FAQ but I did search the list > archive and couldn't get an answer. > > I am running Postfix and Mailman on Fedora Core 5 system. [...] > I have a bunch of lists that *were* working under Sendmai

Re: [Mailman-Users] Script problem

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jewel wrote: > I am trying to write a script which will email me a list of all the > lists and their members. The script below will only output a count of list members (that's what the |wc -l does). > I was able to find the following below but keep

Re: [Mailman-Users] Pipermail directs to http instead of https?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ryan Steele wrote: > Todd Zullinger wrote: [...] >> If RedirectPermanent broke things horribly, it likely wouldn't be >> in the FAQ. It should only cause one redirection, from http to >> https. >> >> > I

Re: [Mailman-Users] Pipermail directs to http instead of https?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ryan Steele wrote: > I can't see having RedirectPermanent being a good solution...many > servers limit the number of redirections, and I know that Firefox > and IE will suffer from redirection limits as well...there is > extensive documentation of this

Re: [Mailman-Users] Pipermail directs to http instead of https?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Patrick Bogen wrote: > On 6/27/06, Ryan Steele <[EMAIL PROTECTED]> wrote: >> I have a peculiar problem. An existing list I'm trying to repair has >> problems accessing the archives. The archives link changes the protocol >> to http instead of keeping

Re: [Mailman-Users] Members list settings

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mark Sapiro wrote: > I prefer however to think in terms of the RFEs on this which ask for > various things from simply exposing the parameter in the web > interface to providing a radio button selection (e.g. 20, 50, 100, > all) on the pages to paginat

Re: [Mailman-Users] changing domain name in list

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 ArteryPlanet.Net :: Manuel Kissoyan wrote: > I just moved an account from one server to another and then changed > the domain name, for some reason the control panel (cPanel) hasnt > changed the mailman domain name Ahhh, the beauty of control panels.

Re: [Mailman-Users] Archived Messages Not Saved

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Charles J. Hargrove wrote: > I am using the FC5 Mailman package. The archive files since the new > build are being kept in /var/lib/mailman/archives/private/. That's good. What does $ ls /var/lib/mailman/archives/private/$listname* show? Also

Re: [Mailman-Users] Archived Messages Not Saved

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Charles J. Hargrove wrote: > I recently had to rebuild my server after a long run of 6 years. > The drive that contained the Mailman archives, mailing lists, member > records, etc was mounted as the secondary drive so that I would not > lose the info.

Re: [Mailman-Users] Permissions on public archives (apache 403)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michael Berkowski wrote: >> What are the permissions on /var/lib/mailman? Are you running >> SeLinux or any other 'extra' access controls? > > SELinux is running and /var/lib/mailman looks like: > drwxrwsr-x 9 mailman mailman 4096 Apr 17 15:17 mailma

Re: [Mailman-Users] follow up: help request: new 1300 member list results inmostly bounces

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nathan wrote: > Below is the response from the host. They seem to feel it's all on > the recipient's end. Does this make sense? or is it passing the > buck? [...] > They suggest sending out 10-15 emails at a time - is there a way to > set mailman up to

Re: [Mailman-Users] FW: Install issues

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Defryn, Guy wrote: > Doh! After rebooting I did not start the processes again > Seems to work now Cool. If you want to be sure the services start at each boot on a RH/Fedora system, use chkconfig to turn them on. For postfix and mailman: # chkconf

Re: [Mailman-Users] FW: Install issues

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Defryn, Guy wrote: > I did run genaliases and that generated the following error > > Traceback (most recent call last): > File "./genaliases", line 116, in ? > main() > File "./genaliases", line 106, in main > MTA.create(mlist, nolock=True

Re: [Mailman-Users] changing hostname

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Anne Ramey wrote: > I changed my hostname from the time I first installed mailman. For the > most part, the transition went smoothly, but we still have a few traces > I'd like to get rid of. The host name this list prefers for email has > taken ca

Re: [Mailman-Users] PGP keys causing problems

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mark Sapiro wrote: > I have identified the problem with 2.1.5 and earlier. Basically, it > has nothing to do with PGP signed messages. The problem was if a > message contained a multipart MIME sub-part which in turn contained > one or more text/plain p

Re: [Mailman-Users] PGP keys causing problems

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mark Sapiro wrote: > Todd Zullinger wrote: [...] >>Around line 300 in Handlers.Scrubber, the comments say: >> >># All parts should be scrubbed to text/plain by now. >> >>and then a simple test for a non text/pl

Re: [Mailman-Users] PGP keys causing problems

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mark Sapiro wrote: > Before giving up on the archive, look at the 'source' html of the > archive page and look at the 'source' of the scrubbed attachment(s). > I've seen scrubbed attachments that look like X is missing when > viewed in browser A and lo

Re: [Mailman-Users] PGP keys causing problems

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeff DeReus wrote: > On 5/17/06, Todd Zullinger <[EMAIL PROTECTED]> wrote: [...] >> To be clear, does the message arrive properly to list members or is >> the attachment and body stripped there as well as in the archives? >

Re: [Mailman-Users] Everything is an attachment

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mark Sapiro wrote: > As far as it being worth it to upgrade to 2.1.6, there are a few > security issues in 2.1.5 that are fixed in 2.1.6, so yes, I think > it's worth it, but I would suggest trying to go all the way to 2.1.8 > if possible. But none of

Re: [Mailman-Users] PGP keys causing problems

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeff DeReus wrote: > Unfortunately filter_content was not set to yes. I am assuming that > would be fairly "handy". I'm not sure whether that will any effect on the archiving or not. It's been a long time since I tested that. > Although everything g

Re: [Mailman-Users] Announce-list only.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Fabiano Breves wrote: > I need a tip about securing a announce-list. I've setup every user > to be moderated and set just one non-member e-mail address to post > without moderation but It feels quite insecure. Is there a way to > make this e-mail addre

Re: [Mailman-Users] PGP keys causing problems

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeff DeReus wrote: > The poster uses an OpenPGP/MIME signature. Okay. > the pass_mime_types == > > multipart/mixed > multipart/alternative > text/plain I should have asked whether the filter_content setting was yes or no too. If it's no, then the

Re: [Mailman-Users] PGP keys causing problems

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeff DeReus wrote: > I am running mailman 2.1.5 with sendmail. One of my users sent in > an attachment with a message to the list. When he signs with his > PGP key, only the PGP signature remains in the message. I have yet > to locate the rest of th

Re: [Mailman-Users] Everything is an attachment

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Steve Campbell wrote: > BTW, I did find an RPM, but don't know it validity from: > > http://www.wesmo.com/rpm2html/x86/mailman-2.1.6-1.i386.html > > Is it worth the effort to upgrade from 2.1.5 to 2.1.6? I'd also > really like to stay in the RPM arena

Re: [Mailman-Users] hot to setup a commits list?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Manlio Perillo wrote: > Brad Knowles ha scritto: >> [...] >> >>> But, as I can see, it is the only solution. >> >> Unless you can get the commit notification process to add an >> "Approved: password" line to the headers of your message, or the >> fir

Re: [Mailman-Users] hot to setup a commits list?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I wrote: > I haven't setup any hook-scripts in Subversion, but couldn't you > modify the hook-script to add an Approved: header (or body line)? > > The commit-email.pl script in my (dated) copy of subversion-1.2.3 > looks like it'd be simple to do eit

Re: [Mailman-Users] hot to setup a commits list?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Manlio Perillo wrote: > Brad Knowles ha scritto: >> At 1:52 PM -0200 2006-05-16, Manlio Perillo wrote: >> >>> The list is moderated but, since it is a nuisance to have to >>> approve all messages, I'm thinking to remove the moderation flag >>> on t

Re: [Mailman-Users] Mailman as a newletter manager

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Julianna wrote: > I am looking for software to manage a newsletter, and I think that > with some configuration I can do this with Mailman. The end-product > I want is a newsletter with content contributed my subscribers and > non-subscribers, with a li

Re: [Mailman-Users] Automatic Reply To The List

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 (Oh the irony, I accidentally sent this via private reply and not to the list. Damn Murphy.) Jackson Madison wrote: > Is it possible that mailman can have all my users reply directly to > the list and not the person that sent the email? Yep. > I wa

Re: [Mailman-Users] Problem with the forward slash in digestannouncements

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] wrote: > I've been browsing the archives lately just as a learning tool, and > I'm just finding out that MUAs play such a large part of what I see > here in all of email. OE is what I use at work, Thunderbird at > home, so that expla

Re: [Mailman-Users] mailman crashed; messages are shunted

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mark Sapiro wrote: > This error is in cPanel specific modifications to Mailman having to > do with adding '_domain' to list names to support the 'same' list > name in multiple domains. > > I don't know specifically what their patches are in this area.

Re: [Mailman-Users] mailman crashed; messages are shunted

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chuck Vohs wrote: > I am running cPanel: > WHM 10.8.0 cPanel 10.8.2-C90 > CentOS 4.3 i686 - WHM X v3.1.0 > > Any message sent to any mailman list on my server gets shunted. I > have tried reinstalling python, mailman, spamd, rebooting. How'd you rein

Re: [Mailman-Users] Rpms for RHEL/Centos 4?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Oliver Schulze L. wrote: > anyone knows where to find rpms for the latest version of mailman? > I need for CentOS 4.3 I can't answer your question directly, but if you don't find the rpms you are looking for, it's not very difficult to build your own.

Re: [Mailman-Users] FC5 genaliases problem

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michael McAndrew wrote: > Hi there, > > I'm configuring mailman from a clean standard FC5 installation using > Postfix as the MTA. > > I have checked that the POSTFIX_ALIAS_CMD and POSTFIX_MAP_CMD > variables are set correctly in Defaults.py. They

Re: [Mailman-Users] Confirmation messages

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mark Sapiro wrote: > There are work arounds, but there's no simple way for an admin to > change a members address without confirmation. > > The work arounds are: > > If you have command line access to the Mailman installation, you can > use bin/withl

Re: [Mailman-Users] get members list

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ed wrote: > Todd: > > <> Is there a way to get all the members of a mailing list in a single >> page? Sometimes this is more convenient. > > FAQ 3.62: How do I extract a list of my list's members > (subscribers)?>> > > Although that reply answers ON

Re: [Mailman-Users] get members list

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel Carvalho wrote: > Is there a way to get all the members of a mailing list in a single > page? Sometimes this is more convenient. FAQ 3.62: How do I extract a list of my list's members (subscribers)? http://www.python.org/cgi-bin/faqw-mm.py?que

Re: [Mailman-Users] Can't send or receive via mail lists

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Webmaster wrote: > I'm running a VPS which uses CentOS, Cpanel and WHM. See FAQ 6.11 for info on cPanel. http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq06.011.htp > The first problem I encountered with Mailman, I wasn't able to create

Re: [Mailman-Users] Removing footer text?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Matt Singerman wrote: > All I would like to do is remove the footer text that Mailman adds > on to the end of all messages - the part that reads something like: In addition to what Andre said, I believe you can get the same effect via the web interfac

Re: [Mailman-Users] FAQ 6.9 on Debian Sarge

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Manlio Perillo wrote: > Todd Zullinger ha scritto: > >> But IIRC, the default MTA on Debian is Exim. So there are probably >> less users testing the postfix integration in the packages. That's >> my guess. >> >

Re: [Mailman-Users] FAQ 6.9 on Debian Sarge

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mark Sapiro wrote: > I don't understand the need for the 'adduser' you mentioned in your > first post. Perhaps you can clarify what the permissions, etc. are in > the Debian package as shipped, and what is required so we can get the > FAQ right. Is it

  1   2   >