Robert,
I did that too, but we also had the web
server to deal with and some servers within our building that we couldn’t
connect to without going through ‘fake’ listings in our own DNS.
The long and short is that running my own DNS is an operational requirement
unless we change inter
It looks like it should have passed, http://www.dnsstuff.com/tools/lookup.ch?name=ute-sei.org&type=MX .
I would turn the declude log level to High and send
another test, this will give you more information on how it is
checking.
Thanks,Chris Patterson, CCNANetwork
Engineer/Support Manager
This part of the problem seems to be
fixed. I added an MX record to my internal DNS and I’m no longer getting
the error. I was confused because I checked the DNS lookups and everything
seemed fine but I’d forgotten that it first looks at our internal
version.
Thanks for the reply.
Susan Duncan wrote:
That still
doesn’t explain why
someone who is whitelisted still has some of their email caught.
That's not the issue, they aren't actually both happening at the same
time. It's being double scanned, and it is only being whitelisted when
it is being sent, but n
It seems to be happening when staff are
not in the office when they send the mail. When they are out of office
they connect to email either through webmail or use outlook same as always but
use an outside ISP. In some cases, they have to use some mail proxy
server as some of the ISPs are
Just a little follow up about this.
The first E-mail appears to be sent from your server in some sort of
automated fashion (denoted by the GSC extension on the Q file). These
are either postmaster messages, or some message created by calling
imail1.exe directly (probably some bulk-mail script
This isn't the same issue. See my last note.
Matt
Susan Duncan wrote:
It seems to
be happening when staff are
not in the office when they send the mail. When they are out of office
they connect to email either through webmail or use outlook same as
always but
use an outside
[EMAIL PROTECTED]
sent a message to a bunch of people including [EMAIL PROTECTED] using his dial-up att
global account. I didn’t know there was a limit to the number of
addresses in a send list. If our users aren’t using our
distribution lists, but instead their own address lists, and sen
I reported the false positive (being a good netizin) to MXRATE
(Alligate) and their automated reply included the following:
"Generally, the most common reason an IP address is falsely listed in the MXRate database is when one of your users forwards all their mail to an account on a server pr
You have to trust me that in the headers and logs that you provided,
the E-mail was whitelisted when sent, and the only E-mail that was
double scanned was the one that was forwarded from the prserv.net
server back to [EMAIL PROTECTED]. It might have been sent directly
to [EMAIL PROTECTED], but
Bad DNS server will do it every time. Thanks for your
insight.
Evans
-Original Message-
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Darrell
([EMAIL PROTECTED])
Sent: Sunday, June 05, 2005 10:47
PM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.
11 matches
Mail list logo
