Domainkey with postfix in fedora-8 OS

Discussion in 'HOWTO-Related Questions' started by rajib, Jul 16, 2009.

  1. rajib

    rajib New Member

    HI !

    I am using dk-milter and Postfix in fedora-8 to implement domainkey.

    But when I putting following to statement in /postfix/main.cf


    smtpd_milters = unix:/var/run/dk-milter/dk.sock unix:/var/run/dk-milter/dk.sock
    non_smtpd_milters = unix:/var/run/dk-milter/dk.sock unix:/var/run/dk-milter/dk.sock


    I am getting ERROR :: =======>> stat=Deferred:
    ================

    Jul 16 17:02:31 time2travelindia postfix/smtpd[5280]: NOQUEUE: milter-reject: EHLO from localhost.localdomain[127.0.0.1]: 451 4.7.1 Service unavailable - try again later; proto=SMTP
    Jul 16 17:02:31 time2travelindia postfix/smtpd[5280]: NOQUEUE: milter-reject: MAIL from localhost.localdomain[127.0.0.1]: 451 4.7.1 Service unavailable - try again later; proto=ESMTP helo=<time2travelindia.com>
    Jul 16 17:02:31 time2travelindia sendmail[5279]: n6GBWVlX005279: [email protected], ctladdr=addate@localhost (501/501), delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=30556, relay=[127.0.0.1] [127.0.0.1], dsn=4.0.0, stat=Deferred: 451 4.7.1 Service unavailable - try again later
    Jul 16 17:02:31 time2travelindia postfix/smtpd[5280]: disconnect from localhost.localdomain[127.0.0.1]
    Jul 16 17:02:32 time2travelindia dovecot: imap-login: Login: user=<addate>, method=PLAIN, rip=::ffff:127.0.0.1, lip=::ffff:127.0.0.1, secured
    Jul 16 17:02:32 time2travelindia dovecot: IMAP(addate): Disconnected: Logged out
    Jul 16 17:02:32 time2travelindia dovecot: imap-login: Login: user=<addate>, method=PLAIN, rip=::ffff:127.0.0.1, lip=::ffff:127.0.0.1, secured
    Jul 16 17:02:32 time2travelindia dovecot: IMAP(addate): Disconnected: Logged out
    Jul 16 17:06:17 time2travelindia dovecot: imap-login: Login: user=<addate>, method=PLAIN, rip=::ffff:127.0.0.1, lip=::ffff:127.0.0.1, secured
    Jul 16 17:06:17 time2travelindia dovecot: IMAP(addate): Disconnected: Logged out


    If I do not put those two statement , mail is going from my mail fedora-8 server.


    I would like to know how this problem will be solve ???????
    Any help regarding this will be appreciated.
     
  2. topdog

    topdog Active Member

    Either postfix cannot access the milter socket or the milter is not running. Check that, you can also try running the milter on a tcp port instead.
     
  3. rajib

    rajib New Member

    HI,

    dk-milter is ruining successfully.
    only when I placing these two statements in /postfix/main.cf

    smtpd_milters = unix:/var/run/dk-milter/dk.sock
    non_smtpd_milters = unix:/var/run/dk-milter/dk.sock

    on that time showing mail stat=Deferred.


    If I do not put these two state ment in /postfix/main.cf mail is going successfully.


    Mail stat=Deferred ERROR ::
    =====================


    Jul 17 01:04:26 time2travelindia postfix/smtpd[4049]: warning: connect to Milter service unix:/var/run/dk-milter/dk.sock: Permission denied
    Jul 17 01:04:26 time2travelindia postfix/smtpd[4049]: NOQUEUE: milter-reject: CONNECT from localhost.localdomain[127.0.0.1]: 451 4.7.1 Service unavailable - try again later; proto=SMTP
    Jul 17 01:04:26 time2travelindia postfix/smtpd[4049]: NOQUEUE: milter-reject: EHLO from localhost.localdomain[127.0.0.1]: 451 4.7.1 Service unavailable - try again later; proto=SMTP
    Jul 17 01:04:26 time2travelindia postfix/smtpd[4049]: NOQUEUE: milter-reject: MAIL from localhost.localdomain[127.0.0.1]: 451 4.7.1 Service unavailable - try again later; proto=ESMTP helo=<time2travelindia.com>
    Jul 17 01:04:26 time2travelindia sendmail[4048]: n6GJYQWc004048: [email protected], ctladdr=addate@localhost (501/501), delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=30535, relay=[127.0.0.1] [127.0.0.1], dsn=4.0.0, stat=Deferred: 451 4.7.1 Service unavailable - try again later
    Jul 17 01:04:26 time2travelindia postfix/smtpd[4049]: disconnect from localhost.localdomain[127.0.0.1]
    Jul 17 01:04:26 time2travelindia dovecot: imap-login: Login: user=<addate>, method=PLAIN, rip=::ffff:127.0.0.1, lip=::ffff:127.0.0.1, secured
    Jul 17 01:04:26 time2travelindia dovecot: IMAP(addate): Disconnected: Logged out
    Jul 17 01:04:26 time2travelindia dovecot: imap-login: Login: user=<addate>, method=PLAIN, rip=::ffff:127.0.0.1, lip=::ffff:127.0.0.1, secured
    Jul 17 01:04:26 time2travelindia dovecot: IMAP(addate): Disconnected: Logged out
    Jul 17 01:05:19 time2travelindia dovecot: imap-login: Login: user=<addate>, method=PLAIN, rip=::ffff:127.0.0.1, lip=::ffff:127.0.0.1, secured
    Jul 17 01:05:19 time2travelindia dovecot: IMAP(addate): Disconnected: Logged out




    I would like to know who to solve this problem.
     
  4. topdog

    topdog Active Member

    Can you not see that postfix is clearly telling you that i cannot access the milter socket ?

    Jul 17 01:04:26 time2travelindia postfix/smtpd[4049]: warning: connect to Milter service unix:/var/run/dk-milter/dk.sock: Permission denied
     
  5. rajib

    rajib New Member

    HI,

    What exactly doing these following two statements in /postfix/main.cf ??

    smtpd_milters = unix:/var/run/dk-milter/dk.sock
    non_smtpd_milters = unix:/var/run/dk-milter/dk.sock


    only create socket ??

    what is exact function of smtpd_milters, non_smtpd_milters in main.cf .


    Any help regarding this will be appreciated.
    Thanks for response.
     
  6. topdog

    topdog Active Member

    That is how postfix sends the message to the milter application.
     
  7. rajib

    rajib New Member

    HI,

    how to connect

    connect to Milter service unix:/var/run/dk-milter/dk.sock: ?????


    Thanks.
     
  8. topdog

    topdog Active Member

    what is the output of
    Code:
    ls -l /var/run/dk-milter/dk.sock
    The postfix user or group needs to be able to read and write to that socket
     
  9. rajib

    rajib New Member

    Getting this is it right ???

    [root@PSC ~]# ls -l /var/run/dk-milter/dk.sock
    srwxrwx--- 1 dk-milt mail 0 2009-07-17 01:04 /var/run/dk-milter/dk.sock



    Thanks.
     
  10. topdog

    topdog Active Member

    what is the output of
    Code:
    sestatus
    ?
     
  11. topdog

    topdog Active Member

    where do you have the sockets listed twice here ?
    Code:
    smtpd_milters = unix:/var/run/dk-milter/dk.sock unix:/var/run/dk-milter/dk.sock
    non_smtpd_milters = unix:/var/run/dk-milter/dk.sock unix:/var/run/dk-milter/dk.sock
    It should be

    Code:
    smtpd_milters = unix:/var/run/dk-milter/dk.sock 
    non_smtpd_milters = unix:/var/run/dk-milter/dk.sock 
     
  12. rajib

    rajib New Member

    sestatus
    SELinux status: enabled
    SELinuxfs mount: /selinux
    Current mode: enforcing
    Mode from config file: enforcing
    Policy version: 21
    Policy from config file: targeted
     
  13. topdog

    topdog Active Member

    I suspect that is the issue, either you create a custom module using audit2allow or you disable selinux which ever is easier for you.
     
  14. rajib

    rajib New Member


    Yes I have given once

    smtpd_milters = unix:/var/run/dk-milter/dk.sock
    non_smtpd_milters = unix:/var/run/dk-milter/dk.sock

    But same problem.
     
  15. rajib

    rajib New Member


    Is it right ???
     
  16. rajib

    rajib New Member

    HI .

    Thanks for communication.
     
  17. rajib

    rajib New Member

    [root@PSC Test]# sestatus
    SELinux status: enabled
    SELinuxfs mount: /selinux
    Current mode: enforcing
    Mode from config file: enforcing
    Policy version: 21
    Policy from config file: targeted
     
  18. rajib

    rajib New Member

    HI,

    how to teporary disable SElinux ??
     
  19. falko

    falko Super Moderator Howtoforge Staff

    Run
    Code:
    setenforce 0
     
  20. rajib

    rajib New Member

    HI I have soled . It's working properly.


    HI friend thanks for communication.
     

Share This Page