HM4227, HM4208, HM5519 - regular causes

This section contains user-submitted tutorials.
Post Reply
User avatar
jimimaseye
Moderator
Moderator
Posts: 10053
Joined: 2011-09-08 17:48

HM4227, HM4208, HM5519 - regular causes

Post by jimimaseye » 2017-07-30 11:26

KNOWLEDGE BASE

Scenario
There can be occasions where there following is error is encountered (appearing in your logs as written below) upon trying to send an email:

Condition

Code: Select all

"APPLICATION"	12392	"2017-07-30 09:50:49.342"	"SMTPDeliverer - Message 78: Delivering message from user@yourdomain.net to user@recipient.com. File: C:\Program Files (x86)\hMailServer\Data\{5414EEBD-2E3F-491C-9F08-A6BFC3A76AAC}.eml"
"ERROR"	12392	"2017-07-30 09:50:50.129"	"Severity: 3 (Medium), Code: HM4227, Source: File::ReadFile, Description: An unknown error occurred while reading file from disk."
"ERROR"	12392	"2017-07-30 09:50:50.527"	"Severity: 2 (High), Code: HM4208, Source: ExceptionHandler::Run, Description: An error occured while executing 'Task-DeliveryTask', Message: Attempt to read from file which has not been opened."
"ERROR"	12392	"2017-07-30 09:51:08.622"	"Severity: 1 (Critical), Code: HM5519, Source: StackLogger::Log, Description: An error has been detected. A mini dump has been written to C:\Program Files (x86)\hMailServer\Logs\minidump_2017-07-30 095050_{E26A1626-878C-4C54-92BA-20A01EA41AF8}.dmp"
Errors HM4227, HM4208, HM5519 are issued (as shown) along with a minidump.

HM4227, Source: File::ReadFile, Description: An unknown error occurred while reading file from disk."
HM4208, Source: ExceptionHandler::Run, Description: An error occured while executing 'Task-DeliveryTask', Message: Attempt to read from file which has not been opened."
HM5519, Source: StackLogger::Log, Description: An error has been detected. A mini dump has been written


Causes and Solutions
There can be a number of reasons and here I would highlight 2 common scenarios/causes that often appear. You may choose to review the following before posting your problem.

1, DKIM signing has been enabled
You may have DKIM signing enabled in the individual sending domain and you have stated a certificate file that cannot be read:

a, check the path is correct - you may have moved or renamed the physical certificate file but not updated Hmailserver to reflect the change.

b, check that the permissions for this file is sufficient to allow the Hmailserver.exe service account (usually 'SYSTEM' by default) to read it.

People often encounter this error after restoring or migrating to another server, and move or forget to change the reference to the certificate path.

2, Antivirus intervention
Some antivirus solutions monitor and may remove content of an email message during the conversation. The AV software may be that running on the sending email client or on the Hmailserver server itself.

a, Temporarily turn OFF completely both AV's on the client and the Hmailserver server and perform another sending test. If the mail the successfully sends you can then turn back on one by one to determine which was responsible.

b, If the AV intervention is on the server, you could then re-enable it but ensure the data directory is completely exempt from scanning and realtime protection. (This should always be the case if you have Antivirus checking set up in Hmailserver anyway to prevent conflicts). In some cases this may enable you to continue with your AV software without it further negatively affecting your Hmailserver. If you are not, and you know the sending email is completely safe and without risk, then you will need to review your Antivirus solution as it is affecting communications with your Hmailserver.
5.7 on test.
SpamassassinForWindows 3.4.0 spamd service
AV: Clamwin + Clamd service + sanesecurity defs : https://www.hmailserver.com/forum/viewtopic.php?f=21&t=26829

User avatar
Snorkasaurus
Normal user
Normal user
Posts: 191
Joined: 2010-08-29 16:32
Location: Canada
Contact:

Re: HM4227, HM4208, HM5519 - regular causes

Post by Snorkasaurus » 2021-12-01 05:12

jimimaseye wrote: 1, DKIM signing has been enabled
Thanks a heap jimimaseye! This was exactly what I did when I moved to a new server tonight and forgot to copy over the dkim files... I'm glad this was here to save me from pulling out the last few hairs on my head. :-)

s.

User avatar
jimimaseye
Moderator
Moderator
Posts: 10053
Joined: 2011-09-08 17:48

Re: HM4227, HM4208, HM5519 - regular causes

Post by jimimaseye » 2021-12-01 09:46

Cheers Snork.
5.7 on test.
SpamassassinForWindows 3.4.0 spamd service
AV: Clamwin + Clamd service + sanesecurity defs : https://www.hmailserver.com/forum/viewtopic.php?f=21&t=26829

Post Reply