In one of the environments I plan to run Zimbra, it will be for a set of
mostly email-only users, mixed in with a handful of administrators and power
users who have accounts on the machine.
Zimbra is perfect for the email-only users. It's also perfect for these admins
and power users. Well, almost.
The folks with accounts on the machine are used to using things like procmail
and mutt for managing email. Now, one can certainly continue to use both mutt
and Zimbra via IMAP. It's procmail that I'm curious about.
Do you have any thoughts as to how one might integrate procmail and Zimbra
together, expecially when the desire is to only use a single piece of hardware
to do so?
Being able to use procmail to specify what folder to store data in Zimbra would
be kind of neat, though Zimbra does provide that sort of functionality as a filter already.
However, another use of procmail is to automate tasks based on emails that
arrive. If someone receives an email to a particular address with a particular
subject, run some command on the system.
One way I can think of to do this would be to run a non-Zimbra mail daemon on
port 25, that delivers to a user if one exists /etc/passwd, or to Zimbra
otherwise. The biggest problem here is that there are now two mail daemons,
and two sets of email accounts (those with system accounts and those with
Do you see a better way of handling this? For starters, could Zimbra perhaps
offer the ability to run a system command based on certain criteria within an
email? That of course would need to be something the system admin could enable
or disable, not all admins would want users executing commands.
Beyond that though, do you see a way to provide the full power of procmail
within Zimbra for those who get lonely without their command line? :-)