Davide wrote:
> Bill Says :
> The 'sent_archive_delivery' transport should store mail in either a
> common-systemwide, common-source-domain-wide (virtual hosting?), or
> by-destination-domain structure, depending on your environment and expected
> manner of analysis/recovery.
>
>
> I want to save mail in a directory in account maildir ... i have only one
> account ... inside a folder than can I subscribe with an IMAP client and
> read it .
>
With just one account, you may be able to do that more easily with the IMAP
client itself. Mozilla Mail, among others, can keep copies of sent traffic on
both the IAMP server and in the local file system.
Now if it is the traffic of *other users* - best check the ToS, contracts, and
law of the land' where you operate, AND where those other users sit.
The archiver code we illustrated was for a Corporate mail server, and access is
not ordinarily available to even their staff.
> How can I set to do this ?
>
> BR Razi
If you want to use Exim to manage any sort of 'special' IMAP-visible server-side
folder, then you need only to insure that it creates and fills said folder in
the location the IMAP client will seek it, and with naming convention and access
privileges the IMAP client expects.
Perhaps the best way to start that is to first use your IMAP client to create a
new empty folder with the name you want.
THEN go in on the server, look into the Maildir in question, see what the full
path to that folder is, who 'owns' it, and what file perms exist on it.
That way you have covered any differences between your server's storage and
those of other folks.
Mine might be:
Dovecot ONLY:
/data/mail/conducive.org/wbh/Maildir/.Special
Dovecot OR Courier-IMAP:
/data/mail/conducive.org/wbh/Maildir/.INBOX.Special
I am not current on Cyrus-IMAP storage...
Whatever is working, now take that identical path and use it for the
line in your special transport that starts with: 'directory = '
The rest - file privileges, user, group - shoudl be that same as whatever is
*working* for you other mail deliveries.
Variables or lookups, if needed, work the same as for any other delivery, but
with just one user, you can probably just hard-code the path. SO LONG AS the
calling router is picking up only what you want it to pick up.
HTH,
Bill
PS: Anyone thinking to keep an (unauthorized) eye on mail of family members,
lady friends, co-workers, or the Boss, should expect serious legal problems, if
not worse. Same goes for simply reading their Maildirs on the server.
Running a server or being a mailadmin does not magically convey legal immunity,
nor does it make you 'invisible', bullet-proof, or resistant to a sound
thrashing, verbal or physical.
Server admins must cultivate discretion, even 'selective blindness', at least
until served with a court order.
>
>
> -----Messaggio originale-----
> Da: exim-users-bounces@??? [mailto:exim-users-bounces@exim.org] Per
> conto di W B Hacker
> Inviato: martedì 29 agosto 2006 1.42
> A: exim-users@???
> Oggetto: Re: [exim] Exim4 And outgoing Filters
>
> Davide Minardi wrote:
>
>
>>Hi, I have debian sarge installed . I have installed Exim 4 as outgoing
>
> mail server and incoming by fetchmail.
>
>>I want to save, for backup event, outgoing message in a Maildir subfolder
>
> named "backup" . I connect on my server with IMAP Client (courier-imap is
> server side) .
>
>>When i send a message from another host in my LAN, Exim4 shuold be save
>
> outgoing mail in a subfolder. I have read on Internet that is possible. I
> must write a filter rules but ...how and where ?
>
>>Any ideas ?
>>
>>Best regards ...
>>
>>Raziel
>
>
> No filter needed. Use 'unseen' to chain two routers:
>
> This works:
>
> The routers:
>
> =====================
>
> # Route 2_C normal remote DNS lookup
> #
> dnslookup:
> driver = dnslookup
> domains = ! +local_domains
> transport = remote_smtp
> ignore_target_hosts = 0.0.0.0 : 127.0.0.0/8
> unseen
>
> # ROUTE_2D REMOTE: archiving of outbound traffic.
> #
> sentarchiver:
> driver = dnslookup
> domains = ! +local_domains ### Note - this is optional...
> transport = sent_archive_delivery
> ignore_target_hosts = 0.0.0.0 : 127.0.0.0/8
>
> =====================
>
> The remote_smtp transport is default/'conventional.
>
> The 'sent_archive_delivery' transport should store mail in either a
> common-systemwide, common-source-domain-wide (virtual hosting?), or
> by-destination-domain structure, depending on your environment and expected
> manner of analysis/recovery.
>
> Bill
>
>
>
>
> --
> ## List details at http://www.exim.org/mailman/listinfo/exim-users
> ## Exim details at http://www.exim.org/
> ## Please use the Wiki with this list - http://www.exim.org/eximwiki/
>
>
>
