Changes

From SME Server
Jump to navigationJump to search
30 bytes removed ,  23:48, 11 February 2013
Presentation formating for the FAQ
Line 1: Line 1: −
==Email==
+
Information on the email subsystem used in SME Server covering sending/recieving, spam filtering, virus checking, webmail, domains and users.
===Troubleshooting===
     −
Q. I am having trouble getting sme to send and receive email.
+
==Troubleshooting==
 +
I am having trouble getting sme to send and receive email.
   −
A. Sending and receiving email are separate functions. You need to investigate each individually.
+
Sending and receiving email are separate functions. You need to investigate each individually.
   −
====Sending====
+
===Sending===
 
If SME server does not send mail, you need to examine the /var/log/qmail/current logs to see what happens when it tries. Most commonly problems can be solved by sending via your ISP's mail server, possibly using encryption and/or authentication. Read the manual.
 
If SME server does not send mail, you need to examine the /var/log/qmail/current logs to see what happens when it tries. Most commonly problems can be solved by sending via your ISP's mail server, possibly using encryption and/or authentication. Read the manual.
   −
====Receiving====
+
===Receiving===
 
If SME server does not receive mail, then you need to ensure that SMTP connections reach your SME server (DNS settings, router configuration, ISP port blocks) and then you need to examine /var/log/qpsmtpd/current logs to determine what SME server does with the incoming connections. Most problems are DNS, router or ISP issues, and have nothing to do with SME server operation or configuration.
 
If SME server does not receive mail, then you need to ensure that SMTP connections reach your SME server (DNS settings, router configuration, ISP port blocks) and then you need to examine /var/log/qpsmtpd/current logs to determine what SME server does with the incoming connections. Most problems are DNS, router or ISP issues, and have nothing to do with SME server operation or configuration.
   −
=====qpsmtpd "Connection Timed Out" errors=====
+
====qpsmtpd "Connection Timed Out" errors====
 
See [[Bugzilla:6888]] and [[Bugzilla:2360]]
 
See [[Bugzilla:6888]] and [[Bugzilla:2360]]
   Line 36: Line 36:  
  signal-event post-upgrade; signal-event reboot
 
  signal-event post-upgrade; signal-event reboot
   −
====Webmail broken after upgrade====
+
===Webmail broken after upgrade===
 
After the usual post-upgrade and reboot, webmail is broken with messages like the following in the messages log:
 
After the usual post-upgrade and reboot, webmail is broken with messages like the following in the messages log:
   Line 44: Line 44:  
As workaround, logout of Horde, close the browser, reopen, log in to Horde, Webmail should now be fully functional. (Based on suggested fix in [[Bugzilla:5177]])
 
As workaround, logout of Horde, close the browser, reopen, log in to Horde, Webmail should now be fully functional. (Based on suggested fix in [[Bugzilla:5177]])
   −
===Spam===
+
==Spam==
====Spamassassin====
+
===Spamassassin===
 
+
====Message Retention Time====
=====Message Retention Time=====
   
Set spamassassin for automatically delete junkmail.
 
Set spamassassin for automatically delete junkmail.
 
You can change the "days" that spamassassin sets to automatically delete junkmail, to delete after two months  
 
You can change the "days" that spamassassin sets to automatically delete junkmail, to delete after two months  
Line 64: Line 63:  
This happens because by default, no mail (except for viruses) gets rejected without the admin doing something first.
 
This happens because by default, no mail (except for viruses) gets rejected without the admin doing something first.
   −
=====X-Spam-Level Header in Email Messages=====
+
====X-Spam-Level Header in Email Messages====
 
SME does not create an X-Spam-Level header in processed email messages by default.
 
SME does not create an X-Spam-Level header in processed email messages by default.
   Line 73: Line 72:  
(Based on [[Bugzilla:3505]])
 
(Based on [[Bugzilla:3505]])
   −
=====Custom Rule Scores=====
+
====Custom Rule Scores====
 
You can customize the score assigned by a specific Spamassassin rule (SARE_ADULT2 in this case) as follows:
 
You can customize the score assigned by a specific Spamassassin rule (SARE_ADULT2 in this case) as follows:
 
  mkdir -p /etc/e-smith/templates-custom/etc/mail/spamassassin/local.cf
 
  mkdir -p /etc/e-smith/templates-custom/etc/mail/spamassassin/local.cf
