Incoming mails are rejected with PROCESSING ERROR

mparaskevaidis · May 26, 2025, 6:13am

Hello,

I get the same error for all my users in our Windows Axigen Server and incoming RemotePOP mails are not delivered to users inboxes.

2025-05-26 08:30:37 +0300 08 THINKCENTREM700 JOBLOG:90000000: userA@domainX.com: Conversation index job triggered
2025-05-26 08:30:37 +0300 08 THINKCENTREM700 PROCESSING:0006DC15: Shepherd thread received signal for processing
2025-05-26 08:30:37 +0300 08 THINKCENTREM700 PROCESSING:0006DC15: Set recipient userA@domainX.com state to RECEIVED
2025-05-26 08:30:37 +0300 08 THINKCENTREM700 PROCESSING:0006DC15: Set mail state to PROCESSING
2025-05-26 08:30:37 +0300 08 THINKCENTREM700 PROCESSING:0006DC15: Start processing mail
2025-05-26 08:30:37 +0300 08 THINKCENTREM700 PROCESSING:0006DC15: Set recipient userA@domainX.com state to PROCESSING
2025-05-26 08:30:37 +0300 08 THINKCENTREM700 PROCESSING:0006DC15: Start filter AV:Tnef of type socket filter from server
2025-05-26 08:30:37 +0300 08 THINKCENTREM700 PROCESSING:0006DC15: Processing started
2025-05-26 08:30:37 +0300 08 THINKCENTREM700 PROCESSING:0006DC15: Shepherd thread finished processing signal
2025-05-26 08:30:37 +0300 16 THINKCENTREM700 PROCESSING:0006DC15: << welcome to Axigen TNEF Decoder (1.4.5)
2025-05-26 08:30:37 +0300 16 THINKCENTREM700 PROCESSING:0006DC15: >> filter|
2025-05-26 08:30:37 +0300 16 THINKCENTREM700 PROCESSING:0006DC15: >> C:\Program Files\Axigen Mail Server\queue\06\DDC15.00
2025-05-26 08:30:37 +0300 16 THINKCENTREM700 PROCESSING:0006DC15: >> |
2025-05-26 08:30:37 +0300 16 THINKCENTREM700 PROCESSING:0006DC15: >> C:\Program Files\Axigen Mail Server\queue\06\DDC15.01
2025-05-26 08:30:37 +0300 16 THINKCENTREM700 PROCESSING:0006DC15: << done
2025-05-26 08:30:37 +0300 08 THINKCENTREM700 PROCESSING:0006DC15: Filter AXI-TNEF(127.0.0.1:8888):[PASS]: pass - no changes
2025-05-26 08:30:37 +0300 08 THINKCENTREM700 PROCESSING:0006DC15: Finished filtering mail object 06DC15 with filter: AV:Tnef of type socket filter from server
2025-05-26 08:30:37 +0300 08 THINKCENTREM700 PROCESSING:0006DC15: Set recipient userA@domainX.com data version to 1
2025-05-26 08:30:37 +0300 08 THINKCENTREM700 PROCESSING:0006DC15: Set recipient userA@domainX.com state to PROCESSING
2025-05-26 08:30:37 +0300 08 THINKCENTREM700 PROCESSING:0006DC15: Start filter AV:SpamAssassin of type socket filter from server
2025-05-26 08:30:39 +0300 02 THINKCENTREM700 PROCESSING:0006DC15: Filter SpamAssassin Filter(127.0.0.1:783):[ERROR]: Could not connect to filter
2025-05-26 08:30:39 +0300 02 THINKCENTREM700 PROCESSING:0006DC15: Error connecting to socket filter: SpamAssassin Filter(127.0.0.1:783)
2025-05-26 08:30:39 +0300 08 THINKCENTREM700 PROCESSING:0006DC15: Finished filtering mail object 06DC15 with filter: AV:SpamAssassin of type socket filter from server
2025-05-26 08:30:39 +0300 08 THINKCENTREM700 PROCESSING:0006DC15: Set recipient userA@domainX.com state to PROCESSING ERROR
2025-05-26 08:30:39 +0300 08 THINKCENTREM700 PROCESSING:0006DC15: Set mail state to PROCESSING ERROR
2025-05-26 08:30:39 +0300 08 THINKCENTREM700 PROCESSING:0006DC15: Processing finished

We do not have SA installed and it’s corresponding settings is switched off in Webadm AntiVirus & AntiSpam Supported apps.

I do not think that it is related but this behavior started after applying these advanced routing settings

Any ideas?

Thank you

florin.burada · June 15, 2025, 2:02pm

Hello,

According to the log file provided the message is stuck in the Queue due to the SpamAssasin that is enabled:

2025-05-26 08:30:37 +0300 08 THINKCENTREM700 PROCESSING:0006DC15: Set recipient [userA@domainX.com](mailto:userA@domainX.com) state to PROCESSING
2025-05-26 08:30:37 +0300 08 THINKCENTREM700 PROCESSING:0006DC15: Start filter AV:SpamAssassin of type socket filter from server
2025-05-26 08:30:39 +0300 02 THINKCENTREM700 PROCESSING:0006DC15: Filter SpamAssassin Filter(127.0.0.1:783):[ERROR]: Could not connect to filter
2025-05-26 08:30:39 +0300 02 THINKCENTREM700 PROCESSING:0006DC15: Error connecting to socket filter: SpamAssassin Filter(127.0.0.1:783)
2025-05-26 08:30:39 +0300 08 THINKCENTREM700 PROCESSING:0006DC15: Finished filtering mail object 06DC15 with filter: AV:SpamAssassin of type socket filter from server
2025-05-26 08:30:39 +0300 08 THINKCENTREM700 PROCESSING:0006DC15: Set recipient [userA@domainX.com](mailto:userA@domainX.com) state to PROCESSING ERROR
2025-05-26 08:30:39 +0300 08 THINKCENTREM700 PROCESSING:0006DC15: Set mail state to PROCESSING ERROR

Please check that SpamAssassin service is running and is listening on port 783. Note that SpamAssassin is not part of Axigen package and should be installed manually.

Regards,
Florin

mparaskevaidis · June 19, 2025, 12:10pm

Hello Florin

Thank you for your answer.
We do not have an active Spamassassin installation on the machine. This is the strange part.
Netstat shows axigen service senting SYN packets and not receiving Acknowledgment which is normal since Spamassassin is not installed

TCP 127.0.0.1:1518 THINKCENTREM700:783 SYN_SENT [axigen.exe]

Spamassassin settings is switched off in Webadm AntiVirus & AntiSpam Supported apps.
Settings screenshot attached.

Thank you again
Miltos

indreias · June 19, 2025, 1:20pm

Hello,

But what about the status for SpamAssasin filter at domain level?

WebAdmin > Manage Domains > Configure your domain > Message Filters > AntiVirus / AntiSpam Filters

HTH,
Ioan

mparaskevaidis · June 20, 2025, 12:35pm

Hello Ioan and welcome back!

Indeed the corresponding setting was set to on in the domain antispam settings.
Clearing it did the trick.
Emails are processed and delivered normally now.

Thank you for the help

Regards

Miltos