John == John W Baxter [EMAIL PROTECTED] writes:
John In addition, the Message-Id values would have to be
John filtered, if used as is, for URL-unfriendly characters
I don't think so. AFAIK, that was fixed about 2000 RFCs ago. When
used as URLs, conforming agents will URL-encode them.
At 2:29 PM +0900 2005-09-29, Stephen J. Turnbull wrote:
BradBecause some MUAs generate message-ids that are likely
Brad to collide.
Can we stop pandering to the broken mailers, please? Are we not
hackers? We know how to handle collisions.
I don't really care how
I've jsut installed mailman, and think I've done everything right so far.
When I try to browse to the mailman site though it doesn't seem to
work properly. I've found other similar questions in the archive, but
none of those had any resolution.
When I browse to http://10.0.253.82/mailman/
I
Christopher Adams wrote:
However, I have another question about issuing email commands for
subscribing. In the web interface, I can add information along with the
email address, by using the syntax Joe Blow[EMAIL PROTECTED]. If
I issue this by email, Mailman chokes on it. Here is an example.
I had this problem myself - very recently. This was on a Solaris
implementation of Mailman.
I'm on OpenBSD
The values in question are:
DEFAULT_EMAIL_HOST = 'hostname'
DEFAULT_URL_HOST = 'hostname'
I had appended these values to the file:
/usr/local/mailman/Mailman/mm_cfg.py
That
Douglas B. Jones wrote:
I am trying to print:
http://www.gnu.org/software/mailman/mailman-install.pdf
Regardless on which computer (W2K or XP), I get:
'The document could not be printed'
Works for me using the 'print' button in Adobe Reader 7.0.3.
--
Mark Sapiro [EMAIL PROTECTED] The
On Thu, 2005-09-29 at 13:55 -0400, Joe Damico wrote:
Bryan:
I had this problem myself - very recently. This was on a Solaris
implementation of Mailman.
The values in question are:
DEFAULT_EMAIL_HOST = 'hostname'
DEFAULT_URL_HOST = 'hostname'
I had appended these values to the file:
On Thu, 2005-09-29 at 14:23 -0400, John Dennis wrote:
I suspect the problem is the http configuration for the directory that
was originally posted omitted the Options ExecCGI which is required to
tell the http server it is permissible to execute cgi scripts in this
directory.
Oh, almost
Here is what I use, adjust the path to your installation:
ScriptAlias /mailman/ /usr/lib/mailman/cgi-bin/
Directory /usr/lib/mailman/cgi-bin/
AllowOverride None
Options ExecCGI
Order allow,deny
Allow from all
/Directory
Here's how it reads now after editing that file (and
Elvis Fernandes wrote:
I am setting up a brand new mailman server.
After doing per the documentation, I tried creating a testing test mail
list.
However, I get an error that says illegal list name: [EMAIL PROTECTED]
Any idea's on what I am missing?
It looks like you have an invalid or missing
paul collen wrote:
Yep, works fine in any client apart from Outlook!! ;o)
Does anybody know how to manually edit the Sender address mailman uses?
If you do this (by modifying code), you'll break automated bounce
processing.
--
Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers,
Alysson Dias wrote:
How I restore backup (file mailman.tar of complete /home/mailman) of
only 1 list in the server?
restore the /home/mailman/lists/listname directory and maybe the
/home/mailman/archives/private/listname and
/home/mailman/archives/private/listname.mbox directories.
--
Mark
Hi,
You have to accesss http://10.0.253.82/mailman/listinfo.
Without the script name in the end of URI, Apache returns error because
you set Options None. Options ExecCGI should not be used here for
ScriptAliases is already specified. Options Indexes is the
configuration for directory view
Bill Moseley wrote:
Two questions about bounce processing in 2.1.5.
First question:
The bounce_info_stale_after is regardless of list traffic? I.e. is
the bounce information discarded after bounce_info_stale_after days
regardless if there's been any outgoing mail?
Yes, but only the most
I had done several test installs, with real, and fake users (installed
via OpenBSD ports), and when I'd remove an install, I'd manually
remove /usr/local/lib/mailman, but never noticed /var/spool/mailman,
which although reported it was owned by _mailman, it actually wasn't
because the uid number
Darren G Pifer wrote:
On Fri, 2005-09-16 at 12:33, Mark Sapiro wrote:
Is there a global mailbox file at
archives/private/telephone_logs.mbox/telephone_logs.mbox or just the
archives/private/telephone_logs.mbox/ directory without the file?
There is an archives/private/telephone_logs.mbox file
Gary Casterline wrote:
We've set up chain of hierarchical lists to accommodate annual groups.
Each year we create a list for the new cohorts:
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
and then add the new class-of list to the umbrella list:
[EMAIL PROTECTED]
Hello,
Running version 2.1.4 it seems that mail is taking longer and longer.
What used to take a few minutes is now taking an hour or two to get
thru Mailman. Top indicates the machine is not busy and the mail is
not in the queue. It seems to be waiting in the mailman process.
Any ideas?
can somebody explain this please?... thanks
# ./remove_members -n -N aaac [EMAIL PROTECTED]
# ./remove_members -a -n -N aaac
Traceback (most recent call last):
File ./remove_members, line 186, in ?
main()
File ./remove_members, line 176,
michael dunston wrote:
Can someone tell me where (in Mailman) the private archive session cookies are
being set, or where I might find more information about the use of cookies for
enforcing private archive access? I am trying to add this level of protection
to a swish-e search CGI. Thanks
and this - executed in the directory of the aaac list:
who cares if s/he is a member - just get it out... why would you need to
assertIsMember?!? doesn't make sense
[~/aaac]# grep -rl [EMAIL PROTECTED] *
[~/aaac]# ../../bin/remove_members -a -n -N aaac
Traceback (most recent call last):
kalin mintchev wrote:
and this - executed in the directory of the aaac list:
who cares if s/he is a member - just get it out... why would you need to
assertIsMember?!? doesn't make sense
Because the method which is used to remove the member is more general
than that.
[~/aaac]# grep -rl
Because the method which is used to remove the member is more general
than that.
aha... ok.
It appears something is messed up in the lists config.pck or perhaps
there is a transparent character or something similar in the actual
member address.
right. but grep didn't find it either...
- Original Message ---
Subject: Re: [Mailman-Users] doesn't work...
From: kalin mintchev [EMAIL PROTECTED]
Date: Thu, 29 Sep 2005 22:23:13 -0400 (EDT)
To: Mark Sapiro [EMAIL PROTECTED]
Cc: mailman-users@python.org
Because the method which is used to remove the
Con Wieland wrote:
Running version 2.1.4 it seems that mail is taking longer and longer.
What used to take a few minutes is now taking an hour or two to get
thru Mailman. Top indicates the machine is not busy and the mail is
not in the queue. It seems to be waiting in the mailman process.
Brad Knowles wrote:
I've taken your submission and incorporated that, as well as
fixing another bug that was brought to my attention by Adrian Wells.
It turns out that there is a minor log file difference between
Mailman versions 2.1.5 and 2.1.6, which causes the smtp log to be
written
26 matches
Mail list logo
