Re: Empty message header and body
Sorry. My fault. Em qui., 16 de jul. de 2020 às 16:52, escreveu: > > > On 2020-07-16 21:35, Marcelo Machado wrote: > > Just an observation. > > The migration documentation on the website does not mention anything > > about the piler.key file. > > "Make sure that piler.key on NEW is the same as on OLD, and if the 'iv' > parameter is set on OLD in piler.conf, it must have the same value on > NEW." > > See http://www.mailpiler.org/wiki/current:migration-to-new-host for > more. > > Janos > >
Re: Empty message header and body
On 2020-07-16 21:35, Marcelo Machado wrote: Just an observation. The migration documentation on the website does not mention anything about the piler.key file. "Make sure that piler.key on NEW is the same as on OLD, and if the 'iv' parameter is set on OLD in piler.conf, it must have the same value on NEW." See http://www.mailpiler.org/wiki/current:migration-to-new-host for more. Janos
Re: Empty message header and body
Just an observation. The migration documentation on the website does not mention anything about the piler.key file. Em qui., 16 de jul. de 2020 às 15:56, escreveu: > > > On 2020-07-16 20:31, Marcelo Machado wrote: > > - is there an iv parameter in the old host's piler.conf file? > > No. > > > > - are the piler.key files on old and new host identical? > > > > Not also. > > That's the problem. Legacy emails can be decrypted with old piler.key > only. > However, you started to encrypt new emails with a different key. > > I suggest you to stop piler, then export all new emails, and start over > the migration process. Be sure to use piler.key from old host. > > Verify that you can access legacy emails on the new host, and then > import the exported emails. > > Janos > >
Re: Empty message header and body
OK. I will try. Thank you. Em qui., 16 de jul. de 2020 às 15:56, escreveu: > > > On 2020-07-16 20:31, Marcelo Machado wrote: > > - is there an iv parameter in the old host's piler.conf file? > > No. > > > > - are the piler.key files on old and new host identical? > > > > Not also. > > That's the problem. Legacy emails can be decrypted with old piler.key > only. > However, you started to encrypt new emails with a different key. > > I suggest you to stop piler, then export all new emails, and start over > the migration process. Be sure to use piler.key from old host. > > Verify that you can access legacy emails on the new host, and then > import the exported emails. > > Janos > >
Re: Empty message header and body
On 2020-07-16 20:31, Marcelo Machado wrote: - is there an iv parameter in the old host's piler.conf file? No. - are the piler.key files on old and new host identical? Not also. That's the problem. Legacy emails can be decrypted with old piler.key only. However, you started to encrypt new emails with a different key. I suggest you to stop piler, then export all new emails, and start over the migration process. Be sure to use piler.key from old host. Verify that you can access legacy emails on the new host, and then import the exported emails. Janos
Re: Empty message header and body
- is there an iv parameter in the old host's piler.conf file? No. - are the piler.key files on old and new host identical? Not also. Em qui., 16 de jul. de 2020 às 02:55, escreveu: > Usually I don't require any sensitive information to troubleshoot, > eg. your mysql password, or even the attached encryption key. > > Anyway, I can see that no 'iv' parameter in piler.conf on the > new host. However, > > - is there an iv parameter in the old host's piler.conf file? > - are the piler.key files on old and new host identical? > > Janos > > On 2020-07-16 00:42, Marcelo Machado wrote: > > In attachment is my piler.key > > > > Below is my piler.conf (I changed the domain): > > > > archive_emails_not_having_message_id=0 > > archive_only_mydomains=0 > > backlog=20 > > check_for_client_timeout_interval=20 > > > cipher_list=ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+3DES:DH+3DES:RSA+AESGCM:RSA+AES:RSA+3DES:!aNULL:!MD5:!DSS > > clamd_socket=/tmp/clamd > > default_retention_days=90 > > enable_chunking=0 > > enable_cjk=0 > > enable_folders=0 > > encrypt_messages=1 > > extract_attachments=1 > > extra_to_field=X-Envelope-To: > > helper_timeout=20 > > hostid=arch...@piler.mydomain.com.br > > listen_addr=0.0.0.0 > > listen_port=2525 > > max_connections=64 > > max_requests_per_child=1 > > memcached_servers=127.0.0.1 > > memcached_to_db_interval=900 > > memcached_ttl=86400 > > min_message_size=100 > > min_word_len=1 > > mmap_dedup_test=0 > > mysqlcharset=utf8mb4 > > mysql_connect_timeout=2 > > mysqldb=piler > > mysqlpwd=n3ts0l > > mysqlsocket=/var/run/mysqld/mysqld.sock > > mysqluser=piler > > number_of_worker_processes=2 > > pemfile=/usr/local/etc/piler/piler.pem > > pidfile=/opt/run/piler/piler.pid > > piler_header_field=X-piler-id: > > process_rcpt_to_addresses=0 > > server_id=0 > > smtp_timeout=60 > > spam_header_line=X-Spam-Flag: YES > > syslog_recipients=0 > > tls_enable=1 > > tweak_sent_time_offset=0 > > update_counters_to_memcached=0 > > username=piler > > verbosity=1 > > workdir=/opt/piler/tmp > > queuedir=/opt/piler/store > > > > Em qua., 15 de jul. de 2020 às 08:33, Janos SUTO > > escreveu: > > > >> Sorry, piler.key is a file, not an entry in piler.conf. > >> > >> Janos > >> On 15 Jul 2020, at 12:25, Marcelo Machado > >> wrote: > >> > >> Thanks for the answer. > >> > >> The parameter iv is cipher_list.There is no line with piler.key. > >> I was unable to read the contents of piler.key. > >> > >> Marcelo > >> > >> Em qua., 15 de jul. de 2020 às 00:46, Janos SUTO < s...@acts.hu> > >> escreveu: > >> > >> Hello Marcelo, > >> > >> check if piler.key and the iv parameter in piler.conf (if there's > >> any) are the same. > >> > >> Janos > >> On 14 Jul 2020, at 23:42, Marcelo Machado < mmgom...@gmail.com> > >> wrote: > >> > >> Hello everyone. > >> > >> After I migrated MailPiler to a new hardware, the header and body of > >> old messages no longer appear. The new ones are OK. > >> > >> I followed the migration documentation on the website. > >> > >> Marcelo Gomes >
