Hello,

The protocol between the shows(8) daemon and the postqueue(1) command
has changed.

     postqueue: warning: unexpected attribute reason from public/showq socket 
(expecting: log_class)

The warning message demonstrates that your script uses the postqueue
command from Postfix 3.11-20251218, but your showq daemon runs an
older Postfix version.

To debug version mismatches like this, Postfix binaries are stamped
with a mail version string. Here are mine:

     % strings /usr/sbin/postqueue | grep mail_version=
     mail_version=3.11-20251218

     % strings /usr/libexec/postfix/showq | grep mail_version=
     mail_version=3.11-20251218

Maybe you can

     % find /usr \( -name postqueue -o -name showq \)  |
        xargs strings -af | grep mail_version=

For me, that produces

/usr/sbin/postqueue: mail_version=3.11-20251218
/usr/libexec/postfix/showq: mail_version=3.11-20251218

root@butterfly:/usr/sbin# find /usr -name postqueue | xargs strings -af | grep 
mail_version=
/usr/sbin/postqueue: mail_version=3.11-20251218

root@butterfly:/usr/sbin# find /usr -name showq | xargs strings -af | grep 
mail_version=
/usr/lib/postfix/sbin/showq: mail_version=3.8.6
/usr/lib/postfix/showq: mail_version=3.11-20251218

Hmm. Now we have something. Or not. I moved the /usr/lib/postfix/sbin dir to 
/usr/lib/postfix/sbin.old to deactivate it -in case it might be used, which I 
doubt. postfix stop ; postfix start. no errors.

Then
root@butterfly:/usr/lib/postfix# !ma
mail -s test [email protected]
Cc:
test
test
.

root@butterfly:/usr/lib/postfix# mq
postqueue: warning: unexpected attribute reason from public/showq socket 
(expecting: log_class)
postqueue: fatal: malformed showq server response

Same situation.

root@butterfly:/etc/postfix# grep sbin main.cf
command_directory = /usr/sbin
sendmail_path = /usr/sbin/sendmail

I guess the .../sbin/ dir was from the original ubuntu package.


Florian



_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to