Michael Alberghini wrote:
For some reason my new subscriber messages are going out with only
my hostname, not the full domain name in the urls.
For example the welcome messages tells people to click
http://mailbox/mailman/listinfo/galileo
instead of
http://mailbox.gsu.edu/mailman/listinfo/galile
On Fri, 2003-10-31 at 21:38, Alexis wrote:
> Im running mailman 2.1.3 at my box, and i need to change a setting related
> to destination address, ive been reading and trying but i cannot get it
> working.
>
> I have a list called test.
>
> when i send a post to this lists, i need that the destina
On Fri, 2003-10-31 at 21:29, Scott Lambert wrote:
> On Sat, Nov 01, 2003 at 12:59:24AM +0100, Brad Knowles wrote:
> > At 6:21 PM -0500 2003/10/31, Scott Lambert wrote:
> > > I haven't looked at the code yet, and probably won't (ENOTIME), but
> > > it almost sounds to me like it's not pruning it's l
On Fri, 2003-10-31 at 20:52, Michael Wood wrote:
> All of our lists are closed and our members are internal; they don't need
> or want to subscribe or unsubscribe, etc.
>
> As it is, the headers and the subscribe/unsubscribe, etc. lines are filling
> the page. We'd like to either remove them or
Im running mailman 2.1.3 at my box, and i need to change a setting related
to destination address, ive been reading and trying but i cannot get it
working.
I have a list called test.
when i send a post to this lists, i need that the destination address in the
msgs that subscribers receive be the
On Sat, Nov 01, 2003 at 12:59:24AM +0100, Brad Knowles wrote:
> At 6:21 PM -0500 2003/10/31, Scott Lambert wrote:
> > I haven't looked at the code yet, and probably won't (ENOTIME), but
> > it almost sounds to me like it's not pruning it's list of handled
> > messages and has to walk all of them ea
All of our lists are closed and our members are internal; they don't need
or want to subscribe or unsubscribe, etc.
As it is, the headers and the subscribe/unsubscribe, etc. lines are filling
the page. We'd like to either remove them or move them below the message
area. Is there a way to do thi
On Friday, October 31, 2003, at 11:59 pm, Brad Knowles wrote:
At 6:21 PM -0500 2003/10/31, Scott Lambert wrote:
I haven't looked at the code yet, and probably won't (ENOTIME), but
it
almost sounds to me like it's not pruning it's list of handled
messages
and has to walk all of them each t
At 6:21 PM -0500 2003/10/31, Scott Lambert wrote:
I haven't looked at the code yet, and probably won't (ENOTIME), but it
almost sounds to me like it's not pruning it's list of handled messages
and has to walk all of them each time. I would have expected queue
handling to get faster as the que
On Fri, Oct 31, 2003 at 03:52:34PM -0500, Scott Lambert wrote:
> Once I kill off the mailman queue runners and clean up the several lock
> files for this mailing list, it runs just fine and manages to empty the
> archive queue.
Well, the above statement is not entirely accurate. It was working
qu
On Fri, 2003-10-31 at 14:39, Garey Mills wrote:
> Hi -
>
> I've got Mailman 2.1b2 installed. I have a problem because Mailman
> occasionally inserts a newline (x010) after the list name close bracket
> and before the subject description in the Subject: header line. It appears
> that this hap
John wrote...
> Well you've pegged it. That was a bug in version 2.1.2 which is fixed
> in 2.1.3. The patch for 2.1.2 should still be available - you could
> probably patch your running system and just leave it at that (an upgrade
> will bring the patch in anyway).
I am having trouble finding th
On Friday, October 31, 2003, at 08:52 pm, Scott Lambert wrote:
On Fri, Oct 31, 2003 at 09:40:11AM -0500, Jon Carnes wrote:
On Fri, 2003-10-31 at 09:26, Jay West wrote:
I'm using Mailman 2.1.2 on FreeBSD v4.8-Release, built using the
port. MTA
is sendmail 8.12.8p1
Very frequently I will see the
On Fri, Oct 31, 2003 at 09:40:11AM -0500, Jon Carnes wrote:
> On Fri, 2003-10-31 at 09:26, Jay West wrote:
> > I'm using Mailman 2.1.2 on FreeBSD v4.8-Release, built using the port. MTA
> > is sendmail 8.12.8p1
> >
> > Very frequently I will see the ArchRunner process using 99+ % of cpu. I have
>
Hi -
I've got Mailman 2.1b2 installed. I have a problem because Mailman
occasionally inserts a newline (x010) after the list name close bracket
and before the subject description in the Subject: header line. It appears
that this happens only with longer subject lines.
This causes
For some reason my new subscriber messages are going out with only
my hostname, not the full domain name in the urls.
For example the welcome messages tells people to click
http://mailbox/mailman/listinfo/galileo
instead of
http://mailbox.gsu.edu/mailman/listinfo/galileo
I can't find a way t
Hi,
I was currently using mailman 2.0.13.
This system was deployed into /home/mailman directory.
I redeploy a new server in mandrake 9.2 I use the package mailman-2.1.2.
The current install is in /var/lib/mailman.
How can I import my previous mailing list configuration and archive from
mailman 2
Well you've pegged it. That was a bug in version 2.1.2 which is fixed
in 2.1.3. The patch for 2.1.2 should still be available - you could
probably patch your running system and just leave it at that (an upgrade
will bring the patch in anyway).
Good Luck - Jon Carnes
On Fri, 2003-10-31 at 09:26,
I'm using Mailman 2.1.2 on FreeBSD v4.8-Release, built using the port. MTA
is sendmail 8.12.8p1
I was using a previous release of mailman, v2.0.x. I built a new machine to
run 2.1.2 on and did a fresh mailman install, then just moved the lists and
archives from the old machine to the new machine.
I'm using Mailman 2.1.2 on FreeBSD v4.8-Release, built using the port. MTA
is sendmail 8.12.8p1
Very frequently I will see the ArchRunner process using 99+ % of cpu. I have
searched the archives and found lots of messages about qrunners using large
percentages of cpu, but they all seem to talk abo
Hi Pascal,
> I was wondering if there was a reason why the only Mailman version
> available as a stable debian package is version 2.0.11?
> Version 2.1.3 is marked as unstable. Is the new version still in beta or
> is it ready to be deployed on a production site. In other words, would you
> recomm
Thank you Richard. When i've changed the "if" sentence four or six
messages to the locked list was received inmediatly. It's first time
that i don't need to remove the list and create again to continueing
receiving messages... very nice :-D
Maybe this is the solution, because now one machine-lis
22 matches
Mail list logo
