امروز mail server تحت ویندوز که سبک و کارآمد هست رو با شما به اشتراک بذارم ، همانطور که میدونید این نرم افزار از EXCHANGE بسیار سبک تر است و همچنین کار کردن با این نرم افزار هم خیلی راحت تر است .اگر سازمان کوچیکی دارید بدون شک پیشنهاد ما به شما این mail server است .
Activation instructions Mdaemon 14 (in english see below)
1. Install or copy the installed Mdaemon to the desired location.
2. If there is any license for Mdaemon 14 (valid or trial), go to item 4
3. Get the trial and activate it. We stop Mdaemon.
4. We close 443 port on services.altn.com
5. Save the license (license \ license.xml) in a safe place.
6. Start and stop Mdaemon.
7. Let’s edit license.xml for you (see license-example.xml):
A header with fields <Key>, <DateTime> </ DateTime>, <Next> </ Next>, <RemoteIP>
do not touch.
If the license is transferred from another computer, the <PCID> field is taken from the license_request.xml file
The <UsageKey> field is the registration key, it consists of 5 parts. Parts 3-5 correspond to the serial number.
The <SerialNumber> field is a serial number, consists of 3 parts. (you can use the famous keygen) Be sure to prescribe the same in mdaemon.ini
The <Trial> field is a value of 1 (trial mode) value of 0 (a proprietary Mdaemon)
The <StartDate> field is the start date of use (you can leave it untouched. <StartDate> is not older than <DateTime>)
Field <EndDate> the end date of use (more than 10 years did not check)
The <Deactivate> field is the deactivation date (set the same as <EndDate>)
<Plugin> section
<Product> AS </ Product>
……
… ..
… ..
</ Plugin>
Repeats for each plug-in in the <Product> field the name of the plug-in to be used
AS – ActiveSync
OC – Outlook Connector
AV – Antivirus / SecurityPlus
The structure of the section is the same as described above (the names and values of the fields are absolutely identical, you can stupidly copy)
<UsageKey>, <SerialNumber> can be the same. Do not forget about mdaemon.ini
In sections with plug-ins we add
<LastValidVersion>
inside everything that stands in <CurrentVersion> </ CurrentVersion>
</ LastValidVersion>
example:
<CurrentVersion>
<Version> 14.0.0 </ Version>
<ReleaseDate> 2014-03-25 </ ReleaseDate>
</ CurrentVersion>
<LastValidVersion>
<Version> 14.0.0 </ Version>
<ReleaseDate> 2014-03-25 </ ReleaseDate>
</ LastValidVersion>
</ Plugin>
Fields with the word Error, for example <ProductErrorCode> <ProductErrors> – are deleted.
Save the license.xml and just in case copy it to a safe place.
8. We replace the original files with patches.
9. We close 443 port on services.altn.com
10. Launch the Mdaemon. We check the launch of plug-ins. If the plugins do not run once again checks license.xml We draw attention to the section <CurrentVersion>, the <Version> field must match the value from license_request.xml If all the changes have disappeared, then the port is not closed !!!
11. Correcting errors in license.xml and mdaemon.ini
12. Run and check the work.
Updating the working MDAEMON version 13.6 and below:
1) close services.altn.com
2) copy the license folder with the prepared files to the folder with the installed Mdaemon
3) we rule mdaemon.ini (prescribe the serials from license.xml)
4) run the installation of md14ru.exe
5) setup thinks for a while (apparently want to reach altn.com) and offers to update the current version)
6) copy the patch before starting.
7) start and stop.
8) take the <PCID> tag from license_request.xml and substitute it in license.xml
9) run and test the work.
10) if an error or something is checked with license.xml, if necessary, take the <PCID> tag from the license_request.xml file and substitute it in license.xml
Updating the working MDAEMON version 14.0 and higher:
1) Stop the MD
2) Run the installation in silent mode (key / s)
3) Apply the patch.
Fix license.xml
Pay attention to the <Version> </ Version> tag
4) and the <LastValidVersion> </ LastValidVersion> section in the plugins section, incorrect values in these tags affect the operation of the modules. AS, for example, without these tags does not see public folders !!!
5) We start.
Ports do not need to be opened, the license remains.
PS. On the operation of OC and AV modules
If the modules do not start, then
Example for AV:
we try to change the <Data> 1 </ Data> tag to <Data> 0 </ Data> or vice versa
and try to specify the version and release date correctly (we take the date to the version from the Release Note on altn.com)
for example for securityplus version 4.1.5:
<CurrentVersion>
<Version> 4.1.5 </ Version>
<ReleaseDate> 2012-10-30 </ ReleaseDate>
</ CurrentVersion>
Similarly for OC
PSS Attention !!! Pay attention to the <Version> </ Version> tag
and to the <LastValidVersion> </ LastValidVersion> section in the plugins section, the incorrect values in these tags affect the operation of the modules. AS, for example, without these tags does not see public folders !!!
Good luck!
Activation Instructions Mdaemon 14
1. Install new or use old Mdaemon.
2. If there is any license (purchased or trial) for Mdaemon 14, go to step 4
3. Obtain trial license and activate it. Stop Mdaemon service.
4. Close 443 port on services.altn.com (or in hosts: services.altn.com = 127.0.0.1)
5. Save the license (license \ license.xml) in a safe place.
6. Start and stop Mdaemon.
7. Edit license.xml (see license-example.xml):
Activation instructions Mdaemon 14 (in english see below)
1. Install or copy the installed Mdaemon to the desired location.
2. If there is any license for Mdaemon 14 (valid or trial), go to item 4
3. Get the trial and activate it. We stop Mdaemon.
4. We close 443 port on services.altn.com
5. Save the license (license \ license.xml) in a safe place.
6. Start and stop Mdaemon.
7. Let’s edit license.xml for you (see license-example.xml):
A header with fields <Key>, <DateTime> </ DateTime>, <Next> </ Next>, <RemoteIP>
do not touch.
If the license is transferred from another computer, the <PCID> field is taken from the license_request.xml file
The <UsageKey> field is the registration key, it consists of 5 parts. Parts 3-5 correspond to the serial number.
The <SerialNumber> field is a serial number, consists of 3 parts. (you can use the famous keygen) Be sure to prescribe the same in mdaemon.ini
The <Trial> field is a value of 1 (trial mode) value of 0 (a proprietary Mdaemon)
The <StartDate> field is the start date of use (you can leave it untouched. <StartDate> is not older than <DateTime>)
Field <EndDate> the end date of use (more than 10 years did not check)
The <Deactivate> field is the deactivation date (set the same as <EndDate>)
<Plugin> section
<Product> AS </ Product>
……
… ..
… ..
</ Plugin>
Repeats for each plug-in in the <Product> field the name of the plug-in to be used
AS – ActiveSync
OC – Outlook Connector
AV – Antivirus / SecurityPlus
The structure of the section is the same as described above (the names and values of the fields are absolutely identical, you can stupidly copy)
<UsageKey>, <SerialNumber> can be the same. Do not forget about mdaemon.ini
In sections with plug-ins we add
<LastValidVersion>
inside everything that stands in <CurrentVersion> </ CurrentVersion>
</ LastValidVersion>
example:
<CurrentVersion>
<Version> 14.0.0 </ Version>
<ReleaseDate> 2014-03-25 </ ReleaseDate>
</ CurrentVersion>
<LastValidVersion>
<Version> 14.0.0 </ Version>
<ReleaseDate> 2014-03-25 </ ReleaseDate>
</ LastValidVersion>
</ Plugin>
Fields with the word Error, for example <ProductErrorCode> <ProductErrors> – are deleted.
Save the license.xml and just in case copy it to a safe place.
8. We replace the original files with patches.
9. We close 443 port on services.altn.com
10. Launch the Mdaemon. We check the launch of plug-ins. If the plugins do not run once again checks license.xml We draw attention to the section <CurrentVersion>, the <Version> field must match the value from license_request.xml If all the changes have disappeared, then the port is not closed !!!
11. Correcting errors in license.xml and mdaemon.ini
12. Run and check the work.
Updating the working MDAEMON version 13.6 and below:
1) close services.altn.com
2) copy the license folder with the prepared files to the folder with the installed Mdaemon
3) we rule mdaemon.ini (prescribe the serials from license.xml)
4) run the installation of md14ru.exe
5) setup thinks for a while (apparently want to reach altn.com) and offers to update the current version)
6) copy the patch before starting.
7) start and stop.
8) take the <PCID> tag from license_request.xml and substitute it in license.xml
9) run and test the work.
10) if an error or something is checked with license.xml, if necessary, take the <PCID> tag from the license_request.xml file and substitute it in license.xml
Updating the working MDAEMON version 14.0 and higher:
1) Stop the MD
2) Run the installation in silent mode (key / s)
3) Apply the patch.
Fix license.xml
Pay attention to the <Version> </ Version> tag
4) and the <LastValidVersion> </ LastValidVersion> section in the plugins section, incorrect values in these tags affect the operation of the modules. AS, for example, without these tags does not see public folders !!!
5) We start.
Ports do not need to be opened, the license remains.
PS. On the operation of OC and AV modules
If the modules do not start, then
Example for AV:
we try to change the <Data> 1 </ Data> tag to <Data> 0 </ Data> or vice versa
and try to specify the version and release date correctly (we take the date to the version from the Release Note on altn.com)
for example for securityplus version 4.1.5:
<CurrentVersion>
<Version> 4.1.5 </ Version>
<ReleaseDate> 2012-10-30 </ ReleaseDate>
</ CurrentVersion>
Similarly for OC
PSS Attention !!! Pay attention to the <Version> </ Version> tag
and to the <LastValidVersion> </ LastValidVersion> section in the plugins section, the incorrect values in these tags affect the operation of the modules. AS, for example, without these tags does not see public folders !!!
Good luck!
Activation Instructions Mdaemon 14
1. Install new or use old Mdaemon.
2. If there is any license (purchased or trial) for Mdaemon 14, go to step 4
3. Obtain trial license and activate it. Stop Mdaemon service.
4. Close 443 port on services.altn.com (or in hosts: services.altn.com = 127.0.0.1)
5. Save the license (license \ license.xml) in a safe place.
6. Start and stop Mdaemon.
7. Edit license.xml (see license-example.xml):