Sender notifications - disable? customize?

[Patrick Ben Koetter]

* MRob <mrobti at insiberia.net>:
> I tried setting to undef instead of 0, but warning/notices are still sent
> out by amavis.  So I appear to have a problem with these settings being
> overridden somewhere else(?)(or not understanding the right settings to use)
> but I hope someone can still answer my other questions:

Did you set mynetworks and local_domain_maps? Without these settings amavis
won't be able to tell which directions - inbound/outbound -  mails are
flowing. By default it only notifies recipients who belong to hosts/domains in
local_domain_maps. Without this it won't notify at all.


> - Are there best practices advice about sender notifications?

Don't notify senders for

- spam
- viruses
- unchecked

as the envelope sender is usually forged. You'd end up barking up the wrong
tree and the server might get listed as backscatter server.

Notify senders for:

- banned files



> - 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?

Yes.


> - I cannot find a way to disable them - tried setting these all to 0 but no
> luck: $warnbadhsender $warnbannedsender $warn_offsite

See my remarks on mail flow directions.


> - I'm having a very hard time finding documentation on any of those
> settings, what exactly they do - where can I find that?

There isn't any. Amavis is orphaned.


> - Also, is there a place to customize the message body (and possibly
> headers) for these notifications ("warnings?")?

They are placed within amavis as templates. Which platform do you run amavis
on?

p at rick



> On 2016-11-26 23:34, Dominic Raferd wrote:
> > I don't think there is a way to check what the current active settings
> > are for amavisd-new (nothing like postconf -n) - including all
> > defaults - unfortunately. We can of course check our own settings with
> > something like: grep -r "warn" /etc/amavis/conf.d|grep -v "\s*#"
> > 
> > The defaults that I am aware of are:
> > 
> > $warnbannedsender = undef;
> > $warnbadhsender   = undef;
> > $warn_offsite     = undef;
> > $warnvirusrecip   = undef;
> > $warnbannedrecip  = undef;
> > $warnbadhrecip    = undef;
> > 
> > I presume this means 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 <mrobti at insiberia.net> wrote:
> > 
> > > 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 these all to 0
> > > but no luck: $warnbadhsender $warnbannedsender $warn_offsite
> > > 
> > > I'm having a very hard time finding documentation on any of those
> > > settings, what exactly they do - where can I find that?
> > > 
> > > Also, is there a place to customize the message body (and possibly
> > > headers) for these notifications ("warnings?")?
> > > 
> > > Thank you for your great product.

-- 
[*] sys4 AG
 
https://sys4.de, +49 (89) 30 90 46 64
Schleißheimer Straße 26/MG,80333 München
 
Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein