rolandrosenfeld / lbdb Goto Github PK

If the variable INMAIL_DB is not set, then the default db value set in m_inmail is not visible to lbdb-munge. Therefore the database file just grows and grows.
It seems like lbdb-munge should use m_inmail_db instead of INMAIL_DB.
As a workaround just setting INMAIL_DB to the default value in lbdbrc fixes the problem. But people might not be aware of this.
I am using lbdbq version 0.48.1. But taking a look into the code in the git repo, the problem is still in the code.

hey, long-time super happy user of lbdb. i recently had to setup a new system, and my outgoing mails get truncated on them. i traced it to my sendmail wrapper which calls lbdb-fetchaddr, for years i used this:

#!/bin/bash
tee >(lbdb-fetchaddr -a)|/usr/sbin/sendmail -oem -oi $@

i minimized the testcase to this (/tmp/x is a random mail i sent):

%  wc -l </tmp/x; tee >(lbdb-fetchaddr -a) </tmp/x | wc -l
1546
957

it seems the pipe is closed early and the wc at the end of the pipe gets only truncated output. if i replace the lbdb-fetchaddr with cat >/dev/null the final wc at the end of the pipe gets the correct number of lines.

now i understand that you recommend using lbdb-fetchaddr in procmail (which is btw considered harmful[1]) for incoming mails, but i would like to avoid that since that also has unsolicited mails coming in with addresses i don't want added to my lbdb, i prefer only mails in lbdb that i sent mail to. i think i found this sendmail wrapper somewhere decades ago online[2].

i fixed/workarounded this issue by appending an extra

cat >/dev/null

at the end of lbdb-fetchaddr. maybe this is something for you to consider as a permanent solution to this issue (which others also might encounter).

kudos for your work on lbdb!

[1] https://anarc.at/blog/2022-03-02-procmail-considered-harmful/
[2] https://www.mail-archive.com/[email protected]/msg27678.html