On 12/29/06, Benjamin Melançon <[EMAIL PROTECTED]> wrote:
> Here's a nice, low-key, thoroughly unimportant error (I hope).
>
> It's caused because /var/lib/texmf doesn't exist (although we have
> more files than anyone could want in /usr/share/texmf). Does anyone
> know offhand the proper resoluti
Hello Mailman experts,
Here's a nice, low-key, thoroughly unimportant error (I hope).
It's caused because /var/lib/texmf doesn't exist (although we have
more files than anyone could want in /usr/share/texmf). Does anyone
know offhand the proper resolution?
This is on CentOS (red hat enterprise
I am, since talking to you developing errors galore in
my system, with same boundry messages and it has
serious effect not just some undirected emails and is
getting worse. I will take care of but the time jibes
with when i visited you guys,it looks to be some sort
of protected streaming messages
Noah writes:
> thanks for following up. we just solved the problem.
Good!
> it was a misused wildcard in the mailman filter rules. I might
> have missed it but it feels like there is not enough verbose output
> in the mailman logs files to tell me that a message was filtered
> and an entr
Having been charged temporarily of a certain service, I've been asked to
solve in this period the following problem:
on a machine running many different virtual hosts, each time that a new
list is created with mailman, mailman adds to the list name the full
virtual domain name.
I mean: if I creat
