But I can only specify one domain in SiteDomain, even though I host several domains on my machine. If I specify a SiteDomain in the AWStats configuration, emails from this domain is shown as "Local" in the statistics. What I can't figure out is how AWStats determines whether an sender is local or external. If you check the sample statistics, it splits statistics for senders & receivers in two groups, Local & External. This would have the effect that the SMTP Error codes never shows error codes given by hMailServer - only error codes giving by the receiving servers.īut then email from external servers to users on the hMailServer machine wouldn't be logged at all, which would be very confusing as well. Not when it receives messages from other servers. So my best bet right now is that hMailServer should only log when it sends messages to other servers. For example, the SMTP Error codes statistics would contain error codes both from hMailServer, and from some external server. If hMailServer would count both received / sent and put them both in the Mail succesfully sent column, it would be very confusing. If you look on the statistics, it counts Mail successfully sent but there doesn't seem to be a mail succesfully received. I've already managed to create a log which AWStats can parse.Īnyway, there's still a couple of things that I can't figure out.ĪWStats seems to be made only for outgoing SMTP traffic, not incoming. I think we're misunderstanding eachother. That's how the Apache logs work anyway.Īs for the log format, I played with AWStats and hMail logs a while back trying to figure a way to make it work, and I believe it requires a one line detail of the mail action performed (not like hMail currently where there are multiple lines) I could be wrong but that was my impression. I *think* that it is not necessary to delete the file after parsing (unless it is just too darn big) If I remember correctly, AWStats will remember it's place in the log file and pick up from there the next time. So when you want to update your statistics, you take a copy of the file, delete the original, parse the statistics in the copy, and then delete the copy. Here is how I upgrade my Awstats from 7.1 to 7.3ġ) Download the gz file from the official site in the terminal window of VPS.Ģ) Decompress the gz file in command line.ģ) Copy the files which in If you check this, hMailServer will create a log file with a fixed name (hmailserver_awstats.log) which awstats records will be written to. Since updating Webmin to 1.53, the Add New Config File screen layout is Move version system to sourceforge Git instead of CVS. #918 $MinHit used in sub HTMLShowLogins. #881 Avoid warning mixed http/https with module graphgooglechartapi. Restore detection of Opera browsers versions. When using builddate option of script awstats_buildstaticpages, #877 Windows 8 + iOS Support in AWStats For exemple : Working line in hmailserverawstats. Update domains, robots and search engines database: in Awstats file generated by Hmail Server, the colum with the vartiable hostr is most part of the time empty inhmailserverawstats.log, which cause Awststs to see all the parsing records as corrupted. Better error management of geoip modules. Let’s have a look at the changes since Awstats 7.1 Last time, I upgrade my Awstats to 7.1, is almost two years ago. I haven’t upgrade my installation for a long time. I am using Advanced Web Statistics(Awstats) for many years.
0 Comments
Leave a Reply. |