Line 95: Line 94:       −
=====Pyzor Timeout=====
+
====Pyzor Timeout====
    
See [[Bugzilla: 5973]]
 
See [[Bugzilla: 5973]]
Line 125: Line 124:  
  signal-event email-update
 
  signal-event email-update
   −
====Real-time Blackhole List (RBL)====
+
===Real-time Blackhole List (RBL)===
 
Enabling RBL's <br>
 
Enabling RBL's <br>
 
RBL's are disabled by default to allow maximum accommodation (your ISP may be on a RBL & you may not know it). You can enable RBL's by:
 
RBL's are disabled by default to allow maximum accommodation (your ISP may be on a RBL & you may not know it). You can enable RBL's by:
Line 147: Line 146:       −
====Server Only====
+
===Server Only===
 
Some of the spam filter rules cannot work unless the SMESERVER knows the external IP of the box. If you put a SMESERVER in server-only mode behind other firewalls, it will lose some of the anti-spam rules.  For example, the rule that blocks attempts where spammers try "HELO a.b.c.d" where a.b.c.d is your external IP address.
 
Some of the spam filter rules cannot work unless the SMESERVER knows the external IP of the box. If you put a SMESERVER in server-only mode behind other firewalls, it will lose some of the anti-spam rules.  For example, the rule that blocks attempts where spammers try "HELO a.b.c.d" where a.b.c.d is your external IP address.
   Line 153: Line 152:       −
====I want to enable GreyListing====
+
===I want to enable GreyListing===
 
GreyListing support is under the covers and can easily be enabled for those who know what they are doing. However, many experienced users found that they spent more time looking after the greylisting configuration than they received in benefit.
 
GreyListing support is under the covers and can easily be enabled for those who know what they are doing. However, many experienced users found that they spent more time looking after the greylisting configuration than they received in benefit.
   −
====Bayesian Autolearning====
+
===Bayesian Autolearning===
    
The default SME settings do not include bayesian filtering in spamassassin to allow spamassassin to learn from received email and improve over time. [[Bugzilla: 6822]]
 
The default SME settings do not include bayesian filtering in spamassassin to allow spamassassin to learn from received email and improve over time. [[Bugzilla: 6822]]
Line 188: Line 187:  
* 'autolearn' as HAM any email with a score below 0.10
 
* 'autolearn' as HAM any email with a score below 0.10
   −
====The Sonora Communications "Spam Filter Configuration for SME 7" howto====
+
===The Sonora Communications "Spam Filter Configuration for SME 7" howto===
    
http://www.sonoracomm.com/support/19-inet-support/49-spam-filter-configuration-for-sme-7
 
http://www.sonoracomm.com/support/19-inet-support/49-spam-filter-configuration-for-sme-7
   −
====GeoIP: spam blocking based on geographical information====
+
===GeoIP: spam blocking based on geographical information===
    
The GeoIP plugin for Spamassasin lets us know where our mail server is receiving mail from. If we're receiving too much spam from a particular location, this will help track it down. We can then use that info to reject connections from that place taking the load off our server.
 
The GeoIP plugin for Spamassasin lets us know where our mail server is receiving mail from. If we're receiving too much spam from a particular location, this will help track it down. We can then use that info to reject connections from that place taking the load off our server.
Line 200: Line 199:  
You can find information how to install and use it on the [[GeoIP]] page.
 
You can find information how to install and use it on the [[GeoIP]] page.
   −
===Anti Virus===
+
==Anti Virus==
 
