Re: [Declude.JunkMail] OT: DNS / Web help

2005-06-06 Thread Dave Doherty
That's why groups like this are so valuable. Another set of eyes on the problem can bring a fresh view to it, and often a quick solution. I've certainly been the recipient of a lot of help here, and I'm glad to have helped.   -d - Original Message - From: Cris Porter To

Re: [Declude.JunkMail] X-RBL-Warning // Whitelisted but not

2005-06-06 Thread Robert
we just put our mail server ip in the hosts file.   just a mention.   robert - Original Message - From: Susan Duncan To: Declude.JunkMail@declude.com Sent: Monday, June 06, 2005 5:12 PM Subject: RE: [Declude.JunkMail] X-RBL-Warning // Whitelisted but not

RE: [Declude.JunkMail] X-RBL-Warning // Whitelisted but not

2005-06-06 Thread Susan Duncan
I fixed the DNS already.  As I said it was missing the MX record in my internal dns.  I need to run a separate DNS as the email server is behind the firewall and with the current configuration the only way for anyone internal to see the web or email server is to run my own mini dns.   06

RE: [Declude.JunkMail] OT: DNS / Web help

2005-06-06 Thread Cris Porter
Thanks everybody - I had been staring at it so long, I couldn't see the forest for the trees. (or the 1 for the 2)   Amazing how the CORRECT ip address in DNS helps.   Sorry for the bother.   Thanks so much! Cris -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROT

RE: [Declude.JunkMail] whitelisted but not

2005-06-06 Thread Dan Horne
It likely means that the sender also uses Declude and scans outgoing email. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Susan DuncanSent: Monday, June 06, 2005 3:05 PMTo: Declude.JunkMail@declude.comSubject: RE: [Declude.JunkMail] whitelisted but not

Re: [Declude.JunkMail] X-RBL-Warning // Whitelisted but not

2005-06-06 Thread Matt
Susan, Things are being double scanned and that should be looked into, but your DNS might well be the culprit. The server that Declude is using for lookups must have all of the records for your domain.  This means not just the MX records, but also the A records that the MX records correspond

RE: [Declude.JunkMail] X-RBL-Warning // Whitelisted but not

2005-06-06 Thread Susan Duncan
Matt,   Because of firewall settings, I’m running DNS on the IMAIL server pointing to internal IP addresses while a third party does DNS for the rest of the world to see.  The only thing missing on the internal version was the MX information which I’ve added.  It should have found it bas

RE: [Declude.JunkMail] whitelisted but not

2005-06-06 Thread Susan Duncan
Yes, I notice that afterwards.  I’m not sure why there are two spoolname lines or two test lines.  Looking up info in the logfile got very confusing.    Susan Duncan Web/Communications Officer / Agent des Communications/web Union of Taxation Employees / Syndicat des employées de l'Im

RE: [Declude.JunkMail] whitelisted but not

2005-06-06 Thread Dan Horne
um, there are 2 X-Declude-Tests lines.  One of them is proably added by the sender (likely the whitelisted line).  Note that there are also 2 X-Declude-Spoolname lines with different spoolnames. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Susan DuncanSent: Mo

Re: [Declude.JunkMail] X-RBL-Warning??

2005-06-06 Thread Matt
The MAILFROM test will only fail if Declude fails to find an A or MX record for the domain in question.  Since it exists, I would assume that it is the result of something involving DNS.  You should check your DNS and make sure that your server is resolving properly, and that it is the same DNS

[Declude.JunkMail] whitelisted but not

2005-06-06 Thread Susan Duncan
Here are the headers from a message that was forwarded to my spam email account.  It shows that it’s whitelisted but it was still caught.   X-Declude-Sender: [EMAIL PROTECTED] [127.0.0.1] X-Declude-Spoolname: D5E8705DC5A1F.GSC X-Declude-Note: Scanned by Declude 2.0.6 (http://www.declu

RE: [Declude.JunkMail] X-RBL-Warning??

2005-06-06 Thread Susan Duncan
  I’m resending this as I didn’t get any replies.  Anyone?? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Susan Duncan Sent: May 31, 2005 9:35 AM To: Declude.JunkMail@declude.com Subject: [Declude.JunkMail] X-RBL-Warning??   Our own domain

RE: [Declude.JunkMail] OT: DNS / Web help

2005-06-06 Thread Patrick Childers
When I try to ping sales.jvcdiscusa.com it returns an IP of 65.144.173.133. (Instead of 65.244.173.133) You might want to check your DNS.   HTH, Patrick From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cris PorterSent: Monday, June 06, 2005 10:35 AMTo: Declude.J

Re: [Declude.JunkMail] OT: DNS / Web help

2005-06-06 Thread Dave Doherty
Hi Cris-   DNS lookup returns 144 for the second octet, not 244.   -Dave Doherty  Skywaves, Inc.  301-652-8822 x209     - Original Message - From: Cris Porter To: Declude.JunkMail@declude.com Sent: Monday, June 06, 2005 10:35 AM Subject: [Declude.JunkMail] OT: DN

Re: [Declude.JunkMail] OT: DNS / Web help

2005-06-06 Thread NIck Hayer
Hi Chris   The only thing different about this site is that it uses Windows authentication to force a login.   Any ideas? Does the site work with anonymous access enabled? Host header for domain correct? -Nick

RE: [Declude.JunkMail] OT: DNS / Web help

2005-06-06 Thread Andy Schmidt
Well, if the DNS is pointing to the right IP and if access via the IP works - then the problem is with web server configuration and its association of FQDN to the IP.   I assume IIS?  Is the IP address a "shared" IP for several web sites? If yes, did you remember to add the "host header" nam

[Declude.JunkMail] OT: DNS / Web help

2005-06-06 Thread Cris Porter
Question for the Declude collective, this is driving me crazy.   I've got a website -  http://sales.jvcdiscusa.com running on 65.244.173.133   I've got an A record in my DNS for the website but... I can't open the site using the name but I can using the IP address. If I ping the name, I