On Mon, 14 Mar 2005, Jeffrey D. Wheelhouse wrote:
> In order to do this, one would need some sort of logic (i.e. procmail) to fan
> the messages out into the multiple IMAP folders. In most cases, that's
> probably just as much work as setting up extra mailboxes. Eventum seems to
> like to want to fan things out rather than concentrate them, so if you try to
> go the opposite way, you may be going uphill unnecessarily.
I think it depends on what you want to do. If you're creating 5-10 real
system accounts, you have to set password for each of them. Depending on
the anti-spam system you're using, assuming you're using one, there might
be per-account settings that need to be managed. And from a security
standpoint, the less system accounts you have, the better.
We create one system account, and have all Eventum managed E-mail aliases
come into it. Using simple procmail rules, things are sorted out into
separate mailboxes. We use DSPAM in front of this one system account to
keep out spam, although you could use any other type of anti-spam system
you were confident in.
The following simple shell script is used in conjunction with cron to
check all the accounts:
# This script runs the Eventum download_emails.php script for multiple
SCRIPT="/local/bin/php -q ./download_emails.php"
MBOXES="project1 project2 project3 project4 project5"
for mbox in $MBOXES
# echo "Processing new Eventum mail for [$mbox] mailbox"
cd $DIR; $SCRIPT $USER $SERVER $mbox
> Does this message-id you've referring to (which I'm assuming is not the
> actual Message-ID: header) have something to do with my email association
> issue? From what I've read here, it's sounding that way, but I don't quite
> understand what it is or how it's used to identify responses. I checked the
> code briefly, but it did not give up its secrets to such a cursory
There should not be any problems with message-ids as long as the same
E-mail is not ending up in two projects. But if you are trying to use one
support alias for multiple projects, you will run into this problem. Use
one alias per project. If you like to keep things managable and more
scalable, setup one system account and use procmail to sort things into
separate mailboxes based on To:/CC: of the support alias.