Surgemail mail server

They are different systems. This is achieved by the following magic incantations. Add MX records to point your.domain to mail.your.domain Add aliases for the domain in surgemail.ini so it will accept mail for mail.your.domain as well as your.domain, host_alias "mail.your.domain" (in each domain) Add g_server_name url="*.domain.com" name="domain.com" so that web connections will figure out the right domain In webmail.ini the imap server etc should be defined as 'mail.your.domain' not 'your.domain' So in your DNS you have: mail.your.domain --> x.x.x.x (your mail server) your.domain --> y.y.y.y (your web server) your.domain MX --> mail.your.domain When you add a domain in SurgeMail it will ask you about your 'DNS' and 'MX' names, if you specify them as different, it will correctly setup your webmail.ini and surgemail.ini to cope, but you still need to setup the correcdt DNS/MX records in your DNS server. Domain identification using WebMail with SurgeMail Webmail combined with surgemail can host multiple domains on one server. There are several options for having webmail identify the correct domain. Web browser URL based(most commonly used) Domain dopdown list Fully specified login Using IP address 1. Using the web browser URL The normal way of handling multiple domains is to login to webmail using your web browser on a URL of Webmail will then display a login page that has the domain correctly identified. For this to work this domain needs to be configured in several places in surgemail and webmail. The vdomain in question must be defined in surgemail: surgemail.ini: vdomain address="" name="mydomain.com" mailbox_path "C:\surgemail\mbox\mydomain.com" {... other settings} and in webmail: surgemail/web_work/surgehost.ini: vhost mydomain.com domain mydomain.com suffix @mydomain.com imaphost 127.0.0.1 smtphost 127.0.0.1 vend The definition of the domain in both places is generally done automatically by surgemail when you create this domain using the surgemail web admin interface or tellmail commands, but can be manually added if required. When the browser connects to surgemail on the url it passes "Host: mydomain.com". SurgeMail matches this host value against g_server_name settings, domain names, url_host values and also compares the ip address of the domain to the ip being connected to. When it finds a match it passes a SERVER_NAME enviroment variable to WebMail with the appropriate value. WebMail matches this value against the vhost sections, identifying the domain. If your url does not match your vdomain name eg you want your users to connect to to send email of user@mydomain.com, surgemail will need to do this name translation. If the domain has a unique ip, and the url domain resolves to that ip then it should automatically work (surgemail 3.7a-21 onward). If you have only 1 such url domain name then you can set the domain url_host setting to this value (this has the side effect that SurgeMail will also use this value in any url it generates internally). If you have several values you can use a g_server_name rule, this rule may contain a wildcard. eg. surgemail.ini: g_server_name url="*.mydomain.com" name="mydomain.com" 2. Domain dropdown list An alternative to having webmail identify the domain using

To enforce spf for your domain:So add the dns entry: _dmarc.example.comA 'txt' record containing: "v=DMARC1; p=reject; aspf=r; adkim=r"or if you want reports: "v=DMARC1; p=reject; aspf=r; adkim=r; rua=mailto:dmarc-feedback@example.com"That's probably all you need. You can send from any address 1.2.3.0-1.2.3.255 which will probably be fine for most purposes. It's simple, and efficient. If you want though you could add a little more. But remember the more you add, the slower it is to process, and the more likely you will make a mistake. Here is a good basic rule that adds in the mx records which will help if you change things in future... v=spf1 ip4:1.2.3.4/24 a mx -all Token Explanation v=spf1 Version of SPF syntax ip4:1.2.3.4/24 Allow any ip address 1.2.3.0-1.2.3.255 (change to match your own mail server ip address) a Allow any ip which matches the IP address of this domain (doing a simple 'a' lookup) mx Allow any ip which matches the IP address of a mail server that accepts incoming mail for this domain. -all Block any mail from an ip other than those listed above How do I check my spf record for my domain The best way is to use the SPF test page in surgemail (Spam Control - SPF Settings - Test SPF Records). This will allow you to test any sending ip address + from address + spf record combination. This allows you to: Check your new spf record before configuring your DNS server Test any domain to see whether an spf record has been setup, and setup correctly eg sending mail from valid (216.65.3.228) and invalid (1.2.3.4) ip address for surgemail-support account on domain netwinsite.com : spf: Start ip=216.65.3.228 from=surgemail-support@netwinsite.com spf: lookup (txt) (netwinsite.com) --> (v=spf1 ip4:216.65.3.0/16 ip4:210.54.44.0/16 a mx -all) spf: SPF txt record found (v=spf1 ip4:216.65.3.0/16 ip4:210.54.44.0/16 a mx -all) spf:

