[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [cobalt-users] OT: ISP's and Port 25 blocks



At 07:11 AM 5/23/2003, you wrote:
Greetings list,
I'm sure that many of you are aware of have been directly affected by
various ISP's blocking port 25....
About 95% of our clients are small businesses which we allow for them
to relay through our servers (smpt=mail.their-domain-name.com). Within
the last few days, we began receiving calls from our clients that they
couldn't send email - and it took us a few hours to realize this was
due to a local ISP initiating a port 25 block for their residential
users. We contacted the ISP in question, and were told that this was
becoming the norm, regardless of the fact that they were essentially
blocking *our* clients from *our* services - the service for which our
clients are paying.
We're looking for a solution to this - obviously we need to keep port
25 active on our servers in order to receive mail from outside sources
(correct me if I'm wrong, but please don't flame).....but there must be
an alternative to this - perhaps mapping the smtp port to an unused
port?
I'm open to suggestions, and need a solution quickly.

Thanks in advance,
Mike


The easiest way for your customers that use "residential ISP services" is to have them use the ISP's smtp server with their return address set to you server and pop3 set to your server. Most services don't require a log in to the smtp server if they are connected to ISP. The biggest know exception here is MSN which requires the customer to login to the ISP's smtp server. Outlook and outlook express can handle logging into two servers (SMTP and POP3) at the same time. Most other mail clients only have one login.

they would have
smtp server:    mail.ispserver.com
pop3 server:    mail.theirsite.com
return address: user@xxxxxxxxxxxxx




--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.