Aaron Stone wrote:
Ilja Booij <[EMAIL PROTECTED]> said:
That would imply parsing every message on delivery..would that make
sense? A lot of messages don't have to be parsed, because they're only
retreived using POP. Sounds like a waste of resources to me, unless we
have other reasons to parse the message.
Isn't that the plan for the header and mime cache table? It would
certainly make sense to be able to disable parse-on-delivery if you only
use POP, but most people probably use all IMAP or a mixture of the two.
Doesn't it make sense to parse the message only the first time it's
fetched? Messages read using
IMAP will only have to be parsed once. Messages read using POP will not
have to be parsed.
It would make the fetching a bit more cumbersome.. But it could work
like this:
Message already parsed:
1. Fetch parsed message
2. parsed message returned to client
Message not yet parsed
1. Fetched parsed message
2. no message returned
3. fetch raw message
4. parse message
5. store parsed message
6. return parsed message
So, at the moment I'm looking into the possibility of setting a
different from: address for the messages,
which should be read from the config file.
I'm concerned that the intended recipient won't have any notification that
a message almost came through. The postmaster gets a copy to know that
something
broke, but first and foremost, the intended recipient needs a copy.
What I'm doing (read: trying to do) now is not that the postmaster gets
an email, but that the recipient gets the raw e-mail, with postmaster as
From: address.
Ilja
--
Ilja Booij
IC&S B.V.
Stadhouderslaan 57
3583 JD Utrecht
www.ic-s.nl
T algemeen: 030 6355730
T direct: 030 6355739
F: 030 6355731
E: [EMAIL PROTECTED]
