[opendmarc-users] mkdb.mysql or schema.mysql?
Niklaas Baudet von Gersdorff
stdin at niklaas.eu
Sat Oct 29 12:02:01 PDT 2016
Niklaas Baudet von Gersdorff [2016-10-29 14:47 +0200] :
> On my systems, I'll initialise the database with the patched
> schema.mysql.
So I tried that but running `opendmarc-import` I ran into the
following error:
opendmarc-import: failed to create table ID: Field 'repuri' doesn't have a default value
I stumbled upon the following post. Being quite recent, it might
be of interest for you too:
https://schipka.com/archives/154
Under "Importing with opendmarc-import" the author refers to the
same error message and suggests changing the database scheme.
Following the author's advice I could solve these errors. I had
to change tables `messages` and `requests`:
ALTER TABLE messages MODIFY COLUMN policy_domain int(10) UNSIGNED DEFAULT NULL;
ALTER TABLE requests MODIFY COLUMN adkim tinyint(4) DEFAULT NULL;
ALTER TABLE requests MODIFY COLUMN aspf tinyint(4) DEFAULT NULL;
ALTER TABLE requests MODIFY COLUMN pct tinyint(4) DEFAULT NULL;
ALTER TABLE requests MODIFY COLUMN policy tinyint(4) DEFAULT NULL;
ALTER TABLE requests MODIFY COLUMN repuri VARCHAR(255) DEFAULT NULL;
ALTER TABLE requests MODIFY COLUMN spolicy tinyint(4) DEFAULT NULL;
Can you verify this? In my case, I no longer ran into issues when
executing `opendmarc-import` after these changes.
In the post, the author mentions additional issues. At the end
they write:
I didn’t bother to create a patch or submit bugs properly, but
I may do so in the future.
So I am not sure whether the issues have already been reported,
are real issues, or simply caused by wrong configuration. Any
comment is very much appreciated.
Niklaas
More information about the opendmarc-users
mailing list