Hi, We have been using the Mailman software for almost 14 years now. At present, we are on ver 2.1.12 / RH Fedora 9 OS.
I'm the moderator of a discussion list, which was started almost 2 decades ago. There are more than 7K members on the list.
Off and on, I have been experiencing the following issue:
Some of the approved messages, doesn't get broadcasted. They do get archived, though. One such recent message is accessible at http://ncsi.iisc.ernet.in/pipermail/lis-forum/2013-March/014786.html
I have noticed that messages that contain non-ascii chars (typically, content copied and pasted directly from a word processor) exibit such a behaviour. When such messages are edited (removal on non-ascii) and forwarded to the list by the list moderator they do get broadcasted.
I have also noticed that many of the postings that contain non-ascii chars do get broadcasted upon approval.
Could you pl let me know what is it that causes such a behaviour and how do we overcome it.
Thanks for your time and help.
- Francis
JRD Tata Library, IISc, Bangalore, India
-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
franc@library.iisc.ernet.in wrote:
Off and on, I have been experiencing the following issue:
Some of the approved messages, doesn't get broadcasted. They do get archived, though. One such recent message is accessible at http://ncsi.iisc.ernet.in/pipermail/lis-forum/2013-March/014786.html
[...]
Could you pl let me know what is it that causes such a behaviour and how do we overcome it.
What entries are there in Mailman's log files with time stamps near "Fri Mar 8 10:09:05 IST 2013" (the time this message was archived)?
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Tue, 2 Apr 2013, Mark Sapiro wrote:
franc@library.iisc.ernet.in wrote:
Off and on, I have been experiencing the following issue:
Some of the approved messages, doesn't get broadcasted. They do get archived, though. One such recent message is accessible at http://ncsi.iisc.ernet.in/pipermail/lis-forum/2013-March/014786.html
[...]
Could you pl let me know what is it that causes such a behaviour and how do we overcome it.
What entries are there in Mailman's log files with time stamps near "Fri Mar 8 10:09:05 IST 2013" (the time this message was archived)?
Thanks for the replay.
I have searched all the log files, but couldn't locate the pattern, "Fri Mar 8 10:09:05 IST 2013" in any of the log files. I even tried the following caommands, but no match is found:
grep -r "Fri Mar 8 10:09:05 IST 2013" *
grep -r "Fri Mar 9" *
grep -r "Mar 8" *
The following log files are located in the 'bin' directory. -rw-rw-r-- 1 mailman mailman 6044575 Mar 25 11:12 bounce -rw-rw-r-- 1 root mailman 1619626 Apr 2 15:50 error -rw-rw-r-- 1 mailman mailman 172191 Apr 1 10:48 locks -rw-rw-r-- 1 mailman mailman 231131 Apr 1 16:13 mischief -rw-rw-r-- 1 mailman mailman 3075673 Apr 2 14:12 post -rw-rw-r-- 1 mailman mailman 297638 Apr 3 12:31 qrunner -rw-rw-r-- 1 mailman mailman 47281636 Apr 3 12:48 smtp -rw-rw-r-- 1 mailman mailman 7681705 Jan 31 15:54 smtp-failure -rw-rw-r-- 1 mailman mailman 4296065 Apr 2 18:39 subscribe -rw-rw-r-- 1 mailman mailman 16958139 Apr 3 12:38 vette
- Francis
-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
On Wed, 3 Apr 2013, Stephen J. Turnbull wrote:
franc@library.iisc.ernet.in writes:
grep -r "Fri Mar 8 10:09:05 IST 2013" *
Try
grep -r "Fri Mar 8 10:09:05 IST 2013" *
(note two spaces before 8 in "Mar 8")
Grep is not very smart that way....
Thanks for the replay. I used the grep command as you have suggested, but it doesn't help. Had a look at the archived msg in question. There is only once space between Mar and 8.
- Francis
-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
franc@library.iisc.ernet.in wrote:
I have searched all the log files, but couldn't locate the pattern, "Fri Mar 8 10:09:05 IST 2013" in any of the log files. I even tried the following caommands, but no match is found:
The timestamp format in the logs is not the same as the one I copied from your archived message. If you want to use grep, use the pattern "Mar 08 10:[01]" to find all the messages near that time.
You will still have to open the relevant logs and look because the grep will only find the first line of multi-line messages, but at least it will tell you what logs to look in.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
franc@library.iisc.ernet.in wrote:
I have searched all the log files, but couldn't locate the pattern, "Fri Mar 8 10:09:05 IST 2013" in any of the log files. I even tried the following caommands, but no match is found:
Mark Sapiro mark@msapiro.net
The timestamp format in the logs is not the same as the one I copied from your archived message. If you want to use grep, use the pattern "Mar 08 10:[01]" to find all the messages near that time.
You will still have to open the relevant logs and look because the grep will only find the first line of multi-line messages, but at least it will tell you what logs to look in.
I have tried several possibilities like "Fri Mar", "Mar 8", "Mar 08" but the pattern hasn't been found.
Does the presence of some non-ascii characters trigger such a behaviour?
Thanks,
- Francis
The reported problem is being faced almost every day now.
-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
franc@library.iisc.ernet.in wrote:
Mark Sapiro mark@msapiro.net
The timestamp format in the logs is not the same as the one I copied from your archived message. If you want to use grep, use the pattern "Mar 08 10:[01]" to find all the messages near that time.
You will still have to open the relevant logs and look because the grep will only find the first line of multi-line messages, but at least it will tell you what logs to look in.
I have tried several possibilities like "Fri Mar", "Mar 8", "Mar 08" but the pattern hasn't been found.
The "Mar 08" pattern should find all messages from March 8.
Maybe the relevant logs have been rotated out of existence by now? You may have to wait until this occurs again and look more quickly.
Does the presence of some non-ascii characters trigger such a behaviour?
It shouldn't, but it might. I can't tell without seeing some log information.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
franc＠library.iisc.ernet.in -
Mark Sapiro -
Stephen J. Turnbull