[Postfix] – warning: mail_queue_enter: create file maildrop Permission denied

After trying to setup postgrey, I had a lot of warning messages in my mail.log file like this:

May  7 12:26:19 gandalf postfix/postdrop[6065]: warning: mail_queue_enter: create file maildrop/713410.6065: Permission denied
May  7 12:26:29 gandalf postfix/postdrop[6119]: warning: mail_queue_enter: create file maildrop/724102.6119: Permission denied
May  7 12:26:29 gandalf postfix/postdrop[6065]: warning: mail_queue_enter: create file maildrop/734104.6065: Permission denied
May  7 12:26:39 gandalf postfix/postdrop[6119]: warning: mail_queue_enter: create file maildrop/744803.6119: Permission denied
May  7 12:26:39 gandalf postfix/postdrop[6065]: warning: mail_queue_enter: create file maildrop/754805.6065: Permission denied
May  7 12:26:49 gandalf postfix/postdrop[6119]: warning: mail_queue_enter: create file maildrop/765505.6119: Permission denied
May  7 12:26:49 gandalf postfix/postdrop[6065]: warning: mail_queue_enter: create file maildrop/775505.6065: Permission denied
May  7 12:26:59 gandalf postfix/postdrop[6119]: warning: mail_queue_enter: create file maildrop/786207.6119: Permission denied

To get rid of this messages, I had to do the following:

root@gandalf:/var/spool/postfix# postfix check
postfix/postfix-script: warning: not owned by group postdrop: /var/spool/postfix/public
postfix/postfix-script: warning: not owned by group postdrop: /var/spool/postfix/maildrop

SOLUTION:

root@gandalf:/var/spool/postfix# /etc/init.d/postfix stop
root@gandalf:/var/spool/postfix# killall -9 postdrop
root@gandalf:/var/spool/postfix# chgrp -R postdrop /var/spool/postfix/public
root@gandalf:/var/spool/postfix# chgrp -R postdrop /var/spool/postfix/maildrop/
root@gandalf:/var/spool/postfix# postfix check
root@gandalf:/var/spool/postfix# postfix reload

23 thoughts on “[Postfix] – warning: mail_queue_enter: create file maildrop Permission denied

  1. Thank you !!

    With mine it was:
    postfix/postfix-script: warning: not owned by group postdrop: /usr/sbin/postqueue
    postfix/postfix-script: warning: not owned by group postdrop: /usr/sbin/postdrop

    And after chgrp-ing those two files to postdrop:
    postfix/postfix-script: warning: not set-gid or not owner+group+world executable: /usr/sbin/postqueue
    postfix/postfix-script: warning: not set-gid or not owner+group+world executable: /usr/sbin/postdrop

    A ‘chmod g+s /usr/sbin/postqueue /usr/sbin/postdrop’ then fixed that.

  2. Thanks for the info. I had the same ownesrship and set-gid issues as Terry did. Strange thing is that this issue began after a power outage a few days ago.

  3. Gràcis, tio! Això ha estat un 10! Melassa!
    Déu t’ho pagui amb fills 😉

  4. Excelente ayuda amigo, funciono perfecto.

    Excelent job, its work fine!! Thanks

    /etc/init.d/postfix stop
    killall -9 postdrop
    chgrp -R postdrop /var/spool/postfix/public
    chgrp -R postdrop /var/spool/postfix/maildrop/
    postfix check
    /etc/init.d/postfix start

  5. Thanks a lot for that hint!
    In my case I had the following issues:

    postfix/postfix-script: warning: not owned by group postdrop: /usr/sbin/postqueue
    postfix/postfix-script: warning: not owned by group postdrop: /usr/sbin/postdrop
    postfix/postfix-script: warning: not set-gid or not owner+group+world executable: /usr/sbin/postqueue
    postfix/postfix-script: warning: not set-gid or not owner+group+world executable: /usr/sbin/postdrop

    Solved with:
    chgrp -R postdrop /var/spool/postfix/public
    chgrp -R postdrop /var/spool/postfix/maildrop/
    chown root:postdrop /usr/sbin/postqueue /usr/sbin/postdrop
    chmod g+s /usr/sbin/postqueue /usr/sbin/postdrop

  6. Hi would you mind stating which blog platform you’re using? I’m looking to start
    my own blog in the near future but I’m having a tough time deciding between BlogEngine/Wordpress/B2evolution and Drupal. The reason I ask is because your design and style seems different then most blogs and I’m looking for something completely unique.
    P.S Apologies for being off-topic but I had to ask!

Leave a Reply