It's a pity that MAAWG or another group hasn't written a
specification for the automatic downloading of configuration (with
certificates, to be sure, for some kind of repudiation) and the
update thereof, for adoption by the leading consumer e-mail clients.
MAAWG decided it's not in the standards
-
From: Frank Bulk [mailto:frnk...@iname.com]
Sent: Monday, June 22, 2009 11:14 AM
To: 'John Levine'; nanog@nanog.org
Subject: RE: Is your ISP blocking outgoing port 25?
The bootstrap question is addressed by requiring the end-user to know
their
e-mail address and password. Based
At 9:38 AM -0700 6/22/09, John R. Levine wrote:
The bootstrap question is addressed by requiring the end-user to know their
e-mail address and password. Based on the domain name, the implementation
would reach out to https://something.domain-name.tld and download the
relevant schema and data
We just open port 2525 for customers from ISP's blocking official SMTP
ports so they can use their dedicated servers/domain mailservers.
Lyndon Nerenberg wrote:
On Thu, 2009-06-18 at 16:14 -0400, Joe Provo wrote:
then you should be shifting your userbase to authenticated on the
SUBMIT
Sent from my iPhone, please excuse any errors.
On Jun 19, 2009, at 8:53, Jeroen Wunnink jer...@easyhosting.nl wrote:
We just open port 2525 for customers from ISP's blocking official
SMTP ports so they can use their dedicated servers/domain mailservers.
Is there any reason you do not use
Yes..
1. Customers remember it more easily
2. Some ISP's also block 587 (hence 'SMTP ports' rather then 'SMTP port'
in my previous comment ;-)
Patrick W. Gilmore wrote:
Sent from my iPhone, please excuse any errors.
On Jun 19, 2009, at 8:53, Jeroen Wunnink jer...@easyhosting.nl wrote:
We just open port 2525 for customers from ISP's blocking official SMTP
ports so they can use their dedicated servers/domain mailservers.
for personal use, i have a box that has sshd running on 443 and i tunnel
2525 through it. that worked even in the narita red rug when they were
at their
. Customers
may send outbound mail through our SMTP server, or connect via alternate ports
to their SMTP server.
From: Zhiyun Qian [zhiy...@umich.edu]
Sent: Thursday, June 18, 2009 2:36 PM
To: nanog@nanog.org
Subject: Is your ISP blocking outgoing port 25
ATT is the major one that I know of that is still enforcing this
policy.
But they said they can unblock port 25 upon request. I am not sure
how easy
it is.
It's trivial. A web form. You get the link when you try to send mail
to port 25 anywhere else. At least with Yahoo/SBC dsl.
I got
On Fri, 19 Jun 2009, Jeroen Wunnink wrote:
1. Customers remember it more easily
2. Some ISP's also block 587 (hence 'SMTP ports' rather then 'SMTP port' in
my previous comment ;-)
Those same clueless ISPs will probably block 2525 someday too, clueless
expands to fill any void. And using
Most MTAs don't come preconfigured with port 587 either. It is amazing
how many people/organizations go with the if it isn't broke, don't fix
it mentality, even though it clearly needs to be revised and something
new needs to be done/supported. Email needs to be revamped on a larger
scale than
Sean Donelan wrote:
On Fri, 19 Jun 2009, Jeroen Wunnink wrote:
1. Customers remember it more easily
2. Some ISP's also block 587 (hence 'SMTP ports' rather then 'SMTP
port' in my previous comment ;-)
Those same clueless ISPs will probably block 2525 someday too,
clueless expands to fill any
Subject: Is your ISP blocking outgoing port 25?
It has been long heard that many ISPs block outgoing port 25 for the
purpose
of reducing spam originated from their network.
I wonder which ISPs are still doing so. I know comcast has been doing
that
but they cancelled it after many complaints
Zhiyun Qian wrote:
It has been long heard that many ISPs block outgoing port 25 for the purpose
of reducing spam originated from their network.
Well blocking or redirecting to there servers, which have an
undocumented filtering policy. All one needs to do in order to bypass
that is use a
We don't force SSL but do have several SMTP servers they can use
-Original Message-
From: Charles Wyble [mailto:char...@thewybles.com]
Sent: Thursday, June 18, 2009 3:55 PM
To: NANOG list
Subject: Re: Is your ISP blocking outgoing port 25?
Do you provide your users an SMTP server
On Thu, Jun 18, 2009 at 03:36:44PM -0400, Zhiyun Qian wrote:
It has been long heard that many ISPs block outgoing port 25 for the purpose
of reducing spam originated from their network.
Yes, it is standard practice for non-server accounts and most dynamic-only
accounts; only allow
I wonder which ISPs are still doing so. I know comcast has been doing
that but they cancelled it after many complaints. It seems to be the
same case for Verizon.
You're mistaken. Comcast most certainly does port 25 filtering,
although not necessarily on every line at every moment. So does
On Thu, 2009-06-18 at 16:14 -0400, Joe Provo wrote:
then you should be shifting your userbase to authenticated on the
SUBMIT
port [587] anyway...
Except for those ISPs who choose to intercept port 587 as well. This is
a big problem with Rogers in Vancouver. They hijack port 587 connections
On Thu, Jun 18, 2009 at 4:27 PM, Lyndon Nerenberglyn...@orthanc.ca wrote:
On Thu, 2009-06-18 at 16:14 -0400, Joe Provo wrote:
then you should be shifting your userbase to authenticated on the
SUBMIT
port [587] anyway...
Except for those ISPs who choose to intercept port 587 as well. This is
Christopher Morrow wrote:
in all seriousness, most isp's (consumer provider folk) today do some
form of blocking of port 25, if you are 'smart' enough to evade this
sort of thing, then you can still do email/blah. 99.999% of users are:
1) not interested in bypassing it
2) not clued into what's
20 matches
Mail list logo
