> -----Original Message-----
> From: exim-users-bounces@??? [mailto:exim-users-bounces@exim.org]On
> Behalf Of Alon
> Sent: Wednesday, January 19, 2005 8:48 PM
> To: exim-users@???
> Subject: Re: [exim] Re: copy/unseen - where to plug the code?
>
>
> There are two options:
>
> 1. Folks, you don't know the answer to my question.
> 2. You are all waiting for me to ask: "Hey.. anyone here wants
> money to come
> and do the work"?
>
> I have had 5 responses here none of them are code related (Tom Kistner
> excluded).
>
> Is there a concensous here not to share knowledge?
> Are you (most,. not all) affraid somebody will think less of you if you
> offer assistance here?
>
> I'm roamed around various newsgroups and mailman lists in the
> past 10 years
> to see a huge response in
> every possible listings.
> I'm sorry to say this has been a very tasteless experience in here.
>
> Please don't respond unless you address the question that is in
> the subject
> line.
>
[...]
I will offer some help, but also an explanation. This groups is VERY helpful
and VERY sharing in almost every instance for the years I have been here.
But your original message basically stated "I don't know anything about what
I am trying to do and I have a LOT of people depending on me doing it
right...". The responsible answers are really the ones that you got
initially. Not only do the 1000s of users rely on you doing it right, so
does the rest of the world with whom your system communicates. There are a
lot of "Simple" things you can do to a mail server that can cause havoc with
your users and those they communicate with.
I believe had you not represented your self as lacking in technical skills
and responsible for thousands of users you would have gotten a much
different response. Most of these people are professional and do actually
care about the profession they are engaged in.
That said: Here is a modified router I use to grab any mail that my kids
send out from our home mail system. the changes are slight (I actually have
a list of senders, the kids, instead of a whole sender domain) So it should
work as is. The changes in the To: header are to provide a way to filter or
sort the mail that has been redirected. For instance if you set the line
To: Some Name <address@???>
to To: Mail Copy <address@???> you could send the mail to "the
boss" and he can set his MUA to filter anything inbound with Mail Copy in
the To: field to go into a folder other than his inbox so it's not
intermixed with personal mail.
This router would go at the top of your routers and assumes the following:
that the redirect address is local
that you have a local user router named localuser
that you do not want copies of internal to internal mail
you do not want copies of mail sent by the "archive" user
if you are using an dual (separate inbound and outbound) daemon arrangement
you will place this in the outbound daemon's configuration file
Copy_Messages:
driver = redirect
check_ancestor
# this should be the domain you want to archive outbound mail from
sender_domains = the_domain_in_question
headers_remove = Envelope-to:To
headers_add = Envelope-to: address@???\n\
To: Some Name <address@???>
# This says if the sender domain and recipient domain are NOT both
# domain-name (because of above criteria) and the sender is not
# the "archive" user then make the redirection
condition = ${if and {\
{!eq{${lc:$domain}}{domain-name.com}}\
{!match {$sender_address}{address@???}}\
}\
{1}{0}}
data = address@???
# do this and process the rest of the message normally
unseen = true
# Do not use this router during address verification
no_verify
# skip to the local user router. If it's not going to a local user
# then change the below line to reflect the correct router such as
# smtp. This is only useful if you KNOW the address you are using
# won't have aliases, forwards, etc
redirect_router = localuser
Rick
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
