"Message Failed Verification" on all mails in web interface

Issue #971 resolved
Dom created an issue

I'm using piler version 1.3.4 build 994 and used the instructions on 'http://www.mailpiler.org/wiki/current:installation' to successfully set up the system.

The mail archive is working fine and so is the web interface, but all mails (both with and without attachments) are being labeled as "Message Failed Verification" and I can neither view the mail bodies nor the attachments. Downloading any email via the web interface leads to an empty file.

My test message is correctly archived under '/var/piler/store/00/5c9/9e/la' as '400000005c938d5c30b736dc00219f209e1a.m'. It has the subject 'sdagöiohsdögo' and the body text 'öiasdhg-lasiihgöosaodjgaseg'. Both recipient and sender are the same address.

I tried 'pilerexport -r recipient@domain.tld', which successfully exported the email and was readable by my mail client 'Evolution' without problems.

'pilerget 400000005c938d5c30b736dc00219f209e1a' yields:

Received: from mx.domain.tld (localhost [127.0.0.1]) by mx.domain.tld (Postfix) with ESMTP id 44Q6bj6vlrz2sgS for archive@archive2.domain.tld; Thu, 21 Mar 2019 14:10:41 +0100 (CET) Authentication-Results: mx.domain.tld (amavisd-new); dkim=pass (1024-bit key) reason="pass (just generated, assumed good)" header.d=domain.tld DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=domain.tld; h= content-transfer-encoding:mime-version:x-mailer:content-type :content-type📅date:to:from:from:subject:subject:message-id; s=dkim; t=1553173841; x=1555765842; bh=2bLYyztTbI2SxAErHwZvxZtu KMS5K1+H9jiUe6L/UFI=; b=VDUwzbjPh3vSeHnVU8aZPq1N+kU1xXQvuPmJEOCx Odiq8+M65maD14Ak/6TziRK3idwG9G82dPVe+c5lVw5c80DJeZpGonEcZXpmzfNI TurPALskXfBxnaJ5lYOE3/qhct3CcnLyuZNwWYGVfCukeOanu7HNWu/RW80yzeXf 2wk= X-Virus-Scanned: Debian amavisd-new at mx.domain.tld Received: from mx.domain.tld ([127.0.0.1]) by mx.domain.tld (mx.domain.tld [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 60G6tcZbyFGq for archive@archive2.domain.tld; Thu, 21 Mar 2019 14:10:41 +0100 (CET) Received: from pc (xxxxxxxxx.dyn.telefonica.de [xx.xx.xx.xx]) by mx.domain.tld (Postfix) with ESMTPSA id 44Q6bj3wZSz2sgN for dom@domain.tld; Thu, 21 Mar 2019 14:10:41 +0100 (CET) Message-ID: 1553173800.4261.1.camel@domain.tld Subject: =?ISO-8859-1?Q?sdag=F6iohsd=F6go?= From: dom dom@domain.tld To: dom@domain.tld Date: Thu, 21 Mar 2019 14:10:00 +0100 Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.22.6-1+deb9u1 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable

=C3=B6iasdhg-lasiihg=C3=B6osaodjgaseg=20

Comments (9)

  1. Dom reporter

    Hey there,

    thank you for your time! I forgot to attach the syslog the other day.

    We've investigated further and found two errors in the logs.

    This is from the php log:

    2019/03/26 13:25:27 [error] 19602#19602: *342 FastCGI sent in stderr: "PHP message: PHP Notice: Uninitialized string offset: 0 in /var/piler/www/system/helper/mime.php on line 178PHP message: PHP Notice: Undefined index: date in /var/piler/www/system/helper/mime.php on line 143PHP message: PHP Notice: Uninitialized string offset: 0 in /var/piler/www/system/helper/mime.php on line 178PHP message: PHP Notice: Undefined index: date in /var/piler/www/system/helper/mime.php on line 143" while reading response header from upstream, client: xx.xx.xx.xx, server: piler_host, request: "POST /message.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php/php7.3-fpm.sock:", host: "archive2.xx.xx", referrer: "https://archive2.xx.xx/search.php"

    The other error was in the mail.log (I'll attach the most recent one for context):

    SSL_accept() result, rc=-1, errorcode: 2, error text: error:00000000:lib(0):func(0):reason(0)

  2. Dom reporter

    Hi Janos,

    thanks to your help we could find and resolve the issue.

    Since we're using Debian (Buster) we had to change some path variables to the following values in the file config-site.php: $config['DECRYPT_BINARY'] = '/usr/bin/pilerget'; $config['DECRYPT_ATTACHMENT_BINARY'] = '/usr/bin/pilerget';

    Maybe it'd be beneficial to include a note in the post-install section for Debian users if it turns out to be a common configuration error.

    Thanks once again for your help!

  3. Log in to comment