2018-11-08 8:49 GMT+01:00 Dominic Raferd :
> On Thu, 8 Nov 2018 at 07:35, Poliman - Serwis wrote:
>
>> I have domain kamir-transport.pl deployed on the server with dns zone
>> where are configured google MX servers like aspmx.l.google.com,
>> alt1.aspmx.l.google.com (and few more). Mailboxes are
Hi, I can see what the error message says . But I confess at this moment, I’m
at a loss as to how to fix it?
Where is it looking for this db?
-DMACOSX -c dict_db.c
dict_db.c:758:2: error: "Unsupported Berkeley DB version"
#error "Unsupported Berkeley DB version"
^
1 error generated.
make: ***
On Thu, 8 Nov 2018 at 08:07, Poliman - Serwis wrote:
>
>
> 2018-11-08 8:49 GMT+01:00 Dominic Raferd :
>
>> On Thu, 8 Nov 2018 at 07:35, Poliman - Serwis wrote:
>>
>>> I have domain kamir-transport.pl deployed on the server with dns zone
>>> where are configured google MX servers like
On 8 Nov 2018, at 8:20 pm, Robert Chalmers wrote:
>
>
> It’s almost through the build but failing on this.
>
> Undefined symbols for architecture x86_64:
> "_db_create", referenced from:
> import-atom in libpostfix-util.dylib
> "_db_env_create", referenced from:
> import-atom in
On 8 Nov 2018, at 2:34, Poliman - Serwis wrote:
Honestly I don't fully understand this log. Looks like google mx says
that
some message from webmas...@kamir-transport.pl belong to ip
54.38.202.128
(what is 15 after ip address?) looks suspicious, although is send to
another mailbox in this
Matus UHLAR - fantomas wrote on Thu, 8 Nov 2018 12:12:49 +0100:
> the problem lies in "parent_domain_matches_subdomains" which is (and should
> be) empty in postfix and apparently even is in new postfix version.
As I wrote earlier, it *is* set implicitely by backwards-compatibilty.
> First I
I’ve been having the same issue. Apple changed their logging system a few
releases ago (Sierra?) to use the Unified Logging System, which logs to RAM
rather than disk files.
I can create the file at /var/log/mail.log, give it correct permissions, etc,
but it remains at 0 bytes.
I have managed
Noel Jones wrote on Wed, 7 Nov 2018 13:30:08 -0600:
With the above list, check_sender_access comes first. Postfix does
not reorder the list you have specified.
On 08.11.18 01:31, Kai Schaetzl wrote:
Thanks for the answer. But, please look again.
/etc/mail/access:
createsend.com REJECT
On 08.11.18 01:31, Kai Schaetzl wrote:
Thanks for the answer. But, please look again.
/etc/mail/access:
createsend.com REJECT
cmail20.com REJECT
On 08.11.18 12:06, Matus UHLAR - fantomas wrote:
you should specify .createsend.com, because the connecting domain is
It’s almost through the build but failing on this.
Undefined symbols for architecture x86_64:
"_db_create", referenced from:
import-atom in libpostfix-util.dylib
"_db_env_create", referenced from:
import-atom in libpostfix-util.dylib
"_db_version", referenced from:
>
> People are telling you the answer, and you're refusing to listen, I
> find this puzzling, unless you're no longer getting email from the
> list (which seems plausible).
I am afraid that my comprehension of what has been written is limited.
I regret the defect but there it is.
> Every MTA
> On Nov 8, 2018, at 9:52 AM, James B. Byrne wrote:
>
> We have been experiencing an prolonged outage at our off-site dns
> location. The two NS in question are located there. The
> establishment of NS at multiple location was intended to handle this
> sort of situation. We are dealing with
> On Nov 8, 2018, at 2:42 AM, James Brown wrote:
>
> I’ve been having the same issue. Apple changed their logging system a few
> releases ago (Sierra?) to use the Unified Logging System, which logs to RAM
> rather than disk files.
It’s been discussed here before. And so far, no one has come
> On Nov 8, 2018, at 10:01 AM, Viktor Dukhovni
> wrote:
>
> My analysis is that some of upstream providers have broken DNSSEC
> implementations that don't handle NSEC3 properly or at all, and
> therefore "authenticated denial of existence" is not working for
> your domain.
>
> If the problem
> On Nov 8, 2018, at 4:20 AM, Robert Chalmers wrote:
>
> s almost through the build but failing on this.
>
> Undefined symbols for architecture x86_64:
> "_db_create", referenced from:
> import-atom in libpostfix-util.dylib
> "_db_env_create", referenced from:
> import-atom in
I appreciate your help on this.
I have visited http://dnsviz.net, rerun the analysis, and followed the
DNS tree from root to leaf. I see this:
DNSKEYalg=8, id=203262048 bit
DNSKEYalg=8, id=21342048 bits (secure)
DSdigest alg=2 (secure)
DNSKEYalg=8, id=21342048 bits (secure)
DNSKEYalg=8,
I picked this up from documentation somewhere:-
/etc/cron.daily/postfix_pfs_edh_regenerate
#!/bin/bash
cd /etc/postfix
umask 022
for legth in 512 1024 2048
do
openssl dhparam -out dh_$legth.tmp $legth && mv dh_$legth.tmp dh_$legth.pem
chmod 644 dh_$legth.pem
done
--
Regards =dn
On 8 Nov 2018, at 01:18, Robert Chalmers wrote:
> Hi, I can see what the error message says . But I confess at this moment, I’m
> at a loss as to how to fix it?
> Where is it looking for this db?
Postix used Berkely db for hash tables (files end in .db) nosema,ly the virtual
file and the alias
On 8 Nov 2018, at 4:20, Robert Chalmers wrote:
It’s almost through the build but failing on this.
Undefined symbols for architecture x86_64:
"_db_create", referenced from:
import-atom in libpostfix-util.dylib
"_db_env_create", referenced from:
import-atom in
19 matches
Mail list logo
