|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: mouss (mouss
netoyen.net)
Date: Mon Feb 04 2008 - 01:31:15 CST
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Terry Carmen wrote:
> I'm working on a Postfix Policy server, and I'm a little confused
> about the SMTPD_POLICY_README.html#protocol section.
>
> According to my understanding, the example shows connecting to a
> policyd server via a TCP socket, however there also seems to be a Perl
> script involved
>
> 1 /etc/postfix/master.cf:
> 2 127.0.0.1:9998 inet n n n - 0
> spawn
> 3 user=nobody argv=/usr/bin/perl
> /usr/libexec/postfix/greylist.pl
> 4
> 5 /etc/postfix/main.cf:
> 6 127.0.0.1:9998_time_limit = 3600
>
> My understanding of other processes that connect to TCP sockets is
> that it's a network operation that could connect to anywhere on the
> net, and doesn't require any local files. According to the above
> sample, Postfix should connect to a policy server listening on port
> 9998 on IP 127.0.0.1, send a number of name/value pairs, then listen
> for a response. How is Perl and a local script involved in this
> transaction?
if you don't want to write a server, then postfix will do it for you via
the spawn service. in the example, postfix will listen on 127.0.0.1:9998
and spawn greylist.pl (which will inherit the socket).
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]