zlacker

>>todsac+(OP)
> We see that that’s a quite a long line. Mail servers don’t like that

Why do mail server care about how long a line is? Why don't they just let the client reading the mail worry about wrapping the lines?

>>tibors+Qa
SMTP is a line–based protocol, including the part that transfers the message body

The server needs to parse the message headers, so it can't be an opaque blob. If the client uses IMAP, the server needs to fully parse the message. The only alternative is POP3, where the client downloads all messages as blobs and you can only read your email from one location, which made sense in the year 2000 but not now when everyone has several devices.

>>direwo+6j
Hey, POP3 still makes sense. Having a local copy of your emails is useful.

>>fluori+8v
Isn’t the only difference between pop and imap that pop removes the mail from the server? I only use imap, and all my email is available offline.

>>Jaxan+Jt1
Not at all. IMAP can do a lot of complex operations on the email while leaving it on the server, for example you can have the server search the email, flag it (mark it important, or read, or unread).

POP can download the email, and that's about it.

>>ars+YO2
Yeah, because then the client can do whatever it wants with the messages. The operations don't need any further support from the protocol.

>>fluori+Kp3
The idea with IMAP is multiple clients can work with your email - for example your desktop and your phone can both see the same messages and manipulate them, even offline.

Gmail basically is IMAP with a couple extras, and your desktop (via a browser) and your phone (via a dedicated app) can both see the same messages. Only the phone can work offline though, because there is little demand for a dedicated desktop email client, it's always via a browser. But Google could easily make such a thing if they wanted.