Error in E-Mail Logviewer (Domain/Subscription level)

[rammstein]

Username:

TITLE

Error in E-Mail Logviewer (Domain/Subscription level)

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk Obsidian 18.0.74 Update #2 Web Host Edition, Ubuntu 24.04.3 LTS

PROBLEM DESCRIPTION

Hello everyone,

I’m experiencing an issue with the Plesk Email Log Viewer, but only on the Domain/Subscription level.

Under Tools & Settings → Email, everything works fine.

The error message is:

The log files could not be processed.

PleskExt\LogBrowser\Database\ImapLogins\Table::trackLoginEvent(): Argument #1 ($mailname) must be of type string, null given, called in /opt/psa/admin/plib/modules/log-browser/library/Injest/ImapLoginProcessor.php on line 42

STEPS TO REPRODUCE

Login to Plesk -> Go to an Subscription -> E-Mail Tab -> Tracking Email Delivery -> Klick: Refresh

ACTUAL RESULT

The log files could not be processed.

PleskExt\LogBrowser\Database\ImapLogins\Table::trackLoginEvent(): Argument #1 ($mailname) must be of type string, null given, called in /opt/psa/admin/plib/modules/log-browser/library/Injest/ImapLoginProcessor.php on line 42

EXPECTED RESULT

No Error, refresh of Displayed data

ANY ADDITIONAL INFORMATION

Discussion: Issue - Error in E-Mail Logviewer (Domain/Subscription level)

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug

 

[Sebahat.hadzhi]

Thank you for the report, @rammstein . Unfortunately, I was unable to replicate the described behavior regardless of what I tried (empty IMAP login attempts, non-standard characters, etc.). Just to be sure I have the exact same test environment, is Log browser version 1.9.15-4476? If yes, there's more to the events happening on the server I am can't seem to be able to reproduce. I will double-check with our team if they have any guesses what might be causing the issue and follow-up with more details. In the meantime, if you can double-check /var/log/maillog and more specifically if there are any additional details to IMAP login attempts. Thanks in advance.

 

[Maarten]

On Ubuntu, it's /var/log/mail.log

@rammstein Do you see any items in the list, or is it empty when you go to "Tracking Email Delivery"?

 

[Sebahat.hadzhi]

@rammstein could you please also confirm if you use Dovecot or Courier? Thanks in advance.

 

[rammstein]

Today it is working again! I did not do or change anything!

@rammstein could you please also confirm if you use Dovecot or Courier? Thanks in advance.

I use Courier.

And my Log Browser is also 1.9.15-4476

On Ubuntu, it's /var/log/mail.log

@rammstein Do you see any items in the list, or is it empty when you go to "Tracking Email Delivery"?

When the Problem was still there, I saw some old itmes with date from 29.11.2025. On refresh the error appeared.

Today: Working again, oldest entry from 30.11. and the newest from today 04.12.2025.

 

[Maarten]

I’m curious, any particular reason you chose Courier over Dovecot?

 

[rammstein]

I’m curious, any particular reason you chose Courier over Dovecot?

We’ve standardized on Courier in our Plesk environments because it has proven to be very stable and low-maintenance for us.
It fully covers our customers’ needs, is well integrated in our tooling and monitoring, and switching to Dovecot wouldn’t bring any tangible benefit, only migration risk and additional operational overhead.

Dovecot is a solid option as well – there’s just no practical reason for us to change a working setup.