> While it seems like a sensible shortcut to skip the database if not
> needed, the result is that every forwarding address needs to be processes
> at once. So for 100 forwards, that's 100 instances of sendmail at once!
Offhand, can dbmail simply specify multiple recipients for a message
(ie. one sendmail process, 100 recipients)? It'd of course require
some max limit to be set, and wouldn't address the actual issue here,
but overall seems like it'd make more sense, wouldn't it?
> I think that adding db_* functions to work with a temporary table would be
> a good option to use, but then considered that a simpler option, which
> would require no additional code, would be adding a dedicated dbmail user
> account to the database. For example, reserve useridnr 1 or 0 (although
You wouldn't even need a user account, that I can see. All you
need for using messages/messageblks tables is to point to a mailbox_idnr, for
which you can use value 0 (unless someone has
added foreign key constraints from messages.mailbox_idnr to
mailboxes table, which is not how dbmail currently "ships").
> I'm not sure that an auto_increment column can even hold the number 0...)
FWIW, I know you can in postgres (eg. we reserve an id of 0 for some
special things, which has to be manually inserted, and everything else
gets an auto increment value).
--
Jesse Norell
jesse (at) kci.net
