I'd like to be able to reject mail that contains encrypted content. This is
to satisfy US FCC rules against encrypted content on amateur radio
frequencies. Some of our clients may connect via amateur radio.
I'd like to be able to restrict it only for certain clients. But, as I
understand it,
On 16/07/2016 03:16, /dev/rob0 wrote:
An MX lookup based on client IP is not possible. There are generally
no MX records in "arpa." zones. MX lookup would be based on the
domain in the MAIL FROM: address. That does indeed require SMTP
inspection. As implemented, postscreen does not know the
On Fri, Jul 15, 2016 at 11:00:56PM +0300, Lefteris Tsintjelis wrote:
> On 15/07/2016 16:38, wie...@porcupine.org wrote:
> >That is fundamentally not how postscreen works. postscreen
> >whitelists the client, not the combination (client + SMTP
> >commands). Its purpose is to block bad clients
On 15/07/2016 16:38, wie...@porcupine.org wrote:
That is fundamentally not how postscreen works. postscreen whitelists
the client, not the combination (client + SMTP commands). Its purpose
is to block bad clients with zero overhead for whitelisted clients,
not doing things that require
? ?:
> Hi, people !
>
> Is it possible to multiline short form command arguments in master.cf file.
>
> For example, write this string:
>
> > -o
> >
Lefteris Tsintjelis:
> Is it possible to add points to clients based on valid SPF (-/~all)
> and/or valid MX records? For example, give points to a client if
> it is a valid MX, and/or, give points again if listed in SPF with
> -all, give less points if valid client but SPF is ~all etc.
That is
Вадим Бажов:
Hi, people !
Is it possible to multiline short form command arguments in master.cf file.
For example, write this string:
-o
