, September 06, 2011 5:42 PM
To: Declude.JunkMail@declude.com
Subject: RE: [Declude.JunkMail] AOL Header Test
Rick, you have a space between the colon and the YES and, if I remember
correctly, AOL does not put a space there.
#Email from AOL which they believe is spam
HEADERS 0 CONTAINS X
Hello,
I have a combo test for scrutinizing AOL and the large webmail providers, I am
trying to trigger on an AOL X header with this
HEADERS 0 CONTAINS X-SPAM-FLAG: YES
any idea why this wouldn't hit?
--
Rick
CONFIDENTIALITY NOTICE
This e-mail message and any
.
From: Rick Davidson [mailto:rdavid...@nat.com]
Sent: Tuesday, September 06, 2011 3:06 PM
To: Declude.JunkMail@declude.com
Subject: [Declude.JunkMail] AOL Header Test
Hello,
I have a combo test for scrutinizing AOL and the large webmail
providers, I am trying to trigger on an AOL X header
I see that there is quite a bit of spam coming though .mx.aol.com servers
but I also noticed that they tag the messages as spam in the headers
X-Spam-Flag: YES
As a suggestion if you are receiving messages from .mx.aol.com or @aim.com
addresses that are spam use the following line in a
HEADERS 20 PCRE (X-Spam-Flag:
YES)
A problem with doing this as a single (non-combo) filter is that you
are using a trusting a common x-header regardless of source and/or
documentation. This allows for pretty easy poisoning of a weighted
Looks like AOL has blocked us. We're getting aduse reports from AOL SCOMP, but
the attached email example has no information in it. This is all it contains.
=20
=3D=20
=
Headers are evidently blank. no info at all.
@declude.com
Subject: Re: [Declude.JunkMail] AOL Now blocking Port 25
I searched the archives but couldn't find what I was looking for.
Didn't someone post a link to a small software app that would run on the
mail server and would forward all traffic from port 587 to port 25. We
.
Thanks in advance,
Don
- Original Message -
From: Mark Smith [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Thursday, September 29, 2005 11:34 PM
Subject: RE: [Declude.JunkMail] AOL Now blocking Port 25
Setup Windows IIS SMTP service to listen on port XX (something other than
25
, September 30, 2005 6:08 PM
Subject: Re: [Declude.JunkMail] AOL Now blocking Port 25
I searched the archives but couldn't find what I was looking for.
Didn't someone post a link to a small software app that would run on the
mail server and would forward all traffic from port 587 to port 25. We
] On Behalf Of
[EMAIL PROTECTED]
Sent: Friday, September 30, 2005 3:09 PM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail] AOL Now blocking Port 25
I searched the archives but couldn't find what I was looking for.
Didn't someone post a link to a small software app that would
run
To: Declude.JunkMail@declude.com
Subject: RE: [Declude.JunkMail] AOL Now blocking Port 25
Here is one application I've used, but not recently.
http://www.analogx.com/contents/download/network/pmapper.htm
I just tested it with portmapping ftp in passive mode and it worked
perfectly.
Andrew 8
PM
To: Declude.JunkMail@declude.com
Subject: RE: [Declude.JunkMail] AOL Now blocking Port 25
google rinetd -- we set it up in about 5 minutes,
and it has worked flawlessly (meaning, I didn't have
to mess with it) since.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL
Has anyone else been told AOL is now enfosing this policy and how do we get
around it.
a.. 554 IPT:OA
http://postmaster.info.aol.com/errors/554iptoa.html
EXPLANATION:
The message you received is generated from AOL when sending mail through a
third party program and connecting through the
] On Behalf Of Frederick Samarelli
Sent: Thursday, September 29, 2005 2:20 PM
To: Declude.JunkMail@declude.com
Subject: [Declude.JunkMail] AOL Now blocking Port 25
Has anyone else been told AOL is now enfosing this policy and how do we get
around it.
a.. 554 IPT:OA
http://postmaster.info.aol.com
, 2005 11:39 AM
To: Declude.JunkMail@declude.com
Subject: RE: [Declude.JunkMail] AOL Now blocking Port 25
As a web hosting company, we put an SMTP server listening on a
different TCP
port.
We instruct users to modify their SMTP settings in their mail
client to use
this port.
The server
, September 29, 2005 3:48 PM
Subject: RE: [Declude.JunkMail] AOL Now blocking Port 25
If you are on imail 8.2x you can setup the alternate port. Search for the
thread on the how to. No additional software is needed to do port
forwarding.
Kevin Bilbee
-Original Message-
From: [EMAIL
PIX does not easily do port forwarding.
Kevin
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Dave Doherty
Sent: Thursday, September 29, 2005 1:23 PM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail] AOL Now blocking Port 25
.
- Original Message -
From: Kevin Bilbee [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Thursday, September 29, 2005 5:07 PM
Subject: RE: [Declude.JunkMail] AOL Now blocking Port 25
PIX does not easily do port forwarding.
Kevin
-Original Message-
From: [EMAIL PROTECTED
: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Darin Cox
Sent: Thursday, September 29, 2005 2:28 PM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail] AOL Now blocking Port 25
You mean like this?
static (inside,outside) tcp 10.0.0.10 587 10.1.1.10 smtp netmask
, September 29, 2005 5:35 PM
Subject: RE: [Declude.JunkMail] AOL Now blocking Port 25
What are the issues of doing this. On older versions of PIX this would cause
issues with the standard translation to the inside address. So we never used
it, and received a complicated workarround from cisco
]
[mailto:[EMAIL PROTECTED] Behalf Of Darin Cox
Sent: Thursday, September 29, 2005 2:54 PM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail] AOL Now blocking Port 25
I don't know about earlier versions, but I do know it works fine in 6.x
versions. I've used it for years
Message -
From: Kevin Bilbee [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Thursday, September 29, 2005 6:24 PM
Subject: RE: [Declude.JunkMail] AOL Now blocking Port 25
OK that was the issue can not do more that one maping, and we do not have
enough IP addresses to support the double
Thank you!
-d
- Original Message -
From: Darin Cox [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Thursday, September 29, 2005 5:27 PM
Subject: Re: [Declude.JunkMail] AOL Now blocking Port 25
You mean like this?
static (inside,outside) tcp 10.0.0.10 587 10.1.1.10 smtp
Subject: Re: [Declude.JunkMail] AOL Now blocking Port 25
Anybody out there know the Cisco PIX CLI syntax to do port forwarding on the
firewall?
I'm running Imail 8.15 and I'm stuck with port 25...
-Dave Doherty
Skywaves, Inc.
- Original Message -
From: Kevin Bilbee [EMAIL PROTECTED
Hello -
I am seeing these tags in AOL bounces -
X-AOL-IP: 213.226.82.229
X-AOL-SCOLL-SCORE: 0:2:169167590:15837691
X-AOL-SCOLL-URL_COUNT: 0
Does anyone know what they represent? The first I believe is the
original sender ip; since these are coming to me mainly as a result
of joejobs I'm
Hi Larry:
http://www.computerworld.com/printthis/2004/0,4814,96022,00.html
Quite opposite - the critical part is on the BOTTOM of AOL's statement -
that's what's important for Declude and for all of us:
AOL isn't completely backing out of Sender ID. It won't check Sender ID
records on mail
SpamCop blocked the ActiveServerPages list at 15seconds.com (which is not a
source of spam):
List-Unsubscribe: mailto:[EMAIL PROTECTED]
X-RBL-Warning: SPAMCOP: Blocked - see http://www.spamcop.net/bl.shtml?
The problem with SpamCop is, it's only as reliable as it's users. It would
appear that
Check this out
http://zdnet.com.com/2100-1104-5145065.html
-Dave Doherty
Skywaves, Inc.
---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED],
But what happens when it's not listed in SpamCop and some zombie sends
out spam through it?
It fixes one problem, but creates another. I currently see more spam
coming from ISP mail servers than I see false positives, but of course
that's just my setup. Having SpamCop FP on such a mail
old domain name with an IP will not
get credit, because SPF will not match.
Best Regards
Andy
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Matt
Sent: Friday, January 16, 2004 12:13 PM
To: [EMAIL PROTECTED]
Subject: Re: [Declude.JunkMail] AOL
Andy Schmidt wrote:
Also, the "zombie" will only benefit from SPF, if they take the time and are
able to figure out which domain's SPF TXT record happens to cover that
particular zombie IP. Just using any old domain name with an IP will not
get credit, because SPF will not match.
Title: Message
SpamCop
has a very serious and obvious problem, and I think it might be the result of a
bug or something because clearly this wasn't always the case. Imperfect as
they may be, SpamCop could fix this problem and greatly improve on their present
reliability.
Sorry
for
How? I'm not a SpamCop member nor am I aware of any method to alert
them to such problems. Also, IronPort took over SpamCop, and although
Julian is still involved, it's possible that someone else is calling
the shots??? Maybe IronPort broke this accidentally?
If someone wants to send me an
[mailto:[EMAIL PROTECTED] Sent: Friday, January 16, 2004 12:27
PMTo: [EMAIL PROTECTED]Subject: Re:
[Declude.JunkMail] AOL on SPAMCOPHow? I'm not a
SpamCop member nor am I aware of any method to alert them to such
problems. Also, IronPort took over SpamCop, and although Julian is still
.
Andrew
8)
-Original Message-
From: Matt [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 16, 2004 12:27 PM
To: [EMAIL PROTECTED]
Subject: Re: [Declude.JunkMail] AOL on SPAMCOP
How? I'm not a SpamCop member nor am I aware of any method to alert
them
, December 16, 2003 4:47 PM
To: [EMAIL PROTECTED]
Subject: Re: [Declude.JunkMail] AOL and Reverse DNS
This is exactly why I think we should have a some sort of global internet
council for setting standards, rather than all of us little guys having
to react, after the fact, whenever a large player makes
: RE: [Declude.JunkMail] AOL and Reverse DNS
Isn't the IETF supposed to be this body?_MAt 09:14 PM
12/16/2003, you wrote:
I would agree with this type of governing body. One that sets
standards like RDNS entries and what they mean.
pessimistic rantBut it is still up to each mail admin(s
arent - I love when that happens.Let's not all "go for the
blonde".
-Original Message-From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Hosting SupportSent: Wednesday, December 17,
2003 9:51 AMTo: [EMAIL PROTECTED]Subject: Re:
[Declude.JunkMail] AOL and Rever
] [mailto:Declude.JunkMail-
[EMAIL PROTECTED] On Behalf Of Andy Schmidt
Sent: Tuesday, December 16, 2003 10:40 PM
To: [EMAIL PROTECTED]
Subject: RE: [Declude.JunkMail] AOL and Reverse DNS
Exactly, Chuck.
AOL is implementing the very same checks that we are using in
Declude.
So
what's the whining
dnesday, December 17, 2003 12:02 PM
Subject: RE: [Declude.JunkMail] AOL and Reverse DNS
This is a common perception... and one that I share to some extent. None
the less, it's not an easy problem. The network runs on consensus - and that is
nearly impossible to build and enforce. Ultimately,
PROTECTED] On Behalf Of Todd Holt
Sent: Wednesday, December 17, 2003 12:09 PM
To: [EMAIL PROTECTED]
Subject: RE: [Declude.JunkMail] AOL and Reverse DNS
AOL is implementing the very same checks that we are using in
Declude.
This is true.
So what's the whining all about?
1. AOL publishes a policy
, December 17, 2003 9:46 AM
To: [EMAIL PROTECTED]
Subject: Re: [Declude.JunkMail] AOL and Reverse DNS
Hi Pete,
I do agree with you on all of the problems you present in regards to a
governing body that can enforce it's will. However, I think we're already
there to some degree with the fact
]
Sent: Wednesday, December 17, 2003 2:16 PM
Subject: RE: [Declude.JunkMail] AOL and Reverse DNS
Darin wrote:
I think if the IETF or some other body can gain enough power to enforce
standards that are the consensus of the majority (probably best based on
customer base) it's the best chance we have
, December 17, 2003 10:18 AM
To: [EMAIL PROTECTED]
Subject: RE: [Declude.JunkMail] AOL and Reverse DNS
Good point, they should be more accessible. That would be my biggest
complaint with most black-lists.
As far as policies - as long as their policy is simply to follow RFCs
(or
universally
Sent: Wednesday, December 17, 2003 07:12 PM
To: [EMAIL PROTECTED]
Subject: RE: [Declude.JunkMail] AOL and Reverse DNS
SPAM from AOL accounts - hm, I have to admit that I only see an
(automatically selected) cross-section of spam messages with header
(which
are routed to SPAMCOP for analysis
Title: Message
Hi,
I just noticed that
AOL has stepped up their policies another notch.
They used to say
that "AOL **MAY**" not accept email from servers without Reverse DNS.
In the last two
weeks, that changed:
http://postmaster.aol.com/guidelines/standards.html
AOL's servers will
PM
To: [EMAIL PROTECTED]
Subject: [Declude.JunkMail] AOL
and Reverse DNS
Hi,
I just noticed that AOL has stepped up their policies
another notch.
They used to say that AOL **MAY** not
accept email from servers without Reverse DNS.
In the last two weeks, that changed
to AOL...it encourages customers to move to the large
players to avoid not having mail delivered to their users.
Darin.
- Original Message -
From: Todd Holt
To: [EMAIL PROTECTED]
Sent: Tuesday, December 16, 2003 7:32 PM
Subject: RE: [Declude.JunkMail] AOL and Reverse DNS
I know
Title: Message
OK I
have to reply to this one.
Nice
comparrison.
Kevin
Bilbee
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]On Behalf Of Todd
HoltSent: Tuesday, December 16, 2003 4:33 PMTo:
[EMAIL PROTECTED]Subject: RE: [Declude.JunkMail] AOL
www.xidix.com
702.319.4349
-Original Message-
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hosting Support
Sent: Tuesday, December 16, 2003 4:47 PM
To: [EMAIL PROTECTED]
Subject: Re: [Declude.JunkMail]
AOL and Reverse DNS
This is exactly why I think we should have
Title: Message
Totally agree. I know we'll always be at
their mercy, but at least we would have some warning
then...grin
Darin.
- Original Message -
From: Todd Holt
To: [EMAIL PROTECTED]
Sent: Tuesday, December 16, 2003 9:14 PM
Subject: RE: [Declude.JunkMail] AOL and Reverse
Holt
Xidix Technologies, Inc
Las Vegas, NV USA
www.xidix.com
702.319.4349
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Hosting Support
Sent: Tuesday, December 16, 2003 4:47 PM
To: [EMAIL PROTECTED]
Subject: Re: [Declude.JunkMail] AOL and Reverse DNS
702.319.4349
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Andy Schmidt
Sent: Tuesday, December 16, 2003 3:26 PM
To: [EMAIL PROTECTED]
Subject: [Declude.JunkMail] AOL and Reverse DNS
Hi,
I just noticed that AOL has stepped up their policies another
I will disagree. I do not believe there is any comparison between MS EULA and AOL
mail policies. I do not see AOL's actions as the ...internet-nazi-police
tactics... as you claim. I do not see where AOL is gaining any competitive
advantage, they are simply trying to protect their network
. AOL will not deliver e-mail that contains a hex-encoded Universal Resource
Locator (URL). (Ex: http://%6d%6e%3f
Contains it where, in the body?
John Tolmachoff
Engineer/Consultant/Owner
eServices For You
---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
---
Of DLAnalyzer Support
Sent: Tuesday, December 16, 2003 8:42 PM
To: [EMAIL PROTECTED]
Subject: Re: [Declude.JunkMail] AOL and Reverse DNS
Todd,
I suspect no one has an issue with what AOL is doing is because we are
so
close to the situation (i.e. we are all trying to block spam).
Darrell
]
Subject: RE: [Declude.JunkMail] AOL and Reverse DNS
I will disagree. I do not believe there is any comparison between MS EULA
and AOL mail policies. I do not see AOL's actions as the
...internet-nazi-police tactics... as you claim. I do not see where AOL
is gaining any competitive advantage
Hiya All -
We're seeing outbound e-mail to AOL.com happening very, very slowly.
Our outbound server (64.4.213.165 / 64.4.213.169) appears to be configured
correctly (no problems last week, and no changes since then).
Anybody else seeing AOL delays today?
=
Rob
I'm still seeing mail bounced back for the above domains. It's not
consistent but I do see this message in my SMTP logs.
11:06 12:35 SMTP-(1E00) 220-America Online (AOL) and its affiliated
companies do not
11:06 12:35 SMTP-(1E00) 220- authorize the use of its proprietary
computers and
I'm still seeing mail bounced back for the above domains. It's not
consistent but I do see this message in my SMTP logs.
11:06 12:35 SMTP-(1E00) 220-America Online (AOL) and its affiliated
companies do not
11:06 12:35 SMTP-(1E00) 220- authorize the use of its proprietary
computers
message.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bill Landry
Sent: Thursday, June 26, 2003 7:21 PM
To: [EMAIL PROTECTED]
Subject: Re: [Declude.JunkMail] AOL
I afraid you have got it backwards. The fixup protocol
disables ESMTP, which would
I know I saw a bunch of strings last week regarding AOL so I hate to ask
again but here it goes.
I have users who were able to send to AOL accounts until recently. What
needs to be done on either my end or the AOL end to send mail to them?
Thanks for any insight to this.
Samantha
---
[This
,
Samantha
Sent: Thursday, June 26, 2003 6:54 AM
To: Junkmail 'Declude. (E-mail)
Subject: [Declude.JunkMail] AOL
I know I saw a bunch of strings last week regarding AOL so I hate to ask
again but here it goes.
I have users who were able to send to AOL accounts until recently. What
needs to be done
, Samantha
Sent: Thursday, 26 June, 2003 16:54
To: Junkmail 'Declude. (E-mail)
Subject: [Declude.JunkMail] AOL
I know I saw a bunch of strings last week regarding AOL so I hate to ask
again but here it goes.
I have users who were able to send to AOL accounts until recently. What
needs to be done
]
Subject: RE: [Declude.JunkMail] AOL
Samantha,
You could start with this:
WARNING: One or more of your mailservers claims to be a host other than what
it really is (the SMTP greeting should be a 3-digit code, followed by a
space or a dash, then the host name). This probably won't cause any harm
macombisd.org claims to be host
I'm getting that indication when I run the DNS report from dnsreport.com.
I'm running Imail 8.0 does anybody know how to fix this?
It's actually not an IMail issue -- it's a
: Thursday, June 26, 2003 11:14 AM
To: [EMAIL PROTECTED]
Subject: RE: [Declude.JunkMail] AOL
macombisd.org claims to be host
I'm getting that indication when I run the DNS report from dnsreport.com.
I'm running
PROTECTED]
Reply-To: [EMAIL PROTECTED]
Date: Thu, 26 Jun 2003 17:31:14 +0300
To: [EMAIL PROTECTED]
Subject: RE: [Declude.JunkMail] AOL
Samantha,
You could start with this:
WARNING: One or more of your mailservers claims to be a host other than what
it really is (the SMTP greeting should
Yah.. Something is wack with your mail server...
telnet exmail.macombisd.org 25
Trying 64.88.82.249...
Connected to exmail.macombisd.org.
Escape character is '^]'.
220
**
**
2*
You need to
To: [EMAIL PROTECTED]
Subject: RE: [Declude.JunkMail] AOL
Yah.. Something is wack with your mail server...
telnet exmail.macombisd.org 25
Trying 64.88.82.249...
Connected to exmail.macombisd.org.
Escape character is '^]'.
220
According to you guys its not the mail server it is the Firewallright?
Correct.
What needs to be changed on the Firewall
I believe someone said it is the SMTP Fixup Protocol that needs to be
turned off.
and why is the current setup so bad?
Two reasons:
[1] It makes your server
]
To: [EMAIL PROTECTED]
Sent: Thursday, June 26, 2003 1:48 PM
Subject: RE: [Declude.JunkMail] AOL
According to you guys its not the mail server it is the
Firewallright?
Correct.
What needs to be changed on the Firewall
I believe someone said it is the SMTP Fixup Protocol that needs
:02 PM
Subject: Re: [Declude.JunkMail] AOL
Disabling the SMTP Fixup Protocol at the firewall disables ESMTP and
allows
only SMTP
Anyone using Imail peering will not be able to disable ESMTP
Rick Davidson
Buckeye Internet Inc
www.buckeyeweb.com
440-953-1900 ext: 222
- Original Message
Disabling the SMTP Fixup Protocol at the firewall disables ESMTP and allows
only SMTP
Anyone using Imail peering will not be able to disable ESMTP
Does that mean that Cisco firewalls can't be set up not to interfere with
SMTP transactions?
If enabling the fixup protocol breaks RFC-compliance
Does that mean that Cisco firewalls can't be set up not to interfere
with SMTP transactions?
Nah, PIXes are fine with no smtp fixup.
-Sandy
Sanford Whiteman, Chief Technologist
Broadleaf Systems, a division of
Cypress Integrated Systems, Inc.
e-mail:
To: [EMAIL PROTECTED]
Subject: Re: [Declude.JunkMail] AOL
Isn't that backwards?
Firewall with Fixup - ESMTP will not work, and mail defaults to
ordinary SMTP transaction
Firewall without Fixup -- ESMTP works fine
Jason
- Original Message -
From: Rick Davidson [EMAIL
: Thursday, June 26, 2003 9:26 PM
Subject: Re[2]: [Declude.JunkMail] AOL
Does that mean that Cisco firewalls can't be set up not to interfere
with SMTP transactions?
Nah, PIXes are fine with no smtp fixup.
-Sandy
Sanford Whiteman, Chief Technologist
]: [Declude.JunkMail] AOL
Yes ,exactly
Remove the smtp fixup and everything works fine
Better , remove the PIX firewall from your system , and add a
real firewall
,
You will have much less problems.
Rifat
- Original Message -
From: Sanford Whiteman [EMAIL PROTECTED]
To: R
, 2003 2:14 PM
Subject: Re: [Declude.JunkMail] AOL
Disabling the SMTP Fixup Protocol at the firewall disables ESMTP and
allows
only SMTP
Anyone using Imail peering will not be able to disable ESMTP
Does that mean that Cisco firewalls can't be set up not to interfere with
SMTP transactions
Message -
From: Rick Davidson [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, June 26, 2003 3:04 PM
Subject: Re: [Declude.JunkMail] AOL
Correct. It will disable SMTP AUTH as well
The fixup was added to IOS to allow ESMTP
its quite a pickle
Rick Davidson
Buckeye Internet Inc
Hi,
I was wondering if anyone else out there is seeing
an issue with aol? It seems that we have not been able to connect
toAOLall day. However, AOL has been connecting to us and
sending us mail. Here are some snippets of our log files:
06:06 14:35 SMTP-(0558)
Trying aol.com (0) 06:06
, 2003 12:04 PM
To: [EMAIL PROTECTED]
Subject: [Declude.JunkMail] AOL Connection dropped
Hi,
I was wondering if anyone else out there is seeing an issue with aol? It
seems that we have not been able to connect to AOL all day. However, AOL
has been connecting to us and sending us mail. Here
Glenharbor Circle
Winter Garden, FL 34787
Phone 407-877-8450
Fax 407-877-8451
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of keith -
cribellum
Sent: Friday, June 06, 2003 3:04 PM
To: [EMAIL PROTECTED]
Subject: [Declude.JunkMail] AOL Connection dropped
I did an NSLOOKUP on our servers this morning and mail.aol.com and
mail.cs.com are coming up Non-existant Domains
mail.compuserve.com resolves.
So does that point to them or is it an issue with our DNS servers? Strange
That sounds like a problem with your DNS servers (even if they did have
I did an NSLOOKUP on our servers this morning and mail.aol.com and
mail.cs.com are coming up Non-existant Domains
mail.compuserve.com resolves.
Shows errors here:
http://www.dnsreport.com/tools/dnsreport.ch?domain=mail.aol.com
Try aol.com and cs.com:
FYI -
I am investigating a problem in which messages to a local account,
forwarded to AOL are not received - the thinking is that they are blocked as
spam since they have a FROM [EMAIL PROTECTED] , but come from a non-hotmail
server.
Everything else straight to AOL seems to be working.
I am investigating a problem in which messages to a local account,
forwarded to AOL are not received - the thinking is that they are blocked as
spam since they have a FROM [EMAIL PROTECTED] , but come from a non-hotmail
server.
Everything else straight to AOL seems to be working.
I
To clarify, the email comes to a local account, which is forwarded to an E-mail
address @aol.com . I see in the logs where AOL has accepted the message but
the customer says it never gets to the AOL inbox. I will try to contact AOL
and see what they say.
I am investigating a problem in
To clarify, the email comes to a local account, which is forwarded to an
E-mail
address @aol.com . I see in the logs where AOL has accepted the message but
the customer says it never gets to the AOL inbox. I will try to contact AOL
and see what they say.
Ah, I see. I'm guessing that AOL
If AOL does say anything about this, I would be very interested to know
what they say, as I believe they do not acknowledge the secret spam
filtering (as opposed to the standard spam filtering, where they will
bounce the E-mails).
We had a similar issue where AOL
If AOL does say anything about this, I would be very interested to know
what they say, as I believe they do not acknowledge the secret spam
filtering (as opposed to the standard spam filtering, where they will
bounce the E-mails).
Please, with the amount of junk I get in my AOHell mailbox, and
Please, with the amount of junk I get in my AOHell mailbox, and the amount
of junk I get FROM AOHell through our server, they don't do a very good
job
of Spam control.
Sending and receiving are 2 different actions.
John Tolmachoff MCSE, CSSA
IT Manager, Network Engineer
RelianceSoft, Inc.
Has anyone been having trouble with sending to AOL?
I have a lot of users calling because messages to AOL.COM or CS.COM keep
getting returned after 3 attempts.
It has just started in the last few days. We aren't on AOL's blacklist.
I posted this on the Imail list but so far nothing has helped.
This is being discussed on the CF-Talk list as well. Started up yesterday, I believe.
Someone on that list got hold of an AOL admin (as if there really are any) and posted
this:
| I called AOL and their tech advised me to make RDNS entries
| for every domain then wait 24 hours and try
This is being discussed on the CF-Talk list as well. Started up
yesterday, I believe. Someone on that list got hold of an AOL admin (as
if there really are any) and posted this:
| I called AOL and their tech advised me to make RDNS entries
| for every domain then wait 24 hours and try
Of Dustin Freeman
Sent: Thursday, December 19, 2002 02:44 PM
To: '[EMAIL PROTECTED]'
Subject: [Declude.JunkMail] AOL problem or mine?
Has anyone been having trouble with sending to AOL?
I have a lot of users calling because messages to AOL.COM or CS.COM keep
getting returned after 3 attempts.
It has just
Subject: RE: [Declude.JunkMail] AOL problem or mine?
Hi,
yes, got complaints yesterday as well (one of our mailing lists) - seems to
be back to normal, though.
Best Regards
Andy Schmidt
Phone: +1 201 934-3414 x20 (Business)
Fax:+1 201 934-9206
-Original Message-
From: [EMAIL
: R. Scott Perry [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 19, 2002 3:03 PM
To: [EMAIL PROTECTED]
Subject: Re: [Declude.JunkMail] AOL problem or mine?
This is being discussed on the CF-Talk list as well. Started up
yesterday, I believe. Someone on that list got hold of an AOL admin
Our reverse DNS is fine,(checked it on dnsstuff.com) I went to
postmaster.info.aol.com and nothing there helped.
We are not getting the message from AOL, it appears that it comes from our
server after trying to send the message 3 times and failing each time.
It sounds like AOL is having some
America Online said Monday that it temporarily had blocked e-mail coming
through servers from Microsoft's bCentral, a Web service focused on
small businesses.
http://zdnet.com.com/2100-1105-941128.html
---
[This E-mail scanned for viruses by F-Proto Virus Scanner]
---
[This E-mail was scanned
1 - 100 of 103 matches
Mail list logo
