Surgemail mail server
Author: h | 2025-04-24
Download SurgeMail Mail Server latest version for Windows free to try. SurgeMail Mail Server latest update: Aug MailScan for DMail/SurgeMAIL - The world's first Real-Time e-mail scanner for DMail/SurgeMAIL Mail Server. MailScan 6.8a for DMail/SurgeMAIL is the world's first Real-Time e-mail scanner for DMail/SurgeMAIL Mail Server. This server is published by NetWin Ltd.MailScan 4 for DMail/SurgeMAIL acts like a Content-Security and AntiVirus Software between your Corporate DMai
SurgeMail Mail Server - reviewpoint.org
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 [email protected], 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
Surgemail Mail Server - LinuxQuestions.org
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:[email protected]"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 [email protected] 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:Migrate SurgeMail Mailbox Convert SurgeMail Mail Server
+++ Proccessing Token=(v=spf1) Parameter=(spf1) cidr=32 +++ spf: Processed token (v=spf1) - continuing ......... spf: +++ Proccessing Token=(ip4:216.65.3.0/16) Parameter=(216.65.3.0) cidr=16 +++ spf: spf: cidr(216.65.3.228, 216.65.3.0, /16) Matched Mask spf: Last token {ip4:216.65.3.0/16} (res=PASS) spf: Start ip=1.2.3.4 [email protected] 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: +++ Proccessing Token=(v=spf1) Parameter=(spf1) cidr=32 +++ spf: Processed token (v=spf1) - continuing ............ spf: spf: cidr(1.2.3.4, 216.65.3.228, /32) No match spf: Processed token (mx) - continuing ......... spf: +++ Proccessing Token=(-all) Parameter=() cidr=32 +++ spf: Last token {-all} (res=FAIL) An alternative way to check your SPF record is using nslookup or dig as per: [root@linux]# nslookup > set type=txt > netwinsite.com Server: 10.0.0.25 Address: 10.0.0.25#53 Non-authoritative answer: netwinsite.com text = "v=spf1 ip4:216.65.3.0/16 ip4:210.54.44.0/16 a mx -all" Other SPF resources: The SPF Home Page The SPF wizard for generating rules - Ukraine translation of this web page (by Android SDK) 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, MySQLl, 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). Download SurgeMail Mail Server latest version for Windows free to try. SurgeMail Mail Server latest update: AugMail Server Install Instructions - SurgeMail
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:SurgeMail Mail Server Download - BytesIn
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 protected], 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)SurgeMail Mail Server 7.8k - Download3K
Valid SPF record if the SPF return code is 'FAIL' By default the 'allow' mechanism will be used so nothing is actually blocked unless you set the domain or user default to 'block'. The domain setting to make it actually block by default is spam_block "true". Note: "block" mode will not block email from domains with no SPF record, use "strict" mode instead. stamp Do the SPF processing and add a header to the message, which is then used by the filter to score the message more accurately as spam strict This setting is unique to SurgeMail, it means if there is not a good 'SPF' record then SurgeMail applies a default rule "mx/16 a ptr:%{d2} -all" settable with g_spf_default which basically means is the person sending this message from a mail server that accepts messages for this domain (or close to it) or if I lookup the name of this ip number, does it match the domain name. Then SurgeMail checks if it's an ip address it knows about historically, and if still can't find it, then it blocks the message. This will block some real email, but it will block a 'lot' of spam. By default the 'allow' mechanism will be used so nothing is actually blocked unless you set the domain or user default to 'block'. The domain setting to make it actually block by default is spam_block "true" Set strict for ASPAM scoring only If you just set strict mode, but don't set spam_block "true" or g_spam_block "true" then the messages will be stamped only, the aspam rules will notice this and score them accordingly, so it is useful to set strict mode without setting anything to actually block messages. When SurgeMail does bounce a message (which will be rare anyway due to the other checks). Download SurgeMail Mail Server latest version for Windows free to try. SurgeMail Mail Server latest update: AugComments
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 [email protected], 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
2025-04-10To 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:[email protected]"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 [email protected] 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:
2025-04-0222, 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:
2025-04-01Deliver 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 protected], 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)
2025-03-28With 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 [email protected] 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
2025-04-24