>I suspect it's all related and the `free (comp->c_text)' above is key.
Yeah ... arrrrghhhh. Looks like that was introduced in ff5eb06992. It looks like ... that gets called if it is parsing a component with multiple addresses and the first one is NOT one of your local mailboxes, but later ones are? Maybe. Ralph, does that match the description of your message? I think we might have to accept the memory leak in the format engine in this case and then we will have to sit down and clearly define who owns what memory in the format engine. scan is trying to be smart and reuse buffers (and I understand why), but it's interfering with this. I am wondering if the buffer reuse in scansbr.c is still warranted; should we just accept the price of a bunch of malloc/free calls? --Ken -- Nmh-workers https://lists.nongnu.org/mailman/listinfo/nmh-workers
