On 17/02/2012 12:50 a.m., Dave Cridland wrote:
What, why corporates deploy XMPP? That's wildly off-topic for this list.
why so many.
it's ok, I understand those stats better now. I think they are skewed.
Top 500 sites are quite different to the other 99% of sites.
That's why I keep going back to the 1 port like a broken record.
Maybe it should just be an SSH tunnel... but that;s back-pedalling
quickly and reducing potential user experience with it.
No, I think it's an orthogonal issue.
maybe, but nonetheless real, especially for ISP tech support staff.
Just trying to think of "cheap" ways to get single sign on and single
port using the existing protocols. But it would still be a bandaid.
Auto config is a band-aid as well to the solution of multiple sets of
creds.
It's just part of reducing manual configuration, which we're all
agreed is a good thing.
Using multiple ports has no bearing, though.
not true. Ports can be (and are) individually blocked, filtered
whathaveyou. Therefore availability of individual features within a
mail application can be variable rather than all or nothing. Which is
better is debatable, but there's more confusion associated with partial
failure than complete failure IME.
Right, sure, understood (after s/MTA/MUA/) but what has port 25 got
to do with it?
back to my point about getting everything over 1 port. If we had
that, then blocking 25 wouldn't have affected me.
But my point is that blocking port 25 shouldn't be affecting you anyway.
Submission runs on port 587, has done for years.
ah... well I use SMTP :)
So do many clients. Not enough years I think to make such a big impact.
* SPAM
... an infrastructure problem, mostly.
* UDNs
I'm not familiar with this acronym. Nor is Wikipedia or Google, I'm
afraid.
Un deliverable notifications.... pretty sure I'd seen that TLA around
before.
by and large wrt bounce messages people
* don't read them
* don't understand them
they just ask tech support. We get heaps of such questions. There may
be no helping some people, but it's not free.
* configuration issues
Right, and discovery (and decent implementations using it) solves 99%
of this without any changes to the core protocols.
Discovery is a bit different to config. It's only part of the picture.
I'd like to see it more fully fledged. If ACAP had been widely adopted
and deployed it would be a no-brainer.
Dave.
--
Adrien de Croy - WinGate Proxy Server - http://www.wingate.com
_______________________________________________
imap5 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/imap5
