Auteur: W B Hacker Date: À: exim users Sujet: Re: [exim] Exim + Courier and archiving incoming/outgoing mail
Alltimed wrote: > Hello
>
> I have a customer who wants to archive all of their incoming and outgoing
> mail into an IMAP Maildir folder (say .archive-in and .archive-out). He is
> familiar with Sieve from a previous host and I can't say I know anytihng
> about Sieve or Exim filtering. My question is this. Does Exim by a default
> Cpanel install support Sieve or will this need to be done using the Exim
> filter? And if so any offer support or consulting on this?
>
> Thanks
>
> Bryan
Nothing magical needed, unless you are otherwise already doing
some complex message handling external to Exim:
As routers and transports vary to fit the needs, this is a bit
vague, but hopefully 'generic' enough for you to apply to your
own setup - unless its Debian'ed... ;-)
- locate each of the routers that ordinarily handle the traffic
in question. As a minimum, those for local delivery
('incoming') and remote dns delivery, ('outgoing'), optionally
those for system accounts and aliases. Give a think as to where
'forwarders' or 'vacation' fit into your system. Will they be
'captured' as is, or do you need to do more work?
- terminate each of the selected existing routers with 'unseen'
as the last line.
- immediately following the 'unseen', add a new router section,
but specify a new transport for delivery. Your plan needs at
least two such - your 'archive_in and archive_out transports.
- add the new transports to your transport section. They will
probably most closely resemble the ones you are already using
for local delivery - just to a 'fixed' user identity instead of
local_part. Multiple domains can be kept separate or combined.
W/R the POP or IMAP 'recovery', or Sam's specialized Courier
Webmail, which directly accesses Maildir's (w/o IMAP), give a
think as to which UID and GID Exim is to use when delivering.
This works well for us with selected domains in a
PostgreSQL-driven multiple-virtual domain environment.
CAVEATS:
This presumes pretty much bog-standard routers and transports as
a starting point, and no external filter or shell script
routing. 'Integrated' smtp-time ClamAV & SA are not a problem.
Have a care not to create loops, skip or duplicate traffic, nor
leave it hung on the queue as undeliverable.
Extra logging is (always) good when first implementing changes.
