As designed Server error log

Astra

Active member
Affected version
2.2.4
1.webp2.webp

Code:
Laminas\Mail\Header\Exception\InvalidArgumentException: Bounce message processing failed: Invalid header value detected src/vendor/laminas/laminas-mail/src/Header/GenericHeader.php:64
Generated by: Unknown account Apr 26, 2021 at 5:23 PM
Stack trace
#0 src/vendor/laminas/laminas-mail/src/Headers.php(481): Laminas\Mail\Header\GenericHeader::splitHeaderLine('X-Ham-Report: S...')
#1 src/vendor/laminas/laminas-mail/src/Headers.php(232): Laminas\Mail\Headers->loadHeader('X-Ham-Report: S...')
#2 src/vendor/laminas/laminas-mail/src/Headers.php(96): Laminas\Mail\Headers->addHeaderLine('X-Ham-Report: S...')
#3 src/vendor/laminas/laminas-mime/src/Decode.php(150): Laminas\Mail\Headers::fromString('Return-Path: <>...', '
')
#4 src/vendor/laminas/laminas-mail/src/Storage/Part.php(103): Laminas\Mime\Decode::splitMessage('Return-Path: <>...', 'Return-Path: <>...', 'Это пись...', '
', false)
#5 src/vendor/laminas/laminas-mail/src/Storage/Message.php(53): Laminas\Mail\Storage\Part->__construct(Array)
#6 src/XF/EmailBounce/Parser.php(169): Laminas\Mail\Storage\Message->__construct(Array)
#7 src/XF/EmailBounce/Processor.php(94): XF\EmailBounce\Parser->parseMessage('Return-Path: <>...')
#8 src/XF/EmailBounce/Processor.php(70): XF\EmailBounce\Processor->processMessage('Return-Path: <>...')
#9 src/XF/Job/EmailBounce.php(27): XF\EmailBounce\Processor->processFromStorage(Object(XF\Mail\Storage\Imap), 8)
#10 src/XF/Job/Manager.php(258): XF\Job\EmailBounce->run(8)
#11 src/XF/Job/Manager.php(200): XF\Job\Manager->runJobInternal(Array, 8)
#12 src/XF/Job/Manager.php(84): XF\Job\Manager->runJobEntry(Array, 8)
#13 job.php(43): XF\Job\Manager->runQueue(false, 8)
#14 {main}
Request state
array(4) {
  ["url"] => string(8) "/job.php"
  ["referrer"] => string(71) "https://******.club/threads/ehnergija-okruzhajuschaja-nas.5523/page-3"
  ["_GET"] => array(0) {
  }
  ["_POST"] => array(0) {
  }
}
 
Based on what I'm seeing in the trace, this is likely ultimately the same issue as discussed here:


When I did look at an example mail with the X-Ham-Report header, it genuinely was an invalid header and thus this isn't unexpected. There were special characters in it which were not properly encoded.

If I recall my research from before, X-Ham-Report is not actually applied by SpamAssassin any longer, but by cPanel itself. There is a discussion in the linked thread about removing the header.
 
Top Bottom