|
In one
post I read, the solution the developer found was to send one e-mail every
17 seconds. This would be painfully slow, but it worked for him. So far, this is
the only way that I've heard of getting around the problem.
Here
are my thoughts, the poster was using CFMAIL to connect to a mail server and
send out the messages, which I believe means he was only sending to one address
per connection. You may want to try sending several messages per
connection, but space out those connections by building an e-mail every 20-30
seconds or so. (I'm not sure what the magic numbers are) I know this isn't what
you want to hear when sending out a lot of e-mail, but it may be your only
solution.
What
appears to be happening at AOL's end is that they see a lot of messages from the
same IP or from address within a short period of time and start blocking them.
The block only lasts for a short period of time (hours I think), and is
eventually removed. I haven't worked with this too much seeing as only a tiny
number of our e-mails go to AOL.
HTH,
Marc
Thanks very much for giving us some insight, Marc. How would
we configure the call to cfx_iMSMail to send over longer periods of
time? Here, we run a mass e-mail several times a week that is kicked off
by one of our marketing people. It basically reads e-mail addresses from
a database and sends to those addresses. Would we have to code a delay
within that page just for AOL users? How do you lengthen the period of
time during which you send mail?
Hi
guys,
Are you sending a lot of e-mail to aol over a short period of time?
I've done some research on this issue, and have seen that AOL stops
accepting e-mail from a server when it sends many in a short period of time.
Even if the mail is sent over several connections.
Marc
We are seeing similar troubles with AOL accepting mail, but the
mail never ending up in the recipient's inbox. I will watch this
thread with interest.
"sorry for additional email on AOL, but i
forget the log info"
03/12/2003 11:11:33 AM [016] Send mail
start for 1E08F772EC590443BF36B2584CD7C655.mbx (Priority
0) 03/12/2003 11:11:33 AM [016] Connect to
mailin-02.mx.aol.com 03/12/2003 11:11:33 AM [016] WARNING: SOCKET
ERROR1: (Sock Recv) [10054] Connection reset by peer
(1E08F772EC590443BF36B2584CD7C655.mbx) 03/12/2003 11:11:33 AM [016]
WARNING: Error connecting to mailin-02.mx.aol.com response
follows: 03/12/2003 11:11:33 AM [016] WARNING:
(<-mailin-02.mx.aol.com) SOCKET ERROR: (Sock Recv) [10054] Connection
reset by peer 03/12/2003 11:11:33 AM [016] Connect to
mailin-01.mx.aol.com 03/12/2003 11:11:34 AM [016] Sending mail to
mailin-01.mx.aol.com 03/12/2003 11:11:34 AM [016]
1E08F772EC590443BF36B2584CD7C655.mbx sent successfully to [EMAIL PROTECTED] from <>
598 03/12/2003 11:11:34 AM [016] Completed Processing
thanks.
----- Original Message -----
Sent: Thursday, March 13, 2003
9:10 AM
Subject: [iMS] Re: aol and
email
howie ...i appreciate the personal
response with general info; but i am up against a wall here on time
and unfortunately wear multiple hats as email, web, ....really,
everything digital administrator...
anyway, here is a block from the logs
showing my mail have trouble getting through to aol ...and when it
eventually does, it seems to be delivered ...yet, the recipient does
not get the mail. if i email the same recipient from my
"authentication-required" smtp server on the same box, the user
gets the mail.
therefore, after analyzing all research
from yesterday (via your info) and looking at the [above]
log file, i believe the following:
- i am not on any blacklist (this after
checking over 40 blacklists for my domain name and IP
...including spam cop)
- aol seems to be getting the mail, and
actually excepting it
- it has something to do with the way CFX
delivers mail and/or constructs mail messages.
anyone have any ideas? is the
default header style for CFX incompatible with aol and perhaps they
are kicking me after accepting the mail? if so, what an
acceptable header? i do not understand headers very well, so
manipulation of them is a challenge currently.
any ideas out there
gurus?
thanks in advance.
----- Original Message -----
Sent: Wednesday, March 12, 2003
4:20 PM
Subject: Re: [iMS]
quoted-printable
There is no disadvantage besides the
token issue that I know of. There is no option for encoding
plain text but not the HTML. The new CFX should be ready
for testing soon, BTW.
Regards,
Howie
----- Original Message -----
Sent: Wednesday, March 12,
2003 10:39 AM
Subject: [iMS]
quoted-printable
Hi
Howie,
What
are the disadvantages of using quoted-printable? One I am aware of
is that tokens can be messed up. Are there any
others?
I'm
reasonably sure this isn't a current option, but is there a
setting in the CFX_IMSMAIL tag to only set the plain/text part of
a messaged to quoted-printable?
Regards,
Marc
------------------------------------------------------
Marc Lichtenfeld Senior Programmer/Technology Lead
www.bigdough.com
|