This VBS script (zipped in the attachment) provides a full diagnostic report detailing the Hmailserver setup for aiding analysis on problems relating to email receiving, transmission and connections. It may be run in addition to the internal HMailserver DIAGNOSTIC report.

You may be advised by forum helpers to run the script and copy/paste the resultant file contents in to a REPLY on your forum thread. Note: there is a prompt asking to include 'RULES'; please include them if asked to do so by your forum helper to help solve your problem (the default is to exclude them to save space).

When run just copy the report to a reply without any additional formatting - no formatting will be required (do not add 'quote' or 'code' tagging as it will already contain forum friendly formatting tags). Alternatively you may attach the .TXT report.

Please do not change or redact/obfuscate anything on the report - no sensitive information is disclosed (all domains and aliases are converted to pseudonyms).

Click on the Zip attachment to download, and click on to run the VBS script contained within (or run it from a command line). It must be run interactively as it will prompt for your password. Then follow the interactive prompts. When complete, paste the resultant report to your forum thread as a REPLY (no formatting necessary - it will already contain forum friendly formatting tags.)

How To Use
The report does a certain amount of configuration integrity checking and will advise accordingly. Search the resultant report for double exclamation marks ("!!") throughout - these will highlight any discrepancies or warnings that you should address.

NOTE: In the report "EXTERNAL.TLD" means an FQDN (domain) that is not hosted on your Hmailserver.

(There is nothing harmful or security compromising within the script or its results and you can run it as is. However, no one is forcing you to do so and you are free to read the script before running it to put your mind at ease....or even not to run it at all).

I wonder if this is a good time to ask for the Script AutoUpdate function ?

What do you mean? (Sorry, I dont understand). BTW: Ive shown the entry on the example report above.

It's been way too long time since I worked on phpBB but as I recall, the page title is equal to subject in first post so if you change the subject you also change page title...

So... If you include version number in first post subject this scriptlet should show it - and then you can compare to version hardcoded in script to inform about new version (half an autoupdate solution )

I dont think it is too important with this particular script as by its nature it is really a 'one-off' usage script (for when we are trying to diagnose something on the forum) - that is to say that even if you have already downloaded it its not important to redo it because you (hopefully) shouldnt be needing it again. That is why I didnt bother putting version numbers in the title but instead make the version apparent in the attachment comment instead really for tracking to my updates).

* The routine lists all domains and, if ENABLED, the associated settings (where enabled) such as Signatures, DKIM, Greylisting enablement, Catchall etc.
* All domains and aliases (FQDN's) are 'substituted to DOMAIN1.com, DOMAIN2, ALIAS1.com, ALIAS2.com etc to protect privacy. Clues to the original domain are shown by displaying the first 2 characters only followed by "xxx".
* All substitutions are maintained throughout the report for every occurrence of the domain.

For example, real domain "jimimaseye.home.net" may be assigned to "Domain2.com" in the report and will appear as domain2.com. eg, If it appears as the catchall address "sally@jimimaseye.home.net" then it will be shown as "sally@domain2.com".

For me (and this just may be for me) the DKIM file name also includes the FQDN for each of my domains. Unsure how hard that would be report with xxx's though
All of my .com.au domains look like abxxx.cox.au with the .com.au being changed to .cox.au

Another thing I'd like to see is in the logging section...
Which logging is enabled?
and if the paths actually contain the log file detailed (eg the error log is not created everyday, and only exists when an error has occurred. I can go weeks without one. Perhaps also a count of the number of 'old' log files in that directory, or even a 'size' of the log folder.

And, a count of messages in the root of the data directory, with a comparison to the number of messages in the queue.

Great work jimimaseye!!

Just 'cause I link to a page and say little else doesn't mean I am not being nice.
https://www.hmailserver.com/documentation

mattg wrote:For me (and this just may be for me) the DKIM file name also includes the FQDN for each of my domains. Unsure how hard that would be report with xxx's though
All of my .com.au domains look like abxxx.cox.au with the .com.au being changed to .cox.au

* any mention of the actual domain in the DKIM path or selector now also gets replaced with its pseudonym.
* Domain levels containing 2 letters (eg, .AU, .UK ) or is .COM or .NET do not get masked. (eg. mail1.com.au becomes maxxx.com.au).

Of course there is no distinction between 'mail1.company.com' and 'mail2.company.com' as they will both be listed as "maxxx.coxxxxx.com" - in these cases the Domain number in their pseudonym (eg. "Domain4"), and its placement in the list of domains, will help identify which is which in relation to how they appear within the default DOMAIN view in Admin.

Which logging is enabled?

Already included the report (from v1.25) at the bottom (just above 'SYSTEM TESTS').

v1.58
* Added warning if Domain Greylisting is enabled but Greylisting is not activated. ("Greylisting: !! ENABLED BUT NOT ACTIVATED!!")
* Moved domain = "Enabled: True/False" to the right of the Domain name, and removed a couple of blank lines below the each domain section, to save space in the report

mattg wrote:and if the paths actually contain the log file detailed (eg the error log is not created everyday, and only exists when an error has occurred. I can go weeks without one. Perhaps also a count of the number of 'old' log files in that directory, or even a 'size' of the log folder.

So we have just seen one where no logging is enabled, but the script listed the paths that the logs WOULD BE.
Can we check for existence (OR NOT) of this log file as well please.

just knowing that there is an error log would be helpful.

Perhaps could also include contents of today's error log (they change daily)...

Just 'cause I link to a page and say little else doesn't mean I am not being nice.
https://www.hmailserver.com/documentation

* Added the Last Modified date to the EVENTS log file (in LOGGING) to identify the last write to the file (signifying scripting in use)
* Hide the 'Current' log file path if logging is disabled (continuing to display all other paths)

I think it would be cool Feature if you can add the info if HMS is running as Internetsite SMTP Server
(Standalone) or as Relayserver dependent.

Thanks.

The report is designed to be snapshot of settings at the time of running for diagnostic purposes and not really a 'this is what we think its purpose is' type of feedback. However, it does already report whether there are domains set up and what the SMTP settings are - collectively this should be sufficient for the reader (with the knowledge and understanding) to determine how this particular installation operates. The administrstor should already know the purpose of his machine and can always impart this intention to us in the forum whilst discussing his problem if necessary.

The report isnt really intended for the admin/user of the machine but more for us as helpers to help him. Changing just one setting and the whole report profile, and functionality of the server, can change. There is no added benefit to the admin of running the report betond using it with us on the forum unless he wants to take and record the final snapshot of his settings in print for documentation to accompany his backup.

* Bug fix relating to 'DomainReveal' display error if no Domains or Aliases are present on the system.
* Change "Connection" to "Con. Sec." in SMTP Relay connection.

RvdH wrote:Can't the output not be placed in 'Current Directory'? ....hate i have to browse to %TEMP% every time

The script was designed to open the report automatically after run (by association of .TXT).

In other words, when I run it and click OK to acknowledge, it automatically opens NOTEPAD (which is my association application to .TXT files) and displays the report (making it easy to then do a quick ctrl-A/'select all' to paste in to the forum). This way the location of the file wasnt important and shouldnt need to be found. It was also chosen to send to the TEMP folder because it is technically a temporary file and hopefully subjected to the usual housekeeping of the temp directory that the user performs and there should be no folder permission problems for saving it.