SME Server uses Clam AntiVirus (http://www.clamav.net) as the default and built-in anti virus engine.
 
SME Server uses Clam AntiVirus (http://www.clamav.net) as the default and built-in anti virus engine.
   −
====Signatures====
+
===Signatures===
 
By default SME Server will automatically get virus signature database updates from ClamAV.
 
By default SME Server will automatically get virus signature database updates from ClamAV.
   Line 210: Line 209:  
In order to automate the download and installation of the additional databases, as well as control which databases you use, follow the instruction in the [[Virus:Additional_Signatures|Virus:Additional Signatures]] Howto
 
In order to automate the download and installation of the additional databases, as well as control which databases you use, follow the instruction in the [[Virus:Additional_Signatures|Virus:Additional Signatures]] Howto
   −
====Heuristic Scan====
+
===Heuristic Scan===
 
HeuristicScanPrecedence is a new option in clamav 0.94.
 
HeuristicScanPrecedence is a new option in clamav 0.94.
   Line 222: Line 221:  
Default is disabled.
 
Default is disabled.
   −
====Attachment Filtering====
+
===Attachment Filtering===
 
The functionality to block possible executable and virus files attached to emails has been incorporated into SME Server v7.x. See the [[SME_Server:Documentation:Administration_Manual:Chapter13#E-mail_Filtering|Email]] panel in server manager.
 
The functionality to block possible executable and virus files attached to emails has been incorporated into SME Server v7.x. See the [[SME_Server:Documentation:Administration_Manual:Chapter13#E-mail_Filtering|Email]] panel in server manager.
    
Additional file signature patterns can be added to the SME defaults. See the [[Virus:Email_Attachment_Blocking|Virus:Email Attachment Blocking]] Howto for further information
 
Additional file signature patterns can be added to the SME defaults. See the [[Virus:Email_Attachment_Blocking|Virus:Email Attachment Blocking]] Howto for further information
   −
===Email Clients===
+
==Email Clients==
===="concurrency limit reached" when using IMAP====
+
==="concurrency limit reached" when using IMAP===
 
Sometime shows as Thunderbird giving this error message,
 
Sometime shows as Thunderbird giving this error message,
 
''This Mail-server is not a imap4 mail-server''
 
''This Mail-server is not a imap4 mail-server''
Line 247: Line 246:  
More detail can be found  [http://forums.contribs.org/index.php?topic=33124.0 here].
 
More detail can be found  [http://forums.contribs.org/index.php?topic=33124.0 here].
   −
====Mail server is not an IMAP4 mail server====
+
===Mail server is not an IMAP4 mail server===
 
This is a bug in Thunderbird, the previous tips may help
 
This is a bug in Thunderbird, the previous tips may help
   −
====The Bat====
+
===The Bat===
 
The gives this error message, but they are wrong.<br>
 
The gives this error message, but they are wrong.<br>
 
"This server uses TLS v3.0 which is considered to be obsolete and insecure.  
 
"This server uses TLS v3.0 which is considered to be obsolete and insecure.  
Line 256: Line 255:       −
====Outlook/Outlook Express give error 10060/0x800CCC90====
+
===Outlook/Outlook Express give error 10060/0x800CCC90===
 
Most likely OUTLOOK (EXPRESS) isn't configured correctly.
 
Most likely OUTLOOK (EXPRESS) isn't configured correctly.
 
   
 
   
Line 276: Line 275:  
  -you're finished, your email should work now
 
  -you're finished, your email should work now
   −
====Outlook test message doesn't come through====
+
===Outlook test message doesn't come through===
 
You clicked the TEST ACCOUNT SETTINGS in OUTLOOK didn't you? This is a bug in OUTLOOK. The test message sends a test email with 'no Date header'. As the name suggests, this means a message without any date. Since the server doesn't accept mail with 'no Date header' (because it's required) the message is rejected. To test, send an actual message from OUTLOOK.
 
You clicked the TEST ACCOUNT SETTINGS in OUTLOOK didn't you? This is a bug in OUTLOOK. The test message sends a test email with 'no Date header'. As the name suggests, this means a message without any date. Since the server doesn't accept mail with 'no Date header' (because it's required) the message is rejected. To test, send an actual message from OUTLOOK.
    
If you want, you can try THUNDERBIRD. It's like OUTLOOK but made by a different company. It's completely free and works very well at home and at the office.
 
If you want, you can try THUNDERBIRD. It's like OUTLOOK but made by a different company. It's completely free and works very well at home and at the office.
   −
====I can't receive/send email from my application (ACT!, vTiger, MS Outlook, etc)====
+
===I can't receive/send email from my application (ACT!, vTiger, MS Outlook, etc)===
 
Most likely, this is a bug the application you're using and not a problem with the SMESERVER. The application sends an email with 'no Date header'. As the name suggests, this means a message without any date. Since the server doesn't accept mail with 'no Date header' (because it's required) the message is rejected.  
 
Most likely, this is a bug the application you're using and not a problem with the SMESERVER. The application sends an email with 'no Date header'. As the name suggests, this means a message without any date. Since the server doesn't accept mail with 'no Date header' (because it's required) the message is rejected.  
   Line 299: Line 298:  
  signal-event email-update
 
  signal-event email-update
   −
====After I upgrade my SME Server, my email folders have disappeared when using IMAP====
+
===After I upgrade my SME Server, my email folders have disappeared when using IMAP===
 
After upgrade, if there are missing IMAP folders, the client may need to re-subscribe to folders.  This may affect either webmail users or users who use an IMAP email client.
 
After upgrade, if there are missing IMAP folders, the client may need to re-subscribe to folders.  This may affect either webmail users or users who use an IMAP email client.
   −
====Entourage: Using SME's Self-Signed Certificate for SSL Connections from Entourage on OS X 10.4====
+
===Entourage: Using SME's Self-Signed Certificate for SSL Connections from Entourage on OS X 10.4===
 
The main problem here is that Entourage will only support trusted, PEM Base-64 Encoded certificates.  To use IMAPS or SMTPS from Entourage with your SME server, you will need to:
 
The main problem here is that Entourage will only support trusted, PEM Base-64 Encoded certificates.  To use IMAPS or SMTPS from Entourage with your SME server, you will need to:
 
  1. Login to your Mac as a user with administrative privileges
 
  1. Login to your Mac as a user with administrative privileges
Line 336: Line 335:  
* Click on "Show Keychains" in Apple's "Keychain Access" if you need to delete a certificate and try again.
 
* Click on "Show Keychains" in Apple's "Keychain Access" if you need to delete a certificate and try again.
   −
====How do I get my e-mail to show the correct From Address====
+
===How do I get my e-mail to show the correct From Address===
    
The From address on an e-mail is not supplied by the server. It is supplied by the e-mail client.
 
The From address on an e-mail is not supplied by the server. It is supplied by the e-mail client.
Line 346: Line 345:  
Some system generated email is created by the server, some contribs may send mail externally, in these cases you need a valid domain name for the server, buy one or use a free provider like dyndns.org
 
Some system generated email is created by the server, some contribs may send mail externally, in these cases you need a valid domain name for the server, buy one or use a free provider like dyndns.org
   −
===Server Settings===
+
==Server Settings==
====How long retry before return e-mail as undeliverable====
+
===How long retry before return e-mail as undeliverable===
 
To configure how long SME server will try to delivery a message before return a permanent error
 
To configure how long SME server will try to delivery a message before return a permanent error
   Line 361: Line 360:       −
====Double bounce messages====
+
===Double bounce messages===
 
To stop admin receiving double bounce messages
 
To stop admin receiving double bounce messages
   Line 375: Line 374:  
see a longer explaination [[Email_delete_double-bounce_messages | here]]
 
see a longer explaination [[Email_delete_double-bounce_messages | here]]
   −
====Keep a copy of all emails====
+
===Keep a copy of all emails===
 
You may need to keep a copy of all emails sent to or from your email server.
 
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.
 
This may be for legal, or other reasons.
Line 394: Line 393:  
If you want to view the emails, point your email client at the SME and log on as maillog.
 
If you want to view the emails, point your email client at the SME and log on as maillog.
   −
=====Keep a copy of outgoing emails only=====
+
====Keep a copy of outgoing emails only====
 
In addition to the commands in the [[#Keep_a_copy_of_all_emails | previous section]] we will also have to create a custom template as follows:
 
In addition to the commands in the [[#Keep_a_copy_of_all_emails | previous section]] we will also have to create a custom template as follows:
   Line 416: Line 415:  
  perldoc /usr/share/qpsmtpd/plugins/bcc
 
  perldoc /usr/share/qpsmtpd/plugins/bcc
   −
====Set max email size====
+
===Set max email size===
 
There are several components involved in sending email on a SME server.  Each component has a size limit that may affect an email message that passes through the server.
 
There are several components involved in sending email on a SME server.  Each component has a size limit that may affect an email message that passes through the server.
   Line 466: Line 465:  
* MaxRecursion (default 8)
 
* MaxRecursion (default 8)
   −
====Change Horde Webmail Login Page 'Welcome To' Title====
+
===Change Horde Webmail Login Page 'Welcome To' Title===
 
The login page for Webmail defaults to "Welcome to Horde Webmail". In order to change this to something like "Welcome to MyDomain Mail"
 
The login page for Webmail defaults to "Welcome to Horde Webmail". In order to change this to something like "Welcome to MyDomain Mail"
 
  config setprop horde Name "MyDomain Mail"
 
  config setprop horde Name "MyDomain Mail"
Line 477: Line 476:  
Forum post [http://forums.contribs.org/index.php/topic,31093.0.html 31093]
 
Forum post [http://forums.contribs.org/index.php/topic,31093.0.html 31093]
   −
====Add the admin user as an administrator for Horde====
+
===Add the admin user as an administrator for Horde===
    
  config setprop horde Administration enabled  
 
  config setprop horde Administration enabled  
 
  signal-event email-update
 
  signal-event email-update
   −
==== Large attachments not displaying in webmail ====
+
=== Large attachments not displaying in webmail ===
 
Due to limits set in the PHP configuration it might be that webmail will not display large attachments (see also [[bugzilla:3990]]). The following entries are related to the error and can be found in the log files:
 
Due to limits set in the PHP configuration it might be that webmail will not display large attachments (see also [[bugzilla:3990]]). The following entries are related to the error and can be found in the log files:
   Line 497: Line 496:  
  sv t httpd-e-smith
 
  sv t httpd-e-smith
   −
====Disable mail to a user from an external network====
+
===Disable mail to a user from an external network===
 
Can be either a user, pseudonym or group
 
Can be either a user, pseudonym or group
 
  db accounts setprop groupname/username Visible internal
 
  db accounts setprop groupname/username Visible internal
 
  signal-event email-update
 
  signal-event email-update
   −
====I can't receive mail at: user@mail.domain.tld====
+
===I can't receive mail at: user@mail.domain.tld===
 
Add mail.domain.tld as a virtualdomain.
 
Add mail.domain.tld as a virtualdomain.
 
  -login to SERVER-MANAGER
 
  -login to SERVER-MANAGER
Line 509: Line 508:  
  -type: mail.domain.tld
 
  -type: mail.domain.tld
   −
====How do I find out who is logged into webmail and what IP number.====
+
===How do I find out who is logged into webmail and what IP number.===
 
This is logged is in /var/log/messages.
 
This is logged is in /var/log/messages.
   −
====How do I enable smtp authentication for users on the internal network====
+
===How do I enable smtp authentication for users on the internal network===
 
  mkdir -p /etc/e-smith/templates-custom/var/service/qpsmtpd/config/peers/local
 
  mkdir -p /etc/e-smith/templates-custom/var/service/qpsmtpd/config/peers/local
 
  cd /etc/e-smith/templates-custom/var/service/qpsmtpd/config/peers/local
 
  cd /etc/e-smith/templates-custom/var/service/qpsmtpd/config/peers/local
Line 524: Line 523:  
  signal-event email-update
 
  signal-event email-update
   −
====How do I disable SMTP relay for unauthenticated LAN clients====
+
===How do I disable SMTP relay for unauthenticated LAN clients===
 
http://forums.contribs.org/index.php?topic=38797.msg176490#msg176490
 
http://forums.contribs.org/index.php?topic=38797.msg176490#msg176490
 
* Enable smtp authentication as shown above
 
* Enable smtp authentication as shown above
Line 537: Line 536:  
- enable Authentication against the outgoing mail server
 
- enable Authentication against the outgoing mail server
   −
====Allow SMTP relay of mail without encryption/authentication====
+
===Allow SMTP relay of mail without encryption/authentication===
    
Change the configuration of the system from the default, so that it no longer requires encryption/authentication before allowing relaying of mail.
 
Change the configuration of the system from the default, so that it no longer requires encryption/authentication before allowing relaying of mail.
Line 546: Line 545:  
  signal-event email-update
 
  signal-event email-update
   −
====SMTP Authentication TLS before Auth disable & enable====
+
===SMTP Authentication TLS before Auth disable & enable===
 
Since SME v7.5 the default for SMTP Authentication is requires TLS before Auth to increase security.
 
Since SME v7.5 the default for SMTP Authentication is requires TLS before Auth to increase security.
 
Where a SME7.4 or earlier server with SMTP & SSMTP authentication enabled has been upgraded, users are now unable to send mail.
 
Where a SME7.4 or earlier server with SMTP & SSMTP authentication enabled has been upgraded, users are now unable to send mail.
Line 565: Line 564:       −
====Internet provider's outgoing port 25 is blocked: How to set an alternative outgoing port for the SMTP server====
+
===Internet provider's outgoing port 25 is blocked: How to set an alternative outgoing port for the SMTP server===
 
If your Internet provider is blocking outgoing smtp port 25 on your internet connection but your provider is offering an alternative outgoing port (or when using some relay service) you can simply set this alternative port by adding it to the 'Address of Internet provider's mail server' value in the 'E-mail delivery settings' screen of the server-manager like this:
 
If your Internet provider is blocking outgoing smtp port 25 on your internet connection but your provider is offering an alternative outgoing port (or when using some relay service) you can simply set this alternative port by adding it to the 'Address of Internet provider's mail server' value in the 'E-mail delivery settings' screen of the server-manager like this:
 
  <internet providers mail server name or ip-address>:<alternative port>
 
  <internet providers mail server name or ip-address>:<alternative port>
Line 572: Line 571:  
This setting does not alter the incoming smtp mail server port on SME server, which will still use port 25. Refer to a workaround in http://wiki.contribs.org/PortRedirect
 
This setting does not alter the incoming smtp mail server port on SME server, which will still use port 25. Refer to a workaround in http://wiki.contribs.org/PortRedirect
   −
====How do I enable and configure a disclaimer in email messages====
+
===How do I enable and configure a disclaimer in email messages===
 
  −
 
   
A disclaimer message can be added to the footer of all outgoing email messages.
 
A disclaimer message can be added to the footer of all outgoing email messages.
   Line 630: Line 627:       −
====Email WBL server manager panel====
+
===Email WBL server manager panel===
    
There is a server-manager contrib to allow GUI control of email white and black lists, detailed in the wiki article: [[:Email_Whitelist-Blacklist_Control]].
 
There is a server-manager contrib to allow GUI control of email white and black lists, detailed in the wiki article: [[:Email_Whitelist-Blacklist_Control]].
Line 664: Line 661:       −
====How to block email from one address to another address with check_badmailfromto plugin====
+
===How to block email from one address to another address with check_badmailfromto plugin===
    
Enable the check_badmailfromto plugin. Adapted from [http://forums.contribs.org/index.php/topic,35667.0.html this Forum post]
 
Enable the check_badmailfromto plugin. Adapted from [http://forums.contribs.org/index.php/topic,35667.0.html this Forum post]
Line 719: Line 716:  
  signal-event email-update
 
  signal-event email-update
   −
====Redirect mail.domain.net to Webmail====
+
===Redirect mail.domain.net to Webmail===
 
Setup external dns records
 
Setup external dns records
   Line 728: Line 725:  
where http://sme.dom.ain/webmail is servername.domainname/webmail
 
where http://sme.dom.ain/webmail is servername.domainname/webmail
   −
====E-mail Retrieval====
+
===E-mail Retrieval===
 
http://wiki.contribs.org/SME_Server:Documentation:Administration_Manual:Chapter13#E-mail_Retrieval
 
http://wiki.contribs.org/SME_Server:Documentation:Administration_Manual:Chapter13#E-mail_Retrieval
   Line 745: Line 742:  
As described at [[bugzilla:5602]] [[bugzilla:6483]]
 
As described at [[bugzilla:5602]] [[bugzilla:6483]]
   −
===External Access===
+
==External Access==
====Allow external IMAP mail access====
+
===Allow external IMAP mail access===
 
There was a deliberate decision to remove non-SSL protected username/password
 
There was a deliberate decision to remove non-SSL protected username/password
 
services from the external interface.
 
services from the external interface.
Line 758: Line 755:  
fixme: explain how
 
fixme: explain how
   −
====POP3 & webmail HTTP====
+
===POP3 & webmail HTTP===
 
I want to set my SMESERVER to allow POP3 (or webmail HTTP) but it's not an option, I only see POP3S (or webmail HTTPS).
 
I want to set my SMESERVER to allow POP3 (or webmail HTTP) but it's not an option, I only see POP3S (or webmail HTTPS).
   Line 767: Line 764:  
  signal-event email-update
 
  signal-event email-update
   −
====Allow external pop3 access====
+
===Allow external pop3 access===
    
Email settings > POP3 server access in SME 7.1 server-manager allows only pop3s protocol for clients outside the LAN.  Some email clients (eg The Bat! v3.98.4) won't allow pop3s connections to SME 7.1 because of ssl version conflict.  Until this is sorted out, a workaround is to hack SME to allow regular pop3 on the external interface using the following commands.  
 
Email settings > POP3 server access in SME 7.1 server-manager allows only pop3s protocol for clients outside the LAN.  Some email clients (eg The Bat! v3.98.4) won't allow pop3s connections to SME 7.1 because of ssl version conflict.  Until this is sorted out, a workaround is to hack SME to allow regular pop3 on the external interface using the following commands.  
Line 777: Line 774:  
more information [[bugzilla:2620]]
 
more information [[bugzilla:2620]]
   −
===Imap===
+
==Imap==
====Folders with a dot in name====
+
===Folders with a dot in name===
 
Email folder names that have a period ('.') in the folder name, will be split into sub-folders.
 
Email folder names that have a period ('.') in the folder name, will be split into sub-folders.
 
e.g. folder name 'www.contribs.org' is created as
 
e.g. folder name 'www.contribs.org' is created as
Line 785: Line 782:  
         org
 
         org
   −
===qpsmtpd===
+
==qpsmtpd==
 
SME uses the [http://smtpd.develooper.com qpsmtpd] smtp daemon.
 
SME uses the [http://smtpd.develooper.com qpsmtpd] smtp daemon.
   −
====Official Description====
+
===Official Description===
 
qpsmtpd is a flexible smtpd daemon written in Perl. Apart from the core SMTP features, all functionality is implemented in small "extension plugins" using the easy to use object oriented plugin API.
 
qpsmtpd is a flexible smtpd daemon written in Perl. Apart from the core SMTP features, all functionality is implemented in small "extension plugins" using the easy to use object oriented plugin API.
   Line 795: Line 792:  
qpsmtpd wiki: http://wiki.qpsmtpd.org
 
qpsmtpd wiki: http://wiki.qpsmtpd.org
   −
====Log watching tool====
+
===Log watching tool===
 
qplogtail is a script to to monitor /var/log/qpsmtpd/current, see [[bugzilla:3418]]
 
qplogtail is a script to to monitor /var/log/qpsmtpd/current, see [[bugzilla:3418]]
   −
====Default Plugin Configuration====
+
===Default Plugin Configuration===
 
SME uses the following [http://wiki.qpsmtpd.org/plugins qpsmtpd plugins] to evaluate each incoming email.  
 
SME uses the following [http://wiki.qpsmtpd.org/plugins qpsmtpd plugins] to evaluate each incoming email.  
   Line 915: Line 912:  
|}
 
|}
   −
====Other QPSMTPD Plugins====
+
===Other QPSMTPD Plugins===
 
The following qpsmtpd plugins will work on a SME server, but are either not included or are not configured by default.
 
The following qpsmtpd plugins will work on a SME server, but are either not included or are not configured by default.
 
{| width="100%" border="1" cellpadding="5" cellspacing="0"
 
{| width="100%" border="1" cellpadding="5" cellspacing="0"
Line 932: Line 929:       −
===Internal Mail Servers===
+
==Internal Mail Servers==
 
SME can be configured as a spam and antivirus filter for one or more "Internal" mail servers on a domain-by-domain basis.  The mail server specified does not have to be on the same local network as your SME server.
 
SME can be configured as a spam and antivirus filter for one or more "Internal" mail servers on a domain-by-domain basis.  The mail server specified does not have to be on the same local network as your SME server.
   −
====Deliver ALL email to a single internal mail server====
+
===Deliver ALL email to a single internal mail server===
 
You can set the default delivery location for all domains on your SME server to a single ''internal'' mail server by setting the mail server address in server-manager::Configuration::E-mail::Change e-mail delivery settings::Address of internal mail server.
 
You can set the default delivery location for all domains on your SME server to a single ''internal'' mail server by setting the mail server address in server-manager::Configuration::E-mail::Change e-mail delivery settings::Address of internal mail server.
    
Note: ''Address of internal mail server'' must be blank if you want any email delivered to the SME server itself.
 
Note: ''Address of internal mail server'' must be blank if you want any email delivered to the SME server itself.
   −
====Deliver email for one domain to an internal mail server====
+
===Deliver email for one domain to an internal mail server===
 
You can override the default email delivery destination for individual domains on your SME server (forwarding all email for the specified domain to another server) as follows:
 
You can override the default email delivery destination for individual domains on your SME server (forwarding all email for the specified domain to another server) as follows:
   Line 959: Line 956:  
  signal-event email-update
 
  signal-event email-update
   −
=== Secondary/Backup Mail Server Considerations ===
+
== Secondary/Backup Mail Server Considerations ==
    
Many people misunderstand the issues of using a secondary or backup  
 
Many people misunderstand the issues of using a secondary or backup  
Line 968: Line 965:  
discussed below.
 
discussed below.
   −
====What is ''Backup MX''====
+
===What is ''Backup MX''===
    
A backup MX is a system whereby through your DNS records you tell other
 
A backup MX is a system whereby through your DNS records you tell other
Line 976: Line 973:  
servers. See also http://en.wikipedia.org/wiki/MX_record
 
servers. See also http://en.wikipedia.org/wiki/MX_record
   −
====The process of delivering email to your SME Server====
+
===The process of delivering email to your SME Server===
    
So lets look at how mail gets delivered without and with a  
 
So lets look at how mail gets delivered without and with a  
 
''backup mx'' when your Internet link, ISP or server is down.
 
''backup mx'' when your Internet link, ISP or server is down.
   −
====='''Without''' a backup MX=====
+
===='''Without''' a backup MX====
    
* The sending mail server cannot connect to your server.
 
* The sending mail server cannot connect to your server.
Line 993: Line 990:  
again reachable'''.
 
again reachable'''.
   −
====='''With''' a backup MX=====
+
===='''With''' a backup MX====
    
* The sending mail server cannot contact your server.
 
* The sending mail server cannot contact your server.
Line 1,014: Line 1,011:  
destined for your server on the floor.
 
destined for your server on the floor.
   −
====Backup MX and SPAM Filtering====
+
===Backup MX and SPAM Filtering===
    
On top of the issue, indicated above, there is another issue to consider
 
On top of the issue, indicated above, there is another issue to consider
Line 1,054: Line 1,051:  
* If your secondary MX bounces your mail, you usually have no way to determine what happened other than via reports from the original senders that your mail bounced.
 
* If your secondary MX bounces your mail, you usually have no way to determine what happened other than via reports from the original senders that your mail bounced.
   −
==== Summary ====
+
===Summary===
    
In summary, if your server/Internet connection is available most (let's say >90%) of  
 
In summary, if your server/Internet connection is available most (let's say >90%) of  
Line 1,067: Line 1,064:  
* each gateway can make decisions on whether to accept/reject mail for the users at the domain
 
* each gateway can make decisions on whether to accept/reject mail for the users at the domain
   −
===User accounts===
+
==User accounts==
====Multiple users with the same name on different domains====
+
===Multiple users with the same name on different domains===
 
{{Tip box|msg=The Manual contains a detailed explanation here [[SME Server:Documentation:Administration Manual:Chapter9#Pseudonyms]], however, this question is frequently asked in the forums and this FAQ was added in response to this thread [http://forums.contribs.org/index.php?topic=41558.0;all]}}
 
{{Tip box|msg=The Manual contains a detailed explanation here [[SME Server:Documentation:Administration Manual:Chapter9#Pseudonyms]], however, this question is frequently asked in the forums and this FAQ was added in response to this thread [http://forums.contribs.org/index.php?topic=41558.0;all]}}
  
105

edits

Navigation menu