On 7/7/20 10:23 AM, Shashikanth Komandoor wrote:
I did not see any log records based on that message id in mailman.log. There is a lot much of shunt queue but I don't see any file with the required message id. The same is the bad queue also.
The message-id will not be logged in mailman.log for these issued.
For each such issue, there will be a log message indicating the
exception with a traceback and a 'shunting' message. To see the actual
problem message, you can use mailman qfile to examine the shunted .pck
file.
I find below two lines at that particular time stamp by when the log recorded in vette.log
*Uncaught runner exception: sequence item 0: expected str instance, Header foundTypeError: sequence item 0: expected str instance, Header found*
But I am not sure if the above lines are related to that missing message or not.
Almost certainly, but examine the shunted message with mailman qfile
to be sure.
I am using postgresql as database. FYI, if it brings an idea to you to help me.
That's not relevant to this issue.
Examine the tracebacks and shunted messages. If the problem is not obvious from that, you can post here for help. We need the complete error message with full traceback and the raw message text. For the message, we are primarily interested in all the headers including sub-part headers. Sub-part bodies can be truncated and headers sanitized for privacy if necessary, but the fewer changes you make to the raw message text, the better.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan