Hi, my apologies if this has been answered before. I was just reading through
the smtpd_policy_readme and documentation on spawn but I'm looking for
clarification of this.
Let's say I have this in main.cf
smtpd_recipient_restrictions =
reject_unauth_destination
check_policy_service inet:127.0.0.1:2222
The readme says also to put a corresponding spawn entry into master.cf. Now I
just tried with a tcp server on port 2222 that always replies dunno but
*without* the spawn entry in master.cf and it works. At least with one
manually produced smtp session.
Is there a reason why I should use spawn? Something like parallelism that I
don't understand?
spawn seems resource intensive and a tcp server would listen, start a new
thread on connect and close the connection after action=... (or probably wait
for the socket being closed)
Thanks for any help
Michael