Email

From SME Server
Revision as of 02:18, 31 March 2007 by Snoble (talk | contribs)
Jump to navigationJump to search

Email

Change email settings


Thunderbird 'is not imap4 mail-server'

Mozilla thunderbird with sme7.x imap server sometimes gives this error message, This Mail-server is not a imap4 mail-server

To workaround thunderbirds limitations, increase the ConcurrencyLimitPerIP value

config setprop imap ConcurrencyLimitPerIP 20
config setprop imaps ConcurrencyLimitPerIP 20
signal-event post-upgrade; signal-event reboot

check

config show imap
tail -f /var/log/imap/current | tai64nlocal

Spamassassin

Set spamassassin for automatically delete junkmail. You can change the "days" that spamassassin sets to automatically delete junkmail, to delete after two months

db configuration setprop spamassassin MessageRetentionTime 60  
signal-event email-update 

Keep a copy of all emails

You may need to keep a copy of all emails sent to or from your email server. This may be for legal, or other reasons.

The following instructions will create a new user account (maillog) and forward every email that goes through your SME server to it.

First, log onto the server-manager and create the user maillog

Go to the SME Command Line (logon as root) and issue the following commands:

config setprop qpsmtpd Bcc enabled
signal-event email-update

Optionally make the forwarding of the emails invisible to the end user. Without it, there will be an X-Copied-To: header in each email. Run this command before the signal-event

config setprop qpsmtpd BccMode bcc

If you want to view the emails, point your email client at the SME and log on as maillog.


Allow external IMAP mail access

There was a deliberate decision to remove non-SSL protected username/password services from the external interface.

to allow unsecure IMAP access

config setprop imap access public
signal-event email-update

But before you do this try to use secure IMAP
fixme: explain how

Set max email size

Restrict the size of email messages that can pass through your mail server

config setprop qmail MaxMessageSize x
signal-event email-update

where x is in bytes, eg 6000000 = 6 MB

add the admin user as an administrator for Horde

config setprop horde Administration enabled 
signal-event email-update


"421 per host concurrency limit reached" when I try to send an email using IMAP

A fix is documented here.


delete double bounce

To stop getting double bounce messages

config setprop qmail DoubleBounceTo devnull
signal-event email-update

see a longer explaination here