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
* Marc Stürmer :
> Am 2016-11-28 14:14, schrieb Patrick Ben Koetter:
>
> > I consider amavis orphaned. It is fully functional and if there are known
> > security issues the author, Mark Martinec, fixes them. He releases a new
> > version of amavis about each year. Submitted
Am 2016-11-28 14:14, schrieb Patrick Ben Koetter:
I consider amavis orphaned. It is fully functional and if there are
known
security issues the author, Mark Martinec, fixes them. He releases a
new
version of amavis about each year. Submitted patches may end up
upstream in
the release. But
* MRob :
> On 2016-11-28 15:34, Patrick Ben Koetter wrote:
> > > Given that you advised sending banned notifications to senders, you
> > > consider the backscatter potential an acceptable risk for keeping that
> > > turned on?
> >
> > It's a calculated risk that tries to
On 2016-11-28 15:34, Patrick Ben Koetter wrote:
* MRob :
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
>
> - spam
> - viruses
> -
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
- spam
- viruses
- unchecked
as the envelope sender is usually forged. You'd end up barking up the
wrong
tree and
* Dino Edwards :
> > There isn't any. Amavis is orphaned.
>
> What does that mean exactly?
The docs that come with the TARball are the ones that exist. It's considered
to be best practice to read the RELEASE_NOTES as they elaborate on new
features and how the work
* MRob :
> 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
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:
- Are there
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
10 matches
Mail list logo