How to auto CC to self for every sent message

[Xuanyi]

I want to let every message that I sent out can be cc to myself. Any body knows how to automatically do that?

Thanks in advance!

Noah

 

[Judy Gleeson \(MVP Outlook\)]

You could use a Rule and say if the subject contains a e i o or u send a
copy to your email address.

You forgot to mention your version and many things, including Rules are
slightly different in each version.

Regards

Judy Gleeson
MVP Outlook
Trainer and Consultant www.pragmatix.com.au
Outlook 2003 user? Read "7 settings all Outlook 2003 users should change"
on my website.

..

 

[VanguardLH]

in

"Xuanyi" wrote ...

You could use a Rule and say if the subject contains a e i o or u send
a copy to your email address.

Why is any test clause required? You can create an outbound rule that
applies against all outbound messages.

 

[Xuanyi]

Thanks all, I add a rule that message sent by my account will be cc to the my account.

 

[Judy Gleeson \(MVP Outlook\)]

I could not test that method in an unknown version so I gave an answer I
know works in all versions.

Regards

Judy Gleeson
MVP Outlook
Trainer and Consultant www.pragmatix.com.au
Outlook 2003 user? Read "7 settings all Outlook 2003 users should change"
on my website.

..

 

[Gordon]

Thanks all, I add a rule that message sent by my account will be cc to the
my account.

And why isn't the copy saved in your Sent Items folder sufficient?

 

[VanguardLH]

...

And why isn't the copy saved in your Sent Items folder sufficient?

- YOU sent the message. The mail host accepted it. YOU have a copy of
what got *accepted* by the mail host. You have nothing to show that
your mail host actually SENT your e-mail.

- You want to know WHEN the mail host sent out your e-mail. You don't
want to rely on getting information back from your recipients nor do you
want to bother them with the request assuming they actually forward as
attachment your original e-mail rather than forward it inline (which
strips the original headers).

- You send out using one account but want a copy received back on
another account. Since rules don't work on HTTP accounts, for example,
you may not be able to apply any outbound rules on e-mails you send out
through an HTTP account. However, upon receiving the e-mail back
through your POP account, you can use rules to decide how to organize
your sent e-mails.

- You send out using Outlook but copies of your sent e-mail must be
recorded by a different e-mail program. So you send yourself a copy to
an account that Outlook doesn't monitor but the other e-mail client
does.

I'm sure there are lots of reasons that I haven't thought of. Xuanyi
probably has yet another reason. The first reason is the one that I see
most often needed for verifying the e-mail got sent out and can be seen
from the sender's end.

 

[Gordon]

- YOU sent the message. The mail host accepted it. YOU have a copy of
what got *accepted* by the mail host. You have nothing to show that
your mail host actually SENT your e-mail.

- You want to know WHEN the mail host sent out your e-mail. You don't
want to rely on getting information back from your recipients nor do you
want to bother them with the request assuming they actually forward as
attachment your original e-mail rather than forward it inline (which
strips the original headers).

- You send out using one account but want a copy received back on
another account. Since rules don't work on HTTP accounts, for example,
you may not be able to apply any outbound rules on e-mails you send out
through an HTTP account. However, upon receiving the e-mail back
through your POP account, you can use rules to decide how to organize
your sent e-mails.

- You send out using Outlook but copies of your sent e-mail must be
recorded by a different e-mail program. So you send yourself a copy to
an account that Outlook doesn't monitor but the other e-mail client
does.

I'm sure there are lots of reasons that I haven't thought of. Xuanyi
probably has yet another reason. The first reason is the one that I see
most often needed for verifying the e-mail got sent out and can be seen
from the sender's end.

Well I have NEVER EVER known ANYONE who uses POP email that needs to know
all that. In TWENTY YEARS......

 

[VanguardLH]

Well I have NEVER EVER known ANYONE who uses POP email that needs to know
all that. In TWENTY YEARS......

I found it quite helpful when I noticed that e-mails sent through one
e-mail service seemed to not get recieved very quickly by the
recipients. Was easy to see after doing this testing that the e-mail
provider was batching up the outbound e-mails to send them all at about
1-hour intervals.

Delivery confirmation for postal mail is not just to prove that the
recipient got the package. It also proves the package actually got
sent. Same thing for confirming that a server actually sent an e-mail.

What, you've never heard of users complain that they send e-mails but
they are never received by the recipient? You can go through all the
machinations of analyzing the behavior and logs for your local e-mail
client but all that can prove is that the mail session to your SMTP mail
host went okay. Still doesn't give a clue that the e-mail actually got
sent to ensure the problem wasn't on the sender's end.

And, of course, mail servers never crash, databases are never lost, and
networks never go down with servers that always have complete recovery.