Archive

Archive for the ‘Mail Services ( POP, SMTP , IMAP and Webmail )’ Category

Squirrel Mail Addess book corrupted

October 6th, 2009

If you are unable to access the Addresses of the squirrelMail and getting the error as given below.

Error:
———————————
Address book is corrupted. Required fields are missing
———————————

Reason:
———————————————–
Then the required fields are missing or not given while adding a address to Personal address book. You need to mention 4 fields without failure which are Nickname,E-mail address,First name,Last name. If you miss any of them you will see above error.
———————————————–
Solution:

Login to shell as Root.

Goto the directory
#cd /home/username/.sqmaildata

You will see three files for each email account which are given below. For example you have address book problem for mail account test@domain.com
————————————
test\@icifirm.com.abook
test\@icifirm.com.pref
test\@icifirm.com.sig
————————————
Open the file test\@icifirm.com.abook file where you will see the lines as given below.
————————————
Aam|Aam| |aam@yahoo.com|
Anee|Anee| |anee@yahoo.com|
————————————-
In the above two lines we can clearly see that third field is empty | |.
If you see such blank fields in the .abook file you will get the error as
Address book is corrupted. Required fields are missing.

What you need to do is just fill the empty field with some text as shown below and also see that the line must end with pipe |.
————————————
Aam|Aam| Mr|aam@yahoo.com|
Anee|Anee|Mrs |anee@yahoo.com|
————————————-
Once restart the cpanel service and check the address book from the squirrelMail now. Now you can ask client to edit the Address book and correct third field what we have given.

Mail Services ( POP, SMTP , IMAP and Webmail )

How to disable webmail interface for single account

October 6th, 2009

If you want to disable any of the webmail interface for an account you can follow the procedure given below.

Login to shell as Root

For example if you want to disable ‘Horde’ and ‘Neomail’ for the user ‘test’

Open the file:
vi /var/cpanel/users/test

Then add the following lines ::
skiphorde = 1
skipneomail = 1
skipsqmail=0

save the file and exit.

Note: ‘1′ is for disable and ‘0′ is for enable

The line “skipsqmail=0″ is not required if it is already enabled.

Then restart the cpanel

service cpanel restart or /etc/init.d/cpanel restart Thats it

This will disable ‘Horde’ and ‘Neomail’ for the user ‘test’ for all email accounts under that hosting account.

Mail Services ( POP, SMTP , IMAP and Webmail )

Invalid maidirsize file

October 6th, 2009

We can do the following to resolve any maidirsize issues in the server wide.

You can use this command to remove the maildirsize file server wide
find /home/*/mail/ -name maildirsize | xargs rm -vf

Then run this command to recreate them
/scripts/generate_maildirsize –force –allaccounts

The above commands removes all the mailidirsize files and resets the mail usage quota in the server for all the mail accounts.

Mail Services ( POP, SMTP , IMAP and Webmail )

What is spamassassin And How it works And How to Configure

October 6th, 2009

This is post is explain about spamassassin.
================================

What is spamassassin ?

———————-
The SpamAssassin system is software for analyzing email messages,
determining how likely they are to be spam, and reporting its conclusions.
It is a rule-based system that compares different parts of email messages
with a large set of rules. A message with a high enough score is reported to
be spam.
————————

How it works ? : -
—————

–> There are several ways that SpamAssassin makes up its mind about a
message:
–> The message headers can be checked for consistency and adherence to
Internet standards (e.g., is the date formatted properly?).
–> The headers and body can be checked for phrases or message elements
commonly found in spam (e.g., “MAKE MONEY FAST” or instructions on how to be
removed from future mailings)-in several languages.
–> The headers and body can be looked up in several online databases that
track message checksums of verified spam messages.
–> The sending system’s IP address can be looked up in several online lists
of sites that have been used by spammers or are otherwise suspicious.
–> Specific addresses, hosts, or domains can be blacklisted or whitelisted.
A whitelist can be automatically constructed based on the sender’s past
history of messages.
–> SpamAssassin can be trained to recognize the types of spam that you
receive by learning from a set of messages that you consider spam and a set
that you consider non-spam. (SpamAssassin and the spam-filtering community
often refer to non-spam messages as ham. )
–> The sending system’s IP address can be compared to the sender’s domain
name using the Sender Policy Framework (SPF) protocol (http://spf.pobox.com)
to determine if that system is permitted to send messages from users at that
domain. This feature requires SpamAssassin 3.0.
–> SpamAssassin can privilege senders who are willing to expend some extra
computational power in the form of Hashcash (http://www.hashcash.org).
Spammers cannot do these computations and still send out huge amounts of
mail rapidly. This feature requires SpamAssassin 3.0.

Most of SpamAssassin’s behavior is controlled through a systemwide
configuration file and a set of per-user configuration files. The per-user
configuration can also be stored in an SQL database.

——————————

How to Configure it ? : -
——————-

You can easily customize how SpamAssassin tags and identifies spam by
creating a spamassassin/user_prefs file. You can customize the number of
“spam points” required to identify a message as spam, create new rules, and
re-weight existing rules. Here is a sample user_prefs file. It raises the
threshold for identifying spam from 5 to 6, disables including spam warnings
in the subject and body, reweights a known rule, and adds several blacklist,
whitelist, and header rules.

————————-

Listing 1. A typical user_prefs configuration file

================================================================

#How many hits before a mail is considered spam?
required_hits 6

#Don’t mangle the messages so badly
rewrite_subject 0
use_terse_report 1

#whitelist and blacklist
whitelist_from *@www.eukhost.com
blacklist_from annoying-person@xyz.com

#reweight an existing rule
score BASE64_ENC_TEXT 3

#add some new rules
header KNOWN_LIST List-Id =~ /a-mailing-list-i-like/
score KNOWN_LIST -3

body EVITE /This invitation was sent to you by .* using Evite/
describe EVITE Looks like an eVite
score EVITE -3

================================================================

At heart, SpamAssassin is a set of modules written in the Perl programming
language, along with a Perl script that accepts a message on standard input
and checks it using the modules. For higher-performance applications,
SpamAssassin also includes a daemonized version of the spam-checker and a
client program in C that can accept a message on standard input and check it
with the daemon.
===========================

Mail Services ( POP, SMTP , IMAP and Webmail )

EXIM ACLs for dictionnary attacks

October 6th, 2009

++ ACL Rule Replacement for Exim 4-24.x + anti dictionnary attack rules ++

- Added anti dictionnary attack rules - Have you ever seen spammers attempting to send huge amounts of messages to jane@domain.com, peter@domain.com, ashley@domain.com etc., when in fact neither of these users exists? And if they do exist these users are being dictionnary style spam bombed? These rules will drop the connection and attempt to ban the spammer from connecting for a period of time even when they try to reconnect they will be immediately dropped. God they will be annoyed!!! <SMILE>. In your /var/log/exim_mainlog you will see an entry like Dictionnary attack (x failed probes). Dropping connection!:

Please go through following URL to add new ACLs with anti-dectionary attack rules
http://linux.cvf.net/cp_eximrules.html

Mail Services ( POP, SMTP , IMAP and Webmail )