22, 2009 | Viewed: 2268 Out Spam 1.1 Out Spam is a spam filter program. It can remove junk letters from a POP3 mail server without downloading them to a client computer. The principal way to separate mail is the use of worldwide black lists of spam mail servers. The program can also filter letters by languages and letter header... DOWNLOAD GET FULL VER Cost: $19.00 USD License: Shareware Size: 553.4 KB Download Counter: 16 Released: March 05, 2005 | Added: March 08, 2005 | Viewed: 1875 Native POP3 Connector 2.5.0 It is widely known that Microsoft Exchange Server 2000/2003 doesn't support receiving mail through the POP3 protocol. However, in practice, it has been shown that many users find the absence of this feature inconvenient. All the existing solutions entice users to use a utility agent receiving... DOWNLOAD GET FULL VER Cost: $79.00 USD License: Shareware Size: 1.8 MB Download Counter: 7 Released: April 14, 2011 | Added: April 21, 2011 | Viewed: 1961 febooti Command line email 2.0 Utility to send email from command prompt; send attached files, plain text or HTML (with embedded pictures). Supported - TO, CC (Carbon Copy), BCC (Blind Carbon Copy), SSL and STARTTLS encryption, alternate text for email programs that do not support HTML messages, message text encoding. FREE... DOWNLOAD GET FULL VER Cost: $24.95 USD License: Shareware Size: 1024.0 KB Download Counter: 12 Released: August 07, 2006 | Added: August 10, 2006 | Viewed: 1298 SurgeMail Mail Server 38f3 A Complete, advanced Mail Server, SurgeMail is secure, easy to install and manage with high performance. This aggressively priced email server is fast, reliable and feature rich, with integrated WebMail software. Users can create and manage blogs and the enhanced SPF mode stops most spam early.... DOWNLOAD GET FULL VER Cost: $175.00 USD License:

Deliver Warning: Below is a description of some of the errors you might get when delivering a message. If you were sent here it means the mail server you use is probably using our software. If you have problems please email your admins and not us as we won't be able to help you as we do not administer any servers we just provide the software. If you are an Admin and run SurgeMail then feel free to email us along with your registration number (ie: N#####). This page is to help explain how to read a "Delivery warning/failure" message. The first important point is to examine the 'Subject' of the message you received, if it starts "Delivery Warning..." Then you can safely ignore the message, this warning only means the 'first' attempt to send to the specified address failed, it's likely further attempts will work. However the warning is useful if the message is 'time critical' you can take steps (make a phone call, send a fax) immediately to make sure your 'message' gets through. The rest of the bounce message is in a standard and slightly obscure format, intended to be read by both humans and robots, the key line to examine is this one: For EMAIL@DOMAIN.NAME, REASON That will tell you the address SurgeMail was trying to deliver the message to, and the reason it failed. Click here for a list of specific bounce explanations Please note: this web site is run by NetWin Ltd, we provide the software your ISP is running, we do not run the service in question and cannot help you directly, contact your own system administrator if you have further questions. The rest of this page summarizes some features of SurgeMail. Integrated mail server and web based email Spam and virus free email Web based administration (user, domain and server) Unique Mirror system Full SSL secure support for all protocols Interface to existing user databases (OBDC, MySQL, LDAP, etc or use built in database) Scales to any number of users and domains Runs on platform of choice (Windows, most UNIX versions) Installs in minutes and unparalleled after sales service Cellphone SMS/Text messages via SMSGate (FREE)

