error in tools/route editor :

There has been an error when retrieving routes! The error is:
INVALID_OS_LANGUAGE
Sorry, but the Route Editor only works on English and Spanish as base language for Microsoft Windows.
Please reload this page. If the problem persists, please drop a topic requesting help on our Help & Support forum.

I am a french user !!!
your software should function for everybody and no solely for english and spanish !!!!!

Your download links of the new versions on your site don't function...in France!
Best regards

Christian PIERILLAS
FRANCE

► Go to Downloads Page

If you haven't installed SMTPing, please go to the downloads page and get the installation package.

When running SMTPing for the first time, you'll get the next notification on the dashboard:

Just hit the "OK" button. Then, hit the "Configuration" button at the header:

The Configuration page will open. You should fill the license fields with the info you received from us and hit the "Update license data" button as shown below:

Then, after submitting the info, your license will be set:

You just need to get back to the dashboard and you'll have access to everything without issues.

Note: if you have the WASP distro, you'll surely have the dashboard opened with the included Chromium browser. Just make sure to reload any opened tabs to reflect the license data.

If you have any issues or need some help, don't hesistate on posting a support request here.

Included fixes:

• Added Mail Alerter extension, only for registered users using the WASP distro.
  
• Minor fixes to SNMP extension.
  
• Minor improvements to shell ping facility.

► Go to Downloads Page

Requirements

• You must be running the WASP distro. The PhpDock distro doesn't support extensions.
  
• You need to have a registered license. This extension isn't included in the free extensions bundle.
  
• You must make sure that you can make outbound SMTP connections from your network.

Installation

• Close SMTPing.
  
• Download the extension installer from the downloads page.
  
• Execute the installer.

Configuration

After installing the extension, you'll notice two icons on the sidebar:

• The first icon starts/stops mail alerts.
  
• The second icon (with the gear) invokes the configuration dialog.

When hitting the configuration icon, the dialog will pop up and allow you to enter all details needed to work.

Basic settings

First you need to specify if you're going to use a local server (thus, you have an SMTP daemon with unrestricted access from localhost) or an SMTP Gateway.

The de facto setting you should use is the second: an external server. You'll have to provide the hostname, TCP port, user name, password and encryption type.

If you're going to use TLS or SSL, you must make sure that:

• The remote host has a valid, non-self-signed SSL certificate.
  
• Your network can open outbound connections to the TCP port you set.
  
• The remote host can receive connections from your network.

Also you need to specify the sender email in the "Send mail as" field.

Additional settings

You can send a test email using the "Testing account" field to see if emails are being relayed. Just specify an email address and hit the "Send test e-mail" button.

The "Root" account is the email address that will receive notifications. If you want specific groups to send emails to a different email address, you could do it afterwards.

The Mail Delivery Triggers define the behavior of the extension listener.

• The Group Flag is "Warning" when a few nodes are alerted and "Critical" when all nodes are alerted. This can be defined specifically from the group editor.
  
• For starters, you could set the trigger to 10 consecutive failures. Feel free to set a number that works for you.
  
• Specify twice the amount of consecutive failures to receive notifications, unless you want to get bothered by the mailer

A recommended setting for triggering alerts could be: 3 failures and notify every 10 minutes.

Per Group alerts

When you edit a group, you'll be able to specify an email recipient other than the "root" one specified on the extension configuration. You can set a different recipient for every group on the dashboard, and those groups with no recipient defined will be notified to the "root" account.

Fatal error: __clone method called on non-object in C:\ProgramData\LAVA SoftWorks\SMTPing\www\index.php on line 0

And considering the hotfix we previously released, we packed those changes among with the ones for this extension, so you download a single package.

Remember: the SNMP extension can work on SMTPing starting as of version 1.3 and is targeted to our retail users, so, if you want to give it a try and didn't update SMTPing to 1.3, please do so before grabbing this file!

You can download it from our Downloads page.

We'd like to thank David Stokes for helping us discovering this problem.

The details:

