c."""
>245 if self.input_codec != self.output_codec:
>246 return unicode(s, self.input_codec,
> 'replace').encode(self.output_codec, 'replace')
>247 return unicode(s,
> self.input_codec).encode(self.output_c
).encode(self.output_codec, 'replace')
> +return unicode(s,
> self.input_codec).encode(self.output_codec)
> else:
> return s
>
> is reversed. The '+' is the original code and the '-' is the new code.
&g
odec, 'replace')
+return unicode(s, self.input_codec).encode(self.output_codec)
else:
return s
--
Tokio Kikuchi, tkiku...@is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
--
Mailman-Users mailing l
clude/include is done if the list address appears explicitly on the
To:/Cc: headers. You should write 'staff-info' and 'non-staff-info' in
the regular_exclude_lists of 'All-info' and send a message
'To:staff-info,non-staff-info,A
05d) -> (listname 00123)
Cheers,
--
Tokio Kikuchi, [EMAIL PROTECTED]
http://weather.is.kochi-u.ac.jp/
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.pytho
.\w]+)',
'\g<1>' + atmark + '\g<2>', subject)
finally:
@@ -574,7 +575,7 @@
if mm_cfg.ARCHIVER_OBSCURES_EMAILADDRS:
otrans = i18n.get_translation()
try:
-atmark = unicode(_(
> In my ‘board_member’ list, under “Privacy options” (Sender filters). I
> have:
>
> [EMAIL PROTECTED] in the box labeled “List of non-member addresses whose
> postings
> should be automatically accepted”
http://sourceforge.net/tracker/index.php?func=detail&aid=1220144&group_id=103&atid=300103
sion: 1.0
>
> Doesn't make much sense to me why it's having trouble ingesting MIME.
I believe CTE should not be in the main section of message header if
Content-Type is multipart.
>
> -John
>
--
Tokio Kikuchi, [EMAIL PROTECTED]
http://weather.is.kochi-u.ac.jp/
set_charset
>> TypeError: us-ascii
>
> "mmarch" seems to be having trouble with the Content-Type header line.
> If I pull out that line for a given message, it is ingested, though it
> displays the full MIME text.
What exactly was the Content-
I wrote:
> Hi Jared,
>
> I'm curious what kind of message caused this error.
> I think that the exact message causing this error contains a header like:
>
> Content-Type: text/plain; charset=base64
>
> It would be nice if you can check the moved digest.mbox and answer if my
> hyposis is right
>>>> I have run into a issues where mail has all of a sudden stopped being
>>> sent
>>>> to the mailing list.
>>>
>>> See
>>> <http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.078.htp>,
>>> particularly items
Hi,
> Here is a URL where I created a list for testing
> mailman.
>
> https://mail.bioacademy.gr/pipermail/testlist2/2007-May/thread.html
Your site use Mailman-2.1.5 which is way too old. Upgrade to the
current version (2.1.9) and try again.
--
Tokio Kikuchi, [EMAIL PRO
Mark Sapiro wrote:
> Tokio Kikuchi wrote:
>
>> Hi developers,
>>
>> This particular problem is caused by a bug in email 4.0.1 package which
>> was fixed in the most recent subversion repository.
>> http://svn.python.org/view/python/trunk/Lib/email/me
>
> if not isinstance(charset, unicode):
>
> charset = unicode(charset, 'us-ascii').encode('us-ascii')
>
> except Uni
le
processes like 'cron/senddigests' stops working.
My advice is to remove (or rename for later inspection) the digest.mbox
file from the Japanese list directory and set digestable=0 if they keep
using the 'machine dependent characters'.
>
> Just a thought,
> Krys
Rolf E. Sonneveld wrote:
> Tokio Kikuchi wrote:
>>> However, when I try to access Mailman via my browser (using Apache on
>>> the server side) I get the infamous error message:
>>>
>>
>>> The /usr/local/lib version seems to be more recen
unning under LD_LIBRARY_PATH envrironment. You
should setenv LD_RUN_PATH while compiling or use crle. Read the crle
man for detail.
--
Tokio Kikuchi, [EMAIL PROTECTED]
http://weather.is.kochi-u.ac.jp/
--
Mailman-Users mailing list
Mailman-Users@pyt
tood. It was a little bit too early in the
morning to start working. ;-) (6AM Japan)
I've almost done with this 'format=flowed' patch and others for
Scrubber.py and Decorate.py for the trunk. I'll commit them after
adding some more test codes.
--
Tokio Kikuchi, [EMAIL
ion of this patch,
> please get the current version to avoid this problem.
>
--
Tokio Kikuchi, [EMAIL PROTECTED]
http://weather.is.kochi-u.ac.jp/
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo
gP/XFVeeDBn6QVXkE9oK1YJxyrLZZET5GxT
> TAvTJgfndkcWPuUpbC5D6hcpDNa6sfIgJnR3enoW7MgKpOAtIXTuXqPpNiFMBVT2
> qUhlDHhwYzdJWWyzI/oXGRvt0lMqqA69Iu7A6DAKrgksBB128V/mYxTfv8BPmF4W
> uASb/9MkmAQ=
> =h+IQ
> -END PGP SIGNATURE-
--
Tokio Kikuchi, [EMAIL PROTECTED]
http://weather.
del msg['x-confirm-reading-to']
It should not be difficult to add one or more in the next release.
--
Tokio Kikuchi, [EMAIL PROTECTED]
http://weather.is.kochi-u.ac.jp/
--
Mailman-Users mailing list
Mailman-Users@python.or
epends on what the caller does with it.
>
>
>> Would it be appropriate to set failobj="us-ascii" when
>> calling this method in Scrubber.py?
>
>
> It might be, but I'd like to hear from Tokio first.
>
> Clearly this was considered at one point as a sp
7281
) but we may have to be paranoid against wired message like no-header
text. I believe well behaved MUAs won't generate no-header text parts.
(or, I believed ;-)
--
Tokio Kikuchi, [EMAIL PROTECTED]
http://weather.is.kochi-u.ac.jp/
--
> > (b) Duplicate receiving email addresses (on two or all three of the
> > sublists) are not being eliminated.
>
> No way to win here, currently.
Try this patch.
http://sourceforge.net/tracker/index.php?func=detail&aid=1347962&group_id=103&atid=300103
--
Tokio Kikuch, [EMAIL PROTECTED
> DEFAULT_URL_HOST = 'https://mailman.ce.berkeley.edu'
should be 'mailman.ce.berkeley.edu'.
--
Tokio Kikuchi [EMAIL PROTECTED]
http://weather.is.kochi-u.ac.jp/
--
Mailman-Users mailing list
Mailman-Users@python.org
I imposed on this list is
>
> subject: .*SPAM.*
>
This was fixed in 2.1.8 and now 2.1.9 is out. Please upgrade.
--
Tokio Kikuchi, [EMAIL PROTECTED]
http://weather.is.kochi-u.ac.jp/
--
Mailman-Users mailing list
Mailman-
> In summary my preferences would be:
>
> Mailman 2.1.x supported on Python 2.3, 2.4, and 2.5. Drop support
> for Python 2.1 and 2.2. We've done this accidentally in Mailman
> 2.1.9, so let's make it official.
>
> Mailman 2.2 supported on Python 2.4 and 2.5.
gid on *nix systems. You may have
to change the user's primary group as mailman or use newgrp command on
solaris.
--
Tokio Kikuchi, [EMAIL PROTECTED]
http://weather.is.kochi-u.ac.jp/
--
Mailman-Users mailing list
Mailman-Users@python.
dd the lists? Or are you saying
> some sort of additional request from Gmane is also necessary?
>
Barry has clearly stated "if the Gmane administrators make a formal
request" and this was the point that past mirroring (or archiving
the mailman-2.5.x package from
their ports. File a bug report on their developers site.
In the mean time, you can extract email-2.5.x from our official
distribution and install into /pythonlib directory. Or, you can
edit cron/senddigests to use python2.3 as was suggested earlier.
Cheers,
--
T
>>> import paths
>>> import email
>>> email.__version__
'2.5.7'
The email-3.0.x in Python 2.4 is not suitable for mailman. Mailman
2.1.8(or 9) works best with the email-2.5.7(or 8) which is the bug fix
d the Mailman 2.1.8 source tarball, see:
http://sourceforge.net/project/showfiles.php?group_id=103
(Note that uploading to the mirror sites may be delayed.)
--
Tokio Kikuchi
--
Mailman-Users mailing list
Mailman-Users@python.org
str'
object has no attribute 'as_string' (147). Utils.get_domain()
wrong if VIRTUAL_HOST_OVERVIEW off (1275856).
Miscellaneous
- Brad Knowles' mailman daily status report script updated to 0.0.16.
--
Tokio Kikuchi, tkikuchi@ is.
mistakes delay notice for bounce (1421285). show_qfiles: 'str'
object has no attribute 'as_string' (147). Utils.get_domain()
wrong if VIRTUAL_HOST_OVERVIEW off (1275856).
Miscellaneous
- Brad Knowles' mailman daily status report script up
Actually, a patch to make it possible is waiting to be integrated in
mailman-2.2.
http://sourceforge.net/tracker/index.php?func=detail&aid=1347962&group_id=103&atid=300103
I want to merge into the CVS trunk as soon as the next mailman-2.1.8 bug
fix release is out.
> Alas, this
#x27;X-Spam-Status', '^Yes').
>
Or, you should use:
('x-spam-flag', 'yes'),
Cheers,
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
--
Mailman-Users mailing list
Mailman-Users@
s kind of short-sighted that it takes only one password on
> the command line and hides the typing. Why doesn't mailman ask for a
> confirmation of the password, and keep re-prompting for a new one if they do
> not match?
>
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http
The part that adds
>>
>>import re
>>
>>to Mailman/Cgi/edithtml.py
>>
>>But you may run into one of the other bugs sooner or later, so why not
>>apply the whole patch?
>>
>>--
>>Mark Sapiro <[EMAIL PROTECTED]> The highway is for gambl
27;s no help.
This is *also* fixed by this patch:
http://sourceforge.net/tracker/index.php?func=detail&aid=1405790&group_id=103&atid=300103
Cheers,
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
--
racker/index.php?func=detail&aid=1405790&group_id=103&atid=300103
Apply with patch -p0 (or -p1) < this_patch in the source tree and make
install again.
>
> --
>
> Which doesn't look good :-( Should I be worried?
--
Tokio Kikuchi, tkikuchi@
t want them accepted and posted.
Check also the recipient filter.
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman
d Cc:'s directly to me, and not necessarily the
> above scenario?).
>
No, this is not for multiple lists.
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
--
Mailman-Users mailing list
Mailman-Users@pyth
re running Mailman 2.1.5 and have just found extraordinary
> IO wait issues requiring shutdown|restart of Mailman.
This may or may not related to the DoS issue. I suggest checking lock
files, shunt directory, and pending requests and search mailman FAQ.
>
> The notice suggests all
[EMAIL PROTECTED] wrote:
> Hi,
>
> 2.1.7 is signed by key-id E099F769, but i can't find that key anywhere!
>
> can someone put it on the public keyservers pls?
>
Sorry for the inconvenience. Now it can be found at:
http://keyserver.veridis.com:11371/search?q=0xE099
Please fetch this patch from SF tracker and apply it in mailman-2.1.7
source.
http://sourceforge.net/tracker/index.php?func=detail&aid=1405790&group_id=103&atid=300103
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
---
Barry Warsaw wrote:
> On Mon, 2006-01-16 at 09:25 +0900, Tokio Kikuchi wrote:
>
>
>>In usual mailman qrunner execs, stderr is logged into logs/errors. It
>>is the additional tee_to_real_stderr in LogStdErr() setting which wants
>>to print the error into real stderr
David Gibbs wrote:
> Tokio Kikuchi wrote:
>
>>Can you test this patch?
>
>
> Seems to be working fine.
>
> david
>
>
>
Thank you David. I changed the patch slightly and checked into the CVS.
See also this patch tracker entry:
http://sourceforge.n
Barry Warsaw wrote:
> On Jan 14, 2006, at 9:59 PM, Tokio Kikuchi wrote:
>
>
>>Mark Sapiro wrote:
>>
>>
>>
>>>>File "/usr/lib/python2.3/uu.py", line 139, in decode
>>>> sys.stderr.write("Warning: %s\n" % str(v))
>&g
n'), sfp)
to
uu.decode(StringIO(payload+'\n'), sfp, quiet=True)
There should be other chances that Python builtin modules spew warnings
to sys.stderr. How about this patch for Logging/Utils.py to write these
messages into syslog facility.
--
Tokio Kiku
patch?
Removing SpamDetect from the owner pipeline means spams pass through to
the list owner. This should be inconvenient.
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
Index: SpamDetect.py
===
RCS
lve
> doesn't seem to be kicking in.
>
>
>>So something is going wrong here, but I don't know what. I will
>>investigate, but if you could send me off list what your
>>header_filter_rules are and a copy of the original problem message, it
>>may help me.
&
s OK.
>
> Have I done something stupid, or is it a real bug and I should open a bug
> report ?
>
Sorry for the inconvenience but I've put a new bug in the code while
tighten up the security of the script. Work around is to put a line
import re
in the top part of
ed, it is a error in CookHeaders.py 'List-Id'
processing. The language code and charset for 'Traditional Chinese'
have changes from big5/big5 to zh_TW/utf-8 because of compliance and
code handling difficulty in python gettext. If you have set description
in chi
pgrading from 2.1.5 to 2.1.7 should have no problems. Everything
needed is done during the bin/update run in 'make install'.
Cheers,
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
--
Mailma
you send me more details of error log, if you don't mind ?
>
>
> /thomas
>
>
>
>
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
--
Mailman-Users mailing list
Mailman-Users@python.org
http:/
http://mailman.sourceforge.net/
For links to download the Mailman 2.1.7 source tarball, see:
http://sourceforge.net/project/showfiles.php?group_id=103
Best regards and a happy new year!
--
Tokio Kikuchi
--
Mailman-Users mailing list
Mailman-
Oops, Sorry for the typo in the message title. I mean
Released: Mailman 2.1.7rc1 Release Candidate
Tokio Kikuchi wrote:
> Hi all,
>
> I've just released Mailman 2.1.7rc1 Release Candidate. I'm sorry for
> the violation of file name extension convention because I m
Hi all,
I've just released Mailman 2.1.7rc1 Release Candidate. I'm sorry for
the violation of file name extension convention because I made a small
mistake when tagging the release number. I will be releasing 2.1.7
final by December 31 if there is no problem.
Please download it from SF or:
/Handlers/Scrubber.py", line 447, in
>>> save_attachment
>>>fp = open(path, 'w')
>>>IOError: [Errno 36] File name too long:
>>>'/var/lib/mailman/archives/private/rca-l/attachments/20051207/3d04c3a4/iso-8859-1QThe_surface_of_the_SunA0_Th
Hi all,
I've just released Mailman 2.1.7b1 for beta test and i18n translations.
I'm tempted to jump into RC because the 2.1-maint branch is so stable
and 2.1.7 is mainly for bug fixes, but we need more translations before
the final release. Please download it from SF or:
http://mm.tkikuchi.net/
ged in
the CVS (and next release). See: http://www.list.org/i18n.html
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman
odecs which are included in mailman distribution.
You may want to try my language select patch in the SF tracker:
http://sourceforge.net/tracker/index.php?func=detail&aid=1298355&group_id=103&atid=300103
Or, you can go to the /misc directory and find [Kk]orean
notation in Makefile and pat
51:21 2005
@@ -58,3 +58,12 @@
# changes this.
import korean
import korean.aliases
+# Arabic and Hebrew encoding aliases
+import encodings.aliases
+encodings.aliases.aliases.update({
+'iso_8859_6_e': 'iso8859_6',
+'iso_8859_6_i': 'iso8859_6'
Hi,
What is your problem? Will you please describe it in more detail or
show me some example? And, what is your mailman version?
Hannah Schroeter wrote:
> Hello!
>
> On Tue, Nov 01, 2005 at 09:30:25PM +0900, Tokio Kikuchi wrote:
>
>>[...]
>
>
>>Here i
2.1.6 on a Debian-woody server.
Here is your patch. We have already integrated German and Dannish dialects.
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
Index: Mailman/Handlers/CookHeaders.py
===
RCS file
mm.py?req=show&file=faq03.051.htp
might be helpful. You can use two entries for header_filter_rules like:
first rule =
subject:.*(lang/eng|manual\.html|readme\.txt|version\.php|credits\.txt)
set this "Accept",
second rule = . (single dot),
and set this "Discard".
Chee
sys.stderr.write("Warning: %s\n" % str(v))
> File "/usr/local/mailman/Mailman/Logging/MultiLogger.py", line 45,
> in write
> _logexc(logger, msg)
> File "/usr/local/mailman/Mailman/Logging/Utils.py", line 22, in _logexc
> sys.__stderr__.write(
ess /mailman/ on this server.
>
>
> Here's my httpd.conf
>
> ScriptAlias /mailman/ "/usr/local/lib/mailman/cgi-bin/"
>
>
> AllowOverride None
>Options None
>Order allow,deny
>Allow from all
>
>
>
> Ideas?
>
>
s now versioned 2.2.0a0 and a backport of 2.1.6 plus a few
bug fixes and is as stable as 2.1.6. Upgrading to the CVS HEAD should
be as smooth as upgrading from 2.1.x to 2.1.6.
Cheers,
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.i
cept (TypeError, ValueError, OverflowError):
return None
-----
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
--
Mailman-Users mailing list
Mailman-Users@python.org
list
> Mailman-Users@python.org
> http://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
> Unsubscribe:
> http://mail.python.org/mailman/options/m
also that Scrubber.py is used in the regular delivery (if list
admin set so), the digester, and the archiver.
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
--
Mailman-Users mailing list
Mailman-Users@python.org
htt
least for 'plain' digests. This will result in digest recipients
> seeing MIME part headers, raw HTML, raw base64 encoded data and so
> forth instead of attachments.
>
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
Carl Zwanzig wrote:
> In a flurry of recycled electrons, Tokio Kikuchi wrote:
>
>
>>Remember that current structure of mailman is not good at arbitrary
>>scheduling. You may have to run a scheduling script every hour or so.
>
>
> Seems like this already exists
pt every hour or so.
It would be easier to use your PC (Windows or Linux) to send a message
in a scheduled time. May be you can send a message with an "Approved"
header and a "confirm" command with the confirmation string in t
be able to subscribe to your list and get some mail and browse the
archive if your list policy accepts.
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
--
Mailman-Users mailing list
Mailman-Users@pyth
l-archive.com/mailman-users@python.org/msg32852.html
Strange. At least the prefix '[dept-linux/pedago]' works at my test
site. What is your version of Python and what is your list language
settings?
I may be able to look into the problem if you
unces
> MTA_ALIASES_STYLE = 'qmail'
> DELIVERY_MODULE = 'Qmail'
Non digest delivery personalization is only supported by SMTPDirect
delivery module. Sorry about that but you need considerable hack to
implement it in other modules. :-(
--
Tokio Kikuchi
refuse to learn how to do this manually.
>
> Mike
>
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
ody for the problem message (I omitted
> the routing headers):
>
> MIME-version: 1.0
> Content-type: multipart/mixed; boundry="!!!---===123_4567_890===---!!!"
^^^
This should be 'boundary' not -dry.
--
Tokio Kikuchi,
hon
re.escape() should escape special characters only -- I can't find '%' in
special character list in the manual.
--
Tokio Kikuchi tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
--
Mailman-Users mailing list
Mailman-Users@p
Oh, Yes! The fix should appear soon in anonymous CVS and viewcvs.
http://cvs.sourceforge.net/viewcvs.py/mailman/mailman/
Brad Knowles wrote:
> At 9:42 PM +0900 2005-05-08, Tokio Kikuchi wrote:
>
>
>> I think I could track this down. I used Unicode{En|De}codeError but
>> t
wn. I used Unicode{En|De}codeError but
they are introduced in Python2.3. It should be UnicodeError and this
catches both encode ande decode errots. I've updated CVS with this fix
for Decorate.py and cmd_subscribe.py. It was my fault not Barry's.
--
ix to this and report us also.
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/
xt)
-outer.attach(MIMEMessage(msg))
# Turn off further VERP'ing in the final delivery step. We set
# probe_token for the OutgoingRunner to more easily handling local
# rejects of probe messages.
You may also want to customize your probe.txt in the template directo
the middle of May. :-< So, we have much time to test or translate this
2nd release candidate for the final 2.1.6.
http://sourceforge.net/project/showfiles.php?group_id=103
or
http://mm.tkikuchi.net/mailman-2.1.6rc2.tgz
Cheers,
--
Tokio Kikuchi tkikuchi@ is.kochi-u.ac.jp
http://weather.is.ko
put this in mm_cfg.py:
KNOWN_SPAMMERS = [
('x-spam-flag', 'yes'),
... other stuffs
]
It is better not to use X-Spam-Level because the *'s are special
characters in python regular expression. Better to tweak in the
spamassassin configuration.
--
mm_cfg.py:add_virtualhost( 'lists.antipolis.fr' )
where is my mistake ?
mm_cfg.py:add_virtualhost( 'lists.antipolis.fr', 'lists.antipolis.fr' )
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
--
t the case with quoted-printable.
What is happening here is the original post has
Content-Transfer-Encoding: quoted-printable
This bug should go away if python.org mailman is upgraded to 2.1.6.
Cheers,
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.koc
m the
language champions including Leona for zh_CN (Chinese, China).
Hopefully, I will be able to release the 2.1.6 final within a week.
Cheers,
--
Tokio Kikuchi tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
--
Mailman-Users mailing
Hi all,
Now we are on the last stage before the final release of 2.1.6.
After the release of 2.1.6b5, we've got translation updates from the
language champions including Leona for zh_CN (Chinese, China).
Hopefully, I will be able to release the 2.1.6 final within a week.
Cheers,
--
Tokio Ki
rowsing through the code, it looks like Urgent: is only valid in header
position. Not supported for the first line in body.
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
--
Mailman-Users mailing list
Mailman-U
is probably not safe.
Exiting.
--
Try find Version.py in your /Mailman directory and edit like:
VERSION = "2.2a0" -> "2.1.4"
MINOR_REV = 2 -> 1
MICRO_REV = 0 -> 4
REL_LEVEL = ALPHA -> FINAL
Then install 2.1.6b5 from http://mm.tkikuchi.net/mail
souls to
upgrade 2.1.6 beta and who use this feature, to upgrade again to 2.1.6
beta 5.
The tarball is placed at
http://mm.tkikuchi.net/mailman-2.1.6b5.tgz
# Sorry but it looks like I have not access to the file releases on SF.
--
Tokio Kikuchi tkikuchi@ is.kochi-u.ac.jp
http://weather.
be
kept in the archive area. You may also have to tell the list owners (and
users) your policy and not to use plain text digests but use mime digests.
You will have to hack the code if you want to do this silently.
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.i
I'm running Version 2.1.5. of mailman.
I've tried applying the patch 891491 scrubber.py last ammended by Tokio
Kikuchi
In Sept 2004 using the following command
Patch -p1 < /path/to/patch
With no joy.
patch -p1 < /tmp/scrubber.patch.20040912
can't find file to patch at inp
sted a new entry in the Mailman FAQ Wizard.
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03.051.htp
Feel free to add/edit this to grow the list of recipe.
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
--
Brad Knowles wrote:
At 9:59 PM +0900 2005-02-22, Tokio Kikuchi wrote:
Go to admin -> privacy -> spam page and put following in spam filter
rule 1:
\nto:.*your-list-name
What about "Delivered-to:" and/or "Cc:" headers?
Oh yeah, you can change rule 1
Sorry that I was so noizy by myself. :-P
Tokio Kikuchi wrote:
AAYEE!!
This doesn't work AT ALL! You will get deep recursive hold for
administrative notices. I should look into the code.
Tokio Kikuchi wrote:
Sorry, my mistake.
Go to admin -> privacy -> spam page and put following in
AAYEE!!
This doesn't work AT ALL! You will get deep recursive hold for
administrative notices. I should look into the code.
Tokio Kikuchi wrote:
Sorry, my mistake.
Go to admin -> privacy -> spam page and put following in spam filter
rule 1:
to:.*your-list-name
1 - 100 of 304 matches
Mail list logo
