Masaharu Kawada wrote:
>Kikuchi-san, Mark-san,
>
>I will ask the customer to consider patching it.
>
>Thanks a million!!!
>
>Best Regards,
>
>Tokio Kikuchi wrote:
>> (10/03/04 11:47), Masaharu Kawada wrote:
>>
>>> Hi Mark-san, Kikuchi-san,
>>>
>>> Thank you very much for your help.
>>>
>>> Just
Kikuchi-san, Mark-san,
I will ask the customer to consider patching it.
Thanks a million!!!
Best Regards,
Tokio Kikuchi wrote:
(10/03/04 11:47), Masaharu Kawada wrote:
Hi Mark-san, Kikuchi-san,
Thank you very much for your help.
Just to make sure, about the patch, is it just need to be
(10/03/04 11:47), Masaharu Kawada wrote:
> Hi Mark-san, Kikuchi-san,
>
> Thank you very much for your help.
>
> Just to make sure, about the patch, is it just need to be modified in the
> way you mentioned? Which means that it should be look like below.
Yes, its OK.
>
> # vi /usr/lib/python2.
Hi Mark-san, Kikuchi-san,
Thank you very much for your help.
Just to make sure, about the patch, is it just need to be modified in the
way you mentioned? Which means that it should be look like below.
# vi /usr/lib/python2.4/email/Charset.py
--
243 def convert(self, s):
244
Hi,
(10/03/04 1:58), Mark Sapiro wrote:
> Masaharu Kawada wrote:
>>
>> There is one thing that I wonder, is that if the charset.py is done with
>> that patch, what the current digest.mbox exsisted under lists/
>> are supposed to be? Do they need to be deleted or not? My point on
>> this is that on
Masaharu Kawada wrote:
>
>There is one thing that I wonder, is that if the charset.py is done with
>that patch, what the current digest.mbox exsisted under lists/
>are supposed to be? Do they need to be deleted or not? My point on
>this is that once the patch is done, is there nothing else to do to
Hello Kikuchi-san,
As far as I checked the error messages and compared with each one,
The problem of my customer's seems to be almost the same as one
posted to the thread written in the last Kikuchi-san's email.
There is one thing that I wonder, is that if the charset.py is done with
that patch,
Hello kikuchi-san,
Thank you for your response with a precious information.
Since I am a beginner for mailman, any comments/suggestions
such as this kind of thing are very helpful for me. Including
what Mark-san have been doing for me and you have done
for me as well, I really appreciate the coop
(10/03/03 16:54), Masaharu Kawada wrote:
> Hi Mark-san,
>
> I got a reply from the customer, but it was not possbile for the customer
> to provide the whole digest.mbox to us due to their policy. However,
> sevral parts of the error log and digest.mbox's content have been provided.
> As for the e
Hi Mark-san,
I got a reply from the customer, but it was not possbile for the customer
to provide the whole digest.mbox to us due to their policy. However,
sevral parts of the error log and digest.mbox's content have been provided.
As for the error messages, please see the attachment. And as fo
Mark-san,
Thank you very much for your response. I was kind of misunderstanding
about what the send_digest() does before, but I now got better knowledge
on it because of your explanations for me. I very much appreciate it!!
I have asked the customer for providing the digest.mbox(s) to us and wai
Masaharu Kawada wrote:
>
>So, it doesn't matter if the senddigest fais or not, there are no
>retries. And,
>senddigest via cron runs only once a day at noon. However, whenever
>messages posted to the list, send_digest() will called based on the size of
>digest_size_threshhold, and try to send dige
Mark-san,
Thank you very much for your respose.
There are no retries per se. The list has a setting
digest_size_threshhold (on its Digest options page). When a post
arrives that makes the digest.mbox bigger than digest_size_threshhold,
a digest is triggered immediately. In this case, the digest
Masaharu Kawada wrote:
>
>I am sorry that I would like to know one more thing about
>digestable in advance.
>
>>>---
>>>xxx xx xx:xx:xx 2010 (2129) send_digests() failed: EUC-JP decoding error:
>>>invalid character ..
>>>xxx xx xx:xx:xx 2010 (2129) send_digests() failed: EUC-JP decoding error:
Mark-san,
I am sorry that I would like to know one more thing about
digestable in advance.
---
xxx xx xx:xx:xx 2010 (2129) send_digests() failed: EUC-JP decoding error:
invalid character ..
xxx xx xx:xx:xx 2010 (2129) send_digests() failed: EUC-JP decoding error:
invalid character ..
xx
Masaharu Kawada wrote:
>
> >There was no need to turn off digestable and archive if they were only
> >going to be turned on again.
>
>I did some research and found information that it is necessary to disable
>those options if you want to delete attachments manually, otherwise
>something
>unclaim m
Mark-san,
Thank you very much for your help.
I will try to get all of the digest.mbox located on under lists/LISTNAME/
from the customer. Though it might be difficult since digest.mbox consists
confidential information for the customer. I will update as soon as I
get the
result from the custom
Mark-san,
Thank you very much for your help.
>There was no need to turn off digestable and archive if they were only
>going to be turned on again.
I did some research and found information that it is necessary to disable
those options if you want to delete attachments manually, otherwise
somet
Mark Sapiro wrote:
>
> I consider this behavior to be a bug. I'll look into fixing it. I think
> what I'll need to do is just move the digest.mbox aside and log an
> error message. It would be better if I could just bypass the bad
> message, but that may be difficult.
I have created a bug report
Masaharu Kawada wrote:
>
>Firtst of all, one of my customer wanted to delete attachments to
>make more disk spaces on the server. The server's disk resource
>was getting full because the size of the directory for attachments
>was very big. So the customer did the following works first.
>
>Digest op
Dear list,
I am kind of new to use mailman on administrative, so if this is
an known issue I'm sorry. I would very much appreciate it if you
would kindly answer my questions.
Firtst of all, one of my customer wanted to delete attachments to
make more disk spaces on the server. The server's disk r
21 matches
Mail list logo
