Hi Duncan,
is SELinux enabled?
[EMAIL PROTECTED] root]# getenforce
If SELinux is enforcing set it temporary into permissive mode by
[EMAIL PROTECTED] root]# setenforce 0
and check your webinterface again.
Timm
Mark Sapiro schrieb:
Duncan Drury wrote:
After bringing the RedirectMatch
Carlos Williams wrote:
I have no idea what happened to my mailman installation. As far as I
can tell from a very basic administrative and user level, it works
perfect with my Postifx install. Only only noticed this was a problem
when I started to migrate my mailman data to a new email server I am
On Mon, Jul 14, 2008 at 11:33 AM, Mark Sapiro [EMAIL PROTECTED] wrote:
Someone else reported a similar symptom a month or two ago. (I just
tried to find this in the archive, and I see it was you, not someone
else.)
Yes - I reported this during my migration help email. It was me...
I have no
I'm running Mailman 2.1.9 on Solaris 10. Sometime this weekend we had a
mail loop which pounded our list server. The mail loop has been fixed
but there is a python process that is consuming an entire cpu. Further
inspection of this process reveals:
qrunner --runner=ArchRunner:0:1 -s
I'm
Andy Cravens wrote:
I'm running Mailman 2.1.9 on Solaris 10. Sometime this weekend we
had a mail loop which pounded our list server. The mail loop has
been fixed but there is a python process that is consuming an entire
cpu. Further inspection of this process reveals:
qrunner
Dragon wrote:
Andy Cravens wrote:
I'm running Mailman 2.1.9 on Solaris 10. Sometime this weekend we
had a mail loop which pounded our list server. The mail loop has
been fixed but there is a python process that is consuming an entire
cpu. Further inspection of this process reveals:
On Sun, Jul 13, 2008 at 03:03:41PM -0700, Mark Sapiro wrote:
Because those host names are not in the VIRTUAL_HOSTS dictionary. You
could put something like
add_virtualhost('192.168.1.1', '192.168.1.1')
in mm_cfg.py and then create a list in the '192.168.1.1' domain, but
don't do that
Zbigniew Szalbot writes:
1/ Mailman as a discussion list - like the one we're having here. I
don't imagine spammers would be setting up their lists as discussion
list, would they? I don't actually imagine big time spammers using
mailman. They're all about botnets.
Big time spammers
I often see addresses popping up and subscribing to all visible lists on
my servers.
Sometimes they're a curious individual, and most times they are spammers
harversting addresses (as these are open only to admin).
I wonder what the coding price would be, if it can even work with
mailman,
First, I think it would have better luck on the developers mailing
list :)
But as for the idea, I think it could work, but someone would have to
provide the hosting for the database that would hold all the info. And
we would have to figure out who would be a trusted source to report
the
The problem I see with this is much like the DNSBLs and Block lists
(spamhaus?).
As Jason put it, one person's spam could very much be another person's
ham, so mail starts getting rejected by those who outright trust such a
database and it is hell trying to get removed from those said lists.
A long time ago I wrote a small Python script to allow me to easily manage
held messages for a number of Mailman-managed mailing lists. It worked well
for me, but was still a bit cumbersome because it required me to enter the
admin or moderator password for each list. I fixed that a few days
Gadi,
I think we could certainly do this, but we would need to carefully
vette the subscriptions to try to keep the more advanced spammers from
sneaking in.
Feel free to discuss this with me offline, if you like.
--
Brad Knowles
Sent from my iPhone
On Jul 14, 2008, at 10:25 AM, Gadi
Hi there,
Stephen J. Turnbull:
This is a market to gain for Mailman but it currently lacks a few
features to do that. Well, my post is slowly getting off topic
But IMO it would be quite on-topic for mailman-developers. This kind
of post would be more effective in inciting dev activity if
Mark Sapiro writes:
I have no idea how this happened. I suspect somehow instead of
mailman.mbox/mailman.mbox being a file, it somehow became a link back
to its parent. If this is the case, even rm -rf
/var/lib/mailman/archives/mailman.mbox may not succeed because it may
loop
On Mon, Jul 14, 2008 at 07:04:46PM -0700, Mark Sapiro wrote:
Put the following in mm_cfg.py
DEFAULT_URL_HOST = 'vidiot.com'
DEFAULT_EMAIL_HOST = 'vidiot.com'
Those two lines were there.
VIRTUAL_HOSTS.clear()
Don't see this mentioned in the Defaults.py file.
On Mon, 14 Jul 2008, Krystal Zipfel wrote:
The problem I see with this is much like the DNSBLs and Block lists
(spamhaus?).
As Jason put it, one person's spam could very much be another person's ham,
so mail starts getting rejected by those who outright trust such a database
and it is hell
Mike Brown wrote:
I tried it from work and got the same problem, virtual host unknown:
vidiot.com
Then vidiot.com is not a url host in the VIRTUAL_HOSTS dictionary.
Put the following in mm_cfg.py
DEFAULT_URL_HOST = 'vidiot.com'
DEFAULT_EMAIL_HOST = 'vidiot.com'
VIRTUAL_HOSTS.clear()
Carlos Williams wrote:
So I think I am simply going to just rm -rf
/var/lib/mailman/archives/private/mailman.mbox/mailman.box
This will retain the first mailman.box directory which is expected to
be there and then remove everything beyond that.
I will then assume at some point Mailman will
19 matches
Mail list logo
