Wrong link in Message Quarantine Report
- BruceLeeRoy
- Posts: 47
- Joined: 01 May 2015 13:27
Wrong link in Message Quarantine Report
So I haven't been able to find where I can define efa's url other than in the initial setup. I'd like to be able to allow some of the domain users to see their Quarantine Report. Right now I have been getting the reports myself but the link in them is incorrect, and comes up like this:
http://efa/mailscanner//viewmail.php?id=xxxxxxx
it works if I change it in the browser to:
http://mail.mydomain.com/mailscanner//v ... id=xxxxxxx
It also gives the complaint: "MailScanner has detected a possible fraud attempt from "efa" claiming to be" which is another thing I'm trying to fix.
http://efa/mailscanner//viewmail.php?id=xxxxxxx
it works if I change it in the browser to:
http://mail.mydomain.com/mailscanner//v ... id=xxxxxxx
It also gives the complaint: "MailScanner has detected a possible fraud attempt from "efa" claiming to be" which is another thing I'm trying to fix.
- shawniverson
- Posts: 3650
- Joined: 13 Jan 2014 23:30
- Location: Indianapolis, Indiana USA
- Contact:
Re: Wrong link in Message Quarantine Report
Use EFA-Configure to set your hostname...
Log into the console...
Choose option 4) IP Settings and make your changes to the hostname and the domain name.
Log into the console...
Choose option 4) IP Settings and make your changes to the hostname and the domain name.
- BruceLeeRoy
- Posts: 47
- Joined: 01 May 2015 13:27
Re: Wrong link in Message Quarantine Report
Yes, just double checked that and they are properly set. That's why I'm confused.
Re: Wrong link in Message Quarantine Report
If you logon to the console (ssh to the box and then option 1) what do you get when you run:
you should get back the full hostname of your server in both results.
Code: Select all
cat /etc/MailScanner/MailScanner.conf | grep -v "#"| grep "Hostname = " && hostname
Version eFa 4.x now available!
- shawniverson
- Posts: 3650
- Joined: 13 Jan 2014 23:30
- Location: Indianapolis, Indiana USA
- Contact:
Re: Wrong link in Message Quarantine Report
Quarantine Report uses the hostname as defined by the system.
After running the above command, check /etc/sysconfig/network for a HOSTNAME=<myhostname> entry (no spaces and no <>). If there isn't one there, you need to add one. EFA-Configure assumes that one is already present (as there should be).
After doing this, either restart or run
After running the above command, check /etc/sysconfig/network for a HOSTNAME=<myhostname> entry (no spaces and no <>). If there isn't one there, you need to add one. EFA-Configure assumes that one is already present (as there should be).
After doing this, either restart or run
Code: Select all
sudo service network restart
- BruceLeeRoy
- Posts: 47
- Joined: 01 May 2015 13:27
Re: Wrong link in Message Quarantine Report
ok so cat of the mailscanner.conf file returned 2 lines, the first line was the proper hostname, then 2nd line was just "efa"
I changed /etc/sysconfig/network as it was set HOSTNAME="efa"
This should fix it! I'll know when I get the next Quarantine report, thanks for the help!
I changed /etc/sysconfig/network as it was set HOSTNAME="efa"
This should fix it! I'll know when I get the next Quarantine report, thanks for the help!
- shawniverson
- Posts: 3650
- Joined: 13 Jan 2014 23:30
- Location: Indianapolis, Indiana USA
- Contact:
Re: Wrong link in Message Quarantine Report
Did you happen to run system-config-network at some point?
That is not something EFA would have put into /etc/sysconfig/network.
That is not something EFA would have put into /etc/sysconfig/network.
- BruceLeeRoy
- Posts: 47
- Joined: 01 May 2015 13:27
Re: Wrong link in Message Quarantine Report
I don't remember, most likely I did. However, changing the hostname there didnt fix the link problem.
- BruceLeeRoy
- Posts: 47
- Joined: 01 May 2015 13:27
Re: Wrong link in Message Quarantine Report
when I do this I get:darky83 wrote:If you logon to the console (ssh to the box and then option 1) what do you get when you run:
you should get back the full hostname of your server in both results.Code: Select all
cat /etc/MailScanner/MailScanner.conf | grep -v "#"| grep "Hostname = " && hostname
Hostname = <proper hostname of my server>
efa
I'm assuming the 2nd line "efa' is wrong
Re: Wrong link in Message Quarantine Report
See the file /etc/sysconfig/network
it should state a line:
if your domain.com is missing there, add it and reboot
it should state a line:
Code: Select all
HOSTNAME = efa.domain.com
Version eFa 4.x now available!
- BruceLeeRoy
- Posts: 47
- Joined: 01 May 2015 13:27
Re: Wrong link in Message Quarantine Report
the correct info is in /etc/sysconfig/network
but when I type these commands:
[root@efa ~]# hostname
efa
[root@efa ~]# domainname
(none)
I found if I set the hostname with the hostname command, it changes to the corrent hostname, but eventually it will change it back to "efa" must be from some cronjob?
but when I type these commands:
[root@efa ~]# hostname
efa
[root@efa ~]# domainname
(none)
I found if I set the hostname with the hostname command, it changes to the corrent hostname, but eventually it will change it back to "efa" must be from some cronjob?
Re: Wrong link in Message Quarantine Report
Lets see, the domain should be set on your system in the following locations:
Can you check these?
Code: Select all
EFA-Config:DOMAINNAME:<domain.com>
hosts:172.18.50.11 <hostname>.<domain.com> <hostname>
MailScanner/rules/sig.html.rules:To: *@<domain.com> /etc/MailScanner/reports/en/inline.sig.in.html
MailScanner/rules/sig.text.rules:To: *@<domain.com> /etc/MailScanner/reports/en/inline.sig.in.txt
MailScanner/MailScanner.conf:Hostname = <hostname>.<domain.com>
sysconfig/network:HOSTNAME=<hostname>.<domain.com>
Version eFa 4.x now available!
- BruceLeeRoy
- Posts: 47
- Joined: 01 May 2015 13:27
Re: Wrong link in Message Quarantine Report
EFA-Config:DOMAINNAME:mydomain.com This is correct
hosts:x.x.x.x mail.mydomain mail This is correct
MailScanner/rules/sig.html.rules & sig.text.rules:
To: *@mydomain.com /etc/MailScanner/reports/en/inline.sig.in.html
To: *@mydomain.com /etc/MailScanner/reports/en/inline.sig.in.txt These are correct
MailScanner/MailScanner.conf:
Hostname = mail.mydomain.com This is correct
sysconfig/network:
HOSTNAME="mail.mydomain.com"
DOMAINNAME="mydomain.com" These are correct
I've set the hostname and domain name using the hostname and domainname commands, they seem to save correctly, then later on it eventually changes itself back to:
[root@efa ~]# hostname
efa
[root@efa ~]# domainname
(none)
Does this after a reboot or after a few hours, almost like there is a cron job or something changing it back to the incorrect values. At one point it almost worked when I got the report by having the hostname "mail" instead of "efa" but the next day changed back to "efa"
hosts:x.x.x.x mail.mydomain mail This is correct
MailScanner/rules/sig.html.rules & sig.text.rules:
To: *@mydomain.com /etc/MailScanner/reports/en/inline.sig.in.html
To: *@mydomain.com /etc/MailScanner/reports/en/inline.sig.in.txt These are correct
MailScanner/MailScanner.conf:
Hostname = mail.mydomain.com This is correct
sysconfig/network:
HOSTNAME="mail.mydomain.com"
DOMAINNAME="mydomain.com" These are correct
I've set the hostname and domain name using the hostname and domainname commands, they seem to save correctly, then later on it eventually changes itself back to:
[root@efa ~]# hostname
efa
[root@efa ~]# domainname
(none)
Does this after a reboot or after a few hours, almost like there is a cron job or something changing it back to the incorrect values. At one point it almost worked when I got the report by having the hostname "mail" instead of "efa" but the next day changed back to "efa"
- shawniverson
- Posts: 3650
- Joined: 13 Jan 2014 23:30
- Location: Indianapolis, Indiana USA
- Contact:
Re: Wrong link in Message Quarantine Report
What's in your interface configuration? Any chance DNS is overriding your hostname?
- BruceLeeRoy
- Posts: 47
- Joined: 01 May 2015 13:27
Re: Wrong link in Message Quarantine Report
There is no DNS server running locally on the efa machine, and these changes are happening locally so has nothing to do with DNS
Here is whats happening after reboot:
EFA-Config:DOMAINNAME:mydomain.com This stays correct
hosts file changes from:
x.x.x.x mail.mydomain.com mail
to:
x.x.x.x efa
MailScanner/rules/sig.html.rules & sig.text.rules:
To: *@mydomain.com /etc/MailScanner/reports/en/inline.sig.in.html
To: *@mydomain.com /etc/MailScanner/reports/en/inline.sig.in.txt
These stay correct
MailScanner/MailScanner.conf:
Hostname = mail.mydomain.com
This stays correct
sysconfig/network:
HOSTNAME="mail.mydomain.com"
changes to
HOSTNAME="efa"
DOMAINNAME="mydomain.com" This stays correct
Hostname shell command: this changes from mail.mydomain.com to efa
Domainname shell command: this changes from mydomain.com to (none)
Here is whats happening after reboot:
EFA-Config:DOMAINNAME:mydomain.com This stays correct
hosts file changes from:
x.x.x.x mail.mydomain.com mail
to:
x.x.x.x efa
MailScanner/rules/sig.html.rules & sig.text.rules:
To: *@mydomain.com /etc/MailScanner/reports/en/inline.sig.in.html
To: *@mydomain.com /etc/MailScanner/reports/en/inline.sig.in.txt
These stay correct
MailScanner/MailScanner.conf:
Hostname = mail.mydomain.com
This stays correct
sysconfig/network:
HOSTNAME="mail.mydomain.com"
changes to
HOSTNAME="efa"
DOMAINNAME="mydomain.com" This stays correct
Hostname shell command: this changes from mail.mydomain.com to efa
Domainname shell command: this changes from mydomain.com to (none)
- shawniverson
- Posts: 3650
- Joined: 13 Jan 2014 23:30
- Location: Indianapolis, Indiana USA
- Contact:
Re: Wrong link in Message Quarantine Report
Although you shouldn't be using dhcp....
See the following post.
https://www.centos.org/forums/viewtopic.php?t=24927
See the following post.
https://www.centos.org/forums/viewtopic.php?t=24927
- BruceLeeRoy
- Posts: 47
- Joined: 01 May 2015 13:27
Re: Wrong link in Message Quarantine Report
I'm not using DHCP
- BruceLeeRoy
- Posts: 47
- Joined: 01 May 2015 13:27
Re: Wrong link in Message Quarantine Report
Found the problem, the hostname was being changed by the VM server. Had to correct it there.