On Mon, Nov 8, 2010 at 8:11 AM, Wietse Venema wrote:
> The same Postfix program implements SMTP and LMTP.
>
I concluded that the best way to learn the protocol is to write a server
shell that prints its inputs and replies OK to everything :-)
I'm also pondering use of an MQ engine between the
You mean read RFCs for SMTP, ESMTP, LMTP and diff them :-P
On Sun, Nov 7, 2010 at 8:39 PM, Sahil Tandon wrote:
> On Sun, 2010-11-07 at 10:58:20 -0800, Liam wrote:
>
> > On Sun, Nov 7, 2010 at 10:04 AM, Wietse Venema
> wrote:
> >
> > > - LMTP has one END-OF-DATA
Thanks for your help in sorting this out, Wietse.
On Sun, Nov 7, 2010 at 11:19 AM, Wietse Venema wrote:
> > I can support per-node domains, e.g. node-id.mailhost.xyz
> I suppose some wild-card DNS record will do the trick.
>
So that all those node domains resolve MX to my proxy?
>
The non-opti
On Sun, Nov 7, 2010 at 10:04 AM, Wietse Venema wrote:
> - LMTP has one END-OF-DATA status per recipient, instead of just one
> status for the entire mail transaction.
>
OK, I need per-recipient status, so LMTP is indeed the right protocol.
Is it missing any minor features from SMTP that I'm lik
On Sun, Nov 7, 2010 at 10:01 AM, Wietse Venema wrote:
> It sounds like you will be sending all mail to the same outbound
> proxy, meaning that Postfix has no clue what destinations are up
> and what are down, because that is hidden by your outbound proxy
>
I can support per-node domains, e.g. no
On Sun, Nov 7, 2010 at 5:58 AM, Jeroen Geilman wrote:
Jeroen, thanks for your comments.
Websocket is a new protocol to enable persistent, full-duplex, efficient
> connections to web servers.
>
> However, it is just HTTP, right ?
>
Websockets are HTTP-initiated, but messages passed after initia
of queue id's for all my nodes,
there will be a LOT of rather short lists. Is that likely to cause problems?
I'd like to avoid implementing a queue manager, at least in the near term!
:-)
Liam
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.
ing messages over a single connection, otherwise the
number of concurrent connections would exceed what's practical.
Liam
efficient to poke postfix when a client connects whom I know has
messages pending (due to a previous delivery attempt).
Liam
10 matches
Mail list logo
