Re: [Mailman-Users] migrated lists getting firefox error, and new name not original list name

Secondly when I send an email using a test list I also get @mailman2.rmtc.fedex.com as the email address rather than @mailman.rmtc.fedex.com? Get it where? If you mean in things like the List-* headers and the Sender:, fix_url will fix that too if DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST ar

Re: [Mailman-Users] Exim / Mailman No Longer Working

Ben Cummingswrote: > >I am having some difficulty getting Mailman to work with Exim after a >recent upgrade of the email software that we run. The configuration for >exim has remained, as has the configuration for mailman. This *was* >working, but is not after the update. > >The error message i get

Re: [Mailman-Users] migrated lists getting firefox error, and new name not original list name

Troy Campbell wrote: > >I just migrated some lists from a server called >mailman.rmtc.fedex.com to a new server called >mailman2.rmtc.fedex.com (both running >2.1.9) and configuring things to try to keep the >lists the original @mailman.rmtc.fedex.com name >and I'm running into two issues. > >Firs

[Mailman-Users] Exim / Mailman No Longer Working

Hello, I am having some difficulty getting Mailman to work with Exim after a recent upgrade of the email software that we run. The configuration for exim has remained, as has the configuration for mailman. This *was* working, but is not after the update. The error message i get in the Exim log:

[Mailman-Users] migrated lists getting firefox error, and new name not original list name

Hello, I just migrated some lists from a server called mailman.rmtc.fedex.com to a new server called mailman2.rmtc.fedex.com (both running 2.1.9) and configuring things to try to keep the lists the original @mailman.rmtc.fedex.com name and I'm running into two issues. First I've started getting

Re: [Mailman-Users] Mailman Archives page not updating

LexIcon wrote: > >Ok, so I ran... > >chown -hR mailman private/ > >... and changed the owner of everything in there to the mailman user. I >then ran... What you really want is chgrp -R mailman private/ >./unshunt > >... which took a long time to process, and then I ran... > >./arch listname

Re: [Mailman-Users] Mailman Archives page not updating

Mark Sapiro wrote: Then the recent posts are probably not in the archives/private/LISTNAME.mbox/LISTNAME.mbox file, perhaps because of some permissions error. If that is the reason, they are probably all shunted and in the shunt queue. If so, you will find error messages and tracebacks in Mailman

Re: [Mailman-Users] Indexing mail right after delivery

To follow up on this thread, there is now a FAQ at which contains an attached template, Ext_Arch.py, which can be used as an external archiver and which will add the message to the pipermail archive, and then call a stub function with arguments of the list name, host n

Re: [Mailman-Users] Mailman Archives page not updating

LexIcon wrote: >Ok, so I ran... > >//usr/lib/mailman/bin///checkperms -f/ > >... and it fixed a bunch of issues... the current result is "No problems >found" ... and now and I'm running... > >//usr/lib/mailman/bin/arch listname// >/ >... which processes a bunch of stuff, but the archive still doe

Re: [Mailman-Users] Mailman Archives page not updating

Mark Sapiro wrote: LexIcon wrote: I am entering "arch" in the /bin directory (/usr/lib/mailman/bin on a CentOS server), but the archive does not rebuild, and I only get the message "i686" back. I tried using "cleanarch" but I get the error message "bash: cleanarch: command not found"

Re: [Mailman-Users] Mailman Error

Gordon Smith wrote: > >We're running Mailman under Mac OSX Server 10.6.2. For the most part, it runs >incredibly well and I'm more than happy with it. > >However, we're having a problem which nobody seems to be able to resolve and >we cannot find out from anybody at Apple how to fix. > >We have

Re: [Mailman-Users] Mailman Archives page not updating

You're using the wrong arch; there's an arch command that tells you your machine's architecture (i.e. i686). What you'll want to do is go into /usr/lib/mailman/bin and execute ./arch and similarly for cleanarch ./cleanarch from there to make sure that you're executing the right thing. Or yo

Re: [Mailman-Users] Mailman Archives page not updating

LexIcon wrote: >I am entering "arch" in the /bin directory (/usr/lib/mailman/bin on a >CentOS server), but the archive does not rebuild, and I only get the >message "i686" back. > >I tried using "cleanarch" but I get the error message "bash: cleanarch: >command not found" > >I also get "bash: m

[Mailman-Users] Mailman Error

Hi Really sorry to bother you guys; I'm sure you're busy with lots of development issues. I'm just hoping you might be able to help with a problem with our Mailman configuration, even though it's not standard Mailman. We're running Mailman under Mac OSX Server 10.6.2. For the most part, it ru

[Mailman-Users] Mailman Archives page not updating

In regards to previous list message http://mail.python.org/pipermail/mailman-users/2008-February/060593.html ... I am entering "arch" in the /bin directory (/usr/lib/mailman/bin on a CentOS server), but the archive does not rebuild, and I only get the message "i686" back. I tried using "clea