I'd like to request a little more benefit of the doubt, gentlemen... :-) I need to send messages (many from ordinary email sources) on an IP WAN with unreliable connections to/from nodes whose IPs may vary from session to session. This is part of a larger application that I can't discuss publicly. It's not a website app; it's more like an IMAP service that doesn't retain messages.
>From what I read, IMAP isn't efficient enough for the loads I expect. Dovecot users report that they can handle ~4K concurrent connections per server. I need like 100x that. Websockets are designed for that kind of concurrency. Since my gateway would be local to the postfix host, LMTP with pipelining seems right, and I see that postfix caches LMTP client connections and has a configurable concurrency max. So far, so good. Now assume I keep a list of recipients which had delivery fail on the last attempt. When a node reconnects to my gateway, can I tell postfix to retry items for its recipients? Websocket nitty gritty: http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-03 On Sat, Nov 6, 2010 at 9:17 PM, Stan Hoeppner <[email protected]>wrote: > It sounds as if you have yourself a nifty solution in search of a > problem to solve. Usually it's the other way round, in the real world. > >
