Yes, that's it. My problem solving may be a little different because I have
a shared server with vhosting and is custom configured in such a way that
the majordomo digest will not work. So, I did a workaround which involves
sending the digest by a daily cron script. The part of the script that got
around the "dot" problem was this:
mail -s "MY-DIGEST" mylist-digest@themembers.org < mydigest
Of course, the "mydigest" is a file with all of the day's messages
containing the pesty "dot".
I got lucky! Hope this helps....
At 05:32 PM 5.31.2001 +0200, Tomas Garcia Ferrari wrote:
>Hello,
>
>It's similar to your problem: is a dot at the end of one line!
>
>Example:
>---
>Esta es la parte que creo no les llegó tampoco a Uds.
>Otra:
><<Ramiro estoy deacuerdo con vos en cuanto a obtener tipografias oroginales.
>Además, acá seguiría el mensaje original, etc.
>[...]
>---
>
>The message was trimmed after the word "oroginales".
>
>Could you explain me with more details what did you do to fix it?
>
>Regards and tks,
>Tomás
>
>> Tomas: Yes, I had the problem setting up a digest. One member of the list
>> used a "lone dot '.' " on a single line right after his signature. He was
>> among the top 3 messages on the list and all of the other member messages
>> after that lone dot were missing. It's because the mail program considers
>> the lone dot as an "end of message" command. Apparently the member is a
>> programmer and used the lone dot out of habit, but sure messed up the
digest.
>>
>> To fix, I changed the mail command which ignored the dot and delivers the
>> entire digest again....
>>
>> What character(s) did you encounter?
>
>+-- --+
> Tomás García Ferrari
> Bigital
> http://bigital.com/
>+-- --+
>
>
>
>
Best regards,
Jack L. Stone,
Administrator
Sage American
http://www.sage-american.com
jacks@sage-american.com
References:
|
|
