RE: Troublesome IMS

2002-01-17 Thread Earl, Daniel

No, we don't have a Cisco Pix.
Could it be a setting on the Cisco 2600 router?
This is the only Cisco kit we have.

Thanks,

Dan.

-Original Message-
From: Andy David [mailto:[EMAIL PROTECTED]]
Sent: 16 January 2002 12:54
Subject: RE: Troublesome IMS


No SMTP fixup for you!
Check the archives, tons of info there on this issue :)


-Original Message-
From: Atkinson, Daniel [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 16, 2002 7:29 AM
To: Exchange Discussions
Subject: RE: Troublesome IMS


is this essential? i just checked our pix and smtp fixup is enabled - i'm
not aware of any problems though...


 -Original Message-
 From: Monteleone-Haught Matt - Millville
 [mailto:[EMAIL PROTECTED]]
 Sent: 16 January 2002 12:23
 To: Exchange Discussions
 Subject: RE: Troublesome IMS
 
 
 Cisco PIX?  No SMTP fixup
 
 -Original Message-
 From: Earl, Daniel [mailto:[EMAIL PROTECTED]] 
 Sent: Wednesday, January 16, 2002 6:21 AM
 To: Exchange Discussions
 Subject: Troublesome IMS
 
 
 
  Hello all,
  
  Our Exchange server is suffering from a problem where a 
 mail gets 
  delivered, but the mail sticks in the IMS's 'Outbound mail 
 awaiting 
  delivery' queue with '(host unreachable)' next to it. This 
 results in 
  the IMS retrying to redeliver the mail at the set 
 intervals and the 
  somewhat annoyed recipient receiving multiple copies of 
 the mail until 
  it expires. This only happens occasionally - most mail 
 goes out fine. 
  I have noticed that is does happen to one email that gets sent 
  regularly from one of our users to an external mailbox.
  I have tried using nslookup from the server and can telnet 
 in to port 25
  of the other servers without a problem.
  
  Our box is set up as follows:
  
  NT4, Sp6a, PIII, 3 processors, 1gb mem.
  Exchange 5.5 sp4 (configured as per Q181420 - 'How to Configure 
  Exchange or other SMTP with Proxy Server') Network Associates 
  GroupShield (Antivirus Server Extension: 4.5.572.171  
 Server Admin 
  Extension: 4.5.572.128) Network Associates Netshield 4.5.0 
 (with the 
  recommended Exchange directories excluded from scanning).
  
  I also had the Network Associates Message Body Scanning 
 tool installed 
  but thought this might have been contributing to the 
 problem so I 
  removed it a few months ago, but the problem sill continues.
  
  Any ideas?
  
  Many thanks,
  
  Daniel.
  
  
 This e-mail may contain proprietary and confidential 
 information, and is intended for the named recipient(s) only. 
 If you are not one of the named recipients, then disclosure, 
 distribution, copying or printing of this e-mail is strictly 
 prohibited and it must be deleted. 
 Additionally you should notify the sender of the 
 distribution error. 
 Heal's will not accept any liability or responsibility for the 
 completeness or accuracy of its contents and attachments.
 
 
 _
 List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
 Archives:   http://www.swynk.com/sitesearch/search.asp
 To unsubscribe: mailto:[EMAIL PROTECTED]
 Exchange List admin:[EMAIL PROTECTED]
 
 
 _
 List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
 Archives:   http://www.swynk.com/sitesearch/search.asp
 To unsubscribe: mailto:[EMAIL PROTECTED]
 Exchange List admin:[EMAIL PROTECTED]
 

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]


--
The information contained in this email message is privileged and
confidential information intended only for the use of the individual or
entity to whom it is addressed.  If the reader of this message is not the
intended recipient, you are hereby notified that any dissemination,
distribution or copy of this message is strictly prohibited.  If you have
received this email in error, please immediately notify Veronis Suhler
Stevenson by telephone (212)935-4990, fax (212)381-8168, or email
([EMAIL PROTECTED]) and delete the message.  Thank you.


==


This e-mail may contain proprietary and confidential information, and is
intended for the named recipient(s) only. 
If you are not one of the named recipients, then disclosure, 
distribution, copying or printing of this e-mail is strictly 
prohibited and it must be deleted. 
Additionally you should notify the sender of the distribution error. 
Heal's will not accept any liability or responsibility for the 
completeness or accuracy of its contents and attachments

RE: Troublesome IMS

2002-01-16 Thread Monteleone-Haught Matt - Millville

Cisco PIX?  No SMTP fixup

-Original Message-
From: Earl, Daniel [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, January 16, 2002 6:21 AM
To: Exchange Discussions
Subject: Troublesome IMS



 Hello all,
 
 Our Exchange server is suffering from a problem where a mail gets 
 delivered, but the mail sticks in the IMS's 'Outbound mail 
awaiting 
 delivery' queue with '(host unreachable)' next to it. This 
results in 
 the IMS retrying to redeliver the mail at the set 
intervals and the 
 somewhat annoyed recipient receiving multiple copies of 
the mail until 
 it expires. This only happens occasionally - most mail 
goes out fine. 
 I have noticed that is does happen to one email that gets sent 
 regularly from one of our users to an external mailbox.
 I have tried using nslookup from the server and can telnet 
in to port 25
 of the other servers without a problem.
 
 Our box is set up as follows:
 
 NT4, Sp6a, PIII, 3 processors, 1gb mem.
 Exchange 5.5 sp4 (configured as per Q181420 - 'How to Configure 
 Exchange or other SMTP with Proxy Server') Network Associates 
 GroupShield (Antivirus Server Extension: 4.5.572.171  
Server Admin 
 Extension: 4.5.572.128) Network Associates Netshield 4.5.0 
(with the 
 recommended Exchange directories excluded from scanning).
 
 I also had the Network Associates Message Body Scanning 
tool installed 
 but thought this might have been contributing to the problem so I 
 removed it a few months ago, but the problem sill continues.
 
 Any ideas?
 
 Many thanks,
 
 Daniel.
 
 
This e-mail may contain proprietary and confidential 
information, and is intended for the named recipient(s) only. 
If you are not one of the named recipients, then disclosure, 
distribution, copying or printing of this e-mail is strictly 
prohibited and it must be deleted. 
Additionally you should notify the sender of the distribution error. 
Heal's will not accept any liability or responsibility for the 
completeness or accuracy of its contents and attachments.


_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]


_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]



RE: Troublesome IMS

2002-01-16 Thread Atkinson, Daniel

is this essential? i just checked our pix and smtp fixup is enabled - i'm
not aware of any problems though...


 -Original Message-
 From: Monteleone-Haught Matt - Millville
 [mailto:[EMAIL PROTECTED]]
 Sent: 16 January 2002 12:23
 To: Exchange Discussions
 Subject: RE: Troublesome IMS
 
 
 Cisco PIX?  No SMTP fixup
 
 -Original Message-
 From: Earl, Daniel [mailto:[EMAIL PROTECTED]] 
 Sent: Wednesday, January 16, 2002 6:21 AM
 To: Exchange Discussions
 Subject: Troublesome IMS
 
 
 
  Hello all,
  
  Our Exchange server is suffering from a problem where a 
 mail gets 
  delivered, but the mail sticks in the IMS's 'Outbound mail 
 awaiting 
  delivery' queue with '(host unreachable)' next to it. This 
 results in 
  the IMS retrying to redeliver the mail at the set 
 intervals and the 
  somewhat annoyed recipient receiving multiple copies of 
 the mail until 
  it expires. This only happens occasionally - most mail 
 goes out fine. 
  I have noticed that is does happen to one email that gets sent 
  regularly from one of our users to an external mailbox.
  I have tried using nslookup from the server and can telnet 
 in to port 25
  of the other servers without a problem.
  
  Our box is set up as follows:
  
  NT4, Sp6a, PIII, 3 processors, 1gb mem.
  Exchange 5.5 sp4 (configured as per Q181420 - 'How to Configure 
  Exchange or other SMTP with Proxy Server') Network Associates 
  GroupShield (Antivirus Server Extension: 4.5.572.171  
 Server Admin 
  Extension: 4.5.572.128) Network Associates Netshield 4.5.0 
 (with the 
  recommended Exchange directories excluded from scanning).
  
  I also had the Network Associates Message Body Scanning 
 tool installed 
  but thought this might have been contributing to the 
 problem so I 
  removed it a few months ago, but the problem sill continues.
  
  Any ideas?
  
  Many thanks,
  
  Daniel.
  
  
 This e-mail may contain proprietary and confidential 
 information, and is intended for the named recipient(s) only. 
 If you are not one of the named recipients, then disclosure, 
 distribution, copying or printing of this e-mail is strictly 
 prohibited and it must be deleted. 
 Additionally you should notify the sender of the 
 distribution error. 
 Heal's will not accept any liability or responsibility for the 
 completeness or accuracy of its contents and attachments.
 
 
 _
 List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
 Archives:   http://www.swynk.com/sitesearch/search.asp
 To unsubscribe: mailto:[EMAIL PROTECTED]
 Exchange List admin:[EMAIL PROTECTED]
 
 
 _
 List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
 Archives:   http://www.swynk.com/sitesearch/search.asp
 To unsubscribe: mailto:[EMAIL PROTECTED]
 Exchange List admin:[EMAIL PROTECTED]
 

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]



RE: Troublesome IMS

2002-01-16 Thread Monteleone-Haught Matt - Millville

I'll have to defer to those that are running PIX.[1]  A quick search through
the archives will more then likely reveal that no fixup protocol smtp 25
is highly recommended.  Additionally, a quick web search on no fixup
protocol smtp 25 will reveal that use of the command is mixed.  Some claim
it is not needed others claim it is.  
Here is a quote from a poster on securepoint.com mailing list, This has
been a problem forever.  It has been fixed in some releases of the PIX
firmware, but it has been broken in more releases than not.  Just give up
and turn 
off the smtp protocol fixup.
 no fixup protocol smtp 25
Better yet, I could suggest you do what we have done.  Dump the Cisco PIX

YMMV,
--
Matthew Monteleone-Haught
Information Technology
E-mail: [EMAIL PROTECTED]
Wheaton USA Inc
A member of the ALCAN group of companies 
MCSE
[1]perfectly happy with my CheckPoint FW! 

-Original Message-
From: Atkinson, Daniel [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, January 16, 2002 7:29 AM
To: Exchange Discussions
Subject: RE: Troublesome IMS


is this essential? i just checked our pix and smtp fixup is 
enabled - i'm not aware of any problems though...


 -Original Message-
 From: Monteleone-Haught Matt - Millville 
 [mailto:[EMAIL PROTECTED]]
 Sent: 16 January 2002 12:23
 To: Exchange Discussions
 Subject: RE: Troublesome IMS
 
 
 Cisco PIX?  No SMTP fixup
 
 -Original Message-
 From: Earl, Daniel [mailto:[EMAIL PROTECTED]]
 Sent: Wednesday, January 16, 2002 6:21 AM
 To: Exchange Discussions
 Subject: Troublesome IMS
 
 
 
  Hello all,
  
  Our Exchange server is suffering from a problem where a
 mail gets
  delivered, but the mail sticks in the IMS's 'Outbound mail
 awaiting
  delivery' queue with '(host unreachable)' next to it. This
 results in
  the IMS retrying to redeliver the mail at the set
 intervals and the
  somewhat annoyed recipient receiving multiple copies of
 the mail until
  it expires. This only happens occasionally - most mail
 goes out fine.
  I have noticed that is does happen to one email that gets sent
  regularly from one of our users to an external mailbox.
  I have tried using nslookup from the server and can telnet 
 in to port 25
  of the other servers without a problem.
  
  Our box is set up as follows:
  
  NT4, Sp6a, PIII, 3 processors, 1gb mem.
  Exchange 5.5 sp4 (configured as per Q181420 - 'How to 
Configure
  Exchange or other SMTP with Proxy Server') Network Associates 
  GroupShield (Antivirus Server Extension: 4.5.572.171  
 Server Admin
  Extension: 4.5.572.128) Network Associates Netshield 4.5.0
 (with the
  recommended Exchange directories excluded from scanning).
  
  I also had the Network Associates Message Body Scanning
 tool installed
  but thought this might have been contributing to the
 problem so I
  removed it a few months ago, but the problem sill continues.
  
  Any ideas?
  
  Many thanks,
  
  Daniel.
  
  
 This e-mail may contain proprietary and confidential
 information, and is intended for the named recipient(s) only. 
 If you are not one of the named recipients, then disclosure, 
 distribution, copying or printing of this e-mail is strictly 
 prohibited and it must be deleted. 
 Additionally you should notify the sender of the 
 distribution error.
 Heal's will not accept any liability or responsibility for the
 completeness or accuracy of its contents and attachments.
 
 
 
_
 List posting FAQ:   
http://www.swinc.com/resource/exch_faq.htm
 Archives:
   http://www.swynk.com/sitesearch/search.asp
 To unsubscribe: mailto:[EMAIL PROTECTED]
 Exchange List admin:[EMAIL PROTECTED]
 
 
 _
 List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
 Archives:   http://www.swynk.com/sitesearch/search.asp
 To unsubscribe: mailto:[EMAIL PROTECTED]
 Exchange List admin:[EMAIL PROTECTED]
 

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]


_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]