With SurgeMail version 2.0h or later use g_spf_skip "x.x.x.x" where 'x.x.x.x' is the ip address of your other mail server(s) (a comma seperated or wild card list). Turn on g_spf_rewrite "True", which means anything that is accepted for delivery by the secondary mx is from then on immune to spf checks from 'any' server. On the primary server list the secondary server as a trusted host e.g. 'g_verify_mx_skip x.x.x.x' where 'x.x.x.x' is the ip address of the secondary server. Use g_spf_share "other.host1,other.host2" on each server so they can share allow information between themselves. NOTE: Copy the file srs.secret between all cluster/mx servers so it matches on all systems, this file contains a random number which is used to verify srs and allow emails. This file will only exist once you start using SPF, it resides in the g_home directory. tellmail spf_export file.name tellmail spf_import file.name Exports the list of 'known' ip addresses to a file suitable to copy to another system, use this when adding an incoming mx gateway if you want it to already know about all existing 'trusted' ip addresses. The file name is relative to the surgemail home directory, not your current working directory! Authent Module support Your authent module must support an extra string field 'spf_block' spf_block, valid values are 'true,false,blank' true = block false = don't block blank = system default. +OK user@here.com 0 spf_block="FALSE" Debugging See the file allow.log to see why messages are let through or blocked when using these settings. How to define an SPF record for my domain Start with something like this, replace 1.2.3.4 with the ip address of your mail server. Add this as a 'txt' record for you email domain, e.g. example.com v=spf1 ip4:1.2.3.4/24 -all In addition you should probably add a DMARC record to tell other servers

Virtual Domains - a guide Unlike web servers there are two basic types of virtual domains for a mail server: Real IP based virtual domains, where you have allocated an IP address to each virtual domain, the server can use this information to figure out which domain it should 'pretend' to be. Fake ones, where you only use a single IP address, then the user must login as 'user@domain.name' when fetching their Email via POP so that the server can figure out which domain they belong to. SurgeMail supports both of these methods or even combinations of them and any number of virtual domains. However, it supports some other systems too :-). For example, you can tell SurgeMail to respond to all domains matching a specific wild card eg: *.mydomain.com You can also use a virtual user table where each user is in a 'domain of their own' (this is useful if you want to sell users their own domain names). In addition, some mail clients do not allow a user to specify user@domain.name as their 'username'. In this case you can define a domain separator like '/' and then the user can login as 'user/domain.name' How to create a virtual domain Simply click on 'domains' 'add' in the web admin tool. Then fill out the details. In addition if you are using WebMail you may need to add these domains to webmail.ini as described. Note: SurgeMail will not create the directory structure until a message is received for the new domain, so don't panic if you can't see the domains directory right away. You can define default settings for new domain by creating/editing the domain_defaults.txt file in the SurgeMail "web" directory (if you create/change this file manually copy it to the mirror too). This file contains only basic settings in the form: one setting per line. It cannot handle the more complex settings eg. setting label="value" label2="value2" Adding IP numbers to your operating system It is fairly easy to add multiple IP numbers for a single machine, up to 255 per interface is fairly straightforward. 1024 is usually possible with minor patches. The exact method varies. On NT just specify extra numbers in the networking control panel. For UNIX, see for more information. As an example, on Linux you would do the following: su - root ifconfig eth0:2 999.59.4.31 up to add a second IP number 999.59.4.31. The number :2 can be anything between :1 and :255 Virtual Domain User (domuser.dat) If every user on your system is in their own domain, e.g. bob@jones.mail.com, john@smith.mail.com then you probably don't want to create a virtual domain entry in surgemail.ini for all 200,000 users. Instead you can use the file domuser.dat to list each user so that SurgeMail knows what virtual domains exist on your system. The format is: delivery_user_domain user_database_lookup_name e.g. xxx@bob.com xxx@bob.comyyy@yyy.com yyy@bob.com*@ccc.com ccc@bob.com So with the above file, if a user 'fred@ccc.com' logged in they would be looked up in the userdatabase as 'ccc@bob.com' and yyy@yyy.com would be