RE: Viewing other person's mailbox folders

2001-11-14 Thread Montgomery, John

In Exchange Admin go to the users mailbox.  Click on the permissions tab
(you may have to check the option "Show permissions page for all objects" in
the Exchange Admin options section).  Add the manager as a user to the
mailbox.  Allow time for the security change to take effect.  The manager
can open that users mailbox in Outlook by adding it to the list of "Open
these additional mailboxes".

-Original Message-
From: Scott Oliver [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 14, 2001 11:17 AM
To: MS-Exchange Admin Issues
Subject: Viewing other person's mailbox folders


Dear Group,

I have a situation where in my company a manager
needs to have access to one of their employees mailbox.  With this they need
to be able to see the folder that the user has created also.  Is it possible
to set the permissions in the "Outlook Today"  folder and have them
propagate down to the other folders?  

Exchange 5.5  NT 4.0 Outlook 2000

Any help with this would be greatly
appreciated.


Scott Oliver
MS Exchange Administrator
Computer Operations Supervisor
Liz Claiborne Shoes
(904)-279-8367


List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm




RE: *** Warning *** New Virus - W32.goner.a@mm

2001-12-04 Thread Montgomery, John

What version of GroupShield do you have?

-Original Message-
From: Glen Macdonald [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 04, 2001 3:47 PM
To: MS-Exchange Admin Issues
Subject: RE: *** Warning *** New Virus - W32.goner.a@mm


We had the same thing happen-Groupshield missed one,
but caught the rest (so far). Fortunately, the
particular user it was sent to is a "power user", and
was smart enought not to open it, and called us
instead. Would love to know why it's not catching them
all.
--- Eric Brouwer <[EMAIL PROTECTED]> wrote:
> Groupsuck REALLY sucks...
> 
> Even though I already had the latest dat installed,
> and all my services are
> running, two instances of this virus made it
> through.  Thankfully I don't
> trust GS, and I sent out a warning and my users
> actually read it, and acted
> on it.
> 
> Any idea why GS might not be catching them? 
> Everything looks like it's set
> up properly.  I caught all the Badtrans viruses last
> week.
> 
> -Original Message-
> From: Dennis Atherton
> [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, December 04, 2001 3:27 PM
> To: MS-Exchange Admin Issues
> Subject: RE: *** Warning *** New Virus -
> W32.goner.a@mm
> 
> 
> Download and save the file sarcx86.exe, and then
> execute it on the system to
> be updated.
> 
> -Original Message-
> From: MHR(Michael Ross) [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, December 04, 2001 11:50 AM
> To: MS-Exchange Admin Issues
> Subject: RE: *** Warning *** New Virus -
> W32.goner.a@mm
> 
> 
> 
> Which file do you grab from there 
> 
> -Original Message- 
> From: Philip Youngworth [
> mailto:[EMAIL PROTECTED]
>  ] 
> Sent: Tuesday, December 04, 2001 1:37 PM 
> To: MS-Exchange Admin Issues 
> Subject: RE: *** Warning *** New Virus -
> W32.goner.a@mm 
> 
> 
> You can get the sarc update from their ftp server. 
> 
>
ftp://ftp2.symantec.com/public/english_us_canada/antivirus_definitions/norto
>
 o>  
> n_antivirus/specdef 
> 
> You should be able to grab the sarc there for it. 
> 
> -Original Message- 
> From: Cicerrella, Steve [ mailto:[EMAIL PROTECTED]
> 
> ] 
> Sent: Tuesday, December 04, 2001 2:24 PM 
> To: MS-Exchange Admin Issues 
> Subject: RE: *** Warning *** New Virus -
> W32.goner.a@mm 
> 
> 
> Seeing this one already.I have not found a patch
> for "Norton for 
> Exchange" yet.Already sent a broadcast to the
> users pleading with them 
> to use some common sense and explicitly telling them
> NOT to open that one. 
> I wonder how many of them will open it anyway..   ;)
> 
> 
> Steve 
> 
> 
> 
> -Original Message- 
> From: Briggs, Bruce [
> mailto:[EMAIL PROTECTED]
>  ] 
> Sent: Tuesday, December 04, 2001 10:41 AM 
> To: MS-Exchange Admin Issues 
> Subject: *** Warning *** New Virus - W32.goner.a@mm 
> 
> 
> Just in case you are not aware yet, there is a new
> virus out there. Lots of
> incoming infected mail here, right now. We got an
> automatic update this
> morning for Antigen which is protecting us. Hope the
> same for you.
> 
>
http:[EMAIL PROTECTED]
>
 >  
> 
> Bruce Briggs 
> System Administration 
> State University of NY 
> 
> List Charter and FAQ at:
>
http://www.sunbelt-software.com/exchange_list_charter.htm
>

>  
> 
> List Charter and FAQ at:
>
http://www.sunbelt-software.com/exchange_list_charter.htm
>

>  
> 
> 
>
***
> 
> The information transmitted in this email is
> intended only for the person(s)
> or entity to which it is addressed and may contain
> confidential and/or
> privileged material.  Any review, 
> 
> retransmission, dissemination or other use of, or
> taking of 
> any action in reliance upon, this information by
> persons or entities other
> than the intended recipient is prohibited. If you
> received this email in
> error, please contact the sender and permanently
> delete the email from any
> computer.
> 
> List Charter and FAQ at:
>
http://www.sunbelt-software.com/exchange_list_charter.htm
>

>  
> 
> List Charter and FAQ at:
>
http://www.sunbelt-software.com/exchange_list_charter.htm
> 
> 
> 
> List Charter and FAQ at:
>
http://www.sunbelt-software.com/exchange_list_charter.htm
> 
> List Charter and FAQ at:
>
http://www.sunbelt-software.com/exchange_list_charter.htm
> 


__
Do You Yahoo!?
Buy the perfect holiday gifts at Yahoo! Shopping.
http://shopping.yahoo.com

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm




RE: Viewing Multiple Mailboxes

2001-08-21 Thread Montgomery, John

On the client just add that mailbox to the list of "Open these Additional
Mailboxes".  This can be found under the advanced tab in the Exchange
properties. 

-Original Message-
From: Sean Martin [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 21, 2001 2:59 PM
To: MS-Exchange Admin Issues
Subject: Viewing Multiple Mailboxes


How can I setup a mailbox to be viewed by a department? 

Scenario: Mailbox created to receive messages from a company that needs to
be viewed by one department. I'd like each user to have the additional
mailbox shown in the folders view of their Outlook 98 client. I've setup the
Global Group to be the Primary NT account for this mailbox. Are there
specific client settings that need to be made? I know I've done this once
before but I can't remember how I accomplished it.
 
Exchange 5.5 sp3, NT 4 sp6a, Outlook 98
 
Regards,
 
Sean Martin, MCSE
Network Administrator
Ribelin Lowell & Company
Insurance Brokers, Inc.
3111 C Street, Suite 300
Anchorage, Alaska 99503
Ph: (907) 561-1250
Fax: (907) 561-4315
Cell: (907) 229-0885
Email:   [EMAIL PROTECTED]
 
List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm


DO NOT read, copy or disseminate this communication unless you are the
intended addressee. This e-mail communication contains confidential and/or
privileged information intended only for the addressee. If you have received
this communication in error, please call us immediately at (907) 561-1250
and ask to speak to the sender of the communication. Also, please e-mail the
sender and notify the sender immediately that you have received the
communication in error.


List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm




Server Client communication

2001-09-10 Thread Montgomery, John

Someone asked me a question that I was not positive of the answer to.  If
you could either answer it for me or point me to where I could find the
answer I would appreciate it.
Is the communication between Exchange 5.5 and Outlook 98 encrypted?  If
someone happened to be sniffing the wire could they read the email that was
being passed?
Thank you for your time,

John Montgomery
Information Technology
LAN Administrator
HoneyBaked Ham

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm




RE: Server Client communication

2001-09-11 Thread Montgomery, John

Thank you.  I must have looked in this tab a thousand times and never
noticed that section.

-Original Message-
From: Neil Hobson [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September 11, 2001 3:59 AM
To: MS-Exchange Admin Issues
Subject: RE: Server Client communication


It's my understanding that, although Exchange and Outlook communicate
using RPCs, you have to configure Outlook to use encrypted RPCs.  In
Outlook, go to Tools / Services and choose the Properties of the
Microsoft Exchange Server service.  On the Advanced tab, you'll see a
section called "Encrypt Information".  It's the settings there that
control whether encrypted RPCs are used or not.

Neil

-Original Message-----
From: Montgomery, John [mailto:[EMAIL PROTECTED]] 
Posted At: 10 September 2001 21:00
Posted To: Sunbelt Exchange List
Conversation: Server Client communication
Subject: Server Client communication


Someone asked me a question that I was not positive of the answer to.
If you could either answer it for me or point me to where I could find
the answer I would appreciate it. Is the communication between Exchange
5.5 and Outlook 98 encrypted?  If someone happened to be sniffing the
wire could they read the email that was being passed? Thank you for your
time,

John Montgomery
Information Technology
LAN Administrator
HoneyBaked Ham

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

**
This eMail and any files transmitted with it are confidential and
intended solely for the use of the individual to whom it is addressed.
Any view or opinions presented are solely those of
the author and do not necessarily represent those of Silversands
or any of its subsidiary companies.
If you have received this eMail in error please contact the Support Desk
Immediately by telephone on 01202-36 or on eMail at
[EMAIL PROTECTED]
**

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm




RE: OWA Password expires in 0 days

2001-09-26 Thread Montgomery, John

You did not give any information about Exchange version so I don't know if
this applies, but take a look at the following Q article...
http://support.microsoft.com/support/kb/articles/Q262/9/02.ASP

-Original Message-
From: Eric Larsen [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 26, 2001 12:30 PM
To: MS-Exchange Admin Issues
Subject: OWA Password expires in 0 days


When any of my users (including myself) log on to the owa page, the
following error is displayed:  Your current password is about to expire in 0
days.  To change your password, go to the Options page after you login.  You
can then click OK and it launches the owa page.  This has been going on for
a week or so.  so much for 0 days. When you click on the options page, then
click on change password button, I get a page cannot be displayed error...
what fun. any ideas?

-Eric Larsen
-Key Knife, Inc.

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm




Antivirus API

2001-10-24 Thread Montgomery, John

Of those of you that are using an antivirus program that utilizes the
Antivirus API, have you seen and or addresses the MAPI issues discussed in
Q264731?  Basically we are seeing issues with MAPI clients accessing
unscanned attachments getting errors.  After the first attempt everything
seems to work fine.  We were told to look at Q264731.  I was curious if
anyone else has done these changes and if so did it fix the issue for you or
did it cause other problems?
Exchange 5.5 SP4
GroupShield 4.5

Thank you for your time,

John Montgomery
Information Technology
LAN Administrator
HoneyBaked Ham

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm




Relay

2001-10-24 Thread Montgomery, John

We are having a strange problem.  We send to a particular domain and get an
NDR back from our server saying that relaying is prohibited.  This same
domain can send to us and we can send to other domains just fine.  We were
able to send to them before.  Has anyone else seen anything like this?  We
have recently upgraded GroupShield to 4.5.  I called their tech support to
see if this was anything that they may know about, but they said that it is
not.  I have tried searching Microsoft but could not find anything.
Exchange 5.5 SP4

Thanks,

John Montgomery
Information Technology
LAN Administrator
HoneyBaked Ham

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm




RE: Relay

2001-10-24 Thread Montgomery, John

I did this and using SAlive made an SMTP connection to the IP address.  It
connected just fine.  What seems strange is that it is coming from our IMS
saying MSEXCH:IMS:HoneyBaked:Site:Server 3550 (000B09AA) 550 5.7.1 Unable to
relay for [EMAIL PROTECTED]  To test the GroupShield scenario I stopped
GroupShield and tried it again.  It still failed so I am assuming that this
is not the problem.

-Original Message-
From: Benjamin Zachary [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 24, 2001 4:52 PM
To: MS-Exchange Admin Issues
Subject: RE: Relay


You may want to nslookup on the MX record for DNS and make sure its
pointing to the correct location. NSLOOKUP -Q=MX DOMAIN.COM

-Original Message-
From: Montgomery, John [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, October 24, 2001 3:30 PM
To: MS-Exchange Admin Issues
Subject: Relay


We are having a strange problem.  We send to a particular domain and get
an NDR back from our server saying that relaying is prohibited.  This
same domain can send to us and we can send to other domains just fine.
We were able to send to them before.  Has anyone else seen anything like
this?  We have recently upgraded GroupShield to 4.5.  I called their
tech support to see if this was anything that they may know about, but
they said that it is not.  I have tried searching Microsoft but could
not find anything. Exchange 5.5 SP4

Thanks,

John Montgomery
Information Technology
LAN Administrator
HoneyBaked Ham

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm



List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm




RE: Relay

2001-10-25 Thread Montgomery, John

How do you look to see if reverse DNS lookup is setup?  I realize that this
would be on their side, but I would like to know for myself.  I have been
looking but can not seem to find it.
Thanks,
John

-Original Message-
From: Simon Taylor [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 25, 2001 5:41 AM
To: MS-Exchange Admin Issues
Subject: RE: Relay


I have in the past had relays refuse when they could not perform a reverse
dns lookup on the address I was coming from - I would check their end if you
can email to other domains just fine..
Cheers
Simon

-Original Message-
From: Montgomery, John [mailto:[EMAIL PROTECTED]] 
Sent: 24 October 2001 23:19
To: MS-Exchange Admin Issues
Subject: RE: Relay


I did this and using SAlive made an SMTP connection to the IP address.  It
connected just fine.  What seems strange is that it is coming from our IMS
saying MSEXCH:IMS:HoneyBaked:Site:Server 3550 (000B09AA) 550 5.7.1 Unable to
relay for [EMAIL PROTECTED]  To test the GroupShield scenario I stopped
GroupShield and tried it again.  It still failed so I am assuming that this
is not the problem.

-Original Message-
From: Benjamin Zachary [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 24, 2001 4:52 PM
To: MS-Exchange Admin Issues
Subject: RE: Relay


You may want to nslookup on the MX record for DNS and make sure its pointing
to the correct location. NSLOOKUP -Q=MX DOMAIN.COM

-Original Message-
From: Montgomery, John [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, October 24, 2001 3:30 PM
To: MS-Exchange Admin Issues
Subject: Relay


We are having a strange problem.  We send to a particular domain and get an
NDR back from our server saying that relaying is prohibited.  This same
domain can send to us and we can send to other domains just fine. We were
able to send to them before.  Has anyone else seen anything like this?  We
have recently upgraded GroupShield to 4.5.  I called their tech support to
see if this was anything that they may know about, but they said that it is
not.  I have tried searching Microsoft but could not find anything. Exchange
5.5 SP4

Thanks,

John Montgomery
Information Technology
LAN Administrator
HoneyBaked Ham

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm



List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm




RE: Relay

2001-10-25 Thread Montgomery, John

That wasn't what I was asking, but that does answer another question I had
so thank you. : )
How can you tell if the IMS on Exchange is setup to perform reverse DNS
lookups on inbound email, or does it just automatically do that?
Thanks,
John

-Original Message-
From: Simon Taylor [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 25, 2001 10:47 AM
To: MS-Exchange Admin Issues
Subject: RE: Relay


Do this
Run nslookup first on your exchange machine (or whatever you call your mail
system.) Then run nslookup again on the ip address it give you for that
system and if it resolves then you are indeed setup for reverse lookups. You
may want to run nslookup off an external dns server as internally it may
work, but not external.


H:\>nslookup
Default Server:  ns5.domain.com
Address:  192.168.1.32

> server ns1.bt.net
Default Server:  ns1.bt.net
Address:  194.72.6.52

> mail.domain.com
Server:  ns1.bt.net
Address:  194.72.6.52

Name:mail.domain.com
Address:  xxx.xxx.xxx.xxx
Aliases:  imap.domain.com

> xxx.xxx.xxx.xxx
Server:  ns1.bt.net
Address:  194.72.6.52

Name:mail.domain.com
Address:  xxx.xxx.xxx.xxx
Aliases:  imap.domain.com
>
---

Let me know if you need anything else...
Cheers
Simon

-Original Message-----
From: Montgomery, John [mailto:[EMAIL PROTECTED]] 
Sent: 25 October 2001 15:13
To: MS-Exchange Admin Issues
Subject: RE: Relay


How do you look to see if reverse DNS lookup is setup?  I realize that this
would be on their side, but I would like to know for myself.  I have been
looking but can not seem to find it. Thanks, John

-Original Message-
From: Simon Taylor [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 25, 2001 5:41 AM
To: MS-Exchange Admin Issues
Subject: RE: Relay


I have in the past had relays refuse when they could not perform a reverse
dns lookup on the address I was coming from - I would check their end if you
can email to other domains just fine.. Cheers Simon

-Original Message-----
From: Montgomery, John [mailto:[EMAIL PROTECTED]] 
Sent: 24 October 2001 23:19
To: MS-Exchange Admin Issues
Subject: RE: Relay


I did this and using SAlive made an SMTP connection to the IP address.  It
connected just fine.  What seems strange is that it is coming from our IMS
saying MSEXCH:IMS:HoneyBaked:Site:Server 3550 (000B09AA) 550 5.7.1 Unable to
relay for [EMAIL PROTECTED]  To test the GroupShield scenario I stopped
GroupShield and tried it again.  It still failed so I am assuming that this
is not the problem.

-Original Message-
From: Benjamin Zachary [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 24, 2001 4:52 PM
To: MS-Exchange Admin Issues
Subject: RE: Relay


You may want to nslookup on the MX record for DNS and make sure its pointing
to the correct location. NSLOOKUP -Q=MX DOMAIN.COM

-Original Message-----
From: Montgomery, John [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, October 24, 2001 3:30 PM
To: MS-Exchange Admin Issues
Subject: Relay


We are having a strange problem.  We send to a particular domain and get an
NDR back from our server saying that relaying is prohibited.  This same
domain can send to us and we can send to other domains just fine. We were
able to send to them before.  Has anyone else seen anything like this?  We
have recently upgraded GroupShield to 4.5.  I called their tech support to
see if this was anything that they may know about, but they said that it is
not.  I have tried searching Microsoft but could not find anything. Exchange
5.5 SP4

Thanks,

John Montgomery
Information Technology
LAN Administrator
HoneyBaked Ham

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm



List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm




RE: Relay

2001-10-25 Thread Montgomery, John

Another interesting thing.  If I do an NSLookup (set type=mx) on their email
domain it returns an IP address for the mail exchanger.  If I do this on any
other domain it gives me an FQDN and then gives the IP of the FQDN later on
in the information returned.  I tried to do a reverse lookup on their IP and
it does not resolve.  They can send to us and I can send to them from my
Hotmail account.  Would this be any reason that I can not send to them from
my Exchange server?  As I am sure you can guess I am pretty new to DNS so
please don't laugh too hard at they way I tried to describe the NSLookup. :
)
 

-Original Message-
From: Simon Taylor [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 25, 2001 11:20 AM
To: MS-Exchange Admin Issues
Subject: RE: Relay


Hey John
To my knowledge you cannot do this in Exchange 5.5, no idea about 2000. I
use Sendmail Switch for my production Mail relays and they can be configured
to do so. You may want to telnet to the smtp server in question and give it
an HELO and it will give you the relay version you are dealing with.
Cheers
Simon


-Original Message-
From: Montgomery, John [mailto:[EMAIL PROTECTED]] 
Sent: 25 October 2001 16:10
To: MS-Exchange Admin Issues
Subject: RE: Relay


That wasn't what I was asking, but that does answer another question I had
so thank you. : ) How can you tell if the IMS on Exchange is setup to
perform reverse DNS lookups on inbound email, or does it just automatically
do that? Thanks, John

-Original Message-
From: Simon Taylor [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 25, 2001 10:47 AM
To: MS-Exchange Admin Issues
Subject: RE: Relay


Do this
Run nslookup first on your exchange machine (or whatever you call your mail
system.) Then run nslookup again on the ip address it give you for that
system and if it resolves then you are indeed setup for reverse lookups. You
may want to run nslookup off an external dns server as internally it may
work, but not external.


H:\>nslookup
Default Server:  ns5.domain.com
Address:  192.168.1.32

> server ns1.bt.net
Default Server:  ns1.bt.net
Address:  194.72.6.52

> mail.domain.com
Server:  ns1.bt.net
Address:  194.72.6.52

Name:mail.domain.com
Address:  xxx.xxx.xxx.xxx
Aliases:  imap.domain.com

> xxx.xxx.xxx.xxx
Server:  ns1.bt.net
Address:  194.72.6.52

Name:mail.domain.com
Address:  xxx.xxx.xxx.xxx
Aliases:  imap.domain.com
>
---

Let me know if you need anything else...
Cheers
Simon

-Original Message-----
From: Montgomery, John [mailto:[EMAIL PROTECTED]] 
Sent: 25 October 2001 15:13
To: MS-Exchange Admin Issues
Subject: RE: Relay


How do you look to see if reverse DNS lookup is setup?  I realize that this
would be on their side, but I would like to know for myself.  I have been
looking but can not seem to find it. Thanks, John

-Original Message-
From: Simon Taylor [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 25, 2001 5:41 AM
To: MS-Exchange Admin Issues
Subject: RE: Relay


I have in the past had relays refuse when they could not perform a reverse
dns lookup on the address I was coming from - I would check their end if you
can email to other domains just fine.. Cheers Simon

-Original Message-----
From: Montgomery, John [mailto:[EMAIL PROTECTED]] 
Sent: 24 October 2001 23:19
To: MS-Exchange Admin Issues
Subject: RE: Relay


I did this and using SAlive made an SMTP connection to the IP address.  It
connected just fine.  What seems strange is that it is coming from our IMS
saying MSEXCH:IMS:HoneyBaked:Site:Server 3550 (000B09AA) 550 5.7.1 Unable to
relay for [EMAIL PROTECTED]  To test the GroupShield scenario I stopped
GroupShield and tried it again.  It still failed so I am assuming that this
is not the problem.

-Original Message-
From: Benjamin Zachary [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 24, 2001 4:52 PM
To: MS-Exchange Admin Issues
Subject: RE: Relay


You may want to nslookup on the MX record for DNS and make sure its pointing
to the correct location. NSLOOKUP -Q=MX DOMAIN.COM

-Original Message-----
From: Montgomery, John [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, October 24, 2001 3:30 PM
To: MS-Exchange Admin Issues
Subject: Relay


We are having a strange problem.  We send to a particular domain and get an
NDR back from our server saying that relaying is prohibited.  This same
domain can send to us and we can send to other domains just fine. We were
able to send to them before.  Has anyone else seen anything like this?  We
have recently upgraded GroupShield to 4.5.  I called their tech support to
see if this was anything that they may know about, but they said that it is
not.  I have tried searching Microsoft but could not find anything. Exchange
5.5 SP4

Thanks,

John Montgomery
Information Technology
LAN Administrator
HoneyBaked Ham

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm



List Charter and FAQ at:
http:/