>In other words, this would be a supported way of using ASSP
There is NO support agreement nor a support warranty in assp. If the way
you use assp works - fine. If not, you can try to get answers in the
mailing lists or the forum.
The docu/wiki describs the common ways, how to use assp. But other ways
may be also possible.
>not expect to be told that 'you are using ASSP in an unsupported way so
we cannot help'
Not because you use assp in an "unsupported way" - but because your
envirionment is so unique, that nobody else is using a similar one.
The same would apply to postfix and amavis-new
>So, are you now saying that using ASSP *instead of* amavisd-new,
Yes instead or in addition to amavis-new. Amavis has no API for a
SMTP-proxy - itself is a SMTP-queuing-proxy.
Simply think about what assp is , what amavis is (which API's it has) and
what postfix is (and what it can do).
postfix
_________________
| |
- assp --- amavis -
postfix
_________________
| |
- amavis --- assp -
postfix
_________________
| | | |
- assp - - amavis -
postfix
_________________
| | | |
- amavis - - assp -
postfix
assp -- ________________
| |
- amavis -
I prever the last environment - because all systems are using a standard
configurations. Its on your boss to change his opinion.
All other variants will require a special configuration of all or some
components. You'll not find any worksheet in the web for them.
The first two variants will require special timing configurations
(SMTP-timeout) in assp and amavis.
How ever, keep in mind: you may get any of the first four variants running
using the current available software components - but any update of any of
the components may break your envirionment in future.
I recommend to have a firewall in front of assp. For example pfsense with
snort and/or pfBlockerNG. Both are able to request the extremeExport
content from assp (StatsInterface - http) to learn localy well known bad
IP's, in addition to there default and special lists and policies.
Thomas
Von: "Charles Marcus" <[email protected]>
An: [email protected]
Datum: 12.06.2019 18:20
Betreff: Re: [Assp-test] Question re: ASSP as post-queue filter
On Wed Jun 12 2019 01:39:08 GMT-0400 (Eastern Standard Time), Thomas
Eckardt <[email protected]> wrote:
>integrate ASSP as a post-queue filter using amavisd-new
Don't try this! Use assp instead of amavis-new. The postfix config should
be the same in both cases. The listeners and targets in assp should be
configured according to amavis-new (the same way).
Ok, so, to be clear...
In your first response to my question, you said:
"I never used assp this way. It may be possible to implement assp as a
milter or like amavis-new, but the postfix config and the assp config will
become very complex (IMHO). It may be also the case, that some assp
features will not work like expected: for example block reporting, the
email interface and resend functions. I think you'll need separate
listeners for this purposes."
So, are you now saying that using ASSP *instead of* amavisd-new, I'll be
able to use it and expect the block reporting email interface and re-send
functions to work as advertised?
In other words, this would be a supported way of using ASSP, and if I had
issues, I could come to the list for help and not expect to be told that
'you are using ASSP in an unsupported way so we cannot help'?
I don't mind dealing with problems if this is an unusual but still
supported configuration, as long as I can expect some help fixing any
issues if/when they arise.
For outgoing mails, the config would be different. You'll need to
implement a second post-filter in postfix, with assp's relayPort as
target.
No worries, I'll do whatever is needed, including setting up multiple
postfix instances if necessary.
Thanks!_______________________________________________
Assp-test mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-test
DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential, legally
privileged and protected in law and are intended solely for the use of the
individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no
known virus in this email!
*******************************************************
_______________________________________________
Assp-test mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-test
