Line 93: |
Line 93: |
| | | |
| see a longer explaination [[Email_delete_double-bounce_messages | here]] | | see a longer explaination [[Email_delete_double-bounce_messages | here]] |
| + | |
| + | ====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). |
| + | |
| + | The SMESERVER is secure by design. POP3 (or webmail HTTP) is viewed as inadequate security and removed as an option from a standard installation to encourage unknowing administrators to select the 'best practice' option -a secure connection with POP3S, IMAPS, or HTTPS. |
| + | |
| + | You can still set your SMESERVER to allow POP3 settings by: |
| + | config setprop pop3 access public |
| + | signal-event email-update |
| + | |
| + | ====Real-time Blackhole List (RBL)==== |
| + | 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: |
| + | config setprop qpsmtpd DNSBL enabled RHSBL enabled |
| + | signal-event email-update |
| + | |
| + | |
| + | ====Spam Filters==== |
| + | I seem to get more spam from a SERVER-ONLY box compared to a SERVER-GATEWAY box. |
| + | |
| + | 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. |
| + | |
| + | Unfortunately, many admins believe that port-forwarding SMTP provides additional security. It doesn't, it limits the SMESERVER's ability to apply some rules. |
| | | |
| <noinclude>[[Category:Howto]]</noinclude> | | <noinclude>[[Category:Howto]]</noinclude> |