Advanced
Mailing List Archive

Mailing List Archive

  1. Home >
  2. DBMail>
  3. users
Installations problems with dbmail 3.2.3
ballier at mail
Oct 9, 2017, 2:31 AM
Post #1 of 17 (3664 views)
Permalink
Hello,

I installed dbmail 3.2.3 under Ubuntu 16.04.3 after compiling the
sources. Everything was well during compilation and installation. As
an authdriver I have set sql. I have used the script for installation
the database tables. I use sockets (but using tcp/ip there is the same
problem (see below)).

Unfortunately, creating a user does not work.
 
If I use the example from the installation manual (or another example):

dbmail-users -a john -w secret -g 0 -m 25M -s
john@dude.org,john@dude.net,@net.com

I always get in /var/log/mysql/mysql.log the following messages:
 
------------------------------------------------------- BEGIN
mysql.log
-----------------------------------------------------------------------------------------
2017-10-09T09:04:51.880410Z       148 Connect   dbmail@localhost on
dbmail using Socket
2017-10-09T09:04:51.880808Z       149 Connect   dbmail@localhost on
dbmail using Socket
2017-10-09T09:04:51.881104Z       150 Connect   dbmail@localhost on
dbmail using Socket
2017-10-09T09:04:51.881349Z       151 Connect   dbmail@localhost on
dbmail using Socket
2017-10-09T09:04:51.881578Z       152 Connect   dbmail@localhost on
dbmail using Socket
2017-10-09T09:04:51.882028Z       148 Prepare   SELECT 1=1 FROM
dbmail_users LIMIT 1 OFFSET 0
2017-10-09T09:04:51.882295Z       148 Close stmt
2017-10-09T09:04:51.882379Z       148 Prepare   SELECT 1=1 FROM
dbmail_mimeparts LIMIT 1 OFFSET 0
2017-10-09T09:04:51.882577Z       148 Close stmt
2017-10-09T09:04:51.882648Z       148 Prepare   SELECT 1=1 FROM
dbmail_header LIMIT 1 OFFSET 0
2017-10-09T09:04:51.882816Z       148 Close stmt
2017-10-09T09:04:51.883040Z       149 Prepare   SELECT 1=1 FROM
dbmail_upgrade_steps WHERE from_version = ? AND to_version = ?
2017-10-09T09:04:51.883343Z       149 Close stmt
2017-10-09T09:04:51.883508Z       149 Prepare   SELECT 1=1 FROM
dbmail_upgrade_steps WHERE from_version = ? AND to_version = ?
2017-10-09T09:04:51.883713Z       149 Close stmt
2017-10-09T09:04:51.883835Z       149 Prepare   SELECT 1=1 FROM
dbmail_upgrade_steps WHERE from_version = ? AND to_version = ?
2017-10-09T09:04:51.884076Z       149 Close stmt
2017-10-09T09:04:51.884224Z       149 Prepare   SELECT 1=1 FROM
dbmail_upgrade_steps WHERE from_version = ? AND to_version = ?
2017-10-09T09:04:51.884505Z       149 Close stmt
2017-10-09T09:04:51.885030Z       148 Prepare   SELECT user_idnr
FROM dbmail_users WHERE lower(userid) = lower(?)
2017-10-09T09:04:51.885249Z       148 Close stmt
2017-10-09T09:04:51.885449Z       148 Prepare   SELECT user_idnr
FROM dbmail_users WHERE lower(userid) = lower(?)
2017-10-09T09:04:51.885675Z       148 Close stmt
2017-10-09T09:04:51.885755Z       148 Query     START TRANSACTION
2017-10-09T09:04:51.885880Z       148 Prepare   INSERT INTO
dbmail_users (userid,passwd,client_idnr,maxmail_size,encryption_type)
VALUES (?,?,?,?,?)
-------------------------------------------- END mysql.log
----------------------------------------------------------------------------------------------------------------------------------------------------

Nothing happens after the last line. The user is not created.
 
What can I do? What are the question marks?


Thanks
Ralph
Re: Installations problems with dbmail 3.2.3 [ In reply to ]
h.reindl at thelounge
Oct 9, 2017, 6:02 AM
Post #2 of 17 (3663 views)
Permalink
Am 09.10.2017 um 11:31 schrieb Ralph Ballier:
> I installed dbmail 3.2.3 under Ubuntu 16.04.3 after compiling the
> sources. Everything was well during compilation and installation. As an
> authdriver I have set sql. I have used the script for installation the
> database tables. I use sockets (but using tcp/ip there is the same
> problem (see below)).

can't say anything about 3.2.x because i hestiate to give it a try as
long this list and dbmail-upstream at all is that silent

> Nothing happens after the last line. The user is not created.
> What can I do? What are the question marks?

https://dev.mysql.com/doc/refman/5.7/en/sql-syntax-prepared-statements.html
_______________________________________________
DBmail mailing list
DBmail@dbmail.org
http://lists.nfg.nl/mailman/listinfo/dbmail
Re: Installations problems with dbmail 3.2.3 [ In reply to ]
ballier at mail
Oct 11, 2017, 3:14 AM
Post #3 of 17 (3657 views)
Permalink
----- Nachricht von Reindl Harald <h.reindl@thelounge.net> ---------
     Datum: Mon, 9 Oct 2017 15:02:53 +0200
       Von: Reindl Harald <h.reindl@thelounge.net>
Antwort an: DBMail mailinglist <dbmail@dbmail.org>
   Betreff: Re: [Dbmail] Installations problems with dbmail 3.2.3
        An: dbmail@dbmail.org

> Am 09.10.2017 um 11:31 schrieb Ralph Ballier:
>> I installed dbmail 3.2.3 under Ubuntu 16.04.3 after compiling the
>> sources. Everything was well during compilation and installation.
>> As an authdriver I have set sql. I have used the script for
>> installation the database tables. I use sockets (but using tcp/ip
>> there is the same problem (see below)).
>
> can't say anything about 3.2.x because i hestiate to give  it a try
> as long this list and dbmail-upstream at all is that silent
>
>> Nothing happens after the last line. The user is not created.
>> What can I do? What are the question marks?
>
> https://dev.mysql.com/doc/refman/5.7/en/sql-syntax-prepared-statements.html
> _______________________________________________

Thanks for explanation. But what can I do to correct the error?

Do I have correctly understood: you advises to continue using dbmail
because it has no future?
 
By the way, I tried it with MariaDB. Since the set-up of the tables
already fails because an index is double (?)

Greetings
Ralph
Re: Installations problems with dbmail 3.2.3 [ In reply to ]
h.reindl at thelounge
Oct 11, 2017, 3:21 AM
Post #4 of 17 (3657 views)
Permalink
Am 11.10.2017 um 12:14 schrieb Ralph Ballier:
> ----- Nachricht von Reindl Harald <h.reindl@thelounge.net
> <mailto:h.reindl@thelounge.net>> ---------
> ? ? ?Datum: Mon, 9 Oct 2017 15:02:53 +0200
> ? ? ? ?Von: Reindl Harald <h.reindl@thelounge.net
> <mailto:h.reindl@thelounge.net>>
> Antwort an: DBMail mailinglist <dbmail@dbmail.org
> <mailto:dbmail@dbmail.org>>
> ? ?Betreff: Re: [Dbmail] Installations problems with dbmail 3.2.3
> ? ? ? ? An: dbmail@dbmail.org <mailto:dbmail@dbmail.org>
>
>> Am 09.10.2017 um 11:31 schrieb Ralph Ballier:
>>
>>> I installed dbmail 3.2.3 under Ubuntu 16.04.3 after compiling the
>>> sources. Everything was well during compilation and installation. As
>>> an authdriver I have set sql. I have used the script for installation
>>> the database tables. I use sockets (but using tcp/ip there is the
>>> same problem (see below)).
>>>
>> can't say anything about 3.2.x because i hestiate to give? it a try as
>> long this list and dbmail-upstream at all is that silent
>>>
>>> Nothing happens after the last line. The user is not created.
>>> What can I do? What are the question marks?
>>>
>> https://dev.mysql.com/doc/refman/5.7/en/sql-syntax-prepared-statements.html
>> _______________________________________________
>
> Thanks for explanation. But what can I do to correct the error?
>
> Do I have correctly understood: you advises to continue using dbmail
> because it has no future?

i can't say anything except that we use the latest 3.1.17 snapshot for
years now with MariaDB 5.5, 10.0, 10.1 and now 10.2.9 and for now i
don't plan upgrade to 3.2

> By the way, I tried it with MariaDB. Since the set-up of the tables
> already fails because an index is double (?)

as said: i did not touch 3.2 and without proper naming the errors nobody
would be able to help you
_______________________________________________
DBmail mailing list
DBmail@dbmail.org
http://lists.nfg.nl/mailman/listinfo/dbmail
Re: Installations problems with dbmail 3.2.3 [ In reply to ]
ballier at mail
Oct 11, 2017, 2:21 PM
Post #5 of 17 (3654 views)
Permalink
----- Nachricht von Reindl Harald <h.reindl@thelounge.net> ---------
     Datum: Wed, 11 Oct 2017 12:21:34 +0200
       Von: Reindl Harald <h.reindl@thelounge.net>
Antwort an: DBMail mailinglist <dbmail@dbmail.org>
   Betreff: Re: [Dbmail] Installations problems with dbmail 3.2.3
        An: DBMail mailinglist <dbmail@dbmail.org>

> Am 11.10.2017 um 12:14 schrieb Ralph Ballier:
>> ----- Nachricht von Reindl Harald <h.reindl@thelounge.net
>> <mailto:h.reindl@thelounge.net>> ---------
>>      Datum: Mon, 9 Oct 2017 15:02:53 +0200
>>        Von: Reindl Harald <h.reindl@thelounge.net
>> <mailto:h.reindl@thelounge.net>>
>> Antwort an: DBMail mailinglist <dbmail@dbmail.org
>> <mailto:dbmail@dbmail.org>>
>>    Betreff: Re: [Dbmail] Installations problems with dbmail 3.2.3
>>         An: dbmail@dbmail.org <mailto:dbmail@dbmail.org>
>>
>>> Am 09.10.2017 um 11:31 schrieb Ralph Ballier:
>>>
>>>> I installed dbmail 3.2.3 under Ubuntu 16.04.3 after compiling the
>>>> sources. Everything was well during compilation and installation.
>>>> As an authdriver I have set sql. I have used the script for
>>>> installation the database tables. I use sockets (but using tcp/ip
>>>> there is the same problem (see below)).
>>>
>>> can't say anything about 3.2.x because i hestiate to give  it a
>>> try as long this list and dbmail-upstream at all is that silent
>>>> Nothing happens after the last line. The user is not created.
>>>> What can I do? What are the question marks?
>>>
>>> https://dev.mysql.com/doc/refman/5.7/en/sql-syntax-prepared-statements.html
>>> _______________________________________________
>>
>> Thanks for explanation. But what can I do to correct the error?
>>
>> Do I have correctly understood: you advises to continue using
>> dbmail because it has no future?
>
> i can't say anything except that we use the latest 3.1.17 snapshot
> for years now with MariaDB 5.5, 10.0, 10.1 and now 10.2.9 and for
> now i don't plan upgrade to 3.2
>
>> By the way, I tried it with MariaDB. Since the set-up of the tables
>> already fails because an index is double (?)
>
> as said: i did not touch 3.2 and without proper naming the errors
> nobody would be able to help you
> _______________________________________________

Thanks for your answer.

I now use 3.1.17. There is the same error message while set up the
tables using "create_tables.mysql":

ERROR 1005 (HY000) at line 401: Can't create table
`dbmail`.`dbmail_auto_replies` (errno: 121 "Duplicate key on write or
update")

Line 401 of "create_tables.mysql" is this:
CREATE TABLE dbmail_auto_replies (
        user_idnr bigint(20) UNSIGNED DEFAULT '0' NOT NULL,
        start_date DATETIME NOT NULL,
        stop_date DATETIME NOT NULL,
        reply_body MEDIUMTEXT,
        INDEX user_idnr_index (user_idnr),
        FOREIGN KEY user_idnr_fk (user_idnr)
                REFERENCES dbmail_users (user_idnr) ON DELETE
CASCADE ON UPDATE CASCADE
) ENGINE InnoDB DEFAULT CHARSET=utf8;
 
Re: Installations problems with dbmail 3.2.3 [ In reply to ]
sandino at sandino
Oct 12, 2017, 1:45 AM
Post #6 of 17 (3653 views)
Permalink
On 11/10/17 05:21, Reindl Harald wrote:
>
>>
>>> Am 09.10.2017 um 11:31 schrieb Ralph Ballier:
>>>
>>>> I installed dbmail 3.2.3 under Ubuntu 16.04.3 after compiling the
>>>> sources. Everything was well during compilation and installation.
>>>> As an authdriver I have set sql. I have used the script for
>>>> installation the database tables. I use sockets (but using tcp/ip
>>>> there is the same problem (see below)).
>>>>
>>> can't say anything about 3.2.x because i hestiate to give? it a try
>>> as long this list and dbmail-upstream at all is that silent
I have been using dbmail 3.2 for 2 years with PostgreSQL. It has been
running stable all this time.
I don't trust MySQL to store my clients' e-mails.
I only had to patch a couple of lines in dm_db.c because insertion into
dbmail_messages was returning the OID instead of message_idnr.

--
Sandino Araico S?nchez
http://sandino.net
Re: Installations problems with dbmail 3.2.3 [ In reply to ]
sandino at sandino
Oct 12, 2017, 2:00 AM
Post #7 of 17 (3653 views)
Permalink
On 11/10/17 16:21, Ralph Ballier wrote:
>
> ----- Nachricht von Reindl Harald <h.reindl@thelounge.net
> <mailto:h.reindl@thelounge.net>> ---------
> ? ? ?Datum: Wed, 11 Oct 2017 12:21:34 +0200
> ? ? ? ?Von: Reindl Harald <h.reindl@thelounge.net
> <mailto:h.reindl@thelounge.net>>
> Antwort an: DBMail mailinglist <dbmail@dbmail.org
> <mailto:dbmail@dbmail.org>>
> ? ?Betreff: Re: [Dbmail] Installations problems with dbmail 3.2.3
> ? ? ? ? An: DBMail mailinglist <dbmail@dbmail.org
> <mailto:dbmail@dbmail.org>>
>
>> Am 11.10.2017 um 12:14 schrieb Ralph Ballier:
>>
>>> ----- Nachricht von Reindl Harald <h.reindl@thelounge.net
>>> <mailto:h.reindl@thelounge.net> <mailto:h.reindl@thelounge.net>>
>>> <mailto:h.reindl@thelounge.net%3E%3E> ---------
>>> ? ? ?Datum: Mon, 9 Oct 2017 15:02:53 +0200
>>> ? ? ? ?Von: Reindl Harald <h.reindl@thelounge.net
>>> <mailto:h.reindl@thelounge.net> <mailto:h.reindl@thelounge.net>>
>>> <mailto:h.reindl@thelounge.net%3E%3E>
>>> Antwort an: DBMail mailinglist <dbmail@dbmail.org
>>> <mailto:dbmail@dbmail.org> <mailto:dbmail@dbmail.org>>
>>> <mailto:dbmail@dbmail.org%3E%3E>
>>> ? ?Betreff: Re: [Dbmail] Installations problems with dbmail 3.2.3
>>> ? ? ? ? An: dbmail@dbmail.org <mailto:dbmail@dbmail.org>
>>> <mailto:dbmail@dbmail.org> <mailto:dbmail@dbmail.org%3E>
>>>
>>>> Am 09.10.2017 um 11:31 schrieb Ralph Ballier:
>>>>
>>>>> I installed dbmail 3.2.3 under Ubuntu 16.04.3 after compiling the
>>>>> sources. Everything was well during compilation and installation.
>>>>> As an authdriver I have set sql. I have used the script for
>>>>> installation the database tables. I use sockets (but using tcp/ip
>>>>> there is the same problem (see below)).
>>>>>
>>>> can't say anything about 3.2.x because i hestiate to give? it a try
>>>> as long this list and dbmail-upstream at all is that silent
>>>>>
>>>>> Nothing happens after the last line. The user is not created.
>>>>> What can I do? What are the question marks?
>>>>>
>>>> https://dev.mysql.com/doc/refman/5.7/en/sql-syntax-prepared-statements.html
>>>> _______________________________________________
>>> Thanks for explanation. But what can I do to correct the error?
>>>
>>> Do I have correctly understood: you advises to continue using dbmail
>>> because it has no future?
>> i can't say anything except that we use the latest 3.1.17 snapshot
>> for years now with MariaDB 5.5, 10.0, 10.1 and now 10.2.9 and for now
>> i don't plan upgrade to 3.2
>>>
>>> By the way, I tried it with MariaDB. Since the set-up of the tables
>>> already fails because an index is double (?)
>>>
>> as said: i did not touch 3.2 and without proper naming the errors
>> nobody would be able to help you
>> _______________________________________________
>
> Thanks for your answer.
>
> I now use 3.1.17. There is the same error message while set up the
> tables using "create_tables.mysql":
>
> ERROR 1005 (HY000) at line 401: Can't create table
> `dbmail`.`dbmail_auto_replies` (errno: 121 "Duplicate key on write or
> update")
>
MySQL error 1005 is an incorrect foreign key. In this case a duplicate
key in dbmail_users.user_idnr.

You must fix all duplicate keys in dbmail_users (there might be more
than one) before table dbmail_auto_replies? can be created .
>
>
> Line 401 of "create_tables.mysql" is this:
> CREATE TABLE dbmail_auto_replies (
> ? ? ? ? user_idnr bigint(20) UNSIGNED DEFAULT '0' NOT NULL,
> ? ? ? ? start_date DATETIME NOT NULL,
> ? ? ? ? stop_date DATETIME NOT NULL,
> ? ? ? ? reply_body MEDIUMTEXT,
> ? ? ? ? INDEX user_idnr_index (user_idnr),
> ? ? ? ? FOREIGN KEY user_idnr_fk (user_idnr)
> ? ? ? ? ? ? ? ? REFERENCES dbmail_users (user_idnr) ON DELETE CASCADE
> ON UPDATE CASCADE
> ) ENGINE InnoDB DEFAULT CHARSET=utf8;
> ?
>
>
> _______________________________________________
> DBmail mailing list
> DBmail@dbmail.org
> http://lists.nfg.nl/mailman/listinfo/dbmail


--
Sandino Araico S?nchez
http://sandino.net
Re: Installations problems with dbmail 3.2.3 [ In reply to ]
ballier at mail
Oct 12, 2017, 2:33 AM
Post #8 of 17 (3653 views)
Permalink
----- Nachricht von Sandino Araico Sánchez <sandino@sandino.net> ---------
     Datum: Thu, 12 Oct 2017 04:00:17 -0500
       Von: Sandino Araico Sánchez <sandino@sandino.net>
Antwort an: DBMail mailinglist <dbmail@dbmail.org>
   Betreff: Re: [Dbmail] Installations problems with dbmail 3.2.3
        An: DBMail mailinglist <dbmail@dbmail.org>, Ralph Ballier
<ballier@mail.schule.de>

[..............]

>> Thanks for your answer.

>> I now use 3.1.17. There is the same error message while set up the
>> tables using "create_tables.mysql":

>> ERROR 1005 (HY000) at line 401: Can't create table
>> `dbmail`.`dbmail_auto_replies` (errno: 121 "Duplicate key on write
>> or update")
>> MySQL error 1005 is an incorrect foreign key. In this case a
>> duplicate key in dbmail_users.user_idnr.

> You must fix all duplicate keys in dbmail_users (there might be more
> than one) before table dbmail_auto_replies  can be created .

Yes, you are right. I find two identical lines in "CREATE TABLE
dbmail_auto_notifications" and in "CREATE TABLE dbmail_auto_replies"
(see below).

But what do you mean with "fix it"? Shall I delete the words FOREIGN
KEY? If yes, in the first or in the second CREATE statement? Or in both?

Thanks

Ralph

CREATE TABLE dbmail_auto_notifications (
        user_idnr bigint(20) UNSIGNED NOT NULL,
        notify_address varchar(100) NOT NULL default '',
        INDEX user_idnr_index (user_idnr),
        FOREIGN KEY USER_IDNR_FK (USER_IDNR)
                REFERENCES dbmail_users (user_idnr) ON DELETE
CASCADE ON UPDATE CASCADE
) ENGINE InnoDB DEFAULT CHARSET=utf8;
 
DROP TABLE IF EXISTS dbmail_auto_replies;
CREATE TABLE dbmail_auto_replies (
        user_idnr bigint(20) UNSIGNED DEFAULT '0' NOT NULL,
        start_date DATETIME NOT NULL,
        stop_date DATETIME NOT NULL,
        reply_body MEDIUMTEXT,
        INDEX user_idnr_index (user_idnr),
        FOREIGN KEY USER_IDNR_FK (USER_IDNR)
                REFERENCES dbmail_users (user_idnr) ON DELETE
CASCADE ON UPDATE CASCADE
) ENGINE InnoDB DEFAULT CHARSET=utf8;
 

>  
>  
Re: Installations problems with dbmail 3.2.3 [ In reply to ]
abrancatelli at schema31
Oct 12, 2017, 4:08 AM
Post #9 of 17 (3653 views)
Permalink
Dear Ralph.

I strongly suggest you to use dbmailt 3.2.x and not 3.1.x which is a
dead branch.

We've been using dbmail 3.2.x since almost two years hosting thousands
(as of now, 48962 exactly) mailboxes without a glitch on MySQL 5.6.

I never used MariaDB but I prefer to stick on officially supported
software, especially with new MySQL's roadmap.

As for your problem with those tables, it's pretty strange you have
problem with the init SQL as I recall it to be pretty straightforward...


Anyhow, that's the definition for those two tables:

CREATE TABLE `dbmail_auto_replies` (
`user_idnr` bigint(20) unsigned NOT NULL DEFAULT '0',
`start_date` datetime NOT NULL,
`stop_date` datetime NOT NULL,
`reply_body` mediumtext,
KEY `user_idnr_index` (`user_idnr`),
CONSTRAINT `dbmail_auto_replies_ibfk_1` FOREIGN KEY (`user_idnr`)
REFERENCES `dbmail_users` (`user_idnr`) ON DELETE CASCADE ON UPDATE
CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

CREATE TABLE `dbmail_auto_notifications` (
`user_idnr` bigint(20) unsigned NOT NULL,
`notify_address` varchar(100) NOT NULL DEFAULT '',
KEY `user_idnr_index` (`user_idnr`),
CONSTRAINT `dbmail_auto_notifications_ibfk_1` FOREIGN KEY (`user_idnr`)
REFERENCES `dbmail_users` (`user_idnr`) ON DELETE CASCADE ON UPDATE
CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

---

Andrea Brancatelli
Schema31 S.p.a.
Chief Technology Officier

ROMA - FI - PA
ITALY
Tel: +39.06.98.358.472
Cell: +39.331.2488468
Fax: +39.055.71.880.466
Società del Gruppo OVIDIO TECH S.R.L.

On 2017-10-12 11:33, Ralph Ballier wrote:

> ----- Nachricht von Sandino Araico Sánchez <sandino@sandino.net> ---------
> Datum: Thu, 12 Oct 2017 04:00:17 -0500
> Von: Sandino Araico Sánchez <sandino@sandino.net>
> Antwort an: DBMail mailinglist <dbmail@dbmail.org>
> Betreff: Re: [Dbmail] Installations problems with dbmail 3.2.3
> An: DBMail mailinglist <dbmail@dbmail.org>, Ralph Ballier <ballier@mail.schule.de>
>
> [..............]
>
>>> Thanks for your answer.
>
>>> I now use 3.1.17. There is the same error message while set up the tables using "create_tables.mysql":
>
>>> ERROR 1005 (HY000) at line 401: Can't create table `dbmail`.`dbmail_auto_replies` (errno: 121 "Duplicate key on write or update")
>
>>> MySQL error 1005 is an incorrect foreign key. In this case a duplicate key in dbmail_users.user_idnr.
>
>> You must fix all duplicate keys in dbmail_users (there might be more than one) before table dbmail_auto_replies can be created .
>
> Yes, you are right. I find two identical lines in "CREATE TABLE dbmail_auto_notifications" and in "CREATE TABLE dbmail_auto_replies" (see below).
>
> But what do you mean with "fix it"? Shall I delete the words FOREIGN KEY? If yes, in the first or in the second CREATE statement? Or in both?
>
> Thanks
>
> Ralph
> CREATE TABLE dbmail_auto_notifications (
> user_idnr bigint(20) UNSIGNED NOT NULL,
> notify_address varchar(100) NOT NULL default '',
> INDEX user_idnr_index (user_idnr),
> FOREIGN KEY USER_IDNR_FK (USER_IDNR)
> REFERENCES dbmail_users (user_idnr) ON DELETE CASCADE ON UPDATE CASCADE
> ) ENGINE InnoDB DEFAULT CHARSET=utf8;
>
> DROP TABLE IF EXISTS dbmail_auto_replies;
> CREATE TABLE dbmail_auto_replies (
> user_idnr bigint(20) UNSIGNED DEFAULT '0' NOT NULL,
> start_date DATETIME NOT NULL,
> stop_date DATETIME NOT NULL,
> reply_body MEDIUMTEXT,
> INDEX user_idnr_index (user_idnr),
> FOREIGN KEY USER_IDNR_FK (USER_IDNR)
> REFERENCES dbmail_users (user_idnr) ON DELETE CASCADE ON UPDATE CASCADE
> ) ENGINE InnoDB DEFAULT CHARSET=utf8;
>
>>
>
> _______________________________________________
> DBmail mailing list
> DBmail@dbmail.org
> http://lists.nfg.nl/mailman/listinfo/dbmail
Re: Installations problems with dbmail 3.2.3 [ In reply to ]
h.reindl at thelounge
Oct 12, 2017, 4:24 AM
Post #10 of 17 (3653 views)
Permalink
Am 12.10.2017 um 13:08 schrieb Andrea Brancatelli:
> Dear Ralph.
>
> I strongly suggest you to use dbmailt 3.2.x and not 3.1.x which is a
> dead branch.

problem is that the 3.2 branch is also not very alive

> We've been using dbmail 3.2.x since almost two years hosting thousands
> (as of now, 48962 exactly) mailboxes without a glitch on MySQL 5.6.

well, and the only person i knew which was also using dbmail tried 3.2
in the hope to get rid of permanent customer complaints about IMAP and
had finally enough that he completly migrated to dovecot

> I never used MariaDB but I prefer to stick on officially supported
> software, especially with new MySQL's roadmap.

define officially supported - looking at the changes from the last 3
years there happened nothing in dbmail which would be related to mysql
and at the end libzdb is the piece who is talking to the database server

BUT looking that RHEL no longer ships oracle MySQl and most other
distributions switched to MariaDB as well as big players like Wikipedia
Oracle MySQL is dead - period
_______________________________________________
DBmail mailing list
DBmail@dbmail.org
http://lists.nfg.nl/mailman/listinfo/dbmail
Re: Installations problems with dbmail 3.2.3 [ In reply to ]
sandino at sandino
Oct 12, 2017, 4:32 AM
Post #11 of 17 (3653 views)
Permalink
On 12/10/17 04:33, Ralph Ballier wrote:
>
> ----- Nachricht von Sandino Araico S?nchez <sandino@sandino.net
> <mailto:sandino@sandino.net>> ---------
> ? ? ?Datum: Thu, 12 Oct 2017 04:00:17 -0500
> ? ? ? ?Von: Sandino Araico S?nchez <sandino@sandino.net
> <mailto:sandino@sandino.net>>
> Antwort an: DBMail mailinglist <dbmail@dbmail.org
> <mailto:dbmail@dbmail.org>>
> ? ?Betreff: Re: [Dbmail] Installations problems with dbmail 3.2.3
> ? ? ? ? An: DBMail mailinglist <dbmail@dbmail.org
> <mailto:dbmail@dbmail.org>>, Ralph Ballier <ballier@mail.schule.de
> <mailto:ballier@mail.schule.de>>
>
> [..............]
>
> >> Thanks for your answer.
>
> >> I now use 3.1.17. There is the same error message while set up the
> tables using "create_tables.mysql":
>
> >> ERROR 1005 (HY000) at line 401: Can't create table
> `dbmail`.`dbmail_auto_replies` (errno: 121 "Duplicate key on write or
> update")
>
> >> MySQL error 1005 is an incorrect foreign key. In this case a
> duplicate key in dbmail_users.user_idnr.
>
> > You must fix all duplicate keys in dbmail_users (there might be more
> than one) before table dbmail_auto_replies? can be created .
>
> Yes, you are right. I find two identical lines in "CREATE TABLE
> dbmail_auto_notifications" and in "CREATE TABLE dbmail_auto_replies"
> (see below).
>
> But what do you mean with "fix it"? Shall I delete the words FOREIGN
> KEY? If yes, in the first or in the second CREATE statement? Or in both?
>
I mean look for two records with the same user_idnr in table
dbmail_users; when found delete one of them and keep the other.
If table dbmail-users is empty and you keep receiving this error 1005
you might have a corrupted database.
>
>
> Thanks
>
> Ralph
>
> CREATE TABLE dbmail_auto_notifications (
> ? ? ? ? user_idnr bigint(20) UNSIGNED NOT NULL,
> ? ? ? ? notify_address varchar(100) NOT NULL default '',
> ? ? ? ? INDEX user_idnr_index (user_idnr),
> *? ? ? ? FOREIGN KEY user_idnr_fk (user_idnr)*
> ? ? ? ? ? ? ? ? REFERENCES dbmail_users (user_idnr) ON DELETE CASCADE
> ON UPDATE CASCADE
> ) ENGINE InnoDB DEFAULT CHARSET=utf8;
> ?
> DROP TABLE IF EXISTS dbmail_auto_replies;
> CREATE TABLE dbmail_auto_replies (
> ? ? ? ? user_idnr bigint(20) UNSIGNED DEFAULT '0' NOT NULL,
> ? ? ? ? start_date DATETIME NOT NULL,
> ? ? ? ? stop_date DATETIME NOT NULL,
> ? ? ? ? reply_body MEDIUMTEXT,
> ? ? ? ? INDEX user_idnr_index (user_idnr),
> *? ? ? ? FOREIGN KEY user_idnr_fk (user_idnr)*
> ? ? ? ? ? ? ? ? REFERENCES dbmail_users (user_idnr) ON DELETE CASCADE
> ON UPDATE CASCADE
> ) ENGINE InnoDB DEFAULT CHARSET=utf8;
> ?
>>
>> ?
>>
>> ?
>
>
> _______________________________________________
> DBmail mailing list
> DBmail@dbmail.org
> http://lists.nfg.nl/mailman/listinfo/dbmail


--
Sandino Araico S?nchez
http://sandino.net
Re: Installations problems with dbmail 3.2.3 [ In reply to ]
abrancatelli at schema31
Oct 12, 2017, 4:59 AM
Post #12 of 17 (3653 views)
Permalink
RHEL doesn't ship MySQL as default anymore just because of licensing
issues, not because of any problem of any kind. You basically just have
to download the RPMs from Oracle site, not a big deal, I'd say.

As per MySQL roadmap you can easily read major things from 5.7 here:

https://dev.mysql.com/doc/refman/5.7/en/mysql-nutshell.html

And from 8.0 here:

https://dev.mysql.com/doc/refman/8.0/en/mysql-nutshell.html

To me the major interesting points are the speed optimizations, the JSON
formats, the Memcached interfaces.

Remember that, although I can see pretty clearly Oracle's pretty closed
mindset, MySQL's codebase is backed by many commits from Facebook and
other big player.

Just take a look at https://www.facebook.com/MySQLatFacebook/ if you're
curious, there are a lot of performances checks monitorings and many
other interesting related things.

---

Andrea Brancatelli
Schema31 S.p.a.
Chief Technology Officier

ROMA - FI - PA
ITALY
Tel: +39.06.98.358.472
Cell: +39.331.2488468
Fax: +39.055.71.880.466
Società del Gruppo OVIDIO TECH S.R.L.

On 2017-10-12 13:24, Reindl Harald wrote:

> Am 12.10.2017 um 13:08 schrieb Andrea Brancatelli:
>
>> Dear Ralph.
>>
>> I strongly suggest you to use dbmailt 3.2.x and not 3.1.x which is a dead branch.
>
> problem is that the 3.2 branch is also not very alive
>
>> We've been using dbmail 3.2.x since almost two years hosting thousands (as of now, 48962 exactly) mailboxes without a glitch on MySQL 5.6.
>
> well, and the only person i knew which was also using dbmail tried 3.2 in the hope to get rid of permanent customer complaints about IMAP and had finally enough that he completly migrated to dovecot
>
>> I never used MariaDB but I prefer to stick on officially supported software, especially with new MySQL's roadmap.
>
> define officially supported - looking at the changes from the last 3 years there happened nothing in dbmail which would be related to mysql and at the end libzdb is the piece who is talking to the database server
>
> BUT looking that RHEL no longer ships oracle MySQl and most other distributions switched to MariaDB as well as big players like Wikipedia Oracle MySQL is dead - period
> _______________________________________________
> DBmail mailing list
> DBmail@dbmail.org
> http://lists.nfg.nl/mailman/listinfo/dbmail
Re: Installations problems with dbmail 3.2.3 [ In reply to ]
h.reindl at thelounge
Oct 12, 2017, 5:05 AM
Post #13 of 17 (3653 views)
Permalink
Am 12.10.2017 um 13:59 schrieb Andrea Brancatelli:
> RHEL doesn't ship MySQL as default anymore just because of licensing
> issues, not because of any problem of any kind

stop speading nonsense - especially don#t explain me as a heavy
Fedora/RHEL users reading all developemnt lists for a decade decisions
of Redhat please

it does because the direct upstream Fedora switched years ago and if
licensing problems would be the reason Fedora would not at the same time
contain "community-mysql" in the repos which is in fact Oralce MySQL

here some backkround
https://fedoraproject.org/wiki/Features/ReplaceMySQLwithMariaDB
_______________________________________________
DBmail mailing list
DBmail@dbmail.org
http://lists.nfg.nl/mailman/listinfo/dbmail
Re: Installations problems with dbmail 3.2.3 [ In reply to ]
abrancatelli at schema31
Oct 12, 2017, 5:17 AM
Post #14 of 17 (3653 views)
Permalink
Don't be rude.

What I'm saying is exactly reported in the link you gave:

"The original company behind MySQL, MySQL AB, were bought out by Sun
which was then bought by Oracle. Recent changes made by Oracle indicate
they are moving the MySQL project to be more closed. They are no longer
publishing any useful information about security issues (CVEs), and they
are not providing complete regression tests any more, and a very large
fraction of the mysql bug database is now not public.

MariaDB, which was founded by some of the original MySQL developers, has
a more open-source attitude and an active community. We have found them
to be much easier to work with, especially in regards to security
matters."

Read it differently: a few years ago a lot of FUD was spread abut MySQL
going closed, but that didn't happen.

The only nonsense here is your statement:

_"BUT looking that RHEL no longer ships oracle MySQl and most other
distributions switched to MariaDB as well as big players like Wikipedia
Oracle MySQL is dead - period"_

Actually, as you said a few minutes later, RHEL ships Oracle MySQL as
"community-mysql", as do FreeBSD, and any other distribution.

Oracle MySQL is not dead at all, and was actually faster than MariaDB (
https://mariadb.org/maria-10-1-mysql-5-7-commodity-hardware/ )
previously and it's actually probably faster now as MySQL 8 is faster
than MySQL 5.7 (
http://dimitrik.free.fr/blog/archives/2017/10/mysql-performance-21m-qps-on-80rc.html
).

BTW, relax, none of this is gonna change our life - we're just talking.

Use whatever you prefer, for the reason you like.

---

Andrea Brancatelli
Schema31 S.p.a.
Chief Technology Officier

ROMA - FI - PA
ITALY
Tel: +39.06.98.358.472
Cell: +39.331.2488468
Fax: +39.055.71.880.466
Società del Gruppo OVIDIO TECH S.R.L.

On 2017-10-12 14:05, Reindl Harald wrote:

> Am 12.10.2017 um 13:59 schrieb Andrea Brancatelli:
>
>> RHEL doesn't ship MySQL as default anymore just because of licensing issues, not because of any problem of any kind
>
> stop speading nonsense - especially don#t explain me as a heavy Fedora/RHEL users reading all developemnt lists for a decade decisions of Redhat please
>
> it does because the direct upstream Fedora switched years ago and if licensing problems would be the reason Fedora would not at the same time contain "community-mysql" in the repos which is in fact Oralce MySQL
>
> here some backkround
> https://fedoraproject.org/wiki/Features/ReplaceMySQLwithMariaDB
> _______________________________________________
> DBmail mailing list
> DBmail@dbmail.org
> http://lists.nfg.nl/mailman/listinfo/dbmail
Re: Installations problems with dbmail 3.2.3 [ In reply to ]
h.reindl at thelounge
Oct 12, 2017, 5:25 AM
Post #15 of 17 (3653 views)
Permalink
> Actually, as you said a few minutes later, RHEL ships Oracle MySQL as
> "community-mysql", as do FreeBSD, and any other distribution

sorry, but when you can't distinct between Fedora and RHEL any
discussion is worthless - RHEL don't ship MySQL but you pretended
"because of license issues" which is not true

Am 12.10.2017 um 14:17 schrieb Andrea Brancatelli:
> Don't be rude.
>
> What I'm saying is exactly reported in the link you gave:

no you pretended "RHEL doesn't ship MySQL as default anymore just
because of licensing issues"

> "The original company behind MySQL, MySQL AB, were bought out by Sun
> which was then bought by Oracle. Recent changes made by Oracle indicate
> they are moving the MySQL project to be more closed. They are no longer
> publishing any useful information about security issues (CVEs), and they
> are not providing complete regression tests any more, and a very large
> fraction of the mysql bug database is now not public.
>
> MariaDB, which was founded by some of the original MySQL developers, has
> a more open-source attitude and an active community. We have found them
> to be much easier to work with, especially in regards to security matters."
>
> Read it differently: a few years ago a lot of FUD was spread abut MySQL
> going closed, but that didn't happen.

but the issues above still existst

> The only nonsense here is your statement:
>
> /"BUT looking that RHEL no longer ships oracle MySQl and most other
> distributions switched to MariaDB as well as big players like Wikipedia
> Oracle MySQL is dead - period"/
>
> Actually, as you said a few minutes later, RHEL ships Oracle MySQL as
> "community-mysql", as do FreeBSD, and any other distribution.

RHEL *does not* ship MySQL
you need to realize that RHEL != Fedora

fact is most Linux distributions ship MySQL any longer as default

> Oracle MySQL is not dead at all, and was actually faster than MariaDB (
> https://mariadb.org/maria-10-1-mysql-5-7-commodity-hardware/ )
> previously and it's actually probably faster now as MySQL 8 is faster
> than MySQL 5.7 (
> http://dimitrik.free.fr/blog/archives/2017/10/mysql-performance-21m-qps-on-80rc.html ).

may i suggest that you inform yourself somehow about MariaDB, what get
backported, what version of InnoDB it uses and so on as you said "I
never used MariaDB" while MariaDB users don't say the same about Oracle
MySQL - comparing MariaDB 10.1 with MySQL 5.7 is nonsense because 10.1
used a older XtraDB generation while 10.2 is at MySQL 5.7 level

2017-10-12 14:23:53 140276216588608 [Note] InnoDB: 5.7.19 started; log
sequence number 16262762714
2017-10-12 14:23:53 140275703867136 [Note] InnoDB: Loading buffer
pool(s) from /mnt/data/db/mysql-srv/ib_buffer_pool

> BTW, relax, none of this is gonna change our life - we're just talking.
>
> Use whatever you prefer, for the reason you like

i don't care much but you are talking about "supported software"
_______________________________________________
DBmail mailing list
DBmail@dbmail.org
http://lists.nfg.nl/mailman/listinfo/dbmail
Re: Installations problems with dbmail 3.2.3 [ In reply to ]
abrancatelli at schema31
Oct 12, 2017, 7:09 AM
Post #16 of 17 (3642 views)
Permalink
Harald,

it's ok ????????

---

Andrea Brancatelli
Schema31 S.p.a.
Chief Technology Officier

ROMA - FI - PA
ITALY
Tel: +39.06.98.358.472
Cell: +39.331.2488468
Fax: +39.055.71.880.466
Società del Gruppo OVIDIO TECH S.R.L.

On 2017-10-12 14:25, Reindl Harald wrote:

>> Actually, as you said a few minutes later, RHEL ships Oracle MySQL as
>> "community-mysql", as do FreeBSD, and any other distribution
>
> sorry, but when you can't distinct between Fedora and RHEL any discussion is worthless - RHEL don't ship MySQL but you pretended "because of license issues" which is not true
>
> Am 12.10.2017 um 14:17 schrieb Andrea Brancatelli:
>
>> Don't be rude.
>>
>> What I'm saying is exactly reported in the link you gave:
>
> no you pretended "RHEL doesn't ship MySQL as default anymore just because of licensing issues"
>
>> "The original company behind MySQL, MySQL AB, were bought out by Sun which was then bought by Oracle. Recent changes made by Oracle indicate they are moving the MySQL project to be more closed. They are no longer publishing any useful information about security issues (CVEs), and they are not providing complete regression tests any more, and a very large fraction of the mysql bug database is now not public.
>>
>> MariaDB, which was founded by some of the original MySQL developers, has a more open-source attitude and an active community. We have found them to be much easier to work with, especially in regards to security matters."
>>
>> Read it differently: a few years ago a lot of FUD was spread abut MySQL going closed, but that didn't happen.
>
> but the issues above still existst
>
>> The only nonsense here is your statement:
>>
>> /"BUT looking that RHEL no longer ships oracle MySQl and most other distributions switched to MariaDB as well as big players like Wikipedia Oracle MySQL is dead - period"/
>>
>> Actually, as you said a few minutes later, RHEL ships Oracle MySQL as "community-mysql", as do FreeBSD, and any other distribution.
>
> RHEL *does not* ship MySQL
> you need to realize that RHEL != Fedora
>
> fact is most Linux distributions ship MySQL any longer as default
>
>> Oracle MySQL is not dead at all, and was actually faster than MariaDB ( https://mariadb.org/maria-10-1-mysql-5-7-commodity-hardware/ [1]) previously and it's actually probably faster now as MySQL 8 is faster than MySQL 5.7 ( http://dimitrik.free.fr/blog/archives/2017/10/mysql-performance-21m-qps-on-80rc.html [2]).
>
> may i suggest that you inform yourself somehow about MariaDB, what get backported, what version of InnoDB it uses and so on as you said "I never used MariaDB" while MariaDB users don't say the same about Oracle MySQL - comparing MariaDB 10.1 with MySQL 5.7 is nonsense because 10.1 used a older XtraDB generation while 10.2 is at MySQL 5.7 level
>
> 2017-10-12 14:23:53 140276216588608 [Note] InnoDB: 5.7.19 started; log sequence number 16262762714
> 2017-10-12 14:23:53 140275703867136 [Note] InnoDB: Loading buffer pool(s) from /mnt/data/db/mysql-srv/ib_buffer_pool
>
>> BTW, relax, none of this is gonna change our life - we're just talking.
>>
>> Use whatever you prefer, for the reason you like
>
> i don't care much but you are talking about "supported software"
> _______________________________________________
> DBmail mailing list
> DBmail@dbmail.org
> http://lists.nfg.nl/mailman/listinfo/dbmail


Links:
------
[1]
https://mariadb.org/maria-10-1-mysql-5-7-commodity-hardware/&Acirc;&nbsp;
[2]
http://dimitrik.free.fr/blog/archives/2017/10/mysql-performance-21m-qps-on-80rc.html&Acirc;&nbsp;
Re: Installations problems with dbmail 3.2.3 [ In reply to ]
ballier at mail
Oct 12, 2017, 7:19 AM
Post #17 of 17 (3642 views)
Permalink
----- Nachricht von Andrea Brancatelli <abrancatelli@schema31.it> ---------
  Datum: Thu, 12 Oct 2017 13:08:09 +0200
    Von: Andrea Brancatelli <abrancatelli@schema31.it>
Betreff: Re: [Dbmail] Installations problems with dbmail 3.2.3
     An: DBMail mailinglist <dbmail@dbmail.org>
     Cc: Ralph Ballier <ballier@mail.schule.de>

> Dear Ralph.
>
> I strongly suggest you to use dbmailt 3.2.x and not 3.1.x which is
> a dead branch.
>
> We've been using dbmail 3.2.x since almost two years hosting
> thousands (as of now, 48962 exactly) mailboxes without a glitch on
> MySQL 5.6.
>
> I never used MariaDB but I prefer to stick on officially supported
> software, especially with new MySQL's roadmap.
>
> As for your problem with those tables, it's pretty strange you
> have problem with the init SQL as I recall it to be pretty
> straightforward...
>
> Anyhow, that's the definition for those two tables:
>
>  
>
> CREATE TABLE `dbmail_auto_replies` (
> `user_idnr` bigint(20) unsigned NOT NULL DEFAULT '0',
> `start_date` datetime NOT NULL,
> `stop_date` datetime NOT NULL,
> `reply_body` mediumtext,
> KEY `user_idnr_index` (`user_idnr`),
> CONSTRAINT `dbmail_auto_replies_ibfk_1` FOREIGN KEY (`user_idnr`)
> REFERENCES `dbmail_users` (`user_idnr`) ON DELETE CASCADE ON UPDATE
> CASCADE
> ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
>  
>  
>  
> CREATE TABLE `dbmail_auto_notifications` (
> `user_idnr` bigint(20) unsigned NOT NULL,
> `notify_address` varchar(100) NOT NULL DEFAULT '',
> KEY `user_idnr_index` (`user_idnr`),
> CONSTRAINT `dbmail_auto_notifications_ibfk_1` FOREIGN KEY
> (`user_idnr`) REFERENCES `dbmail_users` (`user_idnr`) ON DELETE
> CASCADE ON UPDATE CASCADE
> ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
>  
>  
>  
> ---
> ANDREA BRANCATELLI SCHEMA31 S.P.A.CHIEF TECHNOLOGY OFFICIER

Thanks. This works. It was a problem only with MariaSQL, not with
MySQL. MySQL has overlook the double keys. Or is that not an error?

Now I can insert a new user with "dbmail-users -a". That means: INSERT works.

I think, if you use dbmail 3.2.3 together with MySQL 5.7 (not 5.6) or
the newest MariaDB, dbmail deny every INSERT command. This was the
reason for my question in this mailing list.

Ralph

©2024 GT.net. A Gossamer Threads company.
5th Floor, 455 Granville St., Vancouver, BC V6C 1T1, Canada | Legal