Re^2: Postfix: Piping an email into a PERL script

This is definitely something one should think of. My solution is implemented behind the MTA of the network. The MTA takes care of security in my case. I mean as good as it can (DNSBL, spam filter and so on).

The best medicine against depression is a cold beer!

Comment on Re^2: Postfix: Piping an email into a PERL script

Replies are listed 'Best First'.
Re^3: Postfix: Piping an email into a PERL script by MidLifeXis (Monsignor) on Apr 26, 2013 at 15:26 UTC
Is there a need to protect against internal users spoofing this? It is quite easy to speak SMTP. --MidLifeXis	[reply]
Re^4: Postfix: Piping an email into a PERL script by Zzenmonk (Sexton) on Apr 26, 2013 at 15:34 UTC
Indeed! And I do not know how to protect a mail server from faked headers! I mean you can just telnet the port 25 of a MTA and write whatever you want. Mail is a risk, remains a risk and will always remain a risk. The best medicine against depression is a cold beer!	[reply]
Re^5: Postfix: Piping an email into a PERL script by MidLifeXis (Monsignor) on Apr 26, 2013 at 15:42 UTC
Since the transport is insecure, armor the message. See gpg (or the like) as one possible way to assist. It could be set up so that only a validly signed message from an allowed user can pass through. I am not saying you have to go this route, just pointing out some weaknesses in the area of security, and this will probably be the last I say on this particular thread. --MidLifeXis	[reply]
Re^6: Postfix: Piping an email into a PERL script by Zzenmonk (Sexton) on Apr 26, 2013 at 15:51 UTC
Re^7: Postfix: Piping an email into a PERL script by 5mi11er (Deacon) on May 22, 2013 at 12:55 UTC
Some notes below your chosen depth have not been shown here


Keep It Simple, Stupid
	PerlMonks