postfix/qmgr[5875]: warning: connect to transport private/spamassassin: No such file or directory

Discussion in 'Installation/Configuration' started by RobPatton, May 26, 2025.

  1. RobPatton

    RobPatton Member

    So I suspect this has been ongoing a very long time, and I've just not noticed, or opted to ignore it.

    Centos 7, latest ispconfig installed

    Everything (else) is seemingly working perfectly. Except it turns out that I had some email stuck.
    When this happens, I get a
    postfix/qmgr[5875]: warning: connect to transport private/spamassassin: No such file or directory

    If I do a postqueue -f, I get this messages for every email stuck in that que.

    May 26 16:30:10 webhost postfix/error[12133]: 5B5D2435B05A: to=<[email protected]>, relay=none, delay=167097, delays=167097/0.02/0/0.05, dsn=4.3.0, status=deferred (mail transport unavailable)

    I assume the private folder its referring to is /var/spool and yes, there is not a spamassassin file/dir there. Though thats not actually a file or folder, its a socket, (thats where my knowledge ends) Which I dont know how to fix

    Suggestions? Again, everything else is working fine, and only about 3 senders get stuck in this loop/que, which I dont know why, but its dependable...
     
  2. pyte

    pyte Well-Known Member HowtoForge Supporter

    Do you still use a setup with amavis/spamassasin or do you use rspamd?

    If you use rspamd, you can remove the postfix configuration for spamassasin. I assume there is a line like:
    Code:
    content_filter = spamassasin 
    In your postfix main.cf.
     
  3. RobPatton

    RobPatton Member

    I do not use rspamd.

    I have:
    content_filter = amavis:[127.0.0.1]:10024
     
  4. pyte

    pyte Well-Known Member HowtoForge Supporter

  5. RobPatton

    RobPatton Member

    It sounds interesting, will have to see if I can find a centos guide for that. yum install of those apps did not seem to "just work" so I stopped. One of these days when I'm not running "important" things on this box, I'll have to start over with a more modern dist. This install is 10 years old, and I just keep moving the VM to new hardware...
     
  6. pyte

    pyte Well-Known Member HowtoForge Supporter

    Isn't CentOS End of Life already?
     
  7. michelangelo

    michelangelo Active Member

    It is and it is insecure, unless one is using a commercial ELS/ELTS service but even then it is recommended to migrate to a newer distribution like AlmaLinux, if one wants to stay in the CentOS/RHEL universe, because services and programs like PHP from Remi don't receive updates anymore and one would have to patch and build such PHP versions on their own, or they purchase an extended PHP support plan, for example from Tuxcare.
     

Share This Page