List Info

Thread: fallback relay




fallback relay
country flaguser name
United States
2007-07-01 08:24:29
Our ISP just decided to block outgoing port 25 for everyone.
Took us
hours to figure it  out (we were getting "399 TCP Read
failed" errors)
. Even the ISPs support guys didn't know about this new
feature.  :-(

Currently we are using the ISPs mail server as a relay for
all
outgoing email. Once they have their act together we will be
sending
email out directly to the recipient mailservers.  Is it
possible to
only relay email through the ISP mailserver, that has been
stuck in
the outgoing queue for a while as opposed to sending
everything to
them?

sai


Re: fallback relay
country flaguser name
United States
2007-07-01 10:26:07
Tunnelling port 25 is a good way to limit virus infections.
If you have control over both the sending and receiving servers, use Port 587.
If you don't, then you will need to setup arrangements ($) for the ISP to allow port 25 from your static IP address, or ($) let them host the domain, DNS, & email service and then you can use your Surgemail to manage your local emails to & from their server.  It would still be good to run Surgemail for virus & spam filtering.
 
Also check to see if the ISP's Usage Agreement has been revised.  They might no longer allow any servers on certain IP blocks.
 
BarryZ
1USA
 
----- Original Message -----
Sent: Sunday, July 01, 2007 9:24 AM
Subject: [SurgeMail List] fallback relay

Our ISP just decided to block outgoing port 25 for everyone. Took us
hours to figure it  out (we were getting "399 TCP Read failed" errors)
. Even the ISPs support guys didn't know about this new feature.  :-(

Currently we are using the ISPs mail server as a relay for all
outgoing email. Once they have their act together we will be sending
email out directly to the recipient mailservers.  Is it possible to
only relay email through the ISP mailserver, that has been stuck in
the outgoing queue for a while as opposed to sending everything to
them?

sai

Re: fallback relay
country flaguser name
United States
2007-07-03 01:55:28
The ISP has allowed us to send out packets on port 25 again
(if we get
our ip address blacklisted then its our responsibility etc.
etc....)

What I was trying to figure out was if it is possible to try
sending
out mail through the ISPs mail server if the email has been
in the
mail queue for more than 1 hour (or some similar condition
indicating
that our mailserver is unable to send out email because it
has been
blocked/blacklisted).

sai

On 7/1/07, webmaster1usa.com <webmaster1usa.com> wrote:
>
>
> Tunnelling port 25 is a good way to limit virus
infections.
> If you have control over both the sending and receiving
servers, use Port
> 587.
> If you don't, then you will need to setup arrangements
($) for the ISP to
> allow port 25 from your static IP address, or ($) let
them host the domain,
> DNS, & email service and then you can use your
Surgemail to manage your
> local emails to & from their server.  It would
still be good to run
> Surgemail for virus & spam filtering.
>
> Also check to see if the ISP's Usage Agreement has been
revised.  They might
> no longer allow any servers on certain IP blocks.
>
> BarryZ
> 1USA
>
>
> ----- Original Message -----
> From: sai
> To: surgemail-listnetwinsite.com
> Sent: Sunday, July 01, 2007 9:24 AM
> Subject: [SurgeMail List] fallback relay
>
> Our ISP just decided to block outgoing port 25 for
everyone. Took us
> hours to figure it  out (we were getting "399 TCP
Read failed" errors)
> . Even the ISPs support guys didn't know about this new
feature.  :-(
>
> Currently we are using the ISPs mail server as a relay
for all
> outgoing email. Once they have their act together we
will be sending
> email out directly to the recipient mailservers.  Is it
possible to
> only relay email through the ISP mailserver, that has
been stuck in
> the outgoing queue for a while as opposed to sending
everything to
> them?
>
> sai
>
>


[1-3]

about | contact  Other archives ( Real Estate discussion Medical topics )