On 13/10/17 10:40, Matus UHLAR - fantomas wrote:
the only important part is - you apparently should not use milter on
submission ports.
Am 13.10.2017 um 20:42 schrieb Daniele Nicolodi:
Why?
On 13/10/17 15:30, Robert Schetterer wrote:
some milters are fine to use with submission
others not, i.e clamav-milter should work, spamass-milter
on the other hand may slow down sending mail, which might lead to anger
for users, it needs time to find out spamness of an email by doing i.e
outside network operations with razor etc.
So it simply depends on what you trying to goal .....,rethink of your
whole mail design , look at your logs then choose the tool or tec which
design fits best for desired task
Yes, I should have explained it. Simply said - anything that takes much time
should apparently not be used on submission ports, or you may expect your
users to complain about long mail sending delays.
OTOH, it's more effective when you want to reject mail at SMTP time,
because in that case you don't have to generate bounces.
Just be careful that the processing is done within 10 minutes, which is the
timeout for DATA trermination phase, otherwse you can encounter data
duplication or message retransmission. It may be better to have this under 5
minutes.
On 13.10.17 16:09, Daniele Nicolodi wrote:
This is a much less categorical statement.
The possible issues you point out are not specific to milters, but apply
to all mail filtering techniques.
this applies to smtp proxy and milters, but it doesn't apply to content
filter, since that one applies after mail has been received.
--
Matus UHLAR - fantomas, [email protected] ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Nothing is fool-proof to a talented fool.
