Proxmox Mail Gateway 5.2 Released

Proxmox Mail Gateway is a ready made solution for quickly creating a system for controlling email traffic and protecting the internal mail server
27 March 2019   546

Proxmox, known for developing the Proxmox Virtual Environment distribution kit for deploying virtual server infrastructures, introduced the release of the Proxmox Mail Gateway 5.2 distributive. Proxmox Mail Gateway is presented as a turnkey solution for quickly creating a system for controlling email traffic and protecting the internal mail server.

An installation ISO image is available for free download. Distribution-specific components are under the AGPLv3 license. To install updates, you can use both a paid Enterprise repository and two free repositories that differ in the level of stabilization of updates. The system part of the distribution is based on a package based on Debian 9.8 (Stretch) and the Linux kernel 4.15. Proxmox Mail Gateway components can be installed on top of existing Debian 9 servers.

Proxmox Mail Gateway functions as a proxy server, acting as a gateway between the external network and an internal mail server based on MS Exchange, Lotus Domino or Postfix. It is possible to manage all incoming and outgoing mail flow. All correspondence logs are sorted out and available for analysis via a web interface. Both graphs are provided to assess the overall dynamics, as well as various reports and forms for obtaining information about specific letters and delivery status. Cluster configurations are supported for high availability (maintaining a synchronized backup server, data is synchronized via an SSH tunnel) or load balancing.

Perl 6 Programming Language to be Renamed to Raku

Perl 6 Programming Language to be Renamed to Raku
16 October 2019   190

The Perl 6 repository has officially adopted the change, which includes the project name to Raku. It is noted that despite the fact that formally the project has already been given a new name, a name change for a project that has been developing for 19 years requires a lot of work and it will take some time until the rename is complete.

For example, replacing Perl with Raku will also require replacing the reference to “perl” in directories and file names, classes, environment variables, documentation and site processing. There is also a lot of work to do with the community and third-party sites to replace references to Perl 6 with Raku on all kinds of information resources (for example, you may need to add the raku tag to materials with the perl6 tag). The version numbering of the language will remain unchanged for the time being and the next release will be "6.e", which will maintain compatibility with previous releases. But the organization of discussion of the transition to a different numbering of issues is not ruled out.

For scripts, the .raku extension will be used, for the .rakumod modules, for the .rakutest tests, and for the .rakudoc documentation (the shorter .rk extension, it is decided not to use it as it may be confused with the extension ".rkt" already used in the Racket language. New extensions are planned to be fixed in specification 6.e, which will be released next year. Support for old extensions ".pm", ".pm6" and ".pod6" in specification 6.e will be saved, but in the next version 6.f these extensions will be marked as deprecated (a warning will be displayed). the ".perl" method, the Perl class, the $ * PERL variable, the "#! / usr / bin / perl6" in the script title, the PERL6LIB and PERL6_HOME environment variables can be assigned, in version 6.g, many bindings to Perl are left for compatibility may be deleted.

The project will continue to evolve under the auspices of The Perl Foundation. The creation of an alternative organization may be considered if The Perl Foundation decides not to deal with the Raku project. On the website of The Perl Foundation, the Raku project is proposed to be presented as one of the languages ​​of the Perl family, along with RPerl and CPerl. On the other hand, the idea of ​​creating the "The Raku Foundation" is mentioned as an organization only for Raku, leaving the "The Perl Foundation" for Perl 5.

Recall that the main reason for the unwillingness to continue the development of the project under the name Perl 6 is that Perl 6 did not become a continuation of Perl 5, as it was originally expected, but turned into a separate programming language for which tools for transparent migration from Perl 5 were not prepared As a result, there was a situation when under the same name Perl two parallel independent languages ​​are proposed that are not compatible with each other at the source level and have their own developer community. The use of the same name for related, but radically different languages ​​leads to confusion and many users continue to consider Perl 6 a new version of Perl, and not a fundamentally different language. At the same time, the name Perl continues to be associated with Perl 5, and the mention of Perl 6 requires a separate clarification.