On Thu, 15 Jul 1999, Tonya Pope wrote:
> Hi all,
>
> Last week, the ISP we rent rack space from made an error in their DNS
> and our mailserver got swamped with other people's mail.
How did DNS swamp your mailserver? I am not clear on this.
> [...] In various attempts to block this extra mail (over
> 10,000 got queued), get rid of it, etc.,
> They fixed their DNS problem, so we're back to only our own
> mail. Now, we can't mail to, amongst others, AOL. The log has:
>
> Stack connect fail "205.188.146.8"
Scott Crain runs the filters at AOL. You might be in the AOL system
filters. No way for me to tell from here. If you had 10,000 emails in your
output queue, that was not from your customer, that sounds a lot like
spam.
> That example is one of many AOL addresses. There are other domains it
> can't get to as well, but there are a few it can. It does finally get
> there, but only when it has enough tries to go to thru the other
> gateway.
> Unfortunately, the other gateway is our ISP and they never
> clear out old records. SO, email that goes thru them has a 50/50 chance
> of having the "FROM" field altered somehow (some of the IPs we have are
> the same IP addresses we had while on their servers).
>
> SO, is anybody familiar with this particular "stack connect fail" error
> and what could cause it? I've tried resetting everything the way it
> was, but I must have missed something? SMTP security is set to relay
> mail for anyone.
Relaying SMTP for anyone is probably not a good idea for any host directly
connected to the internet.
Your server tmail.team-m.com [207.226.255.37] is listed by 2 Open Relay
lists. That alone can explain why you cannot send mail to some domains.
We always reccomend SMTP relaying for the IP address block that you
control, together with some sort of SMTP AUTH mechanism for roaming users.
> Thanks in advance,
> Tonya
You are welcome,
-bryan
(just my opinion)
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
