Forum

[Ticket Mailbox] CR...
 
Notifications
Retirer tout

[Ticket Mailbox] CRON error when reading reply_to

3 Posts
2 Utilisateurs
0 Reactions
82 Vu
Sylvain Devidal
(@magicbuzz)
Posts: 38
Trusted Member
Début du sujet
 
[#10129]

Hello,

Since we upgraded to 13.0.0 we often have this error in the log (and in the ticket mailbox screen too) :

2026-07-09 11:16:46.345 ** ERROR ** [V13.0.0] ERROR **
2026-07-09 11:16:46.346
** ERROR ** [V13.0.0] on file '/var/www/projeqtor.aznetwork.eu/model/ImapMailbox2.php' at line (289)
2026-07-09 11:16:46.346
** ERROR ** [V13.0.0] cause = Undefined array key "reply_to"
2026-07-09 11:16:46.346
** ERROR ** [V13.0.0] Undefined array key "reply_to" in ImapMailbox2.php at line 289
2026-07-09 11:16:46.346
** ERROR ** [V13.0.0] Error while executing CRON script : fix the source issue and manually restart the CRON Process
2026-07-09 11:16:46.346
** ERROR ** [V13.0.0] EXCEPTION **
2026-07-09 11:16:46.346 ** ERROR ** [V13.0.0] on file '/var/www/projeqtor.aznetwork.eu/model/ImapMailbox2.php' at line (289)
2026-07-09 11:16:46.346 ** ERROR ** [V13.0.0] cause = Call to a member function toString() on null
2026-07-09 11:16:46.346 ** ERROR ** [V13.0.0] => #0 /var/www/projeqtor.aznetwork.eu/model/InputMailboxTicket.php (551) -> getMail()
2026-07-09 11:16:46.346 ** ERROR ** [V13.0.0] => #1 /var/www/projeqtor.aznetwork.eu/model/InputMailboxTicket.php (416) -> treatInputMailbox()
2026-07-09 11:16:46.346 ** ERROR ** [V13.0.0] => #2 /var/www/projeqtor.aznetwork.eu/model/Cron.php (1004) -> checkEmailsTicket()
2026-07-09 11:16:46.346 ** ERROR ** [V13.0.0] => #3 /var/www/projeqtor.aznetwork.eu/model/Cron.php (664) -> checkEmails()
2026-07-09 11:16:46.346 ** ERROR ** [V13.0.0] => #4 /var/www/projeqtor.aznetwork.eu/model/Cron.php (468) -> run()
2026-07-09 11:16:46.346 ** ERROR ** [V13.0.0] => #5 /var/www/projeqtor.aznetwork.eu/tool/cronRelaunch.php (30) -> relaunch()
2026-07-09 11:16:46.346 ** ERROR ** [V13.0.0] Call to a member function toString() on null
2026-07-09 11:16:46.346 ** ERROR ** [V13.0.0] Exception while executing CRON script : fix the source issue and manually restart the CRON Process
2026-07-09 11:16:46.346 ** ERROR ** [V13.0.0] === Trace Stack for last error ===
2026-07-09 11:16:46.346 ** ERROR ** [V13.0.0] => /var/www/projeqtor.aznetwork.eu/tool/projeqtor.php at line 1638 calling debugPrintTraceStack()
2026-07-09 11:16:46.346 ** ERROR ** [V13.0.0] => calling exceptionHandler()
2026-07-09 11:16:46.346 ** ERROR ** [V13.0.0] ===
2026-07-09 11:16:46.410 ** ERROR ** [V13.0.0] CRON abnormally stopped
2026-07-09 11:16:46.410 ** ERROR ** [V13.0.0] === Trace Stack for last error ===
2026-07-09 11:16:46.410 ** ERROR ** [V13.0.0] => /var/www/projeqtor.aznetwork.eu/model/Cron.php at line 326 calling debugPrintTraceStack()
2026-07-09 11:16:46.410 ** ERROR ** [V13.0.0] => /var/www/projeqtor.aznetwork.eu/tool/cronRelaunch.php at line 28 calling Cron:abort()
2026-07-09 11:16:46.410 ** ERROR ** [V13.0.0] => calling cronAbort()
2026-07-09 11:16:46.410 ** ERROR ** [V13.0.0] ===

How to fix it?


 
Posté : 09/07/2026 1:33 pm
(@babynus)
Posts: 14952
Membre Admin
 

From wich version did you migrate ?


 
Posté : 19/07/2026 6:37 pm
Sylvain Devidal
(@magicbuzz)
Posts: 38
Trusted Member
Début du sujet
 

Hello Babynus,

If I remember well, it was 12.1.0

But I'm not sure it's related to the upgrade.
We already had some emails not synchronizing before the upgrade, but I didn't noticed the error in the logs.

It looks like to be related to the emails themselves:

In the mail headers, sometimes the "From:" value is empty.
But the "Sender:" is set.
IMO the current program reads the "From" value and fails if it's empty (or null).
At this time is should try "Sender" and use this value if set properly, or simply reject the mail without error.

Return-Path: 
Received: from abf-zmfront02.aznetwork.priv (LHLO mx5.aznetwork.eu)
 (192.168.49.122) by abf-zmstor01.aznetwork.eu with LMTP; Wed, 15 Jul 2026
 02:21:43 +0200 (CEST)
Received: from localhost (localhost [IPv6:::1])
	by mx5.aznetwork.eu (Postfix) with ESMTP id 88916E0517;
	Wed, 15 Jul 2026 02:21:43 +0200 (CEST)
X-Spam-Flag: NO
X-Spam-Score: -2.004
X-Spam-Level:
X-Spam-Status: No, score=-2.004 required=6.6 tests=[ALL_TRUSTED=-1,
 BAYES_00=-1.9, FSL_HELO_NON_FQDN_1=0.001, HELO_NO_DOMAIN=0.001,
 HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.1, RDNS_NONE=0.793]
 autolearn=no autolearn_force=no
Received: from mx5.aznetwork.eu ([IPv6:::1])
 by localhost (abf-zmfront02.aznetwork.eu [IPv6:::1]) (amavis, port 10032)
 with ESMTP id 0FnZ1J1he5ii; Wed, 15 Jul 2026 02:21:43 +0200 (CEST)
Received: from localhost (localhost [IPv6:::1])
	by mx5.aznetwork.eu (Postfix) with ESMTP id 47C84E0544;
	Wed, 15 Jul 2026 02:21:43 +0200 (CEST)
Authentication-Results:mx5.aznetwork.eu; dkim=permerror (bad message/signature format)
X-Virus-Scanned: amavis at abf-zmfront02.aznetwork.priv
Received: from mx5.aznetwork.eu ([IPv6:::1])
 by localhost (abf-zmfront02.aznetwork.eu [IPv6:::1]) (amavis, port 10026)
 with ESMTP id i21_zyC6Vgba; Wed, 15 Jul 2026 02:21:43 +0200 (CEST)
Received: from mailrelay2.aznetwork.eu (unknown [IPv6:2a05:47c0:61:1049:ace9:ebff:fecb:90e5])
	by mx5.aznetwork.eu (Postfix) with ESMTPS id 29966E0504
	for ; Wed, 15 Jul 2026 02:21:43 +0200 (CEST)
Received: from *02 (unknown [192.168.130.17])
	by mailrelay2.aznetwork.eu (Postfix) with ESMTP id 04B003F9;
	Wed, 15 Jul 2026 02:21:43 +0200 (CEST)
From:
Date: Wed, 15 Jul 2026 02:21:42 +0200
Subject: ERREUR AVRILTRT02 - Supervision des traitements
Message-Id: 
Sender: "*@aznetwork.eu" 
To: "****@aznetwork.eu" 
MIME-Version: 1.0
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

 
Posté : 20/07/2026 11:54 am
Share:
Retour en haut