Feargal Reilly wrote:
Okay... didn't expect that much discussion, glad for it though. Turns
out most of this comes down to your philosophy of what dbmail should
do.
*SNIP*
What didn't get discussed however, and I thought this would generate
more controversy, was the idea of sending a summary to the user as
part of the maintenance run. Do people think this should be part of
dbmail-maintenance, or should it be a separate run?
Sounds reasonable to select *which* with a flag or config option of some
sort. Depending the luserbase, it could create more questions than it
answers...
Finally, as I mentioned, I have no experience with IMAP, so should a
spam mailbox be called 'Spam', '/Spam', or something else?
So long as DBMail relies on external daemonss for IMAP, it is likely to
be 'INBOX.<something>', but I would suggest a short name "other than
SPAM", on the grounds that:
- IF we were *certain* it was spam, we probably wouldn't deliver it at all.
- "Probable spam" seems appropriate if the luser wishes to reiew it in
case his filters are over zealous, but may be too long a name for
convenience...
- How about "Suspect" (INBOX.Suspect)
Bill Hacker
