Hello,
thanks for all the Tipps folks.
But when I say what the mistake was you all gona beet me up.
mailman wasn´t startet.
I could bite in my ass, I spend a lot of time to find whats wrong an then. argh.
I thought the service starts automaticly but anyway.
Thank to all.
Mit
solaris 9
mailman 2.1.3
htdig 3.1.6
patches: indexing-2.1.3-0.1 and htdig-2.1.3-0.4
htdig is working. from the command line i can do:
#/opt/www/htdig/bin/htsearch -c
/usr/local/mailman/archives/htdig/mailman.conf
as users root , mailman and nobody and get the html search results
correctly
Morgan Fletcher [EMAIL PROTECTED] writes:
Do I need to update the data under $prefix/lists/ when upgrading from 2.0.X
to 2.1.X? If so, how? I don't see any mention of it in the 2.1.3 INSTALL or
UPGRADING document, but when I try the upgrade with 2.0.8-era lists/ data,
I get errors about
I have a list with a in the name, is this a dis-allowed character in
the list names?
I have recieved a message back indicating a problem with the use of
the see below:
Final-Recipient: rfc822; arts[EMAIL PROTECTED]
Action: failed
Status: 5.0.0
Diagnostic-Code: X-Postfix; Command died with
What's the Best Current Practice for running Multiple or Redundant
Mailman servers?
I have a distributed mail system - centralized local message store, and
many SMTP/POP heads. I'd *like* to be able to run Mailman on all of them,
with the same lists and configs.
Currently I NFS mount the configs
03-Dec-03 at 10:08, [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote :
I have a list with a in the name, is this a dis-allowed character in
the list names?
I have recieved a message back indicating a problem with the use of
the see below:
Final-Recipient: rfc822; arts[EMAIL PROTECTED]
SW == Simon White [EMAIL PROTECTED] writes:
SW The in shell has a special meaning, it would have to be escaped,
SW because
If you read Business Week, the Tech You column has a comment email
address of tech[EMAIL PROTECTED]
Just because the unix shell does something with doesn't mean it is
While this is all true to some degree, don't overlook something even more
obvious with regards to mailman, the web interface in trying to display
that list name would actually be trying to display a page that takes a
parameter. Apache / IIS would be significantly confused for sure. 's are
not
I'm getting more confused by the second...
I've removed the list and re-created it without the in the name.
What happend is I'm transfering from an old server to a new mailman
server. The list created just fine and displays just fine. It seems
postfix is recieving the list name seperated as two
I'm getting this error when I try to start the mailman qrunner daemon after
upgrading to 2.1.3 from 2.0.13. Actually, I get this 10x, each one causing
the qrunner process to die and spawn anew:
Traceback (most recent call last):
File /usr/local/mailman/bin/qrunner, line 270, in ?
main()
e == ed [EMAIL PROTECTED] writes:
e parameter. Apache / IIS would be significantly confused for sure. 's are
e not valid in HTML file names as they specify a part of a parameter list on
e the url.
If the code isn't URI escaping things when needed, then it is a
security breach waiting to
I just did a
./bin/genaliases
and after that the existing mailing list were ok.
Tom
On Wed, 2003-12-03 at 09:58, Morgan Fletcher wrote:
Morgan Fletcher [EMAIL PROTECTED] writes:
Do I need to update the data under $prefix/lists/ when upgrading from 2.0.X
to 2.1.X? If so, how? I don't see
On Wed, 2003-12-03 at 11:58, Morgan Fletcher wrote:
Morgan Fletcher [EMAIL PROTECTED] writes:
Do I need to update the data under $prefix/lists/ when upgrading from 2.0.X
to 2.1.X? If so, how? I don't see any mention of it in the 2.1.3 INSTALL or
UPGRADING document, but when I try the
Hello there,
i'm new to mailman,
i have installing mailman 2.1.3 on my FBSD 5.1 machine
and have postfix as my MTA, everything work well
till i add my e-mail to list,
but when i'm trying to send mail to my list,
it sent, but it's not sent to other members
i've try this :
jalak# ps -aux | grep
On Wed, 2003-12-03 at 13:41, Charlie Watts wrote:
What's the Best Current Practice for running Multiple or Redundant
Mailman servers?
I have a distributed mail system - centralized local message store, and
many SMTP/POP heads. I'd *like* to be able to run Mailman on all of them,
with the
15 matches
Mail list logo
