php mail not going out stuck in mail queue

Discussion in 'Installation/Configuration' started by hellofantastic, Oct 27, 2014.

  1. hellofantastic

    hellofantastic New Member

    Hello , if anyone has insight into this dilemma, would be appriciated.

    Have ispconfig 3 on centos 6.5 vps, wordpress site installed from APS installer.
    Forgot pass word emails, php mail() emails are sitting in the mail queue.

    netstat -tap has these kinds of entries for smtp

    tcp 0 0 *:ftp *:* LISTEN 7456/pure-ftpd (SER
    tcp 0 0 *:domain *:* LISTEN 24186/named
    tcp 0 0 *:ssh *:* LISTEN 938/sshd
    tcp 0 0 *:smtp *:* LISTEN 10871/master
    tcp 0 0 localhost:rndc *:* LISTEN 24186/named
    tcp 0 0 *:https *:* LISTEN 2661/httpd
    tcp 1 0 localhost:smtp localhost:54677 CLOSE_WAIT -
    tcp 1 0 localhost:smtp localhost:54644 CLOSE_WAIT -
    tcp 1 0 localhost:smtp localhost:54841 CLOSE_WAIT -
    tcp 1 0 localhost:smtp localhost:54850 CLOSE_WAIT -
    tcp 1 0 localhost:smtp localhost:54740 CLOSE_WAIT -
    tcp 1 0 localhost:smtp localhost:54804 CLOSE_WAIT -
    tcp 1 0 localhost:smtp localhost:54776 CLOSE_WAIT -
    tcp 1 0 localhost:smtp localhost:54813 CLOSE_WAIT -
    tcp 1 0 localhost:smtp localhost:54832 CLOSE_WAIT -


    the maillog has
    Oct 27 11:23:22 mydomain postfix/master[10871]: warning: process /usr/libexec/postfix/smtpd pid 17628 exit status 1
    Oct 27 11:23:22 mydomain postfix/master[10871]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling
    Oct 27 11:23:58 mydomain postfix/cleanup[17710]: fatal: open database /etc/mailman/virtual-mailman.db: No such file or directory
    Oct 27 11:23:59 mydomain postfix/master[10871]: warning: process /usr/libexec/postfix/cleanup pid 17710 exit status 1
    Oct 27 11:23:59 mydomain postfix/master[10871]: warning: /usr/libexec/postfix/cleanup: bad command startup -- throttling

    the mailman one I assume is okay as I opted out of installing it I also did not install squirrel mail
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    please run:

    touch /etc/mailman/virtual-mailman
    postmap /etc/mailman/virtual-mailman
    /etc/init.d/postfix restart
     
  3. hellofantastic

    hellofantastic New Member

    touch: cannot touch `/etc/mailman/virtual-mailman': No such file or directory

    but find mailman gives /var/lib/mailman

    I ask should I redo with that directory addition? didn't want to risk a deeper mess up
    touch /var/lib/mailman/virtual-mailman ?
     
    Last edited: Oct 27, 2014
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    mkdir /etc/mailman
    touch /etc/mailman/virtual-mailman
    postmap /etc/mailman/virtual-mailman
    /etc/init.d/postfix restart
     
  5. hellofantastic

    hellofantastic New Member

    okayy the plot thickens
    netstat show *smtp listening

    but maillog:
    C567EB4314 578 Mon Oct 27 12:32:42 [email protected]
    (host 127.0.0.1[127.0.0.1] said: 451 4.5.0 id=12498-01 - Temporary MTA failure on relaying, From MTA() during fwd-connect (No greeting, dt: 1.017 s): id=12498-01 (in reply to end of DATA command))
    [email protected]

    CA1BFB430C 380 Mon Oct 27 11:16:27 [email protected]
    (host 127.0.0.1[127.0.0.1] said: 451 4.5.0 id=12499-02 - Temporary MTA failure on relaying, From MTA() during fwd-connect (No greeting, dt: 35.036 s): id=12499-02 (in reply to end of DATA command))
    [email protected]

    where dallas@ is from me running site page to send out an email

    **update **
    Sorry that's mailq not maillog this is maillog:

    Oct 27 17:09:24 mydomain postfix/smtp[12695]: 78F21B431C: to=<[email protected]>, relay=127.0.0.1[127.0.0.1]:10024, conn_use=4, delay=484, delays=0.02/433/0/50, dsn=4.5.0, status=deferred (host 127.0.0.1[127.0.0.1] said: 451 4.5.0 id=12498-03-4 - Temporary MTA failure on relaying, From MTA() during fwd-connect (No greeting, dt: 35.037 s): id=12498-03-4 (in reply to end of DATA command))
    Oct 27 17:09:33 mydomain postfix/smtpd[13417]: connect from unknown[127.0.0.1]
    Oct 27 17:09:33 mydomain postfix/smtpd[13417]: warning: SASL: Connect to private/auth failed: No such file or directory
    Oct 27 17:09:33 mydomain postfix/smtpd[13417]: fatal: no SASL authentication mechanisms
    Oct 27 17:09:33 mydomain postfix/smtpd[13419]: connect from unknown[127.0.0.1]
    Oct 27 17:09:33 mydomain postfix/smtpd[13419]: warning: SASL: Connect to private/auth failed: No such file or directory
    Oct 27 17:09:33 mydomain postfix/smtpd[13419]: fatal: no SASL authentication mechanisms
    Oct 27 17:09:34 mydomain postfix/master[12687]: warning: process /usr/libexec/postfix/smtpd pid 13417 exit status 1
    Oct 27 17:09:34 mydomain postfix/master[12687]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling
    Oct 27 17:09:34 mydomain postfix/master[12687]: warning: process /usr/libexec/postfix/smtpd pid 13419 exit status 1
    Oct 27 17:10:01 mydomain postfix/smtpd[13454]: connect from localhost[::1]
    Oct 27 17:10:01 mydomain postfix/smtpd[13454]: warning: SASL: Connect to private/auth failed: No such file or directory
    Oct 27 17:10:01 mydomain postfix/smtpd[13454]: fatal: no SASL authentication mechanisms
    Oct 27 17:10:02 mydomain postfix/master[12687]: warning: process /usr/libexec/postfix/smtpd pid 13454 exit status 1
    Oct 27 17:10:02 mydomain postfix/master[12687]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling

    And restarting apache show this
    Starting httpd:
    [Mon Oct 27 18:13:46 2014] [warn] NameVirtualHost *:443 has no VirtualHosts
    [Mon Oct 27 18:13:46 2014] [warn] NameVirtualHost *:80 has no VirtualHosts
    [ OK ]
     
    Last edited: Oct 27, 2014
  6. till

    till Super Moderator Staff Member ISPConfig Developer

    Restart dovecot.
     
  7. hellofantastic

    hellofantastic New Member

    [email protected] ~]# service dovecot restart
    Stopping Dovecot Imap: [FAILED]
    Starting Dovecot Imap: doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 9: Unknown setting: ssl_protocols
    [FAILED]
     
  8. hellofantastic

    hellofantastic New Member

    okay so digging further I found that dovecot 2.0.9 , my version with ispconfig doesn't support the ssl_protocols. Do i want to update dovecot and edit some ispconfig 3 files? (Centos 6.5)
     
  9. hellofantastic

    hellofantastic New Member

    or comment out the ssl protocols line and look at other apache configs to secure against a poodle bite?
     
  10. till

    till Super Moderator Staff Member ISPConfig Developer

    I think its not a good idea to try to update to a newer dovecot version on your server, so better just comment out that line in dovecot.conf. The new ispconfig version that had been released today recognizes dovecot versions better and will not activate that option for versions < 2.1.
     
  11. hellofantastic

    hellofantastic New Member

    okay commented out emails came from site came in... how concerned should I be about the poodle attack business, I am launching a production site this week on this vps. And thank you for all your help.
     

Share This Page