Pages

Search

Single mailbox - Multiple users accessing - Microsoft Exchange

Single mailbox - Multiple users accessing - Microsoft Exchange

Single mailbox - Multiple users accessing

Posted: 10 Jul 2004 03:12 PM PDT

Use a Public Folder:
http://www.msexchange.org/articles/MF021.html

--
Mark Fugatt
Exchange MVP
http://www.exchangetrainer.com
http://www.msexchange.org
"vipont" <net> wrote in message
news:UQZHc.313$uswest.net... 

Delivery restrictions in Exchange 5.5

Posted: 09 Jul 2004 08:00 AM PDT

Thanks, I'll give it a try. Just for my own curiosity,
what am I doing wrong with the "reject messages list" method? 
tab of the IMS 
in message 

Message tracking weirdness

Posted: 08 Jul 2004 06:06 AM PDT

 
sounds like the 
email server? They can 
negatively 
bit overboard)

Right. It seemed rather silly that it might confuse
message tracking but I just wanted to double check.
 
ensure that you 
that we keep the 
7 days. Another 
tracking the message 
access to or that does 

Hmm.. I don't believe it was either of these cases. As we
just setup the Exchange server and enabled message
tracking at that time, we have logs back to the beginning
still. As this is the sole mail server now it shouldn't
have to contact any other internal mail servers either.

Anyway, I'll just ignore it for now and see if it
reappears. If so, I'll worry about it more then. I mostly
wanted to verify that there wasn't something really dumb
going on (relying on the 220 output of the server.)

Thank you for the response and suggestions,

free/busy in exchange 2003

Posted: 07 Jul 2004 12:56 AM PDT

You can not set FreeBusy as privateor public. What Mark is referring to is
setting Calendar to be either viewable or not which you set it by assigning
permission for Default to NONE.

As far as FreeBusy goes, you will not be able to see other people's if that
person has never used calendaring. What I usually do when I create a new
mailbox is to send a test appointment to that box and ask the owner to
accept. Once it has been accepted the freebusy will become visible.



"Mark Arnold [MVP]" <org> wrote in message
news:com... 

The e-mail account does not exist at the organization this message was sent to.

Posted: 06 Jul 2004 08:28 PM PDT

Hi,

Thanks for your inputs, however, I had found that the recipient policy had
the "responsible" option selected - which I disabled to get the system
functional.

Thanks a lot for the help and support.

Regards,

Manoj Shriyan
"Matthew Tisdel" <microsoft.com> wrote in message
news:com... 
receive email for the same domain. You might try looking at the Routing
groups and set up a SMTP connector between the servers. However, I am afraid
that it will send all emails to the other server. 
address, I 
way 
message 
acumen.co.in 
Contact in 
non-acumen.co 
am 
defined 
adivate, 
schourasia 
users, 
this 
recipient 

messages building up in queue

Posted: 06 Jul 2004 02:58 PM PDT

Hi Romero,
in the first place you should not even accept emails which are not addressed
to your local domains/user. Exchange 2003 can be configured out of the box
to not accept this junk. If you are not using echange 2003 or if you want to
reject all the junk to save bandwith you should install a proper antispam
solution.
there alere are lots of free and commercial on the market. I personally
prefer rejecting filter such as my www.aloaha.com.
Futhermore Aloaha can remove read receipt requests and delivery receipt
requets from inbound mails.
Frank

"eric romero" <com> schrieb im Newsbeitrag
news:phx.gbl... 
for 

Outlook Versions?

Posted: 06 Jul 2004 09:25 AM PDT

Hi Neil,

The supported versions of Outlook are Outlook 2000, Outlook 2002, and
Outlook 2003. These are the versions that have been tested with Exchange
Server 2003. Earlier versions of Outlook might work just fine with Exchange
2003, but they have not been rigorously tested, so YMMV.

Hope this helps.
--
Scott Schnoll
Microsoft

This posting is provided "AS IS" with no warranties, and confers no rights.


"Neil Shirley" <complete-it.co.uk> wrote in message
news:phx.gbl... 
support 
this