On Tue, June 26, 2018 16:47, Wietse Venema wrote:
> James B. Byrne:
>> I am configuring a new Postfix-3.3.0 service to act as one of our
>> public MX providers. The address of this new MX service has been
>> published in our DNS but with a lower precedence (higher priority
>> number) than our ac
James B. Byrne:
> I am configuring a new Postfix-3.3.0 service to act as one of our
> public MX providers. The address of this new MX service has been
> published in our DNS but with a lower precedence (higher priority
> number) than our active MX service.
>
> Naturally enough there are countless
I am configuring a new Postfix-3.3.0 service to act as one of our
public MX providers. The address of this new MX service has been
published in our DNS but with a lower precedence (higher priority
number) than our active MX service.
Naturally enough there are countless spam bots regularly hitting
> On Jun 26, 2018, at 1:15 PM, @lbutlr wrote:
>
>> No, it works substantially better in check_sender_access, and very poorly
>> in header_checks.
>
> It works very well for me, and has for years.
The regular expressions you posted are fragile, subject to easy false
posititves and should not
On Jun 26, 2018, at 09:10, Viktor Dukhovni wrote:
> No, it works substantially better in check_sender_access, and very poorly
> in header_checks.
It works very well for me, and has for years.
--
This is my signature. There are many like it, but this one is mine.
> On Jun 26, 2018, at 6:07 AM, @lbutlr wrote:
>
> I use header checks:
>
> /.*\.example.top/ DUNNO
> /.*\.FriendwithJokeDoamin.xxx/ OK
> /.*\.(com|net|org|edu|gov|ca|mx|de|dk|fi|uk|us|tv|info|biz|eu|es|il|it|nl|name|jp|host|au|nz)$/
> DUNNO
> /.*\.*/ 550 Mail to or from this TLD is not allow
Rajneesh Rana:
> hi,
> I have setup postfix using virtualmin on ubuntu 16.04
> Have setup DKIM, MX, SPF etc
> For webmail have setup roundcube and rainloop.
> SSL is setup using let's encrypt.
> Everything works great for emails.
>
> Now we need to restrict some users to be able to send local emai
On 25 Jun 2018, at 14:45, Alex wrote:
> I have a check_sender_access restriction that blocks many TLDs like
> .red and .space. Problem is that we have one legitimate .red customer
> (what was he thinking?) that needs to send us mail. How can I allow
> this single domain?
I use header checks:
/.*
On 06/26/2018 12:03 AM, Viktor Dukhovni wrote:
The EFF announced a certbot plugin for Postfix today, which
is still in beta. A couple of things to keep in mind:
* If you've already deployed DANE, this stands a good chance
of breaking your DANE TLSA records. For the moment do not
dep
> On Jun 26, 2018, at 3:20 AM, Gary wrote:
>
> Am i making a mistake using the same cert for web and email?
Only to the extent that this constrains you operationally
to keep both services on the same key/cert rotation schedule.
From a security perspective, you're probably OK provided you've
Am i making a mistake using the same cert for web and email?
Original Message
From: postfix-us...@dukhovni.org
Sent: June 26, 2018 12:03 AM
To: postfix-users@postfix.org
Reply-to: postfix-users@postfix.org
Subject: New EFF certbot plugin for Postfix
The EFF announced a certbot plugin for P
The EFF announced a certbot plugin for Postfix today, which
is still in beta. A couple of things to keep in mind:
* If you've already deployed DANE, this stands a good chance
of breaking your DANE TLSA records. For the moment do not
deploy this if have inbound DANE.
* Do consider
12 matches
Mail list logo
