You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I just installed v5.4.5-3 of MailScanner on my Ubuntu server (running Plex, using postfix) and configured exactly as described on https://mailscanner.info/postfix
On adding the milter (inet:127.0.0.1:33333) to postfix's main.cf, no mail is delivered to user inbox. Logs suggest "DISCARD" was triggered and also have entries "Unable to kick message" and "Unable to open QMQP socket at 127.0.0.1 on port 628"
I checked the permissions for /var/spool/MailScanner/milterin and /var/spool/MailScanner/milterout and they are as expected: postfix:postfix
To Reproduce
Steps to reproduce the behavior:
Install MailScanner, configure as per installation/config guide, send email to/from domain hosted on server
Expected behavior
Mail passed through MailScanner and delivered to inbox
Examples
-- Below are the logs for a particular message I tested but also seen in logs is "Unable to open QMQP socket at 127.0.0.1 on port 628" repeatedly
Describe the bug
I just installed v5.4.5-3 of MailScanner on my Ubuntu server (running Plex, using postfix) and configured exactly as described on https://mailscanner.info/postfix
On adding the milter (inet:127.0.0.1:33333) to postfix's main.cf, no mail is delivered to user inbox. Logs suggest "DISCARD" was triggered and also have entries "Unable to kick message" and "Unable to open QMQP socket at 127.0.0.1 on port 628"
I checked the permissions for /var/spool/MailScanner/milterin and /var/spool/MailScanner/milterout and they are as expected: postfix:postfix
To Reproduce
Steps to reproduce the behavior:
Install MailScanner, configure as per installation/config guide, send email to/from domain hosted on server
Expected behavior
Mail passed through MailScanner and delivered to inbox
Examples
-- Below are the logs for a particular message I tested but also seen in logs is "Unable to open QMQP socket at 127.0.0.1 on port 628" repeatedly
Server (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: