Hi,
I've set up an ssl based virtual host and changed DEFAULT_URL_PATTERN to
'https://%s/cgi-bin/mailman'. Problem: only new created lists point to
https://. All old list still point to http:// e.g.
from /cgi-bin/mailman/listinfo. I read something about post-rewriting
URLs in the archive, but
Marcus Sobchak wrote:
I've set up an ssl based virtual host and changed DEFAULT_URL_PATTERN to
'https://%s/cgi-bin/mailman'. Problem: only new created lists point to
https://. All old list still point to http:// e.g.
from /cgi-bin/mailman/listinfo. I read something about post-rewriting
URLs in
Xabier == Xabier Guitián [EMAIL PROTECTED] writes:
Xabier What happens if... you kill python after 'theorically'
Xabier shutting down the mailman correctly?
The python process stops, dead.wink
Xabier Is this a problem to the possible mails that were being
Xabier processed?
Ben == Ben Ostrowsky [EMAIL PROTECTED] writes:
Ben As you may remember from our last thrilling episode, I've
Ben upgraded from 2.1.4 to 2.1.5. Our users are trying to send
Ben messages that are being held for review, which is fine. But
Ben when we try to release the messages,
Brad Knowles wrote:
At 11:21 AM + 2005-12-16, John Poltorak wrote:
When an invitation is sent out from a mailing list for someone to join,
how long is it before it expires?
I'm pretty sure that there is no explicit expiration period.
All confirmations including confirmation
All,
I have read through the mailing list and found this thread
http://www.mail-archive.com/mailman-users@python.org/msg33593.html
But I am stil a little confused about integrating all this. Postfix has
been up and running for a long time with virtual domains setup, now I
want a mailing list
Sruli Shaffren wrote:
Hi. I'm runniiing Mailman 2.1.6 and have installed htdig 3.1.6, and
integrated with mailman as per directions in HOWTOs I have found on this
list and elsewhere.
Does this mean you have installed patches 444879 and 444884?
The installation of htdig itself seems okay, as
Xabier Guitián wrote:
What happens if... you kill python after 'theorically' shutting down
the
mailman correctly? That is you execute the script '/etc/init.d/mailman stop'
wait half an hour and then kill the python process who is hoggin the CPU with
99% of use.
Which specific qrunner
Clóvis Tristão wrote
why appear this error in /var/log/mailman/error :
tail -f error
Dec 16 17:08:39 2005 qrunner(20303): main()
Dec 16 17:08:39 2005 qrunner(20303): File
/usr/lib/mailman/bin/qrunner, line 230, in main
Dec 16 17:08:39 2005 qrunner(20303): qrunner.run()
Dec 16
Clovis Tristao wrote:
After install Mailman 2.1.5-35.fc4, i create my own lists, in mailman
log files are appearing:
Dec 16 15:36:55 2005 (14252) delivery to [EMAIL PROTECTED] failed with
code -1: Server not connected
This comes from the SMTPDirect delivery module. The outgoing mail
server
Con Wieland wrote:
any ideas?
Your cron job
/usr/local/bin/python -S /usr/local/mailman/cron/senddigests
produced the following output:
Traceback (most recent call last):
File /usr/local/mailman/cron/senddigests, line 94, in ?
main()
File /usr/local/mailman/cron/senddigests, line
All,
I went ahead and tried to finish setting this all up. I created the test
list and the mailman list and also have the website portion working. But
when I send a message to subscribe or test-subscribe I get this message
in my maillog. I did restart postfix after screating the list.
User
Elijah Savage wrote:
All,
I went ahead and tried to finish setting this all up. I created the test
list and the mailman list and also have the website portion working. But
when I send a message to subscribe or test-subscribe I get this message
in my maillog. I did restart postfix after
13 matches
Mail list logo
