Cannot log in via squirrelmail

Discussion in 'Installation/Configuration' started by flipb18b, Mar 12, 2008.

  1. flipb18b

    flipb18b New Member

    I have installed both the SquirrelMail and RoundCube webmail modules from the ISPConfig website. I am having an issue where I can not log into either from any mail enabled user on the server. Any help would be greatly appreciated Thanks, Flip
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    Please have a look into your mail log and post the errors that you find there.
     
  3. flipb18b

    flipb18b New Member

    Mar 13 11:53:34 sls-gb19p2 imapd: Connection, ip=[::ffff:127.0.0.1]
    Mar 13 11:53:34 sls-gb19p2 imapd: LOGOUT, ip=[::ffff:127.0.0.1], rcvd=30, sent=470
    Mar 13 11:53:41 sls-gb19p2 imapd: Connection, ip=[::ffff:127.0.0.1]
    Mar 13 11:53:41 sls-gb19p2 imapd: LOGIN FAILED, user=web1_test, ip=[::ffff:127.0.0.1]
    Mar 13 11:53:46 sls-gb19p2 imapd: LOGOUT, ip=[::ffff:127.0.0.1], rcvd=49, sent=332
    Mar 13 11:55:32 sls-gb19p2 imapd: Connection, ip=[::ffff:127.0.0.1]
    Mar 13 11:55:32 sls-gb19p2 imapd: LOGOUT, ip=[::ffff:127.0.0.1], rcvd=30, sent=470
    Mar 13 11:55:41 sls-gb19p2 imapd: Connection, ip=[::ffff:127.0.0.1]
    Mar 13 11:55:41 sls-gb19p2 imapd: LOGIN FAILED, [email protected], ip=[::ffff:127.0.0.1]
    Mar 13 11:55:46 sls-gb19p2 imapd: LOGOUT, ip=[::ffff:127.0.0.1], rcvd=59, sent=332
     
  4. falko

    falko Super Moderator ISPConfig Developer

    This is the wrong username. Must be something like web1_test, like here:
    Did you send an email first to the user before you tried to fetch mails? Because if it's a new user, the necessary directories are created automatically when the first email arrives.
    Which distribution are you using? What's the output of
    Code:
    netstat -tap
    ?
     
  5. flipb18b

    flipb18b New Member

    I have sent mail to the addresses and I receive it no problem in /var/spool/mail
    The out put I get from netsat is
    Active Internet connections (servers and established)
    Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
    tcp 0 0 localhost:60000 *:* LISTEN 4226/postgrey.pid -
    tcp 0 0 localhost:mysql *:* LISTEN 5375/mysqld
    tcp 0 0 *:www *:* LISTEN 15937/apache2
    tcp 0 0 *:81 *:* LISTEN 5873/ispconfig_http
    tcp 0 0 sls-gb19p2.dca2.:domain *:* LISTEN 750/named
    tcp 0 0 localhost:domain *:* LISTEN 750/named
    tcp 0 0 *:smtp *:* LISTEN 13651/master
    tcp 0 0 localhost:953 *:* LISTEN 750/named
    tcp 0 0 *:https *:* LISTEN 15937/apache2
    tcp 0 0 sls-gb19p2.dca2.s:41133 205.188.7.181:aol ESTABLISHED30881/pork
    tcp 0 0 sls-gb19p2.dca2.s:51171 205.188.7.182:aol ESTABLISHED28744/pork
    tcp6 0 0 *:imaps *:* LISTEN 4617/couriertcpd
    tcp6 0 0 *:pop3s *:* LISTEN 16479/couriertcpd
    tcp6 0 0 *:pop3 *:* LISTEN 16420/couriertcpd
    tcp6 0 0 *:imap2 *:* LISTEN 4591/couriertcpd
    tcp6 0 0 *:ftp *:* LISTEN 16850/proftpd: (acc
    tcp6 0 0 *:ssh *:* LISTEN 4082/sshd
    tcp6 0 0 *:smtp *:* LISTEN 13651/master
    tcp6 0 0 ip6-localhost:953 *:* LISTEN 750/named
    getnameinfo failed
    tcp6 0 2388 sls-gb19p2.dca2.sup:ssh [UNKNOWN]:19122 ESTABLISHED31257/sshd: flip [p
    tcp6 0 0 localhost:imap2 localhost:60987 TIME_WAIT -
     
  6. flipb18b

    flipb18b New Member

    anyone? :)
     
  7. falko

    falko Super Moderator ISPConfig Developer

    You're using Courier which means you must use Maildir, not mbox. Please enable Maildir under Management > Server > Settings > Email and also do this:
    Code:
    postconf -e 'home_mailbox = Maildir/'
    postconf -e 'mailbox_command ='
    /etc/init.d/postfix restart
     
  8. flipb18b

    flipb18b New Member

    I don't know what's going on but I still cannot log in. Any other opinions? Thanks
     
  9. falko

    falko Super Moderator ISPConfig Developer

    Send an email to that account, then try again. If that doesn't help - are there any errors in the mail log?
     
  10. flipb18b

    flipb18b New Member

    Still have had no luck. I have emailed the account. when I attempt to log in I still get the Invalid user name error from sq mail. The errors in my mail log are as fallows

    Mar 19 11:59:22 sls-gb19p2 postfix/anvil[20307]: statistics: max connection rate 1/60s for (smtp:77.101.99.75) at Mar 19 11:56:01
    Mar 19 11:59:22 sls-gb19p2 postfix/anvil[20307]: statistics: max connection count 1 for (smtp:77.101.99.75) at Mar 19 11:56:01
    Mar 19 11:59:22 sls-gb19p2 postfix/anvil[20307]: statistics: max cache size 1 at Mar 19 11:56:01
    Mar 19 12:02:16 sls-gb19p2 imapd: Connection, ip=[::ffff:127.0.0.1]
    Mar 19 12:02:16 sls-gb19p2 imapd: LOGOUT, ip=[::ffff:127.0.0.1], rcvd=30, sent=470
    Mar 19 12:02:26 sls-gb19p2 imapd: Connection, ip=[::ffff:127.0.0.1]
    Mar 19 12:02:26 sls-gb19p2 imapd: LOGIN FAILED, user=web1_test, ip=[::ffff:127.0.0.1]
    Mar 19 12:02:31 sls-gb19p2 imapd: LOGOUT, ip=[::ffff:127.0.0.1], rcvd=49, sent=332
     
  11. falko

    falko Super Moderator ISPConfig Developer

    Does the MX record for the domain you're sending to point to your server? You can check it like this:
    Code:
    dig mx yourdomain.com
     
  12. flipb18b

    flipb18b New Member

    So I dug the mx record

    ; <<>> DiG 9.4.1-P1 <<>> mx www.willthatdo.com
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19029
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

    ;; QUESTION SECTION:
    ;www.willthatdo.com. IN MX

    ;; AUTHORITY SECTION:
    willthatdo.com. 2904 IN SOA ns8.zoneedit.com. soacontact.zoneedit.com. 1173725254 14400 7200 950400 7200

    ;; Query time: 0 msec
    ;; SERVER: 66.36.226.50#53(66.36.226.50)
    ;; WHEN: Thu Mar 20 11:15:15 2008
    ;; MSG SIZE rcvd: 96



    Does this look right?
     
  13. falko

    falko Super Moderator ISPConfig Developer

    No. There's no MX record, so you should create one.
     
  14. flipb18b

    flipb18b New Member

    ok does this look right?
    ; <<>> DiG 9.4.1-P1 <<>> mx willthatdo.com
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 458
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

    ;; QUESTION SECTION:
    ;willthatdo.com. IN MX

    ;; ANSWER SECTION:
    willthatdo.com. 7200 IN MX 0 mail.willthatdo.com.

    ;; ADDITIONAL SECTION:
    mail.willthatdo.com. 7200 IN A 209.160.65.144

    Still cannot log in thanks, Flip
     
  15. falko

    falko Super Moderator ISPConfig Developer

    Yes, looks ok.

    Can you send an email to that account and at the same time have a look at your mail log? What do you see there?
     
  16. flipb18b

    flipb18b New Member

    so now when I look into my mail logs I'm getting this
    Mar 24 17:59:42 willthatdo postfix/cleanup[14632]: 5F9E2A381E0: message-id=<[email protected]>
    Mar 24 17:59:42 willthatdo postfix/bounce[14601]: 4BF87A381D7: sender non-delivery notification: 5AE3DA381D8
    Mar 24 17:59:42 willthatdo postfix/cleanup[14471]: 5AE4AA381DD: message-id=<[email protected]>
    Mar 24 17:59:42 willthatdo postfix/local[14545]: 50DECA381C8: to=<[email protected]>, relay=local, delay=0.06, delays=0.02/0/0/0.04, dsn=2.0.0, status=sent (delivered to command: /usr/bin/procmail -f-)
    Mar 24 17:59:42 willthatdo postfix/qmgr[4763]: 5F9E2A381E0: from=<>, size=2284, nrcpt=1 (queue active)
    Mar 24 17:59:42 willthatdo postfix/qmgr[4763]: 4BF87A381D7: removed
    Mar 24 17:59:42 willthatdo postfix/qmgr[4763]: 50DECA381C8: removed
    Mar 24 17:59:42 willthatdo postfix/qmgr[4763]: 5AE4AA381DD: from=<[email protected]>, size=382, nrcpt=1 (queue active)
    Mar 24 17:59:42 willthatdo postfix/bounce[14502]: 55C55A38181: sender non-delivery notification: 5F9E2A381E0
    Mar 24 17:59:42 willthatdo postfix/qmgr[4763]: 55C55A38181: removed
    Mar 24 17:59:42 willthatdo postfix/qmgr[4763]: 5AE3DA381D8: from=<>, size=2284, nrcpt=1 (queue active)
    Mar 24 17:59:42 willthatdo postfix/smtp[11385]: 5AE4AA381DD: to=<[email protected]>, relay=none, delay=0.06, delays=0.05/0/0.01/0, dsn=5.4.4, status=bounced (Host or domain name
     
  17. falko

    falko Super Moderator ISPConfig Developer

    Did you take a look at the non-delivery notification? It should tell you where the problem is.
     
  18. flipb18b

    flipb18b New Member

    I'm not sure where I should be looking for this bounced email message. I never received a non delivery email back. Is there some place else I should be looking?
     
  19. flipb18b

    flipb18b New Member

    OK so I figured out that procmail wasn't relaying back. I fixed that now here's the error I've been getting
    This is an automatically generated Delivery Status Notification

    Delivery to the following recipient failed permanently:

    [email protected]

    Technical details of permanent failure:
    PERM_FAILURE: SMTP Error (state 13): 554 5.7.1 <[email protected]>: Relay access denied

    ----- Original message -----

    Received: by 10.141.171.6 with SMTP id y6mr3795267rvo.85.1206480683396;
    Tue, 25 Mar 2008 14:31:23 -0700 (PDT)
    Received: by 10.140.185.10 with HTTP; Tue, 25 Mar 2008 14:31:23 -0700 (PDT)
    Message-ID: <[email protected]>
    Date: Tue, 25 Mar 2008 17:31:23 -0400
    From: Steven <[email protected]>
    To: [email protected]
    Subject: Hello
    MIME-Version: 1.0
    Content-Type: multipart/alternative;
    boundary="----=_Part_16963_33365128.1206480683400"

    Also the mail log reads
    Mar 25 18:44:19 willthatdo postfix/smtpd[17543]: NOQUEUE: reject: RCPT from rv-out-0910.google.com[209.85.198.190]: 554 5.7.1 <[email protected]>: Relay access denied; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<rv-out-0910.google.com>
    Mar 25 18:44:19 willthatdo postfix/smtpd[17543]: disconnect from rv-out-0910.google.com[209.85.198.190]
    Mar 25 18:47:39 willthatdo postfix/anvil[17620]: statistics: max connection rate 1/60s for (smtp:209.85.198.190) at Mar 25 18:44:18
     
    Last edited: Mar 25, 2008
  20. till

    till Super Moderator Staff Member ISPConfig Developer

    You are trying to relay a email to [email protected] trough google, this will not work. Either you configure postfix to deliver emails directly or in case google allows realying for authenticated users, configure postfix to authenticate before the message is relayed.
     

Share This Page