3 messages in net.sourceforge.lists.courier-users[courier-users] imap outbox
FromSent OnAttachments
JorisMay 23, 2004 9:55 pm 
Juri HaberlandMay 24, 2004 12:21 am 
Malcolm WeirMay 24, 2004 12:49 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[courier-users] imap outboxActions...
From:Joris (jor@linux.be)
Date:May 23, 2004 9:55:42 pm
List:net.sourceforge.lists.courier-users

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Hi,

I don't know if this is the place to discuss this, but at least this list has a high concentration of imap knowledge. Feel free to flame me.

This is some idea I picked up from a slashdot discussion. While it's not a standard (yet), I don't see why it couldn't be. [insert cheap joke about imap standards here].

Imap could use an "outbox". Not just a mua outbox queuing up all the mail 'till a connection is made, no, a real outbox. The mail client sends outgoing mail to the outbox on the imap server, wich hands it to the smtp server.

Advantages: Simpler mua configuration. Outgoing mail is already pre-auth'd Outgoing mail doesn't require a seperate connection Outgoing mail doesn't require a connection to the smtp port of some host, wich is very spam-esque behaviour (picture yourself in a cybercafe or corporate network where a policy is enforced). Outgoing mail always comes from the same place (think about the problems with SPF and the like when you're on the road and behind an enforcing firewall) It just seems logical... Mail goes in and out at the same place.

Disadvantages: MUAs, imap servers would need a patch

Any toughts? Is this implementation-worthy? Or push-to-standards-draft-worthy?

iD8DBQFAsYAWNjYk7GBDNwQRAvs/AJ9RTe3G/HrzJRAIVdC2Lic6mOX2FQCaA7tm R3lA7jNgU/jlUISiZfe0Ulw= =lk5Y -----END PGP SIGNATURE-----