Can't access MailWatch

[tjg88]

When I go to the IP address of my EFA system, I get the prompt for username and password. The 2 Linux accounts I have on the system (root and my personal account) do not work. Is there a separate username for MailWatch?

[shawniverson]

Should be your personal account...

Are you able to secure shell into the system with your personal account?

[tjg88]

Yes, I can SSH into my personal account.

When I try MAilWatch with my personal creds, I get the error: Could not search

[shawniverson]

Are you using LDAP in MailWatch? You may want to turn it off if you are to troubleshoot...

[tjg88]

That was it. I had 636 for the LDAP port. I changed it to 389 and it worked.

[shawniverson]

[tjg88]

How do I set my account to be the admin of MailWatch so that I can see all mail traffic, like admin was in ESVA?

[shawniverson]

Question....does your LDAP happen to have an account with the same name as the one you set up during EFA-Init?

[tjg88]

I have 3 accounts on the EFA box: root, my account, and another SysAdmin account. The other SysAdmin did the EFA-Init, he said he used his account in the EFA-Init. My account and his account exist in LDAP, root does not. I turned off LDAP in the conf.php file, and I cannot log into MailWatch with any of those 3 accounts.

[shawniverson]

Ok.

Let's create another admin for mailwatch so that you can get in....

Look in /etc/EFA-Config...

Find the MAILWATCHSQLPWD and copy it

Code: Select all

/usr/bin/mysql --user=mailwatch --password=<MAILWATCHSQLPWD> mailscanner -e "INSERT INTO users SET username = 'tempadmin', password = md5('<SOMEPASSWORD>'), fullname = 'tempadmin', type ='A'"

Where <MAILWATCHSQLPWD> is your mailwatch sql password and <SOMEPASSWORD> is a password of your choosing without the < >.

Then log in as tempadmin. You should be able to see the other accounts and be able to reset passwords, etc.

[tjg88]

I actually blew the server away and started from scratch and I'm able to access it now. I think I didn't have the right creds that were setup in the original server. Thanks for your help, anyway. Keep up the great work!

[tjg88]

I update EFA to 3.0.0.2 and I now get this error in the MailWatch GUI:

MailScanner: YES 3 children
Postfix: YES 1 proc(s)
Load Average:
1.82 2.17 1.59
Please verify read permissions on /var/spool/postfix/hold and /var/spool/postfix/incoming

The permissions for these 2 directories are set to 700, same as my ESVA box. I tried changing it to 740, and the errors didn't go away.
Any idea??

[shawniverson]

The 3.0.0.2 update runs a yum update.

Can you tell me what version of postfix you are on?

Code: Select all

rpm -qa | grep postfix

[shawniverson]

Verify the following owners on the hold and incoming directories:

drwxr-x---. 2 postfix apache 20480 Feb 20 14:01 hold
drwxr-x---. 2 postfix apache 12288 Feb 20 14:01 incoming

[tjg88]

The 3.0.0.2 update runs a yum update.

Can you tell me what version of postfix you are on?

Code: Select all

rpm -qa | grep postfix

postfix-2.6.6-6.el6_5.x86_64

[tjg88]

Verify the following owners on the hold and incoming directories:

drwxr-x---. 2 postfix apache 20480 Feb 20 14:01 hold
drwxr-x---. 2 postfix apache 12288 Feb 20 14:01 incoming

I changed permissions to what you listed:

drwxr-x---. 2 postfix root 4096 Feb 20 14:04 hold
drwxr-x---. 2 postfix root 4096 Feb 20 14:04 incoming

The owner is postfix:root, not postfix:apache like you have though. Should this be changed?

[shawniverson]

Yep, that's the problem. Postfix has updated and reset permissions.

Opening an urgent bug for this to fix quickly.

Yes, please change the ownership to postfix:apache

Code: Select all

chown postfix:apache /var/spool/postfix/incoming
chown postfix:apache /var/spool/postfix/hold
 

[tjg88]

OK, I made the change and the error went away.

[shawniverson]

https://github.com/E-F-A/v3/issues/53