> On 22 Feb 2016, at 13:02, Doug Hardie <bc...@lafn.org> wrote: > > >> On 20 February 2016, at 18:14, Timo Sirainen <t...@iki.fi> wrote: >> >> On 21 Feb 2016, at 02:50, Kevin Kershner <cstke...@outlook.com> wrote: >>> >>> I'd like to revisit and old post if I may, will/does Dovecot support the old >>> qpopper "Bulletin" ability? >>> >>> Basically I need a simple way of posting bulletins to all domain users. >>> Qpopper maintained a bulletin db for each user and sent them the next >>> bulletin in sequence. >> >> I guess there could be a plugin that does this check on each login. But >> would it actually be useful? Why would it be better than simply sending the >> mail to all the users? For example: >> >> doveadm save -A < bulletin.txt > > The reasons for bulletins as I see it are: > > 1. The doveadm save command is undocumented. It does show a cryptic line in > the output of the command "doveadm". However, it doesn't give any clue what > it does or how to provide the message. Your note above provides considerably > more information on that command. I tested it and it works as you have > indicated though.
Yeah, would be good to add a man page to it.. > 2. The doveadm save command causes the email to be saved in each user's > mailbox. If you have a lot of users, thats a lot of wasted disk space. > Qpopper's bulletins only kept one copy and every user downloaded from that > copy. All that was retained per user was a counter of the last bulletin's > sequence number that was downloaded. With sdbox and Maildir formats the mails can be hard linked to provide only one copy. This would have to be done by delivering the mail once and then using doveadm copy to copy it to everybody else. These kind of bulletins would be pretty complicated to implement in a generic way.
