[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] raq3 and smtp support, heeeelllppp...
- Subject: Re: [cobalt-users] raq3 and smtp support, heeeelllppp...
- From: Jeff Lasman <jblists@xxxxxxxxxxxxx>
- Date: Sat Dec 15 17:32:01 2001
- Organization: nobaloney.net
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
Steve Werby wrote:
> A year ago this was a fairly accurate blanket statement, but the tide may be
> turning here soon.
I don't see how it can until we all get both server smtp AND local muas
(Mail User Agents, mail client software) that uses authentication AND
the ISPs stop blocking port 25... more below...
> Over the last year many ISPs that hadn't been already
> have put restrictions on use of their SMTP servers and made it difficult to
> use an SMTP server of your choice. For example, Verizon (with millions of
> dialup and DSL customers) has limited access to their SMTP servers to emails
> sent using the Verizon provided email address in the From header.
They've also made it impossible to use your own server, or any other
server, afaik. In other words, if you've got Verizon there's precious
little hope except to leave.
> Others have blocked port 25 traffic to external locations
Megapop does this; they're used by many (maybe most) small ISPs offering
nationwide access. I'm using a Megapop connection atm, but I CAN use
any return address I want on my outgoing email.
> or redirected it to their own SMTP servers.
AOL does this.
> There are workarounds for the above situations, but
> they're not ideal.
And they are??? One of the "workarounds" is of course webmail. But I
don't think most of our customers want to use webmail for their outgoing
email.
> If this behavior increases, web hosts that don't allow
> their customers to use their SMTP servers will likely lose potential
> customers and send some existing customers packing.
But if you DO allow your clients to use your SMTP server, then he/she
still can't if his ISP is doing either port blocking or redirection (see
your own points above).
One way around this conundrum is for you (the web-hosting company, to
run SMTP on another port. Mind you, scanners will find this, too, so
you'll still have to restrict it to SMTP after POP3, or else
authenticate by incoming IP# or other means.
Jeff
--
Jeff Lasman <jblists@xxxxxxxxxxxxx>
Linux and Cobalt/Sun/RaQ Consulting
nobaloney.net
P. O. Box 52672, Riverside, CA 92517
voice: (909) 778-9980 * fax: (702) 548-9484