• Fixed issues when changing database engine (SQLite --> MySQL or viceversa) from the configuration window. It wasn't saving the new preferences and it remained stuck in the middle of the migration.
  
  
• Removed MySQL info fields from the configuration/Application Settings page on the PhpDock distro (they're useless because of the nature of the distro).

Warning! Do not download this hotfix unless you have version 1.3 installed!

Please pick your file:

• Hotfix for PhpDock distro:
  www.lavasoftworks.com/smtping/downloads/hotfixes/SMTPing-1.3.0.31-PhpDock-Hotfix.exe
  (2.44 Mb, MD5 hash: b7650fef686242ac239eb605cc498667)
  
  
• Hotfix for WASP distro:
  www.lavasoftworks.com/smtping/downloads/hotfixes/SMTPing-1.3.0.31-WASP-Hotfix.exe
  (2.44 Mb, MD5 hash: f0ead069a9be765eb77e63570b409847)

Please note that this extension is pretty barebones and is intented for people who knows about SNMP monitoring. You should document yourself on SNMP before attempting to use this extension on SMTPing, because you'll get lost easily.

This extension will let you specify an item as an SNMP node of a certain type. Right now it supports SNMP v1 and v2 (v3 will be added later on) and it comes with the Net-SNMP MIBs, which will be handy for monitoring Linux servers.

SNMP stuff NOT to miss

• If you have installed Net-SNMP thru CygWin or MinGW, it is for sure you've added the MIBDIRS variable in your system environment. Be warned that the package installer will override this variable and set it to its own MIB library location.
  
  You should backup the next registry value before installing the package:
  
  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment\MIBDIRS
  
  Now, if you want SMTPing to use your MIBs library, you will need to, once installed, go to your system properties and change the MIBDIRS variable to the path where your MIBs reside.
  
  
• After installing the package, you may need to close/open your session or reboot your computer. That's because the MIBDIRS environment variable is going to be added by the installer.
  
  If you do a SNMP walk from an SMTPing node and you get the numeric or ISO OIDs, then you will need to reboot the computer, because the MIB reader needs to detect the MIBDIRS variable from the environment to load all the MIBs properly.
  
  
• If you rebooted the system and still can't get the OIDs on an SNMP walk from SMTPing, please drop us a support request here at the forum.

What the Item Anchoring extension is for

Due to the nature of the results given by SNMP agents (integers, percents, bytes, allocation units, etc.), you shouldn't mix up different types of results within the same group, because the group charts will be all messy if you have a regular ping node (measured in response MS), a TCP port checking node (measured as response in MS), a SNMP Free disk space node (measured in allocation units and converted to bytes) and a CPU activity node (measured in a percentile integer).

So, the correct usage of the SNMP nodes is pretty straight: you must create groups for distinct nodes with the same types of SNMP items inside (only CPU, only Disk, only interface, etc.) Then use the Item Anchoring extension to create a relationship between all of them.

Example:

• You are monitoring two servers, A and B.
  
  
• You create a group with two standard ping items, one for each server. You name them "Ping A" and "Ping B".
  
  
• You create an SNMP group for CPU monitoring with two SNMP nodes, one for each server.
  
  
• You create an SNMP group for Disk monitoring with two SNMP nodes, one for each server.
  
  
• You create an SNMP group for Interface monitoring with four SNMP nodes, two in/two out for each server.
  
  
• You use the Anchoring extension, select the "Ping A" node and tie all the SNMP ones to it.
  
  
• You use the Anchoring extension, select the "Ping B" node and tie all the SNMP ones to it.

Once you reload the dashboard, you'll be able to click on the "Ping A" and "Ping B" nodes to toggle their related nodes' visibility. That's what this extension was made for :)

Still confused?

If you're questioning why there are no screen shots here... well, please be patient. I'll add them later on.

If you need help, don't hesitate on posting a support request here at the forum.

Ok, We haven't changed the name, we'll stick to "SMTPing" for the time being. That's because we had more imporant things at hand.

This release includes a lot of bug fixes, a lot of improvements and some neat stuff that you're going to like :) ...Please review the changelog and check revisions from 22 through 30 (this one) for all the info.

You should update as soon as possible!

► Go to Downloads Page

• Fixed route editor problem with XP that thrown an "INVALID_OS_LANGUAGE" error.
  Note: weird behavoir detected on WinXP/Server 2003. A note about it was added.
  
  
• Configuration/Dashboard: Fixed a bug that prevented displaying theme information.

Giveaway of the Day users can download a special HotFix that includes the updates listed above plus:

• Fixed version number (it was incorrectly set to 1.2.3.20 when published). Just for the record: free/retail release 1.2.4.21 and GOTD release 1.2.2.19 (the one we're publishing now) are essentially the same, but GOTD will no longer receive updates.
  
  
• Removed license check with LSW server - Not neccesary.

Before downloading:

We gave a few users information on how to deal with some issues by manually touching the SMTPing.ini file of the WASP distro (both free/retail and GOTD users). Please note that if you apply this update, your changes will be lost, so, before updating, please backup your file and after updating, apply the manual changes back again.

Now, the download links:

• If you are not a GOTD release user, you can get the update from SMTPing's update checker or downloading your corresponding distro update from the Downloads page.
  
  
• If you are a GOTD release user, please download the file below and run it:
  http://www.lavasoftworks.com/smtping/downloads/hotfixes/SMTPing-1.2.2.19-WASP-GOTD-Hotf...

• Bootstrap.vbs can't be found, yet, it exists in "C:\Program Files\SMTPing"
  
• Can't find script engine "VBScript"

They come up by one of the next reasons:

• Using Windows XP with a Service Pack below SP3 or no Service Pack at all
  
• Some nasty update on Windows Vista
  
• A very kicky security software that blocks the Windows Scripting Host

The workaround for these cases is the next:

1. Open "C:\Program Files\SMTPing\SMTPing.ini" with a text editor.

2. Search for "BootStrap.vbs". You'll get to line 105 or so.

3. Comment that line by prepending a semicolon to it and remove the semicolon of the next line.

From:

Action: shellexecute; FileName: "BootStrap.vbs"; Parameters: """%ChromiumPortable%"" ""%WebRoot%"""; ShowCmd: hidden
; Action: shellexecute; FileName: "%ChromiumPortable%"; Parameters: "%WebRoot%"

To:

; Action: shellexecute; FileName: "BootStrap.vbs"; Parameters: """%ChromiumPortable%"" ""%WebRoot%"""; ShowCmd: hidden
Action: shellexecute; FileName: "%ChromiumPortable%"; Parameters: "%WebRoot%"

Now launch SMTPing and you'll be fixed, but...

Please be adviced that when you update SMTPing, you'll most likely lose this change. So to permanently fix it, you have to deal with your security settings and:

• Allow "C:\Program Files\SMTPing\SMTPing.exe" to run as a full privileged user, or
  
• Whitelist it or flag it as trusted/secure in your security programs, or
  
• Check if something's blocking .vbs files to be properly executed by the Windows Scripting Host.

Please advise.

Thanks...Don

P.S. this is the Giveawayoftheday download.

Important: this procedure applies to SMTPing using SQLite. If you decide to go over MySQL using an existing server, you'll have to manually dump the MySQL database in order to back it up.

1. Open a Windows Explorer window and go to SMTPing's application data folder:

• On Windows Vista and up: C:\ProgramData\LAVA SoftWorks\SMTPing
  
• On Windows XP: C:\Documents and Settings\All Users\Application Data\LAVA SoftWorks\SMTPing

2. From that directory, there are three files to backup:

• The historic database: SMTPing.sqlite2db
  
• The configuration file: www\config.xml
  
• The license file: www\etc\license.dat

3. That's all! If you uninstall and reinstall SMTPing, just restore those files to the specified locations.

Note 1: those three files aren't replaced when updating SMTPing.
Note 2: the GOTD release doesn't have the license file. That's hardcoded.

But the file is there.

What can I do ? Thanks.

This problem caused SMTPing's PyCron to not update the nodes on every heartbeat. You may have not been victim of this bug because it seems to be related to some update on Windows 7 we weren't able to identify.

Anyway, we've rebuilt the setup packages and put that fix on them and released them a few minutes ago.

Please download and apply this update!

► Go to Downloads Page

We've improved the Inno Setup scripts for all packages. Those users to reinstall the whole package instead of just updating will not get the core scripts updates.

This update is not critical or mandatory, so if you don't have the time to update right now, don't sweat about it :)

► Go to Downloads Page

• Fixed changelog entries messed up.
  
• {Bug report} Fixed wrongly specified HTTP port for items in the Group Maintenance form.
  
• Improved updates checker.
  
• Added distro keyname to the setup to keep the user informed when update is needed.
  
• Added some cosmetic improvements to the Basic Template.
  
• Added a direct download link to the new release info dialog of the update checker.
  
• Added version params to styles/scripts to force browser reload on update.
  
• WASP Distro: Updated AETrayMenu version number, previously ignored (doh!)

That's all for now :) please update your installation to get all fixed up!

► Go to Downloads Page

The email you've received contains info of where it has to be placed:

"In order to update your SMTPing installation,
please copy the string BETWEEN THE LINES into the requested
text area in SMTPing's Configuration/license page"

Even when you open SMTping from scratch yo get this dialog:

So, you simply have to hit the "Configuration" button in the header:

As the "License" tab is the first, you just fill in the form:

Please note that at the end of the form you can request license info to be sent to your email:

Once you fill all the blanks, the page shows its confirmation or some error if the info is not correct:

Now, something important!

There was a bug on the license manager prior to version 1.1.0.14 that is already fixed. If you have problems, please update SMTPing to its latest version and retry placing your license info.

► Go to Downloads Page