Re: [Imap-protocol] Is there some way to detect servers which automatically add sent messages to the Sent mailbox?

Dave Cridland <[email protected]>
Newsgroups gmane.mail.imap.general
Message-ID <CAKHUCzzPttroO06o_ZAiKf4yLhpE=aN3Ae0+wk-XksB=zyL7cQ@mail.gmail.com>
On 14 Jan 2013 07:56, "Timo Sirainen" <[email protected]> wrote:
>
> On Mon, 2013-01-14 at 12:39 +0000, Dave Cridland wrote:
> >
> > The setup of BURL from an MUA's perspective is awkward, though,
> > because the BURL capable submission server provides no hints as to
> > which IMAP server is to be used, and vice-versa, making discovery a
> > bit hit and miss.
>
> User (or automation) already has to configure IMAP and submission server
> to MUA, so how does BURL make it any more difficult?

I was dealing with user-directed configuration rather than discovery; maybe
it's changed now. I'm merely relaying the experiences I've had.

> 1. client APPENDs/CATENATEs message to IMAP server
> 2. client requests URLAUTH URL
> 3. client connects to submission server
> 4. client sends message with BURL

Yeah, and that's close to what Polymer does, although it takes into account
POSTADDRESS and whether the message would be shorter via BURL, and connects
to the submission server first so it can proceed in the background, and so
on.

The problem is that there's no way of knowing whether a particular URL will
be acceptable to BURL or not without simply trying it, and that makes me
feel all goose-bumpy inside.

And in vague response to lack of BURL support in servers - yeah. This is
irritating, and very chickeny (and/or eggy) but sitting here and moaning
about it won't change much.

My gut feeling is that if Brandon and Bron implemented BURL, you'd see
clients falling over themselves to implement.

Dave.

_______________________________________________
Imap-protocol mailing list
[email protected]
http://mailman2.u.washington.edu/mailman/listinfo/imap-protocol
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.