[prev in list] [next in list] [prev in thread] [next in thread]
List: ngw
Subject: Re: [ngw] Perplexing GWIA issue
From: "Ralph Lock" <ralph () ipa ! co ! uk>
Date: 2009-07-31 10:03:02
Message-ID: 4A72CF65.7C07.009D.3 () ipa ! co ! uk
[Download RAW message or body]
We had the same problem a while back (not for the same reasons, though).
The fix we implemented is in TID 10010997, which says in essence:
Create a file in the DOMAIN\WPGATE\GWIA directory called ROUTE.CFG. The file should \
look like this:
DomainName [internal IP Address of GWIA]
(you need a hard return on the last line)
This way GWIA will know where to route messages bound for your own domain and not \
send them out to the public IP address.
Good luck
R!
> > > "Jeffrey Carroll" <JCARROL1@cablevision.com> 30/07/2009 16:09 >>>
We have internal GWIA's (7.0.3) for application relaying that had no ACL's on them. \
Anyone could bounce a message off of them. Well a recent MAPI virus put an end to \
that and we had to create ACL's like in TID 3959034. Since creating the ACL's, \
notifications of undeliverables don't get sent back to our user's. I see this in the \
log.
23:20:39 04A DMN: MSG 3012 Accepted connection: [10.128.36.152] \
(c2gwiaoutvs.cablevision.com) - ******* Our outbound GWIA ****** 23:20:39 04A DMN: \
MSG 3012 Receiving file: \
CSCPGWIARLY2/GWIARLY:\DOMAIN\WPGATE\GWIARLY2\receive\749d07a4.461 23:20:39 04A DMN: \
MSG 3012 SMTP session ended: [10.128.36.152] (c2gwiaoutvs.cablevision.com) 23:20:40 \
032 MSG 3015 Processing inbound message: \
CSCPGWIARLY2/GWIARLY:\DOMAIN\WPGATE\GWIARLY2\receive\749D07A4.461 23:20:40 032 MSG \
3015 Recipient: JCARROL1@cablevision.com
Note there is no "Sender: " line and the processing just dies off. No other \
references to this message can be found in the logs. Was looking at the structure of \
an NDR and I noticed the only difference is that the "Return-path: <>" is blank. I \
think this is throwing off the ACL. I tried putting "<>" as an excepted sender but no \
change.
Any ideas?
Thanks,
Jeff
The information transmitted in this email and any of its attachments is intended only \
for the person or entity to which it is addressed and may contain Cablevision \
proprietary information, which is privileged, confidential, or subject to copyright \
belonging to Cablevision. 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 and may be unlawful. If you received \
this in error, please contact the sender immediately and delete and destroy the \
communication and all of the attachments you have received and all copies thereof.
IPA, 44 Belgrave Square, London, SW1X 8QS
http://www.ipa.co.uk
http://twitter.com/IPA_Updates
The Institute of Practitioners in Advertising is a Company
Limited by Guarantee. Registered in England No. 221167
[Attachment #3 (text/html)]
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=utf-8">
<META content="MSHTML 6.00.6000.16825" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>We had the same problem a while back (not for the same reasons, though). \
</DIV> <DIV> </DIV>
<DIV>The fix we implemented is in TID 10010997, which says in essence:<BR><BR>Create \
a file in the DOMAIN\WPGATE\GWIA directory called ROUTE.CFG. The file should \
look like this:<BR><BR>DomainName [internal IP Address of GWIA]<BR><BR>(you need a \
hard return on the last line)<BR><BR>This way GWIA will know where to route messages \
bound for your own domain and not send them out to the public IP address.<BR><BR>Good \
luck<BR>R!<BR><BR><BR>>>> "Jeffrey Carroll" <JCARROL1@cablevision.com> \
30/07/2009 16:09 >>><BR></DIV> <DIV>We have internal GWIA's (7.0.3) for \
application relaying that had no ACL's on them. Anyone could bounce a message \
off of them. Well a recent MAPI virus put an end to that and we had to create ACL's \
like in TID <STRONG>3959034.</STRONG> Since creating the ACL's, notifications of \
undeliverables don't get sent back to our user's. I see this in the log.</DIV> \
<DIV> </DIV> <DIV>
<DIV>23:20:39 04A DMN: MSG 3012 Accepted connection: [10.128.36.152] \
(c2gwiaoutvs.cablevision.com) - ******* Our outbound GWIA \
******<BR>23:20:39 04A DMN: MSG 3012 Receiving file: \
CSCPGWIARLY2/GWIARLY:\DOMAIN\WPGATE\GWIARLY2\receive\749d07a4.461<BR>23:20:39 04A \
DMN: MSG 3012 SMTP session ended: [10.128.36.152] \
(c2gwiaoutvs.cablevision.com)<BR>23:20:40 032 MSG 3015 Processing inbound message: \
CSCPGWIARLY2/GWIARLY:\DOMAIN\WPGATE\GWIARLY2\receive\749D07A4.461<BR>23:20:40 032 MSG \
3015 Recipient: <A href="mailto:JCARROL1@cablevision.com">JCARROL1@cablevision.com</A></DIV>
<DIV><BR> </DIV>
<DIV>Note there is no "Sender: " line and the processing just dies off. No other \
references to this message can be found in the logs. Was looking at the structure of \
an NDR and I noticed the only difference is that the "Return-path: <>" is \
blank. I think this is throwing off the ACL. I tried putting "<>" as an \
excepted sender but no change.</DIV> <DIV> </DIV>
<DIV>Any ideas?</DIV>
<DIV> </DIV>
<DIV>Thanks,</DIV>
<DIV> </DIV>
<DIV>Jeff</DIV></DIV><BR>
<HR>
<B>The information transmitted in this email and any of its attachments is intended \
only for the person or entity to which it is addressed and may contain Cablevision \
proprietary information, which is privileged, confidential, or subject to copyright \
belonging to Cablevision. 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 and may be unlawful. If you received \
this in error, please contact the sender immediately and delete and destroy the \
communication and all of the attachments you have received and all copies thereof.<B> \
<HR> </B></B></BODY></HTML>
<pre>IPA, 44 Belgrave Square, London, SW1X 8QS
http://www.ipa.co.uk
http://twitter.com/IPA_Updates
The Institute of Practitioners in Advertising is a Company
Limited by Guarantee. Registered in England No. 221167
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic