Thomas Ward via Mailman-Developers writes:

 > >> In debugging and diagnosing issues with an archiver I wrote for
 > >> a client of mine, I need to see the message as it's seen by
 > >> Mailman, in its own Message class.

I don't understand what you mean by "as seen by Mailman".  By the time
it gets to your third-party archiver, Mailman "sees"

1.  An incoming LMTP message in wire format (plus LMTP metadata) by
    the 'lmtp' runner
2.  a Mailman queue object (a pickle of an EmailMessage and Mailman
    processing metadata) in the 'in' queue with minimal Mailman
    metadata
3.  a Mailman queue object (maybe in the 'pipeline' queue? not
    sure) that gets updated by Rules and Handlers in the chains and
    pipeline (Rules update metadata for routing, Handlers may modify
    the message or copy it to queues for alternative transports)
4.  a Mailman queue object in the 'archive' queue where it will be
    picked up by the archiver plugins, which was copied from the
    previous queue by the 'toarchive' Handler.  (This assumes that you
    are using an archiver plugin rather than, say, subscribing the
    archiver to the mailing list.  ISTR you wrote that you're using a
    plugin.)

In theory (I haven't tried this), by killing the appropriate runner,
you can trap future queue objects at any of the stages 2, 3, or 4,
copy one out of the queue for examination, then restart Mailman which
will pick up the queue processing where it left off.

In particular it seems most likely that you want a copy of a queue
object from the archive queue, and you can extract the EmailMessage
and the metadata dict using the pickle module, or I guess the 'mailman
qfile' command will show you a serialized version.

Steve



-- 
GNU Mailman consultant (installation, migration, customization)
Sirius Open Source    https://www.siriusopensource.com/
Software systems consulting in Europe, North America, and Japan
_______________________________________________
Mailman-Developers mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/mailman-developers.python.org/
Mailman FAQ: https://wiki.list.org/x/AgA3

Security Policy: https://wiki.list.org/x/QIA9

Reply via email to