Re: dbmail_headervalue

it's statically here - did you

a) restart all services
b) made sure using the correct dbmail.conf

3.1.17 here too over months
it belongs in the [DBMAIL] main-section

Am 22.12.2014 um 19:22 schrieb Jorge Bastos:
> Reidnl,
>
> With:
>
> header_cache_readonly = yes
>
> I keep having new headername's being inserted in dbmail_headername.
>
> Maybe a bug?
>
> I'm on 3.1.17
>
>> -----Original Message-----
>> From: [email protected] [mailto:[email protected]] On
>> Behalf Of Jorge Bastos
>> Sent: domingo, 21 de Dezembro de 2014 22:05
>> To: 'DBMail mailinglist'
>> Subject: Re: [Dbmail] dbmail_headervalue
>>
>> Reindl,
>>
>> Thanks, i just wanna to have a more consistant ideia of the headers to
>> use.
>>
>>> -----Original Message-----
>>> From: [email protected] [mailto:[email protected]] On
>>> Behalf Of Reindl Harald
>>> Sent: sábado, 20 de Dezembro de 2014 12:36
>>> To: [email protected]
>>> Subject: Re: [Dbmail] dbmail_headervalue
>>>
>>>
>>> Am 20.12.2014 um 10:33 schrieb Jorge Bastos:
>>>> Oh hum :)
>>>>
>>>> Do you have:
>>>>
>>>> Date
>>>> Subject
>>>> From
>>>> To
>>>> Sent
>>>
>>> uhm i posted what i have and it's in every quote of that thread
>>>
>>>   > > >> MariaDB [dbmail]> select * from dbmail_headername;  > > >>
>>> +---
>>> -----+-------------------+
>>>   > > >> | id     | headername        |
>>>   > > >> +--------+-------------------+
>>>   > > >> |    183 | cc                |
>>>   > > >> |      8 | content-type      |
>>>   > > >> |      1 | date              |
>>>   > > >> |      2 | from              |
>>>   > > >> |     62 | importance        |
>>>   > > >> |     44 | in-reply-to       |
>>>   > > >> |      3 | message-id        |
>>>   > > >> |      9 | mime-version      |
>>>   > > >> | 111813 | newsgroups        |
>>>   > > >> |    380 | priority          |
>>>   > > >> |     47 | references        |
>>>   > > >> |     38 | reply-to          |
>>>   > > >> |     68 | status            |
>>>   > > >> |      6 | subject           |
>>>   > > >> |     69 | thread-index      |
>>>   > > >> |    179 | thread-topic      |
>>>   > > >> |      7 | to                |
>>>   > > >> | 109464 | x-msmail-priority |
>>>   > > >> | 111823 | x-msoesrec        |
>>>   > > >> | 109408 | x-priority        |
>>>   > > >> | 111825 | x-ref             |
>>>   > > >> +--------+-------------------+  > > >> 21 rows in set (0.00
>>> sec)
>>>
>>>> Question is, the ones that end up with null in the sort column i
>>> think
>>>> are garbage also, am i right? :)
>>>
>>> the only relevant question is if mail cliets are using a header for
>>> sorting, display, threading and so on in the list view
>>>
>>>> "Reindl Harald (mobile)" <[email protected]> wrote:
>>>> Just read what you quoted - the sql result is part of it. :-)
>>>>
>>>>
>>>> -------- Ursprüngliche Nachricht --------
>>>> Von: Jorge Bastos <[email protected]>
>>>> Gesendet: 20. Dezember 2014 00:22:13 MEZ
>>>> An: 'DBMail mailinglist' <[email protected]>
>>>> Betreff: Re: [Dbmail] dbmail_headervalue
>>>>
>>>> Reindl,
>>>>
>>>> Tell me, i'm curious to know which headername do you have, can you
>>> share?
>>>>
>>>> I'm curious.
>>>>
>>>>   > -----Original Message-----
>>>>   > From: [email protected]
>>>> [mailto:[email protected]]
>>>> On  > Behalf Of Jorge Bastos  > Sent: domingo, 14 de Dezembro de
>>>> 2014
>>>> 18:23  > To: 'DBMail mailinglist'
>>>>   > Subject: Re: [Dbmail] dbmail_headervalue  >  > Hum,  >  > Fact
>> is
>>> I
>>>> have garbage in headername table also, i have things that ARE  >
>> NOT
>>>> headers, but they are there (garbage!):
>>>>   >
>>>>   > +--------------------------------------------------+
>>>>   > | headername                                       |
>>>>   > +--------------------------------------------------+
>>>>   > | "x-copyrighted-material                          |
>>>>   > | #content-transfer-encoding                       |
>>>>   > | #content-type                                    |
>>>>   > | /m                                               |
>>>>   > | 0                                                |
>>>>   > | 0/x-total-score                                  |
>>>>   > | 1                                                |
>>>>   > | 2                                                |
>>>>   > | 2/x-brightmail-tracker                           |
>>>>   > | 2/x-total-score                                  |
>>>>   >
>>>>   > So yes, the header_cache_readonly = yes will help on this.
>>>>   > I'm going to delete the garbage headername's like this one's and
>>>> leave  > only the "x-......" and a few extra one's that I know that
>>>> are needed,  > and then apply the header_cache_readonly = yes, and
>>>> after, truncate the  > headervalue's and dbmail-util -by it.
>>>>   >
>>>>   > > -----Original Message-----
>>>>   > > From: [email protected]
>>>> [mailto:[email protected]] On  > > Behalf Of Reindl Harald
>>>>>
>>>>> Sent: domingo, 14 de Dezembro de 2014 17:21  > > To:
>>>> [email protected]  > > Subject: Re: [Dbmail] dbmail_headervalue  >
>>>
>>>>>> correct  > >  > > keep in mind that "header_cache_readonly =
>> yes"
>>>> will prevent from  > > adding any headers again - i removed all,
>>>> inserted the needed  > manually  > > in headernames and than
>> rebuilt
>>>>>>   > > got rid millions of records forever that way  > >  > > Am
>>>> 14.12.2014 um 18:10 schrieb Jorge Bastos:
>>>>   > > > So,
>>>>   > > >
>>>>   > > > Truncate dbmail_headername;
>>>>   > > > Truncate dbmail_headervalue;
>>>>   > > > Dbmail-util -by
>>>>   > > >
>>>>   > > > During this time only IMAP will compaint since it won't have
>>>>
>>>> headers  > > > to show, but there's no problem to have IMAP users
>>>> connecting  > during  > > > this time, when the re-fill is finish,
>>>> everything will look normal  > > > on imap clients, right?
>>>>   > > >
>>>>   > > >> -----Original Message-----
>>>>   > > >> From: [email protected]
>>>> [mailto:[email protected]]
>>>>   > > On
>>>>   > > >> Behalf Of Reindl Harald
>>>>   > > >> Sent: domingo, 14 de Dezembro de 2014 17:03  > > >> To:
>>>> [email protected]  > > >> Subject: Re: [Dbmail] dbmail_headervalue
>>>>>
>>>>>>>   > > >>  > > >> Am 14.12.2014 um 17:59 schrieb Jorge Bastos:
>>>>   > > >>> I have allot, I mean, millions of lost records in the  > >
>>>>>>> dbmail_headervalue table.
>>>>   > > >>>
>>>>   > > >>> About 72 million lost records, with dbmail-util it cannot
>>>> handle  > > >>> it  > > >> in  > > >>> a workable time.
>>>>   > > >>>
>>>>   > > >>> Is it safe to truncate the table, and dbmail-util -by it?
>>>>   > > >>
>>>>   > > >> yes and you should consider "header_cache_readonly = yes"
>>>> and
>>>>>> cleanup  > > >> "dbmail_headername" too - maybe that alone will
>>> be
>>>> enough to get  > > >> rid of 90%  > > >>  > > >> MariaDB [dbmail]>
>>>> select * from dbmail_headername;  > > >>
>>>> +--------+-------------------+
>>>>   > > >> | id     | headername        |
>>>>   > > >> +--------+-------------------+
>>>>   > > >> |    183 | cc                |
>>>>   > > >> |      8 | content-type      |
>>>>   > > >> |      1 | date              |
>>>>   > > >> |      2 | from              |
>>>>   > > >> |     62 | importance        |
>>>>   > > >> |     44 | in-reply-to       |
>>>>   > > >> |      3 | message-id        |
>>>>   > > >> |      9 | mime-version      |
>>>>   > > >> | 111813 | newsgroups        |
>>>>   > > >> |    380 | priority          |
>>>>   > > >> |     47 | references        |
>>>>   > > >> |     38 | reply-to          |
>>>>   > > >> |     68 | status            |
>>>>   > > >> |      6 | subject           |
>>>>   > > >> |     69 | thread-index      |
>>>>   > > >> |    179 | thread-topic      |
>>>>   > > >> |      7 | to                |
>>>>   > > >> | 109464 | x-msmail-priority |
>>>>   > > >> | 111823 | x-msoesrec        |
>>>>   > > >> | 109408 | x-priority        |
>>>>   > > >> | 111825 | x-ref             |
>>>>   > > >> +--------+-------------------+  > > >> 21 rows in set (0.00
>>>> sec)

_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEARECAAYFAlSYYjEACgkQhmBjz394AnlgEQCcC5qbLaSEVn16jaHzgVDeaV2e
GogAniOXsQudPt4mPQU0wv4GTCEyMZpY
=ZlxK
-----END PGP SIGNATURE-----