Run /usr/local/libexec/fml/digest $ml_name periodically for digest delivery. It aggregates articles into one MIME/multipart message and send it to members defined by $digest_recipient_maps. Digest delivery program is a simple version yet now. This program uses the following files under $ml_home_dir. seq-digest members-digest recipients-digest seq-digest holds the last sequence delivered as digest. members-digest is dummy. recipients-digest is a recipient list. $digest_recipient_maps is this recipients-digest file only by default. The argument of $digest_recipient_maps is IO::Adapter, so you can use mysql here. Idea on digest commands (references: fml-devel:313). Hmm, how about the further extension? makefml digest $ml $address on makefml digeston $ml $address makefml digest $ml $address off makefml digestoff $ml $address (These commands are implemented already). admin digest $address on admin digest $address off (These commands are implemented already). digest on digest off The confirmation is needed ? Yes, we should need it to unify the fml fundamental design. We should restrict address manipulation functions as could as possible. digeston digestoff ok? §.digest.recipes;