Can you manually force an archive of all
messages? (other than turning archival to 'daily' and waiting for a
day?)
thx
matt
> File "/home/mailman/Mailman/pythonlib/nntplib.py", line 111, in __init__
> self.sock.connect((self.host, self.port))
> socket.error: (111, 'Connection refused')
>
> Can somebody let us know what the problem is?
It says "connection refused", which sure looks like a daemon isn't
running.
> Hi
> I have just installed mailman and get the following error:
>
> Bug in Mailman version 2.0.1
> We're sorry, we hit a bug!
> Please inform the webmaster for this site of this problem. Printing of
> traceback and other system information has been explicitly inhibited, but
> the webmaster ca
Hi,
I've got Mailman up and running (mostly) with demime taking care of MIME
issues. The only problem I've run into so far is mail generated by Outlook
not being properly archived by pipermail. While the emails make it into the
archive, they are not threaded in the index. Emails generated by Pine
Hi,
On a small MailMan list I'm running (30-40 users) the list occasionally
receives duplicate, and on some occasions triplicate, messages. It happens
sporadically so it's hard to pin down exactly what's causing it. The list
will go for a few days running fine, then the next day send a few dups
hi,
the www-scripts don't run: 500 Internal server error
my error logs shows this:
[Thu Feb 8 20:43:48 2001] [error] (1)Operation not permitted: exec of
/opt/home/mailman/cgi-bin/admin failed
[Thu Feb 8 20:43:48 2001] [error] [client 194.119.237.2] Premature end of
script headers: /opt/home/m
Hi,
Sorry if this is a redundant post. I just installed mailman on a RH 7.0
machine, created a test mailing list and configured the list.
The problem is that when I send a mail message to test@.???.com
I get a message saying it could not be delivered. Part of the message is
below. An
Hopefully a quick question.
linux kernel 2.2.17,
postfix MTA
I created user, group and home directory mailman as root.
I created the /etc/aliases entry
I installed mailman from the mailman account.
it installs properly but after I create a list and try sending to it i
get a message that it wan
Len Merikanto wrote:
>- Transcript of session follows -
> Failure to exec script. WANTED gid 12, GOT gid 2. (Reconfigure to take
> 2?)
> 554 5.3.0 "|/home/mailman/mail/wrapper post test"... unknown mailer error
> 2
>
> have installed like 4 or 5 mailmans on freebsd machines and this
Len Merikanto wrote:
>- Transcript of session follows -
> Failure to exec script. WANTED gid 12, GOT gid 2. (Reconfigure to take
> 2?)
> 554 5.3.0 "|/home/mailman/mail/wrapper post test"... unknown mailer error
> 2
>
> have installed like 4 or 5 mailmans on freebsd machines and this
I don't think the RFCs have anything to say about what email I read
and what I throw away. And, I don't route directly to /dev/null; I
toss it into a spam folder that I check about once a month. There's
very little legitimate email in there. What little there is, is
always machine-generated.
The original message was received at Wed, 7 Feb 2001 21:48:10 +0200
from [192.168.0.122]
- The following addresses had permanent fatal errors -
"|/home/mailman/mail/wrapper post test"
(reason: 2)
(expanded from: <[EMAIL PROTECTED]>)
- Transcript of session follows
On 2/8/01 7:28 AM, "George Dinwiddie" <[EMAIL PROTECTED]> wrote:
> Hmmm... Trashing mail without a Message-Id: header is my most effective
> spam filter.
It's just against the RFCs and subject to (as you now find out) false
positives. Makes one wonder how much of that spam you think it's effect
Hmmm... Trashing mail without a Message-Id: header is my most effective
spam filter.
- George
> Christopher P. Lindsey said:
>
> > When people subscribe, using the web, and mailman sendt the mail with
> > the secret to prove your identity, it sends it without any Message-Id
> > line. I proces
Theese locked files come as soon as I try to subscribe to a list.
I does not help to remove them.
I try a complete new installation,
run the securelinux_fix
but the problem is the same:
No subscribing mail after newlist, newalias.
But the logs/smtp said:
Feb 08 13:26:00 2001 (5182) smtp for 1 r
Hello:
We have just upgraded mailman s/w to ver. 2.0.1 After upgradation we are
having problems again. When messages are posted to
[EMAIL PROTECTED] the message is not reaching
[EMAIL PROTECTED]
A crontab message listed below is received by mailman@ncsi
Cron /usr/local/bin/python -S
/ho
Hi:
Upgrading mailman ver 2.0beta6 to mailman 2.0.1 did the trick. Thanks for
your prompt help.
- Francis
PS
--
We are running mailman on a Linux system. Some members send MS Word files
as postings. How do I ensure that the attachment file is virus free?
Bye,
- Francis
--
Hi
I have just installed mailman and get the following error:
Bug in Mailman version 2.0.1
We're sorry, we hit a bug!
Please inform the webmaster for this site of this problem. Printing of
traceback and other system information has been explicitly inhibited, but
the webmaster can find this infor
I have solved the problem by using the remove_members
script (./remove_members list "[EMAIL PROTECTED] \"luis").
Thanks for your help and sorry for not trying this
before...
Omar.
El 07.02.01, Omar Walid Llorente dijo:
:
: :At 19:22 +0100 2/6/01, Omar Walid Llorente
Hello there,
once in a while I see emails from Mailing-lists where I get at the very
bottom: "You are subscribe as '[EMAIL PROTECTED]'". I find this very
useful as people often don't know with which address they are
subscribed. Is there any way to do this with Mailman? TIA,
Alexander
--
"The o
20 matches
Mail list logo
