[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [cobalt-developers] carbon copy of all email sent/received



Danny,

This is standard sendmail functionality, so do not be alarmed. While you
can set up the .forward file in each user's home directory, you should
really leave that as a user to maintain. If they read the file and see that
their mail is getting CC'ed elsewhere they will get pretty annoyed.

The heart of the matter lives in 2 files, /etc/sendmail.cw and /etc/aliases

/etc/sendmail.cw contains a list of the domains that your server is
accepting email for.

/etc/aliases contains a list of mappings for email addresses to local users. 

For example if you are hosting mydomain.com and fredsbank.com, then both
sites will want to have an 'info' email address, so the aliases file
contains these entries:

info@xxxxxxxxxxxxx:	fred
info@xxxxxxxxxxxx:	me

So it is easy to add another addressee for the aliases

info@xxxxxxxxxxxxx:	fred,spyuser
info@xxxxxxxxxxxx:	me,spyuser

I noticed that the standard sendmail.cf that comes with the cobalt is
pretty weak, ie it does not use much of what's there in sendmail. You can
rejig it using more features... This is an example /etc/sendmail.mc

dnl This is the macro config file used to generate the /etc/sendmail.cf
dnl file. If you modify thei file you will have to regenerate the
dnl /etc/sendmail.cf by running this macro config through the m4
dnl preprocessor:
dnl
dnl        m4 /etc/sendmail.mc > /etc/sendmail.cf
dnl
dnl You will need to have the sendmail-cf package installed for this to
dnl work.
include(`/usr/lib/sendmail-cf/m4/cf.m4')
define(`confDEF_USER_ID',``8:12'')
OSTYPE(`linux')
undefine(`UUCP_RELAY')
undefine(`BITNET_RELAY')
define(`confAUTO_REBUILD')
define(`confTO_CONNECT', `1m')
define(`confTRY_NULL_MX_LIST',true)
define(`confDONT_PROBE_INTERFACES',true)
define(`PROCMAIL_MAILER_PATH',`/usr/bin/procmail')
FEATURE(`smrsh',`/usr/sbin/smrsh')
FEATURE(`mailertable',`hash -o /etc/mail/mailertable')
FEATURE(`virtusertable',`hash -o /etc/mail/virtusertable')
FEATURE(redirect)
FEATURE(always_add_domain)
FEATURE(use_cw_file)
FEATURE(local_procmail)
MAILER(procmail)
MAILER(smtp)
FEATURE(`access_db')
FEATURE(`blacklist_recipients')
dnl We strongly recommend to comment this one out if you want to protect
dnl yourself from spam. However, the laptop and users on computers that do
dnl not hav 24x7 DNS do need this.
FEATURE(`accept_unresolvable_domains')
dnl FEATURE(`relay_based_on_MX')

I needed to set up the RAQ as an email secondary. I was concerned that it
would destroy some other system features, but it appears to have worked OK.

Cheers

Mike

At 10:20 20/12/2000 -0800, you wrote:
>I know you can create a .forward file in the users home directory. In this
>file you specify any address you want to forwarded mail to. This only
>encompasses mail that is received.
>
>If you do find a way using send-mail I would be interested to know what it
>is.
>
>-Danny
>  dcd@xxxxxxxxxxxxxxxxxx
>----- Original Message -----
>From: Mike King <mikkel@xxxxxxxxxxxxxxxxxxx>
>To: <cobalt-developers@xxxxxxxxxxxxxxx>
>Sent: Wednesday, December 20, 2000 2:33 AM
>Subject: Re: [cobalt-developers] carbon copy of all email sent/received
>
>
>> Ken,
>>
>> You can do it in the aliases file. You will normally have an alias for
>each
>> mailbox anyway, so just add the monitoring mailbox to each entry in the
>file.
>>
>> Cheers
>>
>> Mike
>>
>> At 01:40 20/12/2000 -0600, you wrote:
>> >Does anyone have any ideas on how you could enable 'carbon copying' on
>> >certain POP accounts, whereby a copy of each new email received (and
>sent?)
>> >is sent to a system mailbox for monitoring/legal purposes?
>> >
>> >I'm currently searching the Internet for Sendmail configuration
>information.
>> >I'm not very knowledgeable about Sendmail.
>> >
>> >TIA,
>> >Ken Reilly
>> >jm@xxxxxxxxx
>> >
>> >_______________________________________________
>> >cobalt-developers mailing list
>> >cobalt-developers@xxxxxxxxxxxxxxx
>> >http://list.cobalt.com/mailman/listinfo/cobalt-developers
>>
>> _______________________________________________
>> cobalt-developers mailing list
>> cobalt-developers@xxxxxxxxxxxxxxx
>> http://list.cobalt.com/mailman/listinfo/cobalt-developers
>>
>
>_______________________________________________
>cobalt-developers mailing list
>cobalt-developers@xxxxxxxxxxxxxxx
>http://list.cobalt.com/mailman/listinfo/cobalt-developers