eans there are no warnings issued unless these
variables are set explicitly, and this isn't the case with ubuntu (or
I think debian) standard installations? Are you sure that warnings are
being issued by amavisd-new on your system?
On 26 November 2016 at 22:44, MRob <mro...@insiberia.net> wrote:
riables are set explicitly, and this isn't the case with ubuntu (or
> I think debian) standard installations? Are you sure that warnings are
> being issued by amavisd-new on your system?
>
> On 26 November 2016 at 22:44, MRob <mro...@insiberia.net> wrote:
>
> >
On 2016-11-28 15:34, Patrick Ben Koetter wrote:
* MRob <mro...@insiberia.net>:
Patrick,
Really appreciate your help, especially if Mark's not around here any
more.
> > - Are there best practices advice about sender notifications?
>
> Don't notify senders for
>
Are there best practices advice about sender notifications?
Looks like default is to have notifications ("warnings?") enabled for
attachments with banned file extensions. Doesn't this risk backscatter
problems when sender address is forged?
I cannot find a way to disable them - tried setting
I found a very helpful example on how to write a hook:
https://marc.info/?l=postfix-users=128438735413057=2
But I need to do a SQL lookup in the before_send hook for outbound mail.
Two questions:
What's the most reliable way to retrieve our sending user? I found that
$msginfo->sender seems
Does disabling $warn_offsite prevent ALL non-local notifications
(based on
$mynetworks?)? Should I set it to undef to disable?
I wouldn't use warn_offsite, because it opens the door to backscatter.
I'd
leave it at its default, effectively disabling offsite warnings.
What I'd do instead is
On 2016-12-01 15:54, Tom Johnson wrote:
We're using sa_userpref for a few customers, but the time penalty
that's incurred doing a save of current preferences and a load of the
new ones is starting to hurt.
We've found we're using only a few of the possible settings that can
be used here, and
