On Thu, Nov 19, 2015 at 4:19 PM, Tom Boland wrote:
> Thanks again for this. It's really useful. It turns out that the
> delimiter is a plain old \n. Who knows how consistent this will be between
> different policy daemons, I don't know!
>
I would check the Postfix docs for that.
> Now, this
Thanks again for this. It's really useful. It turns out that the
delimiter is a plain old \n. Who knows how consistent this will be
between different policy daemons, I don't know!
I've modified it to manage a DeferredQueue which hopefully means I can
just keep throwing requests at it without ev
On Wed, Nov 18, 2015 at 9:28 AM, Tom Boland wrote:
> I think what you've provided me with is useful for me, but I think it's
> backwards for my purposes, as I need to be connecting to the policy daemon
> rather than being the policy daemon!
>
> I wanted to do this with deferred calls in case one
Hi Exvito,
Thanks very much for this. I think I might just give a bit of context
about using this.
I have an SMTP proxy using Nginx. It uses queries an HTTP service to
establish whether mail should be forwarded, and where to (on to
postfix/dovecot/exchange backends). It uses Twisted for the HTT
Tom,
I guess LineReceiver can help you with that, it's a matter of using a
different delimiter. Here is a rough sketch of something you can start
exploring:
from __future__ import print_function
from twisted.internet import reactor, protocol, endpoints, defer
from twisted.protocols import basic
Greetings all.
This may be a very basic question. I'm hoping to implement a postfix
policy check client in twisted. It's a simple protocol. You send
newline separated key value pairs like:
recipient=em...@ddr.ess
sender=anot...@ddr.ess
size=1024
helo_name=mail.server
etc..
you terminate the r
