For it's first installation, Clement configures itself
under clement.'server_domain.name'.
You must update your DNS to link (A or CNAME) hostname (clement)
to your server IP. A quick and dirty way is to add the definition
directly within /etc/hosts (or lmhost) if you do not want to
change your DNS at first.
URL http://clement.'your_domain.name' should display something
like THIS
When Clement installs itself, it creates user root@'server_domain.name', using
root encrypted password found within /etc/shadow. As such, to login within
Clement you can use your own server root password.
Once logged in Clement you should have a page similar to this: WEB page
You can access this FAQ from your local server Clement, click on
(bottom right in all clement pages).
While it might be convenient, it is not mandatory to have Clement
working to reach the FAQ.
Clement interface is nice enough, how can I receive Email?
When installing itself, Clement extract the server current domain and
set its readiness to accept Email to this domain. The root user is defined, and "abuse", "clement" and "postmaster" are all aliased root@'your_domain.name'.
You must set 'your_domain.name' MX to be your server IP, and any email
to "root", "abuse", "clement" and "postmaster" will be accepted.
Well, I am not yet ready to change my main domain MX without comprehensive testing first!
Clicking on [Domain Manag.] icon, you can add a domain of your own
(We'll use testing.'your_domain.name' for our example) to be used as test bench.
Once created, user "root", "abuse" and "postmaster" are automaticaly added as valid users for this new domain.
Change this test domain MX in your DNS and try to send an email from your favorite public
service (hotmail, google, etc..).
Once received by Clement, an email entry is added to the main page, and the "status" and "time"
URL links allow to know more about the email exchange with remote server.
Seems Clement received my test email, how come I can't read it?
Clement is working with dovecot to retreive email. Let's say your test email
was sent to postmaster@testing.'your_domain.name', because of preset aliases,
mail reached root@testing.'your_domain.name' mailbox.
Reading it is fairly standard, providing root@testing.'your_domain.name'
as username and account password to retrieve the email.
(When root@testing.'your_domain.name' account was created, the encrypted server
root password was used too, so use your own root passwd to read the test email)
I've read the Email, how can I add other email account to testing.'your_domain.name'?
Click on [Domain Manag.] -> click on testing.'your_domain.name'
click on the 'New user' folder icon to open it. Add user name and set a password.
Once done click on the 'opened folder icon' to close the entry.
The new user will appear in the domain user list.
You can now send email to that user.
Clement seems to be having issues, where can I find log'd information?
All trouble, alert or Clement 'questioning' are reported
via syslog. you can check /var/log/messages to see about it.
In normal operation, Clement generates very detailed logs, those
logs are stored within the ~clement/logs directory. Logs are generated
on a daily basis, the log 'event-YYYYMMDD.jrl' is the first that should be investigated in case you have question about an email. ALL contact from
remote server are reported, even if the exchange was not successful (email
rejected, remote error, etc...).
If logs are still not detailed enough, you can restart clement after commenting out
the line OPTIONS="-d9" within the /etc/sysconfig/clement file.
Then /var/log/messages will trace detailed clement activities.
My email server is already configured, can I simply use Clement as a front end?
Yes, click on [groups Manag.] and add another group.
To have filtered email forwarded to you internal server, make sure
entry 'Remote SMTP' and 'Remote SMTP Port' are set.
Those values will be used by Clement to check users' very existence on the
internal email server.
You just need to change the domain you want to forward within your DNS,
change the MX to be Clement server IP number. Clement will automaticaly discover domain
to be forwarded by requesting to the internal server.
Clement put some E-mail in server quarantine area,
how can I have that E-mail transmitted.
Easy enough, in the Clement main web page, find out the entry log about
the quarantined email, click on the "quarantine" status and confirm you wish
to receive the email. Mail will be transmitted to you on the spot and
clement will know you want to receive this originator, and next time, mail
will be accepted by "special agreement".
Same, you can click on "rejected" or "accepted" status to have the
Clement current choice overridden for next receiving.
What happen to old E-mail stored in server quarantine area?
A cron shell is executed every day and quarantined E-mail older than "$timeQuar"
are removed. Configuration parameters are within file /etc/sysconfig/clement and
can be used to fine tune Clement parameters according your needs.
Can I use Clement as smart host to post email?
Yes, it is recommended to use Clement to relay email to the outside, each time an email is sent, Clement white-list the connection between your domain email and remote recipient, as such the recipient's answer to initial originator will be accepted regardless of the remote server SBL status or configuration.
Can a plain user access clement?
Yes, there is 4 level of users:
- The root level, this is the super admin level, which can create group, domain and user,
- The group level, which can create domain and user.
- The domain level, which can create user
- The standard user which only priviledge is to be able to change is own password.