From 41ac27ebb3792516c6920f88119a7dd80d833c27 Mon Sep 17 00:00:00 2001 From: Trevor Batley Date: Sat, 7 Sep 2024 20:44:45 +1000 Subject: [PATCH] initial commit of file from CVS for smeserver-mxbackup on Sat Sep 7 20:44:45 AEST 2024 --- .gitignore | 4 + Makefile | 21 + README.md | 16 +- additional/COPYING | 340 ++++++++++++ contriborbase | 1 + createlinks | 32 ++ root/etc/e-smith/GreenLight.jpg | Bin 0 -> 1058 bytes root/etc/e-smith/RedLight.jpg | Bin 0 -> 1055 bytes .../db/configuration/defaults/mxbackup/status | 1 + .../db/configuration/defaults/mxbackup/type | 1 + .../bg/etc/e-smith/web/functions/mxbackup | 122 +++++ .../da/etc/e-smith/web/functions/mxbackup | 122 +++++ .../de/etc/e-smith/web/functions/mxbackup | 122 +++++ .../el/etc/e-smith/web/functions/mxbackup | 122 +++++ .../en-us/etc/e-smith/web/functions/mxbackup | 182 +++++++ .../es/etc/e-smith/web/functions/mxbackup | 122 +++++ .../et/etc/e-smith/web/functions/mxbackup | 122 +++++ .../fr/etc/e-smith/web/functions/mxbackup | 122 +++++ .../he/etc/e-smith/web/functions/mxbackup | 122 +++++ .../hu/etc/e-smith/web/functions/mxbackup | 122 +++++ .../id/etc/e-smith/web/functions/mxbackup | 122 +++++ .../it/etc/e-smith/web/functions/mxbackup | 122 +++++ .../ja/etc/e-smith/web/functions/mxbackup | 122 +++++ .../nb/etc/e-smith/web/functions/mxbackup | 122 +++++ .../nl/etc/e-smith/web/functions/mxbackup | 122 +++++ .../pl/etc/e-smith/web/functions/mxbackup | 122 +++++ .../pt-br/etc/e-smith/web/functions/mxbackup | 122 +++++ .../pt/etc/e-smith/web/functions/mxbackup | 122 +++++ .../ro/etc/e-smith/web/functions/mxbackup | 122 +++++ .../ru/etc/e-smith/web/functions/mxbackup | 122 +++++ .../sl/etc/e-smith/web/functions/mxbackup | 122 +++++ .../sv/etc/e-smith/web/functions/mxbackup | 122 +++++ .../th/etc/e-smith/web/functions/mxbackup | 122 +++++ .../tr/etc/e-smith/web/functions/mxbackup | 122 +++++ .../zh-cn/etc/e-smith/web/functions/mxbackup | 122 +++++ .../zh-tw/etc/e-smith/web/functions/mxbackup | 122 +++++ .../var/qmail/control/rcpthosts/20mxbackup | 29 ++ .../var/qmail/control/smtproutes/30mxbackup | 35 ++ .../qpsmtpd/config/goodrcptto/50MXBackup | 26 + root/etc/e-smith/web/functions/mxbackup | 108 ++++ .../web/panels/manager/cgi-bin/mxbackup | 1 + .../esmith/FormMagick/Panel/mxbackup.pm | 483 ++++++++++++++++++ smeserver-mxbackup.spec | 154 ++++++ 43 files changed, 4482 insertions(+), 2 deletions(-) create mode 100644 .gitignore create mode 100644 Makefile create mode 100755 additional/COPYING create mode 100644 contriborbase create mode 100755 createlinks create mode 100755 root/etc/e-smith/GreenLight.jpg create mode 100755 root/etc/e-smith/RedLight.jpg create mode 100755 root/etc/e-smith/db/configuration/defaults/mxbackup/status create mode 100755 root/etc/e-smith/db/configuration/defaults/mxbackup/type create mode 100644 root/etc/e-smith/locale/bg/etc/e-smith/web/functions/mxbackup create mode 100644 root/etc/e-smith/locale/da/etc/e-smith/web/functions/mxbackup create mode 100644 root/etc/e-smith/locale/de/etc/e-smith/web/functions/mxbackup create mode 100644 root/etc/e-smith/locale/el/etc/e-smith/web/functions/mxbackup create mode 100755 root/etc/e-smith/locale/en-us/etc/e-smith/web/functions/mxbackup create mode 100644 root/etc/e-smith/locale/es/etc/e-smith/web/functions/mxbackup create mode 100644 root/etc/e-smith/locale/et/etc/e-smith/web/functions/mxbackup create mode 100755 root/etc/e-smith/locale/fr/etc/e-smith/web/functions/mxbackup create mode 100644 root/etc/e-smith/locale/he/etc/e-smith/web/functions/mxbackup create mode 100644 root/etc/e-smith/locale/hu/etc/e-smith/web/functions/mxbackup create mode 100644 root/etc/e-smith/locale/id/etc/e-smith/web/functions/mxbackup create mode 100644 root/etc/e-smith/locale/it/etc/e-smith/web/functions/mxbackup create mode 100644 root/etc/e-smith/locale/ja/etc/e-smith/web/functions/mxbackup create mode 100644 root/etc/e-smith/locale/nb/etc/e-smith/web/functions/mxbackup create mode 100644 root/etc/e-smith/locale/nl/etc/e-smith/web/functions/mxbackup create mode 100644 root/etc/e-smith/locale/pl/etc/e-smith/web/functions/mxbackup create mode 100644 root/etc/e-smith/locale/pt-br/etc/e-smith/web/functions/mxbackup create mode 100644 root/etc/e-smith/locale/pt/etc/e-smith/web/functions/mxbackup create mode 100644 root/etc/e-smith/locale/ro/etc/e-smith/web/functions/mxbackup create mode 100644 root/etc/e-smith/locale/ru/etc/e-smith/web/functions/mxbackup create mode 100644 root/etc/e-smith/locale/sl/etc/e-smith/web/functions/mxbackup create mode 100644 root/etc/e-smith/locale/sv/etc/e-smith/web/functions/mxbackup create mode 100644 root/etc/e-smith/locale/th/etc/e-smith/web/functions/mxbackup create mode 100644 root/etc/e-smith/locale/tr/etc/e-smith/web/functions/mxbackup create mode 100644 root/etc/e-smith/locale/zh-cn/etc/e-smith/web/functions/mxbackup create mode 100644 root/etc/e-smith/locale/zh-tw/etc/e-smith/web/functions/mxbackup create mode 100755 root/etc/e-smith/templates/var/qmail/control/rcpthosts/20mxbackup create mode 100755 root/etc/e-smith/templates/var/qmail/control/smtproutes/30mxbackup create mode 100755 root/etc/e-smith/templates/var/service/qpsmtpd/config/goodrcptto/50MXBackup create mode 100755 root/etc/e-smith/web/functions/mxbackup create mode 120000 root/etc/e-smith/web/panels/manager/cgi-bin/mxbackup create mode 100755 root/usr/share/perl5/vendor_perl/esmith/FormMagick/Panel/mxbackup.pm create mode 100644 smeserver-mxbackup.spec diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..cbb3a13 --- /dev/null +++ b/.gitignore @@ -0,0 +1,4 @@ +*.rpm +*.log +*spec-20* +*.tar.gz diff --git a/Makefile b/Makefile new file mode 100644 index 0000000..5bcc044 --- /dev/null +++ b/Makefile @@ -0,0 +1,21 @@ +# Makefile for source rpm: smeserver-mxbackup +# $Id: Makefile,v 1.1 2022/08/31 15:23:04 jcrisp Exp $ +NAME := smeserver-mxbackup +SPECFILE = $(firstword $(wildcard *.spec)) + +define find-makefile-common +for d in common ../common ../../common ; do if [ -f $$d/Makefile.common ] ; then if [ -f $$d/CVS/Root -a -w $$/Makefile.common ] ; then cd $$d ; cvs -Q update ; fi ; echo "$$d/Makefile.common" ; break ; fi ; done +endef + +MAKEFILE_COMMON := $(shell $(find-makefile-common)) + +ifeq ($(MAKEFILE_COMMON),) +# attept a checkout +define checkout-makefile-common +test -f CVS/Root && { cvs -Q -d $$(cat CVS/Root) checkout common && echo "common/Makefile.common" ; } || { echo "ERROR: I can't figure out how to checkout the 'common' module." ; exit -1 ; } >&2 +endef + +MAKEFILE_COMMON := $(shell $(checkout-makefile-common)) +endif + +include $(MAKEFILE_COMMON) diff --git a/README.md b/README.md index 97980a4..949e791 100644 --- a/README.md +++ b/README.md @@ -1,3 +1,15 @@ -# smeserver-mxbackup +# smeserver-mxbackup -SMEServer Koozali developed git repo for smeserver-mxbackup smecontribs \ No newline at end of file +SMEServer Koozali developed git repo for smeserver-mxbackup smecontribs + +## Wiki +
https://wiki.koozali.org/Mxbackup + +## Bugzilla +Show list of outstanding bugs: [here](https://bugs.koozali.org/buglist.cgi?component=smeserver-mxbackup&product=SME%20Contribs&query_format=advanced&limit=0&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=CONFIRMED) + +## Description + +
*This description has been generated by an LLM AI system and cannot be relied on to be fully correct.* +*Once it has been checked, then this comment will be deleted* +
diff --git a/additional/COPYING b/additional/COPYING new file mode 100755 index 0000000..196760e --- /dev/null +++ b/additional/COPYING @@ -0,0 +1,340 @@ + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 + + Copyright (C) 1989, 1991 Free Software Foundation, Inc. + 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + Preamble + + The licenses for most software are designed to take away your +freedom to share and change it. By contrast, the GNU General Public +License is intended to guarantee your freedom to share and change free +software--to make sure the software is free for all its users. This +General Public License applies to most of the Free Software +Foundation's software and to any other program whose authors commit to +using it. (Some other Free Software Foundation software is covered by +the GNU Library General Public License instead.) You can apply it to +your programs, too. + + When we speak of free software, we are referring to freedom, not +price. Our General Public Licenses are designed to make sure that you +have the freedom to distribute copies of free software (and charge for +this service if you wish), that you receive source code or can get it +if you want it, that you can change the software or use pieces of it +in new free programs; and that you know you can do these things. + + To protect your rights, we need to make restrictions that forbid +anyone to deny you these rights or to ask you to surrender the rights. +These restrictions translate to certain responsibilities for you if you +distribute copies of the software, or if you modify it. + + For example, if you distribute copies of such a program, whether +gratis or for a fee, you must give the recipients all the rights that +you have. You must make sure that they, too, receive or can get the +source code. And you must show them these terms so they know their +rights. + + We protect your rights with two steps: (1) copyright the software, and +(2) offer you this license which gives you legal permission to copy, +distribute and/or modify the software. + + Also, for each author's protection and ours, we want to make certain +that everyone understands that there is no warranty for this free +software. If the software is modified by someone else and passed on, we +want its recipients to know that what they have is not the original, so +that any problems introduced by others will not reflect on the original +authors' reputations. + + Finally, any free program is threatened constantly by software +patents. We wish to avoid the danger that redistributors of a free +program will individually obtain patent licenses, in effect making the +program proprietary. To prevent this, we have made it clear that any +patent must be licensed for everyone's free use or not licensed at all. + + The precise terms and conditions for copying, distribution and +modification follow. + + GNU GENERAL PUBLIC LICENSE + TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION + + 0. This License applies to any program or other work which contains +a notice placed by the copyright holder saying it may be distributed +under the terms of this General Public License. The "Program", below, +refers to any such program or work, and a "work based on the Program" +means either the Program or any derivative work under copyright law: +that is to say, a work containing the Program or a portion of it, +either verbatim or with modifications and/or translated into another +language. (Hereinafter, translation is included without limitation in +the term "modification".) Each licensee is addressed as "you". + +Activities other than copying, distribution and modification are not +covered by this License; they are outside its scope. The act of +running the Program is not restricted, and the output from the Program +is covered only if its contents constitute a work based on the +Program (independent of having been made by running the Program). +Whether that is true depends on what the Program does. + + 1. You may copy and distribute verbatim copies of the Program's +source code as you receive it, in any medium, provided that you +conspicuously and appropriately publish on each copy an appropriate +copyright notice and disclaimer of warranty; keep intact all the +notices that refer to this License and to the absence of any warranty; +and give any other recipients of the Program a copy of this License +along with the Program. + +You may charge a fee for the physical act of transferring a copy, and +you may at your option offer warranty protection in exchange for a fee. + + 2. You may modify your copy or copies of the Program or any portion +of it, thus forming a work based on the Program, and copy and +distribute such modifications or work under the terms of Section 1 +above, provided that you also meet all of these conditions: + + a) You must cause the modified files to carry prominent notices + stating that you changed the files and the date of any change. + + b) You must cause any work that you distribute or publish, that in + whole or in part contains or is derived from the Program or any + part thereof, to be licensed as a whole at no charge to all third + parties under the terms of this License. + + c) If the modified program normally reads commands interactively + when run, you must cause it, when started running for such + interactive use in the most ordinary way, to print or display an + announcement including an appropriate copyright notice and a + notice that there is no warranty (or else, saying that you provide + a warranty) and that users may redistribute the program under + these conditions, and telling the user how to view a copy of this + License. (Exception: if the Program itself is interactive but + does not normally print such an announcement, your work based on + the Program is not required to print an announcement.) + +These requirements apply to the modified work as a whole. If +identifiable sections of that work are not derived from the Program, +and can be reasonably considered independent and separate works in +themselves, then this License, and its terms, do not apply to those +sections when you distribute them as separate works. But when you +distribute the same sections as part of a whole which is a work based +on the Program, the distribution of the whole must be on the terms of +this License, whose permissions for other licensees extend to the +entire whole, and thus to each and every part regardless of who wrote it. + +Thus, it is not the intent of this section to claim rights or contest +your rights to work written entirely by you; rather, the intent is to +exercise the right to control the distribution of derivative or +collective works based on the Program. + +In addition, mere aggregation of another work not based on the Program +with the Program (or with a work based on the Program) on a volume of +a storage or distribution medium does not bring the other work under +the scope of this License. + + 3. You may copy and distribute the Program (or a work based on it, +under Section 2) in object code or executable form under the terms of +Sections 1 and 2 above provided that you also do one of the following: + + a) Accompany it with the complete corresponding machine-readable + source code, which must be distributed under the terms of Sections + 1 and 2 above on a medium customarily used for software interchange; or, + + b) Accompany it with a written offer, valid for at least three + years, to give any third party, for a charge no more than your + cost of physically performing source distribution, a complete + machine-readable copy of the corresponding source code, to be + distributed under the terms of Sections 1 and 2 above on a medium + customarily used for software interchange; or, + + c) Accompany it with the information you received as to the offer + to distribute corresponding source code. (This alternative is + allowed only for noncommercial distribution and only if you + received the program in object code or executable form with such + an offer, in accord with Subsection b above.) + +The source code for a work means the preferred form of the work for +making modifications to it. For an executable work, complete source +code means all the source code for all modules it contains, plus any +associated interface definition files, plus the scripts used to +control compilation and installation of the executable. However, as a +special exception, the source code distributed need not include +anything that is normally distributed (in either source or binary +form) with the major components (compiler, kernel, and so on) of the +operating system on which the executable runs, unless that component +itself accompanies the executable. + +If distribution of executable or object code is made by offering +access to copy from a designated place, then offering equivalent +access to copy the source code from the same place counts as +distribution of the source code, even though third parties are not +compelled to copy the source along with the object code. + + 4. You may not copy, modify, sublicense, or distribute the Program +except as expressly provided under this License. Any attempt +otherwise to copy, modify, sublicense or distribute the Program is +void, and will automatically terminate your rights under this License. +However, parties who have received copies, or rights, from you under +this License will not have their licenses terminated so long as such +parties remain in full compliance. + + 5. You are not required to accept this License, since you have not +signed it. However, nothing else grants you permission to modify or +distribute the Program or its derivative works. These actions are +prohibited by law if you do not accept this License. Therefore, by +modifying or distributing the Program (or any work based on the +Program), you indicate your acceptance of this License to do so, and +all its terms and conditions for copying, distributing or modifying +the Program or works based on it. + + 6. Each time you redistribute the Program (or any work based on the +Program), the recipient automatically receives a license from the +original licensor to copy, distribute or modify the Program subject to +these terms and conditions. You may not impose any further +restrictions on the recipients' exercise of the rights granted herein. +You are not responsible for enforcing compliance by third parties to +this License. + + 7. If, as a consequence of a court judgment or allegation of patent +infringement or for any other reason (not limited to patent issues), +conditions are imposed on you (whether by court order, agreement or +otherwise) that contradict the conditions of this License, they do not +excuse you from the conditions of this License. If you cannot +distribute so as to satisfy simultaneously your obligations under this +License and any other pertinent obligations, then as a consequence you +may not distribute the Program at all. For example, if a patent +license would not permit royalty-free redistribution of the Program by +all those who receive copies directly or indirectly through you, then +the only way you could satisfy both it and this License would be to +refrain entirely from distribution of the Program. + +If any portion of this section is held invalid or unenforceable under +any particular circumstance, the balance of the section is intended to +apply and the section as a whole is intended to apply in other +circumstances. + +It is not the purpose of this section to induce you to infringe any +patents or other property right claims or to contest validity of any +such claims; this section has the sole purpose of protecting the +integrity of the free software distribution system, which is +implemented by public license practices. Many people have made +generous contributions to the wide range of software distributed +through that system in reliance on consistent application of that +system; it is up to the author/donor to decide if he or she is willing +to distribute software through any other system and a licensee cannot +impose that choice. + +This section is intended to make thoroughly clear what is believed to +be a consequence of the rest of this License. + + 8. If the distribution and/or use of the Program is restricted in +certain countries either by patents or by copyrighted interfaces, the +original copyright holder who places the Program under this License +may add an explicit geographical distribution limitation excluding +those countries, so that distribution is permitted only in or among +countries not thus excluded. In such case, this License incorporates +the limitation as if written in the body of this License. + + 9. The Free Software Foundation may publish revised and/or new versions +of the General Public License from time to time. Such new versions will +be similar in spirit to the present version, but may differ in detail to +address new problems or concerns. + +Each version is given a distinguishing version number. If the Program +specifies a version number of this License which applies to it and "any +later version", you have the option of following the terms and conditions +either of that version or of any later version published by the Free +Software Foundation. If the Program does not specify a version number of +this License, you may choose any version ever published by the Free Software +Foundation. + + 10. If you wish to incorporate parts of the Program into other free +programs whose distribution conditions are different, write to the author +to ask for permission. For software which is copyrighted by the Free +Software Foundation, write to the Free Software Foundation; we sometimes +make exceptions for this. Our decision will be guided by the two goals +of preserving the free status of all derivatives of our free software and +of promoting the sharing and reuse of software generally. + + NO WARRANTY + + 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY +FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN +OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES +PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED +OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF +MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS +TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE +PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, +REPAIR OR CORRECTION. + + 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING +WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR +REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, +INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING +OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED +TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY +YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER +PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE +POSSIBILITY OF SUCH DAMAGES. + + END OF TERMS AND CONDITIONS + + How to Apply These Terms to Your New Programs + + If you develop a new program, and you want it to be of the greatest +possible use to the public, the best way to achieve this is to make it +free software which everyone can redistribute and change under these terms. + + To do so, attach the following notices to the program. It is safest +to attach them to the start of each source file to most effectively +convey the exclusion of warranty; and each file should have at least +the "copyright" line and a pointer to where the full notice is found. + + + Copyright (C) 19yy + + This program is free software; you can redistribute it and/or modify + it under the terms of the GNU General Public License as published by + the Free Software Foundation; either version 2 of the License, or + (at your option) any later version. + + This program is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + GNU General Public License for more details. + + You should have received a copy of the GNU General Public License + along with this program; if not, write to the Free Software + Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA + + +Also add information on how to contact you by electronic and paper mail. + +If the program is interactive, make it output a short notice like this +when it starts in an interactive mode: + + Gnomovision version 69, Copyright (C) 19yy name of author + Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. + This is free software, and you are welcome to redistribute it + under certain conditions; type `show c' for details. + +The hypothetical commands `show w' and `show c' should show the appropriate +parts of the General Public License. Of course, the commands you use may +be called something other than `show w' and `show c'; they could even be +mouse-clicks or menu items--whatever suits your program. + +You should also get your employer (if you work as a programmer) or your +school, if any, to sign a "copyright disclaimer" for the program, if +necessary. Here is a sample; alter the names: + + Yoyodyne, Inc., hereby disclaims all copyright interest in the program + `Gnomovision' (which makes passes at compilers) written by James Hacker. + + , 1 April 1989 + Ty Coon, President of Vice + +This General Public License does not permit incorporating your program into +proprietary programs. If your program is a subroutine library, you may +consider it more useful to permit linking proprietary applications with the +library. If this is what you want to do, use the GNU Library General +Public License instead of this License. diff --git a/contriborbase b/contriborbase new file mode 100644 index 0000000..9b7fd51 --- /dev/null +++ b/contriborbase @@ -0,0 +1 @@ +contribs10 diff --git a/createlinks b/createlinks new file mode 100755 index 0000000..abab69e --- /dev/null +++ b/createlinks @@ -0,0 +1,32 @@ +#!/usr/bin/perl -w +# This script creates the symlinks needed by this RPM +# Specific support exists to create symlinks within e-smith web "panels" +# and for links from named "events" directories into the "actions" directory + +#sub safe_symlink { +# my ($from, $to) = @_; +# use File::Basename; +# use File::Path; +# mkpath(dirname($to)); +# unlink($to); +# symlink($from, $to) or die "Can't create symlink from $from to $to: $!"; +#} + +#sub panel_link +#{ +# my ($function, $panel) = @_; +# +# my $cgibin = "root/etc/e-smith/web/panels/$panel/cgi-bin"; +# +# safe_symlink("../../../functions/$function", +# "$cgibin/$function") +#} + +use esmith::Build::CreateLinks qw(:all); + +#-------------------------------------------------- +# functions for manager panel +#-------------------------------------------------- +my $panel = "manager"; +panel_link("mxbackup", $panel); + diff --git a/root/etc/e-smith/GreenLight.jpg b/root/etc/e-smith/GreenLight.jpg new file mode 100755 index 0000000000000000000000000000000000000000..8a6fef6d5fcc8575bc81570a0916e30b101cb8cc GIT binary patch literal 1058 zcmex=>1BCL~;mBnMJc1;i{s4AKLlIe{2tRuPmBl82cMqS=9%4Twvi;voA$d=LQ9APiDd z3T1=jL3|JZ(I7KGc7WUo;)CQtd=LQ9AUA;gQx4_B{P+I=gCGZk2m=>0qY?v?AS1IN z&0Dr^+rDGxu0w~996fgY z#K}{aE?>EN?fQ+Iw;n!v{N(Ag=PzEq`uOSdm#^Qx|M>Zfk%1ZF9UzI}A3>mhm{?et zS=d4TVPq-?VrD@WRz*WLA;&=W#6n>uqec!9r-=(U9^_Ou4*DRPRCJL`OvU7(>PL{5 zz&;|*LrrA)2<{=cfBxTM;9+J2CL3l!2788|n-9hFeR*5#)E=;V=PrK3939sX4W4kB z=6N&!WOwh|Qfv3E+S6-#lUr}s7Zn+qy3jB6Z~imPzs=CXz{ZVVnRYv%2G1&3W`dKB9f}=Dhldy zii!%1KyB=7?ED-Y{0gE%qM{0nI}gNkudQ4=SZn7D+b zl&YG#hNhN@shPQjrIoXbtDC!rr&n-DXjpheWK?oWYFc_mW>#@YX<2ziWmR)aYg>Cq zXV;|3Q>IRvK4a#rMT?g#UABD1%2k^-Z`rzS`;MKv4jn#n^w{weCr@3veC6u3>o;!R zdidz^lc&#~zj*oT01cClxVqsxsVF&q#k*OSrnFU!` z6%E;h90S=C3x$=88aYIqCNA7~kW<+>=!0ld(M2vX6_bamA3={1WH_31M*7?!=;mwbBOV`Ck`}njbwq9fiP1^Bu%A}$t&-?aT zocu61-Fv$8HT{yEcjcn3+qakb@ABFh<$caCZ|hDU+8+G!pZfmGNmqhAE=ebG z>9cZgNGQ0&BYK#DP1@FGd%&j2zWaA&X KCY8JYzX<@Sh$poG literal 0 HcmV?d00001 diff --git a/root/etc/e-smith/db/configuration/defaults/mxbackup/status b/root/etc/e-smith/db/configuration/defaults/mxbackup/status new file mode 100755 index 0000000..7a68b11 --- /dev/null +++ b/root/etc/e-smith/db/configuration/defaults/mxbackup/status @@ -0,0 +1 @@ +disabled diff --git a/root/etc/e-smith/db/configuration/defaults/mxbackup/type b/root/etc/e-smith/db/configuration/defaults/mxbackup/type new file mode 100755 index 0000000..24e1098 --- /dev/null +++ b/root/etc/e-smith/db/configuration/defaults/mxbackup/type @@ -0,0 +1 @@ +service diff --git a/root/etc/e-smith/locale/bg/etc/e-smith/web/functions/mxbackup b/root/etc/e-smith/locale/bg/etc/e-smith/web/functions/mxbackup new file mode 100644 index 0000000..b5fc2bf --- /dev/null +++ b/root/etc/e-smith/locale/bg/etc/e-smith/web/functions/mxbackup @@ -0,0 +1,122 @@ + + + FORM_TITLE + Конфигурация на функционирането на резервния MX + + + FIRST_PAGE_DESCRIPTION + По подразбиране SME наистина мрази да бъде ретранслатор на пощата. Това означава че, ако някой извън локалната(ите) мера(и) опита да изпрати до SME сървъра поща за домейн, който не е негов, съобщението ще бъде отхвърлено.

Но можете да изберете да бъдете втори пощенски сървър (или MX Backup) за някой друг хост или домейн. В този случай, трябва да зададете домейните или имената на хостовете, които ще резервирате. Трябва също да укажете дали ще приемате поща само за този хост (ще приемате ел. адреси this_guy@bar.foo но няма да приемате this_other@big.bar.foo) или един цял домейн с всичките му под-домейни (пощенски адреси от вида this_guy@*.bar.foo)

Някои интересни неща:

  • Това е само една част от конфигурацията. Това ще работи само ако DNS на домейните, които планирате да резервирате са правилно настроени (по-точно: Вашият сървър трябва да е MX с приоритет по-висок от 'истинския' MX сървър)
  • Можете да изберете между домейн и хост, но запомнете: Не можете да избирате пощенска кутия (лявата част на ел. адрес)

]]> + + + BUTTON_LABEL_CREATE + Създаване на ново правило за MX-Backup + + + BUTTON_LABEL_START_SERVICE + Включи MX Backup + + + SERVICE_RUNNING + MX Backup e включен + + + BUTTON_LABEL_STOP_SERVICE + Изключи MX Backup + + + SERVICE_STOPPED + MX Backup е изключен + + + SUMMARY_ADD_DESC + Таблицата по-долу показва правилото за MX Backup, което ще добавите. Ако Ви харесва, натиснете бутона "Добави". Ако не, натиснете бутона "Cancel". + + + SUMMARY_REMOVE_DESC + Таблицата по-долу показва правилото за MX Backup, което ще премахнете. Ако сте сигурни, натиснете бутона "Премахни". Ако не, натиснете бутона "Cancel". + + + SHOW_MXBACKUP + По-долу ще видите таблица с текущите mx-backup правила настроени на този сървър. Щракнете на връзката "Премахни" за да премахнете съответното правило. + + + NO_MXBACKUP + Няма резервни MX хостове или домейни в системата. + + + CREATE_PAGE_DESCRIPTION + Задайте името на домейна или хоста, който планирате да резервирате. Ако планирате да резервирате цял домейн изберете 'Домейн'. Ако не сте сигурни, това е най-правилния избор. Ако искате само да бъдете резервен MX за един хост (и без други хостове, които могат да са от под-домейни на този хост) тогава изберете 'Хост'.

]]> + + + DOMAIN + Домейн + + + HOST + Хост + + + LABEL_NAME + Интернет име + + + LABEL_HOST_DOMAIN + ХОСТ или ДОМЕЙН + + + Configuration + Конфигурация + + + MX-Backup + Резервна конфигурация MX + + + SAVE + Запис + + + APPLY + Добави + + + NEXT + Следващ + + + CANCEL + Отказ + + + SUCCESS + Промяната в резервната конфигурация на MX беше успешно записана. + + + REMOVE + Премахване + + + ERR_NO_MXBACKUP_RECORD + Не може да се прочете записа за mxbackup от базата му с данни. + + + ERR_UNSUPPORTED_MODE + Неподдържан режим. + + + ERR_BADNAME + Името, което сте дали не изглежда като валидно интернет име. Името трябва да съдържа само големи, малки букви, цифри и тирета '-'. Името трябва да съдържа между 1 и 4 точки. последната дума (tld) може да съдържа само букви и трябва да поне 2 знака дълга, но не повече от 5. + + + ACTION + Действие + + + ENABLED + ВКЛЮЧЕН + + + DISABLED + ИЗКЛЮЧЕН + + diff --git a/root/etc/e-smith/locale/da/etc/e-smith/web/functions/mxbackup b/root/etc/e-smith/locale/da/etc/e-smith/web/functions/mxbackup new file mode 100644 index 0000000..f2a5694 --- /dev/null +++ b/root/etc/e-smith/locale/da/etc/e-smith/web/functions/mxbackup @@ -0,0 +1,122 @@ + + + FORM_TITLE + Configure the MX Backup function + + + FIRST_PAGE_DESCRIPTION + By default, SME really hate to be a mail relay. This means that, if someone outside your local(s) network(s) try to send to your SME box a mail for a domain that is not owned by this SME box, the mail is rejected.

But you can choose to be a second mail server (or MX Backup) for some others hosts or domains. In this case, you have to set the domains or hosts names that you plan to backup. You have also to say if you accept only one precise host ( you accept mail address like this_guy@bar.foo but you won't accept this_other@big.bar.foo) or one complete domain with all subdomain (mail address in form this_guy@*.bar.foo)

Some point of interest :

  • This is only one part of the configuration. This will only work if the DNS of the domains you plan to backup are correctly set (that is : your server should be a MX with a priority higher than the 'real' MX server)
  • You can choose between a domain and a host, but remember : You cannot choose the mailbox ( The left part of the E-Mail address )

]]> + + + BUTTON_LABEL_CREATE + Create a new MX-Backup rule + + + BUTTON_LABEL_START_SERVICE + Enable MX Backup + + + SERVICE_RUNNING + MX Backup is Enabled + + + BUTTON_LABEL_STOP_SERVICE + Disable MX Backup + + + SERVICE_STOPPED + MX Backup is Disabled + + + SUMMARY_ADD_DESC + The following table summarizes the MX Backup rule that you are about to add. If you are satisfied with the rule, click the "Add" button. If you are not, click the "Cancel" button. + + + SUMMARY_REMOVE_DESC + The following table summarizes the MX Backup rule that you are about to remove. If you are sure you want to remove the rule, click the "Remove" button. If not, click the "Cancel" button. + + + SHOW_MXBACKUP + Below you will find a table summarizing the current mx-backup rules installed on this server. Click on the "Remove" link to remove the corresponding rule. + + + NO_MXBACKUP + There are currently no 'MX Backuped' hosts or domains on the system. + + + CREATE_PAGE_DESCRIPTION + Set the domain name or host name you plan to 'MX Backup'. If you plan to backup an entire domain select 'Domain'. If you're unsure, this is the most sensible choice. If you only want to act as a MX Backup for one host (and no others hosts that could be sub-domains of this host) then select 'Host'.

]]> + + + DOMAIN + Domæne + + + HOST + Vært + + + LABEL_NAME + Internet Name + + + LABEL_HOST_DOMAIN + HOST or DOMAIN + + + Configuration + Opsætning + + + MX-Backup + MX Backup Configuration + + + SAVE + Gem + + + APPLY + Tilføj + + + NEXT + Næste + + + CANCEL + Fortryd + + + SUCCESS + Your change to the MX Backup configuration has been successfully saved. + + + REMOVE + Fjern + + + ERR_NO_MXBACKUP_RECORD + Cannot retrieve mxbackup record from the mxbackup database. + + + ERR_UNSUPPORTED_MODE + Ikke understøttet form. + + + ERR_BADNAME + The name you gave don't seems to be a valid Internet Name.The name should only contain uppercase, lowercase, numbers and the '-' digit. The name should contain between 1 and 4 dot. The last word (the tld) can only contains letters and it shoult have a least 2 characters, but not more than 5. + + + ACTION + Aktivitet + + + ENABLED + AKTIVERET + + + DISABLED + DEAKTIVERET + + diff --git a/root/etc/e-smith/locale/de/etc/e-smith/web/functions/mxbackup b/root/etc/e-smith/locale/de/etc/e-smith/web/functions/mxbackup new file mode 100644 index 0000000..40046f3 --- /dev/null +++ b/root/etc/e-smith/locale/de/etc/e-smith/web/functions/mxbackup @@ -0,0 +1,122 @@ + + + FORM_TITLE + Configure the MX Backup function + + + FIRST_PAGE_DESCRIPTION + By default, SME really hate to be a mail relay. This means that, if someone outside your local(s) network(s) try to send to your SME box a mail for a domain that is not owned by this SME box, the mail is rejected.

But you can choose to be a second mail server (or MX Backup) for some others hosts or domains. In this case, you have to set the domains or hosts names that you plan to backup. You have also to say if you accept only one precise host ( you accept mail address like this_guy@bar.foo but you won't accept this_other@big.bar.foo) or one complete domain with all subdomain (mail address in form this_guy@*.bar.foo)

Some point of interest :

  • This is only one part of the configuration. This will only work if the DNS of the domains you plan to backup are correctly set (that is : your server should be a MX with a priority higher than the 'real' MX server)
  • You can choose between a domain and a host, but remember : You cannot choose the mailbox ( The left part of the E-Mail address )

]]> + + + BUTTON_LABEL_CREATE + Create a new MX-Backup rule + + + BUTTON_LABEL_START_SERVICE + Enable MX Backup + + + SERVICE_RUNNING + MX Backup is Enabled + + + BUTTON_LABEL_STOP_SERVICE + Disable MX Backup + + + SERVICE_STOPPED + MX Backup is Disabled + + + SUMMARY_ADD_DESC + The following table summarizes the MX Backup rule that you are about to add. If you are satisfied with the rule, click the "Add" button. If you are not, click the "Cancel" button. + + + SUMMARY_REMOVE_DESC + The following table summarizes the MX Backup rule that you are about to remove. If you are sure you want to remove the rule, click the "Remove" button. If not, click the "Cancel" button. + + + SHOW_MXBACKUP + Below you will find a table summarizing the current mx-backup rules installed on this server. Click on the "Remove" link to remove the corresponding rule. + + + NO_MXBACKUP + There are currently no 'MX Backuped' hosts or domains on the system. + + + CREATE_PAGE_DESCRIPTION + Set the domain name or host name you plan to 'MX Backup'. If you plan to backup an entire domain select 'Domain'. If you're unsure, this is the most sensible choice. If you only want to act as a MX Backup for one host (and no others hosts that could be sub-domains of this host) then select 'Host'.

]]> + + + DOMAIN + Domäne + + + HOST + Host + + + LABEL_NAME + Internet Name + + + LABEL_HOST_DOMAIN + HOST or DOMAIN + + + Configuration + Configuration + + + MX-Backup + MX Backup Configuration + + + SAVE + Speichern + + + APPLY + Hinzufügen + + + NEXT + Weiter + + + CANCEL + Abbrechen + + + SUCCESS + Your change to the MX Backup configuration has been successfully saved. + + + REMOVE + Entfernen + + + ERR_NO_MXBACKUP_RECORD + Cannot retrieve mxbackup record from the mxbackup database. + + + ERR_UNSUPPORTED_MODE + Nicht unterstützter Modus. + + + ERR_BADNAME + The name you gave don't seems to be a valid Internet Name.The name should only contain uppercase, lowercase, numbers and the '-' digit. The name should contain between 1 and 4 dot. The last word (the tld) can only contains letters and it shoult have a least 2 characters, but not more than 5. + + + ACTION + Aktion + + + ENABLED + Eingeschaltet + + + DISABLED + Ausgeschaltet + + diff --git a/root/etc/e-smith/locale/el/etc/e-smith/web/functions/mxbackup b/root/etc/e-smith/locale/el/etc/e-smith/web/functions/mxbackup new file mode 100644 index 0000000..3f38181 --- /dev/null +++ b/root/etc/e-smith/locale/el/etc/e-smith/web/functions/mxbackup @@ -0,0 +1,122 @@ + + + FORM_TITLE + Configure the MX Backup function + + + FIRST_PAGE_DESCRIPTION + By default, SME really hate to be a mail relay. This means that, if someone outside your local(s) network(s) try to send to your SME box a mail for a domain that is not owned by this SME box, the mail is rejected.

But you can choose to be a second mail server (or MX Backup) for some others hosts or domains. In this case, you have to set the domains or hosts names that you plan to backup. You have also to say if you accept only one precise host ( you accept mail address like this_guy@bar.foo but you won't accept this_other@big.bar.foo) or one complete domain with all subdomain (mail address in form this_guy@*.bar.foo)

Some point of interest :

  • This is only one part of the configuration. This will only work if the DNS of the domains you plan to backup are correctly set (that is : your server should be a MX with a priority higher than the 'real' MX server)
  • You can choose between a domain and a host, but remember : You cannot choose the mailbox ( The left part of the E-Mail address )

]]> + + + BUTTON_LABEL_CREATE + Create a new MX-Backup rule + + + BUTTON_LABEL_START_SERVICE + Enable MX Backup + + + SERVICE_RUNNING + MX Backup is Enabled + + + BUTTON_LABEL_STOP_SERVICE + Disable MX Backup + + + SERVICE_STOPPED + MX Backup is Disabled + + + SUMMARY_ADD_DESC + The following table summarizes the MX Backup rule that you are about to add. If you are satisfied with the rule, click the "Add" button. If you are not, click the "Cancel" button. + + + SUMMARY_REMOVE_DESC + The following table summarizes the MX Backup rule that you are about to remove. If you are sure you want to remove the rule, click the "Remove" button. If not, click the "Cancel" button. + + + SHOW_MXBACKUP + Below you will find a table summarizing the current mx-backup rules installed on this server. Click on the "Remove" link to remove the corresponding rule. + + + NO_MXBACKUP + There are currently no 'MX Backuped' hosts or domains on the system. + + + CREATE_PAGE_DESCRIPTION + Set the domain name or host name you plan to 'MX Backup'. If you plan to backup an entire domain select 'Domain'. If you're unsure, this is the most sensible choice. If you only want to act as a MX Backup for one host (and no others hosts that could be sub-domains of this host) then select 'Host'.

]]> + + + DOMAIN + Τομέας + + + HOST + Host + + + LABEL_NAME + Internet Name + + + LABEL_HOST_DOMAIN + HOST or DOMAIN + + + Configuration + Ρύθμιση παραμέτρων συστήματος + + + MX-Backup + MX Backup Configuration + + + SAVE + Αποθήκευση + + + APPLY + Προσθήκη + + + NEXT + Επόμενο + + + CANCEL + Ακύρωση + + + SUCCESS + Your change to the MX Backup configuration has been successfully saved. + + + REMOVE + Διαγραφή + + + ERR_NO_MXBACKUP_RECORD + Cannot retrieve mxbackup record from the mxbackup database. + + + ERR_UNSUPPORTED_MODE + Μη-υποστηριζόμενη κατάσταση λειτουργίας. + + + ERR_BADNAME + The name you gave don't seems to be a valid Internet Name.The name should only contain uppercase, lowercase, numbers and the '-' digit. The name should contain between 1 and 4 dot. The last word (the tld) can only contains letters and it shoult have a least 2 characters, but not more than 5. + + + ACTION + Ενέργεια + + + ENABLED + ENABLED + + + DISABLED + DISABLED + + diff --git a/root/etc/e-smith/locale/en-us/etc/e-smith/web/functions/mxbackup b/root/etc/e-smith/locale/en-us/etc/e-smith/web/functions/mxbackup new file mode 100755 index 0000000..feac003 --- /dev/null +++ b/root/etc/e-smith/locale/en-us/etc/e-smith/web/functions/mxbackup @@ -0,0 +1,182 @@ + + + FORM_TITLE + Configure the MX Backup function + + + FIRST_PAGE_DESCRIPTION + + By default, SME really hate to be a mail relay. This means + that, if someone outside your local(s) network(s) + try to send to your SME box a mail for + a domain that is not owned by this SME box, the mail is + rejected.

+

+ But you can choose to be a second mail server (or MX Backup) + for some others + hosts or domains. In this case, you have to set the + domains or hosts names that you plan to backup. + You have also to say if you accept only one precise host + ( you accept mail address like this_guy@bar.foo + but you won't accept this_other@big.bar.foo) + or one complete domain with all + subdomain (mail address in form this_guy@*.bar.foo) +

+

+ Some point of interest : +

+

+

    +
  • This is only one part of the configuration. This will + only work if the DNS of the domains you plan to backup are + correctly set (that is : your server should be a MX with a + priority higher than the 'real' MX server) +
  • You can choose between a domain and a host, but remember : + You cannot choose the mailbox ( The left part of the E-Mail address ) +
+

+ ]]> + + + + BUTTON_LABEL_CREATE + Create a new MX-Backup rule + + + BUTTON_LABEL_START_SERVICE + Enable MX Backup + + + SERVICE_RUNNING + MX Backup is Enabled + + + BUTTON_LABEL_STOP_SERVICE + Disable MX Backup + + + SERVICE_STOPPED + MX Backup is Disabled + + + SUMMARY_ADD_DESC + The following table summarizes the MX Backup rule + that you are about to add. If you are satisfied with the rule, + click the "Add" button. If you are not, click the + "Cancel" button. + + + + SUMMARY_REMOVE_DESC + The following table summarizes the MX Backup rule + that you are about to remove. If you are sure you want to + remove the rule, click the "Remove" button. If not, + click the "Cancel" button. + + + + SHOW_MXBACKUP + + Below you will find a table summarizing the current + mx-backup rules installed on this server. Click on the + "Remove" link to remove the corresponding rule. + + + + NO_MXBACKUP + There are currently no 'MX Backuped' hosts or domains on the system. + + + CREATE_PAGE_DESCRIPTION + + Set the domain name or host name you plan to 'MX Backup'. + If you plan to backup an entire domain select 'Domain'. + If you're unsure, this is the most sensible choice. + If you only want to act as a MX Backup for one host (and + no others hosts that could be sub-domains of this host) then + select 'Host'. +

+ ]]> + + + + DOMAIN + Domain + + + HOST + Host + + + LABEL_NAME + Internet Name + + + LABEL_HOST_DOMAIN + HOST or DOMAIN + + + Configuration + Configuration + + + MX-Backup + MX Backup Configuration + + + SAVE + Save + + + APPLY + Add + + + NEXT + Next + + + CANCEL + Cancel + + + SUCCESS + Your change to the MX Backup configuration has been + successfully saved. + + + + REMOVE + Remove + + + ERR_NO_MXBACKUP_RECORD + Cannot retrieve mxbackup record from the mxbackup + database. + + + ERR_UNSUPPORTED_MODE + Unsupported mode. + + + ERR_BADNAME + The name you gave don't seems to be a valid Internet + Name.The name should only contain uppercase, lowercase, numbers and the '-' digit. + The name should contain between 1 and 4 dot. The last word (the tld) can only contains letters and + it shoult have a least 2 characters, but not more than 5. + + + ACTION + Action + + + ENABLED + ENABLED + + + DISABLED + DISABLED + + diff --git a/root/etc/e-smith/locale/es/etc/e-smith/web/functions/mxbackup b/root/etc/e-smith/locale/es/etc/e-smith/web/functions/mxbackup new file mode 100644 index 0000000..4a0812f --- /dev/null +++ b/root/etc/e-smith/locale/es/etc/e-smith/web/functions/mxbackup @@ -0,0 +1,122 @@ + + + FORM_TITLE + Configure the MX Backup function + + + FIRST_PAGE_DESCRIPTION + By default, SME really hate to be a mail relay. This means that, if someone outside your local(s) network(s) try to send to your SME box a mail for a domain that is not owned by this SME box, the mail is rejected.

But you can choose to be a second mail server (or MX Backup) for some others hosts or domains. In this case, you have to set the domains or hosts names that you plan to backup. You have also to say if you accept only one precise host ( you accept mail address like this_guy@bar.foo but you won't accept this_other@big.bar.foo) or one complete domain with all subdomain (mail address in form this_guy@*.bar.foo)

Some point of interest :

  • This is only one part of the configuration. This will only work if the DNS of the domains you plan to backup are correctly set (that is : your server should be a MX with a priority higher than the 'real' MX server)
  • You can choose between a domain and a host, but remember : You cannot choose the mailbox ( The left part of the E-Mail address )

]]> + + + BUTTON_LABEL_CREATE + Create a new MX-Backup rule + + + BUTTON_LABEL_START_SERVICE + Enable MX Backup + + + SERVICE_RUNNING + MX Backup is Enabled + + + BUTTON_LABEL_STOP_SERVICE + Disable MX Backup + + + SERVICE_STOPPED + MX Backup is Disabled + + + SUMMARY_ADD_DESC + The following table summarizes the MX Backup rule that you are about to add. If you are satisfied with the rule, click the "Add" button. If you are not, click the "Cancel" button. + + + SUMMARY_REMOVE_DESC + The following table summarizes the MX Backup rule that you are about to remove. If you are sure you want to remove the rule, click the "Remove" button. If not, click the "Cancel" button. + + + SHOW_MXBACKUP + Below you will find a table summarizing the current mx-backup rules installed on this server. Click on the "Remove" link to remove the corresponding rule. + + + NO_MXBACKUP + There are currently no 'MX Backuped' hosts or domains on the system. + + + CREATE_PAGE_DESCRIPTION + Set the domain name or host name you plan to 'MX Backup'. If you plan to backup an entire domain select 'Domain'. If you're unsure, this is the most sensible choice. If you only want to act as a MX Backup for one host (and no others hosts that could be sub-domains of this host) then select 'Host'.

]]> + + + DOMAIN + Dominio + + + HOST + Anfitrión + + + LABEL_NAME + Internet Name + + + LABEL_HOST_DOMAIN + HOST or DOMAIN + + + Configuration + Configuración + + + MX-Backup + MX Backup Configuration + + + SAVE + Guardar + + + APPLY + Agregar + + + NEXT + Siguiente + + + CANCEL + Cancelar + + + SUCCESS + Your change to the MX Backup configuration has been successfully saved. + + + REMOVE + Eliminar + + + ERR_NO_MXBACKUP_RECORD + Cannot retrieve mxbackup record from the mxbackup database. + + + ERR_UNSUPPORTED_MODE + Modo no soportado. + + + ERR_BADNAME + The name you gave don't seems to be a valid Internet Name.The name should only contain uppercase, lowercase, numbers and the '-' digit. The name should contain between 1 and 4 dot. The last word (the tld) can only contains letters and it shoult have a least 2 characters, but not more than 5. + + + ACTION + Acción + + + ENABLED + HABILITADO + + + DISABLED + DESHABILITADO + + diff --git a/root/etc/e-smith/locale/et/etc/e-smith/web/functions/mxbackup b/root/etc/e-smith/locale/et/etc/e-smith/web/functions/mxbackup new file mode 100644 index 0000000..69f12c3 --- /dev/null +++ b/root/etc/e-smith/locale/et/etc/e-smith/web/functions/mxbackup @@ -0,0 +1,122 @@ + + + FORM_TITLE + Configure the MX Backup function + + + FIRST_PAGE_DESCRIPTION + By default, SME really hate to be a mail relay. This means that, if someone outside your local(s) network(s) try to send to your SME box a mail for a domain that is not owned by this SME box, the mail is rejected.

But you can choose to be a second mail server (or MX Backup) for some others hosts or domains. In this case, you have to set the domains or hosts names that you plan to backup. You have also to say if you accept only one precise host ( you accept mail address like this_guy@bar.foo but you won't accept this_other@big.bar.foo) or one complete domain with all subdomain (mail address in form this_guy@*.bar.foo)

Some point of interest :

  • This is only one part of the configuration. This will only work if the DNS of the domains you plan to backup are correctly set (that is : your server should be a MX with a priority higher than the 'real' MX server)
  • You can choose between a domain and a host, but remember : You cannot choose the mailbox ( The left part of the E-Mail address )

]]> + + + BUTTON_LABEL_CREATE + Create a new MX-Backup rule + + + BUTTON_LABEL_START_SERVICE + Enable MX Backup + + + SERVICE_RUNNING + MX Backup is Enabled + + + BUTTON_LABEL_STOP_SERVICE + Disable MX Backup + + + SERVICE_STOPPED + MX Backup is Disabled + + + SUMMARY_ADD_DESC + The following table summarizes the MX Backup rule that you are about to add. If you are satisfied with the rule, click the "Add" button. If you are not, click the "Cancel" button. + + + SUMMARY_REMOVE_DESC + The following table summarizes the MX Backup rule that you are about to remove. If you are sure you want to remove the rule, click the "Remove" button. If not, click the "Cancel" button. + + + SHOW_MXBACKUP + Below you will find a table summarizing the current mx-backup rules installed on this server. Click on the "Remove" link to remove the corresponding rule. + + + NO_MXBACKUP + There are currently no 'MX Backuped' hosts or domains on the system. + + + CREATE_PAGE_DESCRIPTION + Set the domain name or host name you plan to 'MX Backup'. If you plan to backup an entire domain select 'Domain'. If you're unsure, this is the most sensible choice. If you only want to act as a MX Backup for one host (and no others hosts that could be sub-domains of this host) then select 'Host'.

]]> + + + DOMAIN + Domeen + + + HOST + Host + + + LABEL_NAME + Internet Name + + + LABEL_HOST_DOMAIN + HOST or DOMAIN + + + Configuration + Seadistused + + + MX-Backup + MX Backup Configuration + + + SAVE + Salvesta + + + APPLY + Lisa + + + NEXT + Edasi + + + CANCEL + Tühista + + + SUCCESS + Your change to the MX Backup configuration has been successfully saved. + + + REMOVE + Eemalda + + + ERR_NO_MXBACKUP_RECORD + Cannot retrieve mxbackup record from the mxbackup database. + + + ERR_UNSUPPORTED_MODE + Unsupported mode. + + + ERR_BADNAME + The name you gave don't seems to be a valid Internet Name.The name should only contain uppercase, lowercase, numbers and the '-' digit. The name should contain between 1 and 4 dot. The last word (the tld) can only contains letters and it shoult have a least 2 characters, but not more than 5. + + + ACTION + Tegevus + + + ENABLED + ENABLED + + + DISABLED + DISABLED + + diff --git a/root/etc/e-smith/locale/fr/etc/e-smith/web/functions/mxbackup b/root/etc/e-smith/locale/fr/etc/e-smith/web/functions/mxbackup new file mode 100755 index 0000000..19d307c --- /dev/null +++ b/root/etc/e-smith/locale/fr/etc/e-smith/web/functions/mxbackup @@ -0,0 +1,122 @@ + + + FORM_TITLE + Configurer la fonctionnalité MX Backup + + + FIRST_PAGE_DESCRIPTION + Par défaut, SME déteste vraiment être un relais de messagerie. Cela signifie que, si quelqu'un en dehors de votre (vos) réseau(x) local (locaux) essaie d'envoyer à votre boîte SME un courriel pour un domaine qui n'appartient pas à cette boîte SME, le courriel est rejeté.

Mais vous pouvez choisir d'être un deuxième serveur de messagerie (ou MX Backup) pour certains autres hôtes ou domaines. Dans ce cas, vous devez définir les noms de domaines ou d'hôtes que vous prévoyez de sauvegarder. Vous devez également dire si vous n'acceptez qu'un seul hôte précis (vous acceptez une adresse courriel comme this_guy@bar.foo mais vous n'accepterez pas this_other@big.bar.foo ) ou un domaine complet avec tous les sous-domaines (adresse courriel au format this_guy@*.bar.foo. )

Un point d'intérêt :

  • ce n'est qu'une partie de la configuration. Cela ne fonctionnera que si les DNS des domaines que vous prévoyez de sauvegarder sont correctement définis (c'est-à-dire que votre serveur doit être un MX avec une priorité plus élevée que le « vrai » serveur MX).
  • Vous pouvez choisir entre un domaine et un hôte, mais rappelez-vous : vous ne pouvez pas choisir la boîte aux lettres (la partie gauche de l'adresse de courriel)

]]> + + + BUTTON_LABEL_CREATE + Créer une nouvelle règle MX-Backup + + + BUTTON_LABEL_START_SERVICE + Activer MX-Backup + + + SERVICE_RUNNING + MX-Backup est activé + + + BUTTON_LABEL_STOP_SERVICE + Désactiver MX-Backup + + + SERVICE_STOPPED + MX-Backup est désactivé + + + SUMMARY_ADD_DESC + Le tableau suivant résume la règle de sauvegarde MX que vous êtes sur le point d'ajouter. Si vous êtes satisfait de la règle, cliquez sur le bouton "Ajouter". Si ce n'est pas le cas, cliquez sur le bouton "Annuler". + + + SUMMARY_REMOVE_DESC + Le tableau suivant résume la règle de sauvegarde MX que vous êtes sur le point de supprimer. Si vous êtes sûr de vouloir supprimer la règle, cliquez sur le bouton "Supprimer". Sinon, cliquez sur le bouton "Annuler". + + + SHOW_MXBACKUP + Vous trouverez ci-dessous un tableau récapitulant les règles mx-backup actuelles installées sur ce serveur. Cliquez sur le bouton "Supprimer" pour supprimer la règle correspondante. + + + NO_MXBACKUP + Il n'y a actuellement aucun hôte ou domaine de « MX Backup » sur ce système. + + + CREATE_PAGE_DESCRIPTION + Définissez le nom de domaine ou le nom d'hôte que vous prévoyez en « Sauvegarde MX ». Si vous prévoyez de sauvegarder un domaine entier, sélectionnez « Domaine ». Si vous n'êtes pas sûr, c'est le choix le plus judicieux. Si vous souhaitez uniquement agir en tant que sauvegarde MX pour un hôte (et pour aucun autre hôte pouvant être des sous-domaines de cet hôte), sélectionnez « Hôte ».

]]> + + + DOMAIN + Domaine + + + HOST + Hôte + + + LABEL_NAME + Nom internet + + + LABEL_HOST_DOMAIN + HÔTE ou DOMAINE + + + Configuration + Configuration + + + MX-Backup + Configuration MX Backup + + + SAVE + Enregistrer + + + APPLY + Ajouter + + + NEXT + Suivant + + + CANCEL + Annuler + + + SUCCESS + Vos modifications de configuration du MX Backup ont été correctement enregistrées. + + + REMOVE + Supprimer + + + ERR_NO_MXBACKUP_RECORD + Impossible de récupérer l'enregistrement mxbackup de la base de données mxbackup. + + + ERR_UNSUPPORTED_MODE + Mode non pris en charge. + + + ERR_BADNAME + Le nom que vous avez donné ne semble pas être un nom Internet valide. Le nom ne doit contenir que des majuscules, des minuscules, des chiffres et le caractère «-». Le nom doit contenir entre 1 et 4 points. Le dernier mot (le tld) ne peut contenir que des lettres et il ne doit pas comporter moins de 2 caractères, mais pas plus de 5. + + + ACTION + Action + + + ENABLED + Activé + + + DISABLED + Désactivé + + diff --git a/root/etc/e-smith/locale/he/etc/e-smith/web/functions/mxbackup b/root/etc/e-smith/locale/he/etc/e-smith/web/functions/mxbackup new file mode 100644 index 0000000..a7346f3 --- /dev/null +++ b/root/etc/e-smith/locale/he/etc/e-smith/web/functions/mxbackup @@ -0,0 +1,122 @@ + + + FORM_TITLE + Configure the MX Backup function + + + FIRST_PAGE_DESCRIPTION + By default, SME really hate to be a mail relay. This means that, if someone outside your local(s) network(s) try to send to your SME box a mail for a domain that is not owned by this SME box, the mail is rejected.

But you can choose to be a second mail server (or MX Backup) for some others hosts or domains. In this case, you have to set the domains or hosts names that you plan to backup. You have also to say if you accept only one precise host ( you accept mail address like this_guy@bar.foo but you won't accept this_other@big.bar.foo) or one complete domain with all subdomain (mail address in form this_guy@*.bar.foo)

Some point of interest :

  • This is only one part of the configuration. This will only work if the DNS of the domains you plan to backup are correctly set (that is : your server should be a MX with a priority higher than the 'real' MX server)
  • You can choose between a domain and a host, but remember : You cannot choose the mailbox ( The left part of the E-Mail address )

]]> + + + BUTTON_LABEL_CREATE + Create a new MX-Backup rule + + + BUTTON_LABEL_START_SERVICE + Enable MX Backup + + + SERVICE_RUNNING + MX Backup is Enabled + + + BUTTON_LABEL_STOP_SERVICE + Disable MX Backup + + + SERVICE_STOPPED + MX Backup is Disabled + + + SUMMARY_ADD_DESC + The following table summarizes the MX Backup rule that you are about to add. If you are satisfied with the rule, click the "Add" button. If you are not, click the "Cancel" button. + + + SUMMARY_REMOVE_DESC + The following table summarizes the MX Backup rule that you are about to remove. If you are sure you want to remove the rule, click the "Remove" button. If not, click the "Cancel" button. + + + SHOW_MXBACKUP + Below you will find a table summarizing the current mx-backup rules installed on this server. Click on the "Remove" link to remove the corresponding rule. + + + NO_MXBACKUP + There are currently no 'MX Backuped' hosts or domains on the system. + + + CREATE_PAGE_DESCRIPTION + Set the domain name or host name you plan to 'MX Backup'. If you plan to backup an entire domain select 'Domain'. If you're unsure, this is the most sensible choice. If you only want to act as a MX Backup for one host (and no others hosts that could be sub-domains of this host) then select 'Host'.

]]> + + + DOMAIN + Domain + + + HOST + Host + + + LABEL_NAME + Internet Name + + + LABEL_HOST_DOMAIN + HOST or DOMAIN + + + Configuration + קונפיגורציה + + + MX-Backup + MX Backup Configuration + + + SAVE + שמור + + + APPLY + הוסף + + + NEXT + Next + + + CANCEL + Cancel + + + SUCCESS + Your change to the MX Backup configuration has been successfully saved. + + + REMOVE + הסרה + + + ERR_NO_MXBACKUP_RECORD + Cannot retrieve mxbackup record from the mxbackup database. + + + ERR_UNSUPPORTED_MODE + Unsupported mode. + + + ERR_BADNAME + The name you gave don't seems to be a valid Internet Name.The name should only contain uppercase, lowercase, numbers and the '-' digit. The name should contain between 1 and 4 dot. The last word (the tld) can only contains letters and it shoult have a least 2 characters, but not more than 5. + + + ACTION + פעולה + + + ENABLED + ENABLED + + + DISABLED + DISABLED + + diff --git a/root/etc/e-smith/locale/hu/etc/e-smith/web/functions/mxbackup b/root/etc/e-smith/locale/hu/etc/e-smith/web/functions/mxbackup new file mode 100644 index 0000000..28e919a --- /dev/null +++ b/root/etc/e-smith/locale/hu/etc/e-smith/web/functions/mxbackup @@ -0,0 +1,122 @@ + + + FORM_TITLE + Configure the MX Backup function + + + FIRST_PAGE_DESCRIPTION + By default, SME really hate to be a mail relay. This means that, if someone outside your local(s) network(s) try to send to your SME box a mail for a domain that is not owned by this SME box, the mail is rejected.

But you can choose to be a second mail server (or MX Backup) for some others hosts or domains. In this case, you have to set the domains or hosts names that you plan to backup. You have also to say if you accept only one precise host ( you accept mail address like this_guy@bar.foo but you won't accept this_other@big.bar.foo) or one complete domain with all subdomain (mail address in form this_guy@*.bar.foo)

Some point of interest :

  • This is only one part of the configuration. This will only work if the DNS of the domains you plan to backup are correctly set (that is : your server should be a MX with a priority higher than the 'real' MX server)
  • You can choose between a domain and a host, but remember : You cannot choose the mailbox ( The left part of the E-Mail address )

]]> + + + BUTTON_LABEL_CREATE + Create a new MX-Backup rule + + + BUTTON_LABEL_START_SERVICE + Enable MX Backup + + + SERVICE_RUNNING + MX Backup is Enabled + + + BUTTON_LABEL_STOP_SERVICE + Disable MX Backup + + + SERVICE_STOPPED + MX Backup is Disabled + + + SUMMARY_ADD_DESC + The following table summarizes the MX Backup rule that you are about to add. If you are satisfied with the rule, click the "Add" button. If you are not, click the "Cancel" button. + + + SUMMARY_REMOVE_DESC + The following table summarizes the MX Backup rule that you are about to remove. If you are sure you want to remove the rule, click the "Remove" button. If not, click the "Cancel" button. + + + SHOW_MXBACKUP + Below you will find a table summarizing the current mx-backup rules installed on this server. Click on the "Remove" link to remove the corresponding rule. + + + NO_MXBACKUP + There are currently no 'MX Backuped' hosts or domains on the system. + + + CREATE_PAGE_DESCRIPTION + Set the domain name or host name you plan to 'MX Backup'. If you plan to backup an entire domain select 'Domain'. If you're unsure, this is the most sensible choice. If you only want to act as a MX Backup for one host (and no others hosts that could be sub-domains of this host) then select 'Host'.

]]> + + + DOMAIN + Domén + + + HOST + Gép + + + LABEL_NAME + Internet Name + + + LABEL_HOST_DOMAIN + HOST or DOMAIN + + + Configuration + Konfiguráció + + + MX-Backup + MX Backup Configuration + + + SAVE + Mentés + + + APPLY + Hozzáad + + + NEXT + Következő + + + CANCEL + Mégsem + + + SUCCESS + Your change to the MX Backup configuration has been successfully saved. + + + REMOVE + Eltávolít + + + ERR_NO_MXBACKUP_RECORD + Cannot retrieve mxbackup record from the mxbackup database. + + + ERR_UNSUPPORTED_MODE + Nem támogatott mód. + + + ERR_BADNAME + The name you gave don't seems to be a valid Internet Name.The name should only contain uppercase, lowercase, numbers and the '-' digit. The name should contain between 1 and 4 dot. The last word (the tld) can only contains letters and it shoult have a least 2 characters, but not more than 5. + + + ACTION + Művelet + + + ENABLED + ENABLED + + + DISABLED + DISABLED + + diff --git a/root/etc/e-smith/locale/id/etc/e-smith/web/functions/mxbackup b/root/etc/e-smith/locale/id/etc/e-smith/web/functions/mxbackup new file mode 100644 index 0000000..3d584e7 --- /dev/null +++ b/root/etc/e-smith/locale/id/etc/e-smith/web/functions/mxbackup @@ -0,0 +1,122 @@ + + + FORM_TITLE + Configure the MX Backup function + + + FIRST_PAGE_DESCRIPTION + By default, SME really hate to be a mail relay. This means that, if someone outside your local(s) network(s) try to send to your SME box a mail for a domain that is not owned by this SME box, the mail is rejected.

But you can choose to be a second mail server (or MX Backup) for some others hosts or domains. In this case, you have to set the domains or hosts names that you plan to backup. You have also to say if you accept only one precise host ( you accept mail address like this_guy@bar.foo but you won't accept this_other@big.bar.foo) or one complete domain with all subdomain (mail address in form this_guy@*.bar.foo)

Some point of interest :

  • This is only one part of the configuration. This will only work if the DNS of the domains you plan to backup are correctly set (that is : your server should be a MX with a priority higher than the 'real' MX server)
  • You can choose between a domain and a host, but remember : You cannot choose the mailbox ( The left part of the E-Mail address )

]]> + + + BUTTON_LABEL_CREATE + Create a new MX-Backup rule + + + BUTTON_LABEL_START_SERVICE + Enable MX Backup + + + SERVICE_RUNNING + MX Backup is Enabled + + + BUTTON_LABEL_STOP_SERVICE + Disable MX Backup + + + SERVICE_STOPPED + MX Backup is Disabled + + + SUMMARY_ADD_DESC + The following table summarizes the MX Backup rule that you are about to add. If you are satisfied with the rule, click the "Add" button. If you are not, click the "Cancel" button. + + + SUMMARY_REMOVE_DESC + The following table summarizes the MX Backup rule that you are about to remove. If you are sure you want to remove the rule, click the "Remove" button. If not, click the "Cancel" button. + + + SHOW_MXBACKUP + Below you will find a table summarizing the current mx-backup rules installed on this server. Click on the "Remove" link to remove the corresponding rule. + + + NO_MXBACKUP + There are currently no 'MX Backuped' hosts or domains on the system. + + + CREATE_PAGE_DESCRIPTION + Set the domain name or host name you plan to 'MX Backup'. If you plan to backup an entire domain select 'Domain'. If you're unsure, this is the most sensible choice. If you only want to act as a MX Backup for one host (and no others hosts that could be sub-domains of this host) then select 'Host'.

]]> + + + DOMAIN + Domain + + + HOST + Host + + + LABEL_NAME + Internet Name + + + LABEL_HOST_DOMAIN + HOST or DOMAIN + + + Configuration + Konfigurasi + + + MX-Backup + MX Backup Configuration + + + SAVE + Simpan + + + APPLY + Tambah + + + NEXT + Selanjutnya + + + CANCEL + Batal + + + SUCCESS + Your change to the MX Backup configuration has been successfully saved. + + + REMOVE + Hapus + + + ERR_NO_MXBACKUP_RECORD + Cannot retrieve mxbackup record from the mxbackup database. + + + ERR_UNSUPPORTED_MODE + Mode tidak didukung. + + + ERR_BADNAME + The name you gave don't seems to be a valid Internet Name.The name should only contain uppercase, lowercase, numbers and the '-' digit. The name should contain between 1 and 4 dot. The last word (the tld) can only contains letters and it shoult have a least 2 characters, but not more than 5. + + + ACTION + Aksi + + + ENABLED + ENABLED + + + DISABLED + DISABLED + + diff --git a/root/etc/e-smith/locale/it/etc/e-smith/web/functions/mxbackup b/root/etc/e-smith/locale/it/etc/e-smith/web/functions/mxbackup new file mode 100644 index 0000000..f71e8d6 --- /dev/null +++ b/root/etc/e-smith/locale/it/etc/e-smith/web/functions/mxbackup @@ -0,0 +1,122 @@ + + + FORM_TITLE + Configurare la funzione MX Backup + + + FIRST_PAGE_DESCRIPTION + Per default, SME non è configurato per agire da mail relay. Ciò significa che, se dall'esterno della(e) vostra(e) rete(i) locale(i) si tenta di inviare al vostro SME server una mail per un dominio che non risiede sul server, la mail viene rifiutata.

Ma si può scegliere di configurarlo come mail server secondario (o MX Backup) per altri host/domini. In questo caso, si devono impostare i nomi host o di dominio di cui si prevede di fare il backup. Si deve anche scegliere se accettare un host ben preciso (si accettano indirizzi come this_guy@bar.foo ma non si accetta this_other@big.bar.foo) o un dominio completo con tutti i sottodomini (indirizzi nella forma this_guy@*.bar.foo)

Alcuni chiarimenti:

  • questa è solo una parte della configurazione. Questo funzionerà solo se il DNS dei domini di cui si vuol fare il backup sono impostati correttamente (vale a dire: il server deve essere un MX con una priorità più bassa (es.: MX(20)) server MX 'reale' (es. MX(10)) - priorità più bassa = numero più alto)
  • Si può scegliere tra un dominio e un host, ma ricordare che non si può scegliere una casella di posta (La parte di sinistra dell'indirizzo di posta)

]]> + + + BUTTON_LABEL_CREATE + Creare una nuova regola MX-Backup + + + BUTTON_LABEL_START_SERVICE + Abilita MX Backup + + + SERVICE_RUNNING + MX Backup è abilitato + + + BUTTON_LABEL_STOP_SERVICE + Disabilita MX Backup + + + SERVICE_STOPPED + MX Backup è disabilitato + + + SUMMARY_ADD_DESC + La tabella seguente riassume le regole MX Backup che si stanno per aggiungere. Per accettare la regola, fare click su "Aggiungi" . Per non accettare, fare click su "Annulla" . + + + SUMMARY_REMOVE_DESC + La tabella seguente riassume le regole MX Backup che si stanno per eliminare. Per eliminare la regola, fare click su "Rimuovi" . Per non accettare, fare click su "Annulla" . + + + SHOW_MXBACKUP + Qui sotto si trova una tabella che riassume le regole di mx-backup correntemente installate sul server. Fare click su "Rimuovi" per eliminare la regola correspondente. + + + NO_MXBACKUP + Attualmente non è configurato nessun host o dominio 'MX Backuped' sul sistema. + + + CREATE_PAGE_DESCRIPTION + Impostare in nome dominio o host a cui si vuole collegare un 'MX Backup'. Se si intende fare il backup di un intero dominio selezionare 'Domain'. Se non siete sicuri questa è la scelta più delicata. Se volete agire come MX Backup per un solo host (e per nessun altro host che possa essere un sotto-dominio di questo host) allora selezionare 'Host'.

]]> + + + DOMAIN + Dominio + + + HOST + Host + + + LABEL_NAME + Nome Internet + + + LABEL_HOST_DOMAIN + HOST o DOMAIN + + + Configuration + Configurazione + + + MX-Backup + Configurazione MX Backup + + + SAVE + Salva + + + APPLY + Aggiungi + + + NEXT + Avanti + + + CANCEL + Annulla + + + SUCCESS + La modifica alla configurazione di MX Backup è stata salvata. + + + REMOVE + Rimuovi + + + ERR_NO_MXBACKUP_RECORD + Impossibile trovare il record mxbackup nel database corrispondente. + + + ERR_UNSUPPORTED_MODE + Modo non supportato. + + + ERR_BADNAME + Il nome inserito non è un Nome Internet valido. Il nome può contenere solo lettere maiuscole/minuscole, numeri e il carattere '-'. Il nome può contenere tra 1 e 4 punti. L'ultima parola (il tld) può solo contenere lettere e deve avere almeno 2 caratteri ma non più di 5. + + + ACTION + Azione + + + ENABLED + ABILITATO + + + DISABLED + DISABILITATO + + diff --git a/root/etc/e-smith/locale/ja/etc/e-smith/web/functions/mxbackup b/root/etc/e-smith/locale/ja/etc/e-smith/web/functions/mxbackup new file mode 100644 index 0000000..56d7cbb --- /dev/null +++ b/root/etc/e-smith/locale/ja/etc/e-smith/web/functions/mxbackup @@ -0,0 +1,122 @@ + + + FORM_TITLE + Configure the MX Backup function + + + FIRST_PAGE_DESCRIPTION + By default, SME really hate to be a mail relay. This means that, if someone outside your local(s) network(s) try to send to your SME box a mail for a domain that is not owned by this SME box, the mail is rejected.

But you can choose to be a second mail server (or MX Backup) for some others hosts or domains. In this case, you have to set the domains or hosts names that you plan to backup. You have also to say if you accept only one precise host ( you accept mail address like this_guy@bar.foo but you won't accept this_other@big.bar.foo) or one complete domain with all subdomain (mail address in form this_guy@*.bar.foo)

Some point of interest :

  • This is only one part of the configuration. This will only work if the DNS of the domains you plan to backup are correctly set (that is : your server should be a MX with a priority higher than the 'real' MX server)
  • You can choose between a domain and a host, but remember : You cannot choose the mailbox ( The left part of the E-Mail address )

]]> + + + BUTTON_LABEL_CREATE + Create a new MX-Backup rule + + + BUTTON_LABEL_START_SERVICE + Enable MX Backup + + + SERVICE_RUNNING + MX Backup is Enabled + + + BUTTON_LABEL_STOP_SERVICE + Disable MX Backup + + + SERVICE_STOPPED + MX Backup is Disabled + + + SUMMARY_ADD_DESC + The following table summarizes the MX Backup rule that you are about to add. If you are satisfied with the rule, click the "Add" button. If you are not, click the "Cancel" button. + + + SUMMARY_REMOVE_DESC + The following table summarizes the MX Backup rule that you are about to remove. If you are sure you want to remove the rule, click the "Remove" button. If not, click the "Cancel" button. + + + SHOW_MXBACKUP + Below you will find a table summarizing the current mx-backup rules installed on this server. Click on the "Remove" link to remove the corresponding rule. + + + NO_MXBACKUP + There are currently no 'MX Backuped' hosts or domains on the system. + + + CREATE_PAGE_DESCRIPTION + Set the domain name or host name you plan to 'MX Backup'. If you plan to backup an entire domain select 'Domain'. If you're unsure, this is the most sensible choice. If you only want to act as a MX Backup for one host (and no others hosts that could be sub-domains of this host) then select 'Host'.

]]> + + + DOMAIN + ドメイン + + + HOST + ホスト + + + LABEL_NAME + Internet Name + + + LABEL_HOST_DOMAIN + HOST or DOMAIN + + + Configuration + 設定 + + + MX-Backup + MX Backup Configuration + + + SAVE + 保存 + + + APPLY + 追加 + + + NEXT + 次へ + + + CANCEL + 取消し + + + SUCCESS + Your change to the MX Backup configuration has been successfully saved. + + + REMOVE + 削除 + + + ERR_NO_MXBACKUP_RECORD + Cannot retrieve mxbackup record from the mxbackup database. + + + ERR_UNSUPPORTED_MODE + Unsupported mode. + + + ERR_BADNAME + The name you gave don't seems to be a valid Internet Name.The name should only contain uppercase, lowercase, numbers and the '-' digit. The name should contain between 1 and 4 dot. The last word (the tld) can only contains letters and it shoult have a least 2 characters, but not more than 5. + + + ACTION + Action + + + ENABLED + ENABLED + + + DISABLED + DISABLED + + diff --git a/root/etc/e-smith/locale/nb/etc/e-smith/web/functions/mxbackup b/root/etc/e-smith/locale/nb/etc/e-smith/web/functions/mxbackup new file mode 100644 index 0000000..ab9f3bf --- /dev/null +++ b/root/etc/e-smith/locale/nb/etc/e-smith/web/functions/mxbackup @@ -0,0 +1,122 @@ + + + FORM_TITLE + Configure the MX Backup function + + + FIRST_PAGE_DESCRIPTION + By default, SME really hate to be a mail relay. This means that, if someone outside your local(s) network(s) try to send to your SME box a mail for a domain that is not owned by this SME box, the mail is rejected.

But you can choose to be a second mail server (or MX Backup) for some others hosts or domains. In this case, you have to set the domains or hosts names that you plan to backup. You have also to say if you accept only one precise host ( you accept mail address like this_guy@bar.foo but you won't accept this_other@big.bar.foo) or one complete domain with all subdomain (mail address in form this_guy@*.bar.foo)

Some point of interest :

  • This is only one part of the configuration. This will only work if the DNS of the domains you plan to backup are correctly set (that is : your server should be a MX with a priority higher than the 'real' MX server)
  • You can choose between a domain and a host, but remember : You cannot choose the mailbox ( The left part of the E-Mail address )

]]> + + + BUTTON_LABEL_CREATE + Create a new MX-Backup rule + + + BUTTON_LABEL_START_SERVICE + Enable MX Backup + + + SERVICE_RUNNING + MX Backup is Enabled + + + BUTTON_LABEL_STOP_SERVICE + Disable MX Backup + + + SERVICE_STOPPED + MX Backup is Disabled + + + SUMMARY_ADD_DESC + The following table summarizes the MX Backup rule that you are about to add. If you are satisfied with the rule, click the "Add" button. If you are not, click the "Cancel" button. + + + SUMMARY_REMOVE_DESC + The following table summarizes the MX Backup rule that you are about to remove. If you are sure you want to remove the rule, click the "Remove" button. If not, click the "Cancel" button. + + + SHOW_MXBACKUP + Below you will find a table summarizing the current mx-backup rules installed on this server. Click on the "Remove" link to remove the corresponding rule. + + + NO_MXBACKUP + There are currently no 'MX Backuped' hosts or domains on the system. + + + CREATE_PAGE_DESCRIPTION + Set the domain name or host name you plan to 'MX Backup'. If you plan to backup an entire domain select 'Domain'. If you're unsure, this is the most sensible choice. If you only want to act as a MX Backup for one host (and no others hosts that could be sub-domains of this host) then select 'Host'.

]]> + + + DOMAIN + Domene + + + HOST + Vert + + + LABEL_NAME + Internet Name + + + LABEL_HOST_DOMAIN + HOST or DOMAIN + + + Configuration + Oppsett + + + MX-Backup + MX Backup Configuration + + + SAVE + Lagre + + + APPLY + Legg til + + + NEXT + Neste + + + CANCEL + Avbryt + + + SUCCESS + Your change to the MX Backup configuration has been successfully saved. + + + REMOVE + Fjern + + + ERR_NO_MXBACKUP_RECORD + Cannot retrieve mxbackup record from the mxbackup database. + + + ERR_UNSUPPORTED_MODE + Modus ikke støttet. + + + ERR_BADNAME + The name you gave don't seems to be a valid Internet Name.The name should only contain uppercase, lowercase, numbers and the '-' digit. The name should contain between 1 and 4 dot. The last word (the tld) can only contains letters and it shoult have a least 2 characters, but not more than 5. + + + ACTION + Handling + + + ENABLED + ENABLED + + + DISABLED + DISABLED + + diff --git a/root/etc/e-smith/locale/nl/etc/e-smith/web/functions/mxbackup b/root/etc/e-smith/locale/nl/etc/e-smith/web/functions/mxbackup new file mode 100644 index 0000000..1589a53 --- /dev/null +++ b/root/etc/e-smith/locale/nl/etc/e-smith/web/functions/mxbackup @@ -0,0 +1,122 @@ + + + FORM_TITLE + Configure the MX Backup function + + + FIRST_PAGE_DESCRIPTION + By default, SME really hate to be a mail relay. This means that, if someone outside your local(s) network(s) try to send to your SME box a mail for a domain that is not owned by this SME box, the mail is rejected.

But you can choose to be a second mail server (or MX Backup) for some others hosts or domains. In this case, you have to set the domains or hosts names that you plan to backup. You have also to say if you accept only one precise host ( you accept mail address like this_guy@bar.foo but you won't accept this_other@big.bar.foo) or one complete domain with all subdomain (mail address in form this_guy@*.bar.foo)

Some point of interest :

  • This is only one part of the configuration. This will only work if the DNS of the domains you plan to backup are correctly set (that is : your server should be a MX with a priority higher than the 'real' MX server)
  • You can choose between a domain and a host, but remember : You cannot choose the mailbox ( The left part of the E-Mail address )

]]> + + + BUTTON_LABEL_CREATE + Create a new MX-Backup rule + + + BUTTON_LABEL_START_SERVICE + Enable MX Backup + + + SERVICE_RUNNING + MX Backup is Enabled + + + BUTTON_LABEL_STOP_SERVICE + Disable MX Backup + + + SERVICE_STOPPED + MX Backup is Disabled + + + SUMMARY_ADD_DESC + The following table summarizes the MX Backup rule that you are about to add. If you are satisfied with the rule, click the "Add" button. If you are not, click the "Cancel" button. + + + SUMMARY_REMOVE_DESC + The following table summarizes the MX Backup rule that you are about to remove. If you are sure you want to remove the rule, click the "Remove" button. If not, click the "Cancel" button. + + + SHOW_MXBACKUP + Below you will find a table summarizing the current mx-backup rules installed on this server. Click on the "Remove" link to remove the corresponding rule. + + + NO_MXBACKUP + There are currently no 'MX Backuped' hosts or domains on the system. + + + CREATE_PAGE_DESCRIPTION + Set the domain name or host name you plan to 'MX Backup'. If you plan to backup an entire domain select 'Domain'. If you're unsure, this is the most sensible choice. If you only want to act as a MX Backup for one host (and no others hosts that could be sub-domains of this host) then select 'Host'.

]]> + + + DOMAIN + Domein + + + HOST + Host + + + LABEL_NAME + Internet Name + + + LABEL_HOST_DOMAIN + HOST or DOMAIN + + + Configuration + Configuratie + + + MX-Backup + MX Backup Configuration + + + SAVE + Opslaan + + + APPLY + Toevoegen + + + NEXT + Volgende + + + CANCEL + Annuleer + + + SUCCESS + Your change to the MX Backup configuration has been successfully saved. + + + REMOVE + Verwijderen + + + ERR_NO_MXBACKUP_RECORD + Cannot retrieve mxbackup record from the mxbackup database. + + + ERR_UNSUPPORTED_MODE + Niet ondersteunde modus. + + + ERR_BADNAME + The name you gave don't seems to be a valid Internet Name.The name should only contain uppercase, lowercase, numbers and the '-' digit. The name should contain between 1 and 4 dot. The last word (the tld) can only contains letters and it shoult have a least 2 characters, but not more than 5. + + + ACTION + Actie + + + ENABLED + AAN + + + DISABLED + UIT + + diff --git a/root/etc/e-smith/locale/pl/etc/e-smith/web/functions/mxbackup b/root/etc/e-smith/locale/pl/etc/e-smith/web/functions/mxbackup new file mode 100644 index 0000000..6c59c26 --- /dev/null +++ b/root/etc/e-smith/locale/pl/etc/e-smith/web/functions/mxbackup @@ -0,0 +1,122 @@ + + + FORM_TITLE + Configure the MX Backup function + + + FIRST_PAGE_DESCRIPTION + By default, SME really hate to be a mail relay. This means that, if someone outside your local(s) network(s) try to send to your SME box a mail for a domain that is not owned by this SME box, the mail is rejected.

But you can choose to be a second mail server (or MX Backup) for some others hosts or domains. In this case, you have to set the domains or hosts names that you plan to backup. You have also to say if you accept only one precise host ( you accept mail address like this_guy@bar.foo but you won't accept this_other@big.bar.foo) or one complete domain with all subdomain (mail address in form this_guy@*.bar.foo)

Some point of interest :

  • This is only one part of the configuration. This will only work if the DNS of the domains you plan to backup are correctly set (that is : your server should be a MX with a priority higher than the 'real' MX server)
  • You can choose between a domain and a host, but remember : You cannot choose the mailbox ( The left part of the E-Mail address )

]]> + + + BUTTON_LABEL_CREATE + Create a new MX-Backup rule + + + BUTTON_LABEL_START_SERVICE + Enable MX Backup + + + SERVICE_RUNNING + MX Backup is Enabled + + + BUTTON_LABEL_STOP_SERVICE + Disable MX Backup + + + SERVICE_STOPPED + MX Backup is Disabled + + + SUMMARY_ADD_DESC + The following table summarizes the MX Backup rule that you are about to add. If you are satisfied with the rule, click the "Add" button. If you are not, click the "Cancel" button. + + + SUMMARY_REMOVE_DESC + The following table summarizes the MX Backup rule that you are about to remove. If you are sure you want to remove the rule, click the "Remove" button. If not, click the "Cancel" button. + + + SHOW_MXBACKUP + Below you will find a table summarizing the current mx-backup rules installed on this server. Click on the "Remove" link to remove the corresponding rule. + + + NO_MXBACKUP + There are currently no 'MX Backuped' hosts or domains on the system. + + + CREATE_PAGE_DESCRIPTION + Set the domain name or host name you plan to 'MX Backup'. If you plan to backup an entire domain select 'Domain'. If you're unsure, this is the most sensible choice. If you only want to act as a MX Backup for one host (and no others hosts that could be sub-domains of this host) then select 'Host'.

]]> + + + DOMAIN + Domena + + + HOST + Komputer + + + LABEL_NAME + Internet Name + + + LABEL_HOST_DOMAIN + HOST or DOMAIN + + + Configuration + Konfiguracja + + + MX-Backup + MX Backup Configuration + + + SAVE + Zapisz + + + APPLY + Dodaj + + + NEXT + Dalej + + + CANCEL + Anuluj + + + SUCCESS + Your change to the MX Backup configuration has been successfully saved. + + + REMOVE + Usuń + + + ERR_NO_MXBACKUP_RECORD + Cannot retrieve mxbackup record from the mxbackup database. + + + ERR_UNSUPPORTED_MODE + Unsupported mode. + + + ERR_BADNAME + The name you gave don't seems to be a valid Internet Name.The name should only contain uppercase, lowercase, numbers and the '-' digit. The name should contain between 1 and 4 dot. The last word (the tld) can only contains letters and it shoult have a least 2 characters, but not more than 5. + + + ACTION + Action + + + ENABLED + ENABLED + + + DISABLED + DISABLED + + diff --git a/root/etc/e-smith/locale/pt-br/etc/e-smith/web/functions/mxbackup b/root/etc/e-smith/locale/pt-br/etc/e-smith/web/functions/mxbackup new file mode 100644 index 0000000..9c264a1 --- /dev/null +++ b/root/etc/e-smith/locale/pt-br/etc/e-smith/web/functions/mxbackup @@ -0,0 +1,122 @@ + + + FORM_TITLE + Configure the MX Backup function + + + FIRST_PAGE_DESCRIPTION + By default, SME really hate to be a mail relay. This means that, if someone outside your local(s) network(s) try to send to your SME box a mail for a domain that is not owned by this SME box, the mail is rejected.

But you can choose to be a second mail server (or MX Backup) for some others hosts or domains. In this case, you have to set the domains or hosts names that you plan to backup. You have also to say if you accept only one precise host ( you accept mail address like this_guy@bar.foo but you won't accept this_other@big.bar.foo) or one complete domain with all subdomain (mail address in form this_guy@*.bar.foo)

Some point of interest :

  • This is only one part of the configuration. This will only work if the DNS of the domains you plan to backup are correctly set (that is : your server should be a MX with a priority higher than the 'real' MX server)
  • You can choose between a domain and a host, but remember : You cannot choose the mailbox ( The left part of the E-Mail address )

]]> + + + BUTTON_LABEL_CREATE + Create a new MX-Backup rule + + + BUTTON_LABEL_START_SERVICE + Enable MX Backup + + + SERVICE_RUNNING + MX Backup is Enabled + + + BUTTON_LABEL_STOP_SERVICE + Disable MX Backup + + + SERVICE_STOPPED + MX Backup is Disabled + + + SUMMARY_ADD_DESC + The following table summarizes the MX Backup rule that you are about to add. If you are satisfied with the rule, click the "Add" button. If you are not, click the "Cancel" button. + + + SUMMARY_REMOVE_DESC + The following table summarizes the MX Backup rule that you are about to remove. If you are sure you want to remove the rule, click the "Remove" button. If not, click the "Cancel" button. + + + SHOW_MXBACKUP + Below you will find a table summarizing the current mx-backup rules installed on this server. Click on the "Remove" link to remove the corresponding rule. + + + NO_MXBACKUP + There are currently no 'MX Backuped' hosts or domains on the system. + + + CREATE_PAGE_DESCRIPTION + Set the domain name or host name you plan to 'MX Backup'. If you plan to backup an entire domain select 'Domain'. If you're unsure, this is the most sensible choice. If you only want to act as a MX Backup for one host (and no others hosts that could be sub-domains of this host) then select 'Host'.

]]> + + + DOMAIN + Domínio + + + HOST + Máquina + + + LABEL_NAME + Internet Name + + + LABEL_HOST_DOMAIN + HOST or DOMAIN + + + Configuration + Configuração + + + MX-Backup + MX Backup Configuration + + + SAVE + Salvar + + + APPLY + Adicionar + + + NEXT + Próximo + + + CANCEL + Cancelar + + + SUCCESS + Your change to the MX Backup configuration has been successfully saved. + + + REMOVE + Remover + + + ERR_NO_MXBACKUP_RECORD + Cannot retrieve mxbackup record from the mxbackup database. + + + ERR_UNSUPPORTED_MODE + Modo não suportado. + + + ERR_BADNAME + The name you gave don't seems to be a valid Internet Name.The name should only contain uppercase, lowercase, numbers and the '-' digit. The name should contain between 1 and 4 dot. The last word (the tld) can only contains letters and it shoult have a least 2 characters, but not more than 5. + + + ACTION + Ação + + + ENABLED + HABILITADO + + + DISABLED + DESABILITADO + + diff --git a/root/etc/e-smith/locale/pt/etc/e-smith/web/functions/mxbackup b/root/etc/e-smith/locale/pt/etc/e-smith/web/functions/mxbackup new file mode 100644 index 0000000..bb797c8 --- /dev/null +++ b/root/etc/e-smith/locale/pt/etc/e-smith/web/functions/mxbackup @@ -0,0 +1,122 @@ + + + FORM_TITLE + Configure the MX Backup function + + + FIRST_PAGE_DESCRIPTION + By default, SME really hate to be a mail relay. This means that, if someone outside your local(s) network(s) try to send to your SME box a mail for a domain that is not owned by this SME box, the mail is rejected.

But you can choose to be a second mail server (or MX Backup) for some others hosts or domains. In this case, you have to set the domains or hosts names that you plan to backup. You have also to say if you accept only one precise host ( you accept mail address like this_guy@bar.foo but you won't accept this_other@big.bar.foo) or one complete domain with all subdomain (mail address in form this_guy@*.bar.foo)

Some point of interest :

  • This is only one part of the configuration. This will only work if the DNS of the domains you plan to backup are correctly set (that is : your server should be a MX with a priority higher than the 'real' MX server)
  • You can choose between a domain and a host, but remember : You cannot choose the mailbox ( The left part of the E-Mail address )

]]> + + + BUTTON_LABEL_CREATE + Create a new MX-Backup rule + + + BUTTON_LABEL_START_SERVICE + Enable MX Backup + + + SERVICE_RUNNING + MX Backup is Enabled + + + BUTTON_LABEL_STOP_SERVICE + Disable MX Backup + + + SERVICE_STOPPED + MX Backup is Disabled + + + SUMMARY_ADD_DESC + The following table summarizes the MX Backup rule that you are about to add. If you are satisfied with the rule, click the "Add" button. If you are not, click the "Cancel" button. + + + SUMMARY_REMOVE_DESC + The following table summarizes the MX Backup rule that you are about to remove. If you are sure you want to remove the rule, click the "Remove" button. If not, click the "Cancel" button. + + + SHOW_MXBACKUP + Below you will find a table summarizing the current mx-backup rules installed on this server. Click on the "Remove" link to remove the corresponding rule. + + + NO_MXBACKUP + There are currently no 'MX Backuped' hosts or domains on the system. + + + CREATE_PAGE_DESCRIPTION + Set the domain name or host name you plan to 'MX Backup'. If you plan to backup an entire domain select 'Domain'. If you're unsure, this is the most sensible choice. If you only want to act as a MX Backup for one host (and no others hosts that could be sub-domains of this host) then select 'Host'.

]]> + + + DOMAIN + Domínio + + + HOST + Servidor + + + LABEL_NAME + Internet Name + + + LABEL_HOST_DOMAIN + HOST or DOMAIN + + + Configuration + Configuração + + + MX-Backup + MX Backup Configuration + + + SAVE + Salvar + + + APPLY + Adicionar + + + NEXT + Próximo + + + CANCEL + Cancelar + + + SUCCESS + Your change to the MX Backup configuration has been successfully saved. + + + REMOVE + Remover + + + ERR_NO_MXBACKUP_RECORD + Cannot retrieve mxbackup record from the mxbackup database. + + + ERR_UNSUPPORTED_MODE + Modo não suportado. + + + ERR_BADNAME + The name you gave don't seems to be a valid Internet Name.The name should only contain uppercase, lowercase, numbers and the '-' digit. The name should contain between 1 and 4 dot. The last word (the tld) can only contains letters and it shoult have a least 2 characters, but not more than 5. + + + ACTION + Ação + + + ENABLED + HABILITADO + + + DISABLED + DESABILITADO + + diff --git a/root/etc/e-smith/locale/ro/etc/e-smith/web/functions/mxbackup b/root/etc/e-smith/locale/ro/etc/e-smith/web/functions/mxbackup new file mode 100644 index 0000000..37adf21 --- /dev/null +++ b/root/etc/e-smith/locale/ro/etc/e-smith/web/functions/mxbackup @@ -0,0 +1,122 @@ + + + FORM_TITLE + Configure the MX Backup function + + + FIRST_PAGE_DESCRIPTION + By default, SME really hate to be a mail relay. This means that, if someone outside your local(s) network(s) try to send to your SME box a mail for a domain that is not owned by this SME box, the mail is rejected.

But you can choose to be a second mail server (or MX Backup) for some others hosts or domains. In this case, you have to set the domains or hosts names that you plan to backup. You have also to say if you accept only one precise host ( you accept mail address like this_guy@bar.foo but you won't accept this_other@big.bar.foo) or one complete domain with all subdomain (mail address in form this_guy@*.bar.foo)

Some point of interest :

  • This is only one part of the configuration. This will only work if the DNS of the domains you plan to backup are correctly set (that is : your server should be a MX with a priority higher than the 'real' MX server)
  • You can choose between a domain and a host, but remember : You cannot choose the mailbox ( The left part of the E-Mail address )

]]> + + + BUTTON_LABEL_CREATE + Create a new MX-Backup rule + + + BUTTON_LABEL_START_SERVICE + Enable MX Backup + + + SERVICE_RUNNING + MX Backup is Enabled + + + BUTTON_LABEL_STOP_SERVICE + Disable MX Backup + + + SERVICE_STOPPED + MX Backup is Disabled + + + SUMMARY_ADD_DESC + The following table summarizes the MX Backup rule that you are about to add. If you are satisfied with the rule, click the "Add" button. If you are not, click the "Cancel" button. + + + SUMMARY_REMOVE_DESC + The following table summarizes the MX Backup rule that you are about to remove. If you are sure you want to remove the rule, click the "Remove" button. If not, click the "Cancel" button. + + + SHOW_MXBACKUP + Below you will find a table summarizing the current mx-backup rules installed on this server. Click on the "Remove" link to remove the corresponding rule. + + + NO_MXBACKUP + There are currently no 'MX Backuped' hosts or domains on the system. + + + CREATE_PAGE_DESCRIPTION + Set the domain name or host name you plan to 'MX Backup'. If you plan to backup an entire domain select 'Domain'. If you're unsure, this is the most sensible choice. If you only want to act as a MX Backup for one host (and no others hosts that could be sub-domains of this host) then select 'Host'.

]]> + + + DOMAIN + Domain + + + HOST + Host + + + LABEL_NAME + Internet Name + + + LABEL_HOST_DOMAIN + HOST or DOMAIN + + + Configuration + Configurare + + + MX-Backup + MX Backup Configuration + + + SAVE + Salvează + + + APPLY + Adaugă + + + NEXT + Următorul + + + CANCEL + Anulare + + + SUCCESS + Your change to the MX Backup configuration has been successfully saved. + + + REMOVE + Remove + + + ERR_NO_MXBACKUP_RECORD + Cannot retrieve mxbackup record from the mxbackup database. + + + ERR_UNSUPPORTED_MODE + Unsupported mode. + + + ERR_BADNAME + The name you gave don't seems to be a valid Internet Name.The name should only contain uppercase, lowercase, numbers and the '-' digit. The name should contain between 1 and 4 dot. The last word (the tld) can only contains letters and it shoult have a least 2 characters, but not more than 5. + + + ACTION + Acțiune + + + ENABLED + ACTIV + + + DISABLED + DEZACTIVAT + + diff --git a/root/etc/e-smith/locale/ru/etc/e-smith/web/functions/mxbackup b/root/etc/e-smith/locale/ru/etc/e-smith/web/functions/mxbackup new file mode 100644 index 0000000..7a3e235 --- /dev/null +++ b/root/etc/e-smith/locale/ru/etc/e-smith/web/functions/mxbackup @@ -0,0 +1,122 @@ + + + FORM_TITLE + Configure the MX Backup function + + + FIRST_PAGE_DESCRIPTION + By default, SME really hate to be a mail relay. This means that, if someone outside your local(s) network(s) try to send to your SME box a mail for a domain that is not owned by this SME box, the mail is rejected.

But you can choose to be a second mail server (or MX Backup) for some others hosts or domains. In this case, you have to set the domains or hosts names that you plan to backup. You have also to say if you accept only one precise host ( you accept mail address like this_guy@bar.foo but you won't accept this_other@big.bar.foo) or one complete domain with all subdomain (mail address in form this_guy@*.bar.foo)

Some point of interest :

  • This is only one part of the configuration. This will only work if the DNS of the domains you plan to backup are correctly set (that is : your server should be a MX with a priority higher than the 'real' MX server)
  • You can choose between a domain and a host, but remember : You cannot choose the mailbox ( The left part of the E-Mail address )

]]> + + + BUTTON_LABEL_CREATE + Create a new MX-Backup rule + + + BUTTON_LABEL_START_SERVICE + Enable MX Backup + + + SERVICE_RUNNING + MX Backup is Enabled + + + BUTTON_LABEL_STOP_SERVICE + Disable MX Backup + + + SERVICE_STOPPED + MX Backup is Disabled + + + SUMMARY_ADD_DESC + The following table summarizes the MX Backup rule that you are about to add. If you are satisfied with the rule, click the "Add" button. If you are not, click the "Cancel" button. + + + SUMMARY_REMOVE_DESC + The following table summarizes the MX Backup rule that you are about to remove. If you are sure you want to remove the rule, click the "Remove" button. If not, click the "Cancel" button. + + + SHOW_MXBACKUP + Below you will find a table summarizing the current mx-backup rules installed on this server. Click on the "Remove" link to remove the corresponding rule. + + + NO_MXBACKUP + There are currently no 'MX Backuped' hosts or domains on the system. + + + CREATE_PAGE_DESCRIPTION + Set the domain name or host name you plan to 'MX Backup'. If you plan to backup an entire domain select 'Domain'. If you're unsure, this is the most sensible choice. If you only want to act as a MX Backup for one host (and no others hosts that could be sub-domains of this host) then select 'Host'.

]]> + + + DOMAIN + Домен + + + HOST + Host + + + LABEL_NAME + Internet Name + + + LABEL_HOST_DOMAIN + HOST or DOMAIN + + + Configuration + Конфигурация + + + MX-Backup + MX Backup Configuration + + + SAVE + Сохранить + + + APPLY + Добавить + + + NEXT + Далее + + + CANCEL + Отмена + + + SUCCESS + Your change to the MX Backup configuration has been successfully saved. + + + REMOVE + Удалить + + + ERR_NO_MXBACKUP_RECORD + Cannot retrieve mxbackup record from the mxbackup database. + + + ERR_UNSUPPORTED_MODE + Неподдерживаемый режим. + + + ERR_BADNAME + The name you gave don't seems to be a valid Internet Name.The name should only contain uppercase, lowercase, numbers and the '-' digit. The name should contain between 1 and 4 dot. The last word (the tld) can only contains letters and it shoult have a least 2 characters, but not more than 5. + + + ACTION + Действие + + + ENABLED + ENABLED + + + DISABLED + DISABLED + + diff --git a/root/etc/e-smith/locale/sl/etc/e-smith/web/functions/mxbackup b/root/etc/e-smith/locale/sl/etc/e-smith/web/functions/mxbackup new file mode 100644 index 0000000..8b2f0c9 --- /dev/null +++ b/root/etc/e-smith/locale/sl/etc/e-smith/web/functions/mxbackup @@ -0,0 +1,122 @@ + + + FORM_TITLE + Configure the MX Backup function + + + FIRST_PAGE_DESCRIPTION + By default, SME really hate to be a mail relay. This means that, if someone outside your local(s) network(s) try to send to your SME box a mail for a domain that is not owned by this SME box, the mail is rejected.

But you can choose to be a second mail server (or MX Backup) for some others hosts or domains. In this case, you have to set the domains or hosts names that you plan to backup. You have also to say if you accept only one precise host ( you accept mail address like this_guy@bar.foo but you won't accept this_other@big.bar.foo) or one complete domain with all subdomain (mail address in form this_guy@*.bar.foo)

Some point of interest :

  • This is only one part of the configuration. This will only work if the DNS of the domains you plan to backup are correctly set (that is : your server should be a MX with a priority higher than the 'real' MX server)
  • You can choose between a domain and a host, but remember : You cannot choose the mailbox ( The left part of the E-Mail address )

]]> + + + BUTTON_LABEL_CREATE + Create a new MX-Backup rule + + + BUTTON_LABEL_START_SERVICE + Enable MX Backup + + + SERVICE_RUNNING + MX Backup is Enabled + + + BUTTON_LABEL_STOP_SERVICE + Disable MX Backup + + + SERVICE_STOPPED + MX Backup is Disabled + + + SUMMARY_ADD_DESC + The following table summarizes the MX Backup rule that you are about to add. If you are satisfied with the rule, click the "Add" button. If you are not, click the "Cancel" button. + + + SUMMARY_REMOVE_DESC + The following table summarizes the MX Backup rule that you are about to remove. If you are sure you want to remove the rule, click the "Remove" button. If not, click the "Cancel" button. + + + SHOW_MXBACKUP + Below you will find a table summarizing the current mx-backup rules installed on this server. Click on the "Remove" link to remove the corresponding rule. + + + NO_MXBACKUP + There are currently no 'MX Backuped' hosts or domains on the system. + + + CREATE_PAGE_DESCRIPTION + Set the domain name or host name you plan to 'MX Backup'. If you plan to backup an entire domain select 'Domain'. If you're unsure, this is the most sensible choice. If you only want to act as a MX Backup for one host (and no others hosts that could be sub-domains of this host) then select 'Host'.

]]> + + + DOMAIN + Domena + + + HOST + Host + + + LABEL_NAME + Internet Name + + + LABEL_HOST_DOMAIN + HOST or DOMAIN + + + Configuration + Konfiguracija + + + MX-Backup + MX Backup Configuration + + + SAVE + Shrani + + + APPLY + Dodaj + + + NEXT + Naprej + + + CANCEL + Preklici + + + SUCCESS + Your change to the MX Backup configuration has been successfully saved. + + + REMOVE + Odstrani + + + ERR_NO_MXBACKUP_RECORD + Cannot retrieve mxbackup record from the mxbackup database. + + + ERR_UNSUPPORTED_MODE + Nepodprti nacin dela. + + + ERR_BADNAME + The name you gave don't seems to be a valid Internet Name.The name should only contain uppercase, lowercase, numbers and the '-' digit. The name should contain between 1 and 4 dot. The last word (the tld) can only contains letters and it shoult have a least 2 characters, but not more than 5. + + + ACTION + Izvedi + + + ENABLED + ENABLED + + + DISABLED + DISABLED + + diff --git a/root/etc/e-smith/locale/sv/etc/e-smith/web/functions/mxbackup b/root/etc/e-smith/locale/sv/etc/e-smith/web/functions/mxbackup new file mode 100644 index 0000000..9a1725f --- /dev/null +++ b/root/etc/e-smith/locale/sv/etc/e-smith/web/functions/mxbackup @@ -0,0 +1,122 @@ + + + FORM_TITLE + Configure the MX Backup function + + + FIRST_PAGE_DESCRIPTION + By default, SME really hate to be a mail relay. This means that, if someone outside your local(s) network(s) try to send to your SME box a mail for a domain that is not owned by this SME box, the mail is rejected.

But you can choose to be a second mail server (or MX Backup) for some others hosts or domains. In this case, you have to set the domains or hosts names that you plan to backup. You have also to say if you accept only one precise host ( you accept mail address like this_guy@bar.foo but you won't accept this_other@big.bar.foo) or one complete domain with all subdomain (mail address in form this_guy@*.bar.foo)

Some point of interest :

  • This is only one part of the configuration. This will only work if the DNS of the domains you plan to backup are correctly set (that is : your server should be a MX with a priority higher than the 'real' MX server)
  • You can choose between a domain and a host, but remember : You cannot choose the mailbox ( The left part of the E-Mail address )

]]> + + + BUTTON_LABEL_CREATE + Create a new MX-Backup rule + + + BUTTON_LABEL_START_SERVICE + Enable MX Backup + + + SERVICE_RUNNING + MX Backup is Enabled + + + BUTTON_LABEL_STOP_SERVICE + Disable MX Backup + + + SERVICE_STOPPED + MX Backup is Disabled + + + SUMMARY_ADD_DESC + The following table summarizes the MX Backup rule that you are about to add. If you are satisfied with the rule, click the "Add" button. If you are not, click the "Cancel" button. + + + SUMMARY_REMOVE_DESC + The following table summarizes the MX Backup rule that you are about to remove. If you are sure you want to remove the rule, click the "Remove" button. If not, click the "Cancel" button. + + + SHOW_MXBACKUP + Below you will find a table summarizing the current mx-backup rules installed on this server. Click on the "Remove" link to remove the corresponding rule. + + + NO_MXBACKUP + There are currently no 'MX Backuped' hosts or domains on the system. + + + CREATE_PAGE_DESCRIPTION + Set the domain name or host name you plan to 'MX Backup'. If you plan to backup an entire domain select 'Domain'. If you're unsure, this is the most sensible choice. If you only want to act as a MX Backup for one host (and no others hosts that could be sub-domains of this host) then select 'Host'.

]]> + + + DOMAIN + Domän + + + HOST + Värd + + + LABEL_NAME + Internet Name + + + LABEL_HOST_DOMAIN + HOST or DOMAIN + + + Configuration + Konfiguration + + + MX-Backup + MX Backup Configuration + + + SAVE + Spara + + + APPLY + Lägg till + + + NEXT + Nästa + + + CANCEL + Avbryt + + + SUCCESS + Your change to the MX Backup configuration has been successfully saved. + + + REMOVE + Radera + + + ERR_NO_MXBACKUP_RECORD + Cannot retrieve mxbackup record from the mxbackup database. + + + ERR_UNSUPPORTED_MODE + Ej stödd mod. + + + ERR_BADNAME + The name you gave don't seems to be a valid Internet Name.The name should only contain uppercase, lowercase, numbers and the '-' digit. The name should contain between 1 and 4 dot. The last word (the tld) can only contains letters and it shoult have a least 2 characters, but not more than 5. + + + ACTION + Verkställ + + + ENABLED + AKTIVERAD + + + DISABLED + AVAKTIVERAD + + diff --git a/root/etc/e-smith/locale/th/etc/e-smith/web/functions/mxbackup b/root/etc/e-smith/locale/th/etc/e-smith/web/functions/mxbackup new file mode 100644 index 0000000..70f7d7b --- /dev/null +++ b/root/etc/e-smith/locale/th/etc/e-smith/web/functions/mxbackup @@ -0,0 +1,122 @@ + + + FORM_TITLE + Configure the MX Backup function + + + FIRST_PAGE_DESCRIPTION + By default, SME really hate to be a mail relay. This means that, if someone outside your local(s) network(s) try to send to your SME box a mail for a domain that is not owned by this SME box, the mail is rejected.

But you can choose to be a second mail server (or MX Backup) for some others hosts or domains. In this case, you have to set the domains or hosts names that you plan to backup. You have also to say if you accept only one precise host ( you accept mail address like this_guy@bar.foo but you won't accept this_other@big.bar.foo) or one complete domain with all subdomain (mail address in form this_guy@*.bar.foo)

Some point of interest :

  • This is only one part of the configuration. This will only work if the DNS of the domains you plan to backup are correctly set (that is : your server should be a MX with a priority higher than the 'real' MX server)
  • You can choose between a domain and a host, but remember : You cannot choose the mailbox ( The left part of the E-Mail address )

]]> + + + BUTTON_LABEL_CREATE + Create a new MX-Backup rule + + + BUTTON_LABEL_START_SERVICE + Enable MX Backup + + + SERVICE_RUNNING + MX Backup is Enabled + + + BUTTON_LABEL_STOP_SERVICE + Disable MX Backup + + + SERVICE_STOPPED + MX Backup is Disabled + + + SUMMARY_ADD_DESC + The following table summarizes the MX Backup rule that you are about to add. If you are satisfied with the rule, click the "Add" button. If you are not, click the "Cancel" button. + + + SUMMARY_REMOVE_DESC + The following table summarizes the MX Backup rule that you are about to remove. If you are sure you want to remove the rule, click the "Remove" button. If not, click the "Cancel" button. + + + SHOW_MXBACKUP + Below you will find a table summarizing the current mx-backup rules installed on this server. Click on the "Remove" link to remove the corresponding rule. + + + NO_MXBACKUP + There are currently no 'MX Backuped' hosts or domains on the system. + + + CREATE_PAGE_DESCRIPTION + Set the domain name or host name you plan to 'MX Backup'. If you plan to backup an entire domain select 'Domain'. If you're unsure, this is the most sensible choice. If you only want to act as a MX Backup for one host (and no others hosts that could be sub-domains of this host) then select 'Host'.

]]> + + + DOMAIN + โดเมน + + + HOST + Host + + + LABEL_NAME + Internet Name + + + LABEL_HOST_DOMAIN + HOST or DOMAIN + + + Configuration + การตั้งค่าของระบบ + + + MX-Backup + MX Backup Configuration + + + SAVE + บันทึก + + + APPLY + เพิ่ม + + + NEXT + ถัดไป + + + CANCEL + ยกเลิก + + + SUCCESS + Your change to the MX Backup configuration has been successfully saved. + + + REMOVE + ลบ + + + ERR_NO_MXBACKUP_RECORD + Cannot retrieve mxbackup record from the mxbackup database. + + + ERR_UNSUPPORTED_MODE + โหมดที่ไม่สนับสนุน + + + ERR_BADNAME + The name you gave don't seems to be a valid Internet Name.The name should only contain uppercase, lowercase, numbers and the '-' digit. The name should contain between 1 and 4 dot. The last word (the tld) can only contains letters and it shoult have a least 2 characters, but not more than 5. + + + ACTION + การดำเนินการ + + + ENABLED + ENABLED + + + DISABLED + DISABLED + + diff --git a/root/etc/e-smith/locale/tr/etc/e-smith/web/functions/mxbackup b/root/etc/e-smith/locale/tr/etc/e-smith/web/functions/mxbackup new file mode 100644 index 0000000..1e92018 --- /dev/null +++ b/root/etc/e-smith/locale/tr/etc/e-smith/web/functions/mxbackup @@ -0,0 +1,122 @@ + + + FORM_TITLE + Configure the MX Backup function + + + FIRST_PAGE_DESCRIPTION + By default, SME really hate to be a mail relay. This means that, if someone outside your local(s) network(s) try to send to your SME box a mail for a domain that is not owned by this SME box, the mail is rejected.

But you can choose to be a second mail server (or MX Backup) for some others hosts or domains. In this case, you have to set the domains or hosts names that you plan to backup. You have also to say if you accept only one precise host ( you accept mail address like this_guy@bar.foo but you won't accept this_other@big.bar.foo) or one complete domain with all subdomain (mail address in form this_guy@*.bar.foo)

Some point of interest :

  • This is only one part of the configuration. This will only work if the DNS of the domains you plan to backup are correctly set (that is : your server should be a MX with a priority higher than the 'real' MX server)
  • You can choose between a domain and a host, but remember : You cannot choose the mailbox ( The left part of the E-Mail address )

]]> + + + BUTTON_LABEL_CREATE + Create a new MX-Backup rule + + + BUTTON_LABEL_START_SERVICE + Enable MX Backup + + + SERVICE_RUNNING + MX Backup is Enabled + + + BUTTON_LABEL_STOP_SERVICE + Disable MX Backup + + + SERVICE_STOPPED + MX Backup is Disabled + + + SUMMARY_ADD_DESC + The following table summarizes the MX Backup rule that you are about to add. If you are satisfied with the rule, click the "Add" button. If you are not, click the "Cancel" button. + + + SUMMARY_REMOVE_DESC + The following table summarizes the MX Backup rule that you are about to remove. If you are sure you want to remove the rule, click the "Remove" button. If not, click the "Cancel" button. + + + SHOW_MXBACKUP + Below you will find a table summarizing the current mx-backup rules installed on this server. Click on the "Remove" link to remove the corresponding rule. + + + NO_MXBACKUP + There are currently no 'MX Backuped' hosts or domains on the system. + + + CREATE_PAGE_DESCRIPTION + Set the domain name or host name you plan to 'MX Backup'. If you plan to backup an entire domain select 'Domain'. If you're unsure, this is the most sensible choice. If you only want to act as a MX Backup for one host (and no others hosts that could be sub-domains of this host) then select 'Host'.

]]> + + + DOMAIN + Etki alanı + + + HOST + Host + + + LABEL_NAME + Internet Name + + + LABEL_HOST_DOMAIN + HOST or DOMAIN + + + Configuration + Konfigürasyon + + + MX-Backup + MX Backup Configuration + + + SAVE + Kaydet + + + APPLY + Ekle + + + NEXT + İleri + + + CANCEL + İptal + + + SUCCESS + Your change to the MX Backup configuration has been successfully saved. + + + REMOVE + Kaldır + + + ERR_NO_MXBACKUP_RECORD + Cannot retrieve mxbackup record from the mxbackup database. + + + ERR_UNSUPPORTED_MODE + Desteklenmeyen mod + + + ERR_BADNAME + The name you gave don't seems to be a valid Internet Name.The name should only contain uppercase, lowercase, numbers and the '-' digit. The name should contain between 1 and 4 dot. The last word (the tld) can only contains letters and it shoult have a least 2 characters, but not more than 5. + + + ACTION + Eylem + + + ENABLED + ENABLED + + + DISABLED + DISABLED + + diff --git a/root/etc/e-smith/locale/zh-cn/etc/e-smith/web/functions/mxbackup b/root/etc/e-smith/locale/zh-cn/etc/e-smith/web/functions/mxbackup new file mode 100644 index 0000000..82a6247 --- /dev/null +++ b/root/etc/e-smith/locale/zh-cn/etc/e-smith/web/functions/mxbackup @@ -0,0 +1,122 @@ + + + FORM_TITLE + 设置 MX Backup 功能 + + + FIRST_PAGE_DESCRIPTION + By default, SME really hate to be a mail relay. This means that, if someone outside your local(s) network(s) try to send to your SME box a mail for a domain that is not owned by this SME box, the mail is rejected.

But you can choose to be a second mail server (or MX Backup) for some others hosts or domains. In this case, you have to set the domains or hosts names that you plan to backup. You have also to say if you accept only one precise host ( you accept mail address like this_guy@bar.foo but you won't accept this_other@big.bar.foo) or one complete domain with all subdomain (mail address in form this_guy@*.bar.foo)

Some point of interest :

  • This is only one part of the configuration. This will only work if the DNS of the domains you plan to backup are correctly set (that is : your server should be a MX with a priority higher than the 'real' MX server)
  • You can choose between a domain and a host, but remember : You cannot choose the mailbox ( The left part of the E-Mail address )

]]> + + + BUTTON_LABEL_CREATE + 创建新的 MX-Backup 规则 + + + BUTTON_LABEL_START_SERVICE + 启用 MX Backup + + + SERVICE_RUNNING + MX Backup 已启用 + + + BUTTON_LABEL_STOP_SERVICE + 禁用 MX Backup + + + SERVICE_STOPPED + MX Backup 已禁用 + + + SUMMARY_ADD_DESC + The following table summarizes the MX Backup rule that you are about to add. If you are satisfied with the rule, click the "Add" button. If you are not, click the "Cancel" button. + + + SUMMARY_REMOVE_DESC + The following table summarizes the MX Backup rule that you are about to remove. If you are sure you want to remove the rule, click the "Remove" button. If not, click the "Cancel" button. + + + SHOW_MXBACKUP + Below you will find a table summarizing the current mx-backup rules installed on this server. Click on the "Remove" link to remove the corresponding rule. + + + NO_MXBACKUP + There are currently no 'MX Backuped' hosts or domains on the system. + + + CREATE_PAGE_DESCRIPTION + Set the domain name or host name you plan to 'MX Backup'. If you plan to backup an entire domain select 'Domain'. If you're unsure, this is the most sensible choice. If you only want to act as a MX Backup for one host (and no others hosts that could be sub-domains of this host) then select 'Host'.

]]> + + + DOMAIN + 域名 + + + HOST + 主机 + + + LABEL_NAME + 域名 + + + LABEL_HOST_DOMAIN + 主机名或域名 + + + Configuration + 配置 + + + MX-Backup + MX Backup 设置 + + + SAVE + 保存 + + + APPLY + 添加 + + + NEXT + 下一步 + + + CANCEL + 取消 + + + SUCCESS + 您对 MX Backup 的配置修改已保存. + + + REMOVE + 移除 + + + ERR_NO_MXBACKUP_RECORD + 在 mxbackup 的数据库里找不到 mxbackup 的相关记录. + + + ERR_UNSUPPORTED_MODE + 不支持的模式。 + + + ERR_BADNAME + The name you gave don't seems to be a valid Internet Name.The name should only contain uppercase, lowercase, numbers and the '-' digit. The name should contain between 1 and 4 dot. The last word (the tld) can only contains letters and it shoult have a least 2 characters, but not more than 5. + + + ACTION + 动作 + + + ENABLED + 启用 + + + DISABLED + 禁用 + + diff --git a/root/etc/e-smith/locale/zh-tw/etc/e-smith/web/functions/mxbackup b/root/etc/e-smith/locale/zh-tw/etc/e-smith/web/functions/mxbackup new file mode 100644 index 0000000..a71a71d --- /dev/null +++ b/root/etc/e-smith/locale/zh-tw/etc/e-smith/web/functions/mxbackup @@ -0,0 +1,122 @@ + + + FORM_TITLE + Configure the MX Backup function + + + FIRST_PAGE_DESCRIPTION + By default, SME really hate to be a mail relay. This means that, if someone outside your local(s) network(s) try to send to your SME box a mail for a domain that is not owned by this SME box, the mail is rejected.

But you can choose to be a second mail server (or MX Backup) for some others hosts or domains. In this case, you have to set the domains or hosts names that you plan to backup. You have also to say if you accept only one precise host ( you accept mail address like this_guy@bar.foo but you won't accept this_other@big.bar.foo) or one complete domain with all subdomain (mail address in form this_guy@*.bar.foo)

Some point of interest :

  • This is only one part of the configuration. This will only work if the DNS of the domains you plan to backup are correctly set (that is : your server should be a MX with a priority higher than the 'real' MX server)
  • You can choose between a domain and a host, but remember : You cannot choose the mailbox ( The left part of the E-Mail address )

]]> + + + BUTTON_LABEL_CREATE + Create a new MX-Backup rule + + + BUTTON_LABEL_START_SERVICE + Enable MX Backup + + + SERVICE_RUNNING + MX Backup is Enabled + + + BUTTON_LABEL_STOP_SERVICE + Disable MX Backup + + + SERVICE_STOPPED + MX Backup is Disabled + + + SUMMARY_ADD_DESC + The following table summarizes the MX Backup rule that you are about to add. If you are satisfied with the rule, click the "Add" button. If you are not, click the "Cancel" button. + + + SUMMARY_REMOVE_DESC + The following table summarizes the MX Backup rule that you are about to remove. If you are sure you want to remove the rule, click the "Remove" button. If not, click the "Cancel" button. + + + SHOW_MXBACKUP + Below you will find a table summarizing the current mx-backup rules installed on this server. Click on the "Remove" link to remove the corresponding rule. + + + NO_MXBACKUP + There are currently no 'MX Backuped' hosts or domains on the system. + + + CREATE_PAGE_DESCRIPTION + Set the domain name or host name you plan to 'MX Backup'. If you plan to backup an entire domain select 'Domain'. If you're unsure, this is the most sensible choice. If you only want to act as a MX Backup for one host (and no others hosts that could be sub-domains of this host) then select 'Host'.

]]> + + + DOMAIN + 網域 + + + HOST + 主機 + + + LABEL_NAME + Internet Name + + + LABEL_HOST_DOMAIN + HOST or DOMAIN + + + Configuration + 設定組態 + + + MX-Backup + MX Backup Configuration + + + SAVE + 儲存 + + + APPLY + 新增 + + + NEXT + 下一步 + + + CANCEL + 取消 + + + SUCCESS + Your change to the MX Backup configuration has been successfully saved. + + + REMOVE + 移除 + + + ERR_NO_MXBACKUP_RECORD + Cannot retrieve mxbackup record from the mxbackup database. + + + ERR_UNSUPPORTED_MODE + Unsupported mode. + + + ERR_BADNAME + The name you gave don't seems to be a valid Internet Name.The name should only contain uppercase, lowercase, numbers and the '-' digit. The name should contain between 1 and 4 dot. The last word (the tld) can only contains letters and it shoult have a least 2 characters, but not more than 5. + + + ACTION + 動作 + + + ENABLED + 允許 + + + DISABLED + 禁止 + + diff --git a/root/etc/e-smith/templates/var/qmail/control/rcpthosts/20mxbackup b/root/etc/e-smith/templates/var/qmail/control/rcpthosts/20mxbackup new file mode 100755 index 0000000..194f9fe --- /dev/null +++ b/root/etc/e-smith/templates/var/qmail/control/rcpthosts/20mxbackup @@ -0,0 +1,29 @@ +{ + # vim: ft=perl ts=4 sw=4 et: + # perltidy -pbp + + if ( ( $mxbackup{status} || "disabled" ) eq "enabled" ) { + $OUT = "# Following is a list of systems or domains.\n"; + $OUT .= "# This system is configured to act as a MX Backup for\n"; + $OUT .= "# these systems (if there's only one line) or domains.\n"; + $OUT .= "# If there is a line beginning with a dot, then this\n"; + $OUT .= "# system will accept mails for any hosts of this domain\n"; + $OUT .= "# MX Backup start\n"; + + my $MXFlag = 0; + my %MXValues = split /,/, ( $mxbackup{name} || "" ); + foreach my $data ( + sort { + ( join( "\.", reverse( split /\./, $a ) ) ) + cmp( join( "\.", reverse( split /\./, $b ) ) ) + } + keys %MXValues + ) { + $OUT .= "$data\n"; + $OUT .= ".$data\n" if ( $MXValues{$data} ); + $MXFlag = 1; + } + $OUT .= "### No MX Backup set Now ...\n" if ( !$MXFlag ); + $OUT .= "# MX Backup end\n"; + } +} diff --git a/root/etc/e-smith/templates/var/qmail/control/smtproutes/30mxbackup b/root/etc/e-smith/templates/var/qmail/control/smtproutes/30mxbackup new file mode 100755 index 0000000..c0473de --- /dev/null +++ b/root/etc/e-smith/templates/var/qmail/control/smtproutes/30mxbackup @@ -0,0 +1,35 @@ +{ + # vim: ft=perl ts=4 sw=4 et: + # perltidy -pbp + $OUT = ""; + + # ------------------------------------------------ + # if mxbackup is enabled, we have to check if + # there a 'smart host'. If yes, the smart host + # should not be used for all 'MX-Backuped' domains. + # ------------------------------------------------ + + if ( ( $mxbackup{status} || "disabled" ) eq "enabled" ) { + + #-------------------------------------------------- + # Now check for SMTP smart host + #-------------------------------------------------- + + if ( $SMTPSmartHost + && ( $SMTPSmartHost ne 'off' ) + && ( $SMTPSmartHost !~ /^\s*$/ ) ) { + my %MXValues = split /,/, ( $mxbackup{name} || "" ); + foreach my $data ( + sort { + ( join( "\.", reverse( split /\./, $a ) ) ) + cmp( join( "\.", reverse( split /\./, $b ) ) ) + } + keys %MXValues + ) { + $OUT .= "$data:\n"; + $OUT .= ".$data:\n" if ( $MXValues{$data} ); + } + } + } + chomp($OUT); +} diff --git a/root/etc/e-smith/templates/var/service/qpsmtpd/config/goodrcptto/50MXBackup b/root/etc/e-smith/templates/var/service/qpsmtpd/config/goodrcptto/50MXBackup new file mode 100755 index 0000000..398e9d2 --- /dev/null +++ b/root/etc/e-smith/templates/var/service/qpsmtpd/config/goodrcptto/50MXBackup @@ -0,0 +1,26 @@ +{ + # vim: ft=perl ts=4 sw=4 et: + # perltidy -pbp + if ( ( $mxbackup{status} || "disabled" ) eq "enabled" ) { + $OUT .= "\n"; + $OUT .= "# MX Backup entries start\n"; + $OUT .= "# This is the list of the mail domains\n"; + $OUT .= "# from the MX-Backup configuration of the local system.\n"; + + my $MXFlag = 0; + my %MXValues = split /,/, ( $mxbackup{name} || "" ); + foreach my $data ( + sort { + ( join( "\.", reverse( split /\./, $a ) ) ) + cmp( join( "\.", reverse( split /\./, $b ) ) ) + } + keys %MXValues + ) { + $OUT .= "\@$data\n"; + $MXFlag = 1; + } + $OUT .= "### No MX Backup set Now ...\n" if ( !$MXFlag ); + $OUT .= "# MX Backup entries end\n\n"; + } +} + diff --git a/root/etc/e-smith/web/functions/mxbackup b/root/etc/e-smith/web/functions/mxbackup new file mode 100755 index 0000000..51ebff6 --- /dev/null +++ b/root/etc/e-smith/web/functions/mxbackup @@ -0,0 +1,108 @@ +#!/usr/bin/perl -wT +# vim: ft=xml ts=4 sw=4 et: +#---------------------------------------------------------------------- +# heading : Configuration +# description : MX-Backup +# navigation : 6000 6710 +#---------------------------------------------------------------------- +#---------------------------------------------------------------------- +# copyright (C) 2004 Schirrm's Studio +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program; if not, write to the Free Software +# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA +#---------------------------------------------------------------------- + +use strict; +use esmith::FormMagick::Panel::mxbackup; +my $form = esmith::FormMagick::Panel::mxbackup->new(); +# Uncomment the next line for debugging purposes. +# $form->debug(1); +$form->display(); + + +__DATA__ +
+ + + + FIRST_PAGE_DESCRIPTION + + + + + + + CREATE_PAGE_DESCRIPTION + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
diff --git a/root/etc/e-smith/web/panels/manager/cgi-bin/mxbackup b/root/etc/e-smith/web/panels/manager/cgi-bin/mxbackup new file mode 120000 index 0000000..d5310ac --- /dev/null +++ b/root/etc/e-smith/web/panels/manager/cgi-bin/mxbackup @@ -0,0 +1 @@ +../../../functions/mxbackup \ No newline at end of file diff --git a/root/usr/share/perl5/vendor_perl/esmith/FormMagick/Panel/mxbackup.pm b/root/usr/share/perl5/vendor_perl/esmith/FormMagick/Panel/mxbackup.pm new file mode 100755 index 0000000..fdce422 --- /dev/null +++ b/root/usr/share/perl5/vendor_perl/esmith/FormMagick/Panel/mxbackup.pm @@ -0,0 +1,483 @@ +#---------------------------------------------------------------------- +# $Id: portforwarding.pm,v 1.31 2003/04/08 15:28:55 msoulier Exp $ +# vim: ft=perl ts=4 sw=4 et: +#---------------------------------------------------------------------- +# copyright (C) 2004 Pascal Schirrmann +# copyright (C) 2002 Mitel Networks Corporation +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program; if not, write to the Free Software +# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA +#---------------------------------------------------------------------- + +package esmith::FormMagick::Panel::mxbackup; + +use strict; +use esmith::ConfigDB; +use esmith::FormMagick; +use esmith::cgi; +use Exporter; + +use constant TRUE => 1; +use constant FALSE => 0; + +our @ISA = qw(esmith::FormMagick Exporter); + +our @EXPORT = qw( + show_mx_backup create_new validate_name + display_create_summary + ); + +our $VERSION = sprintf '%d.%03d', q$Revision: 0.10 $ =~ /: (\d+).(\d+)/; +our $mdb = esmith::ConfigDB->open + or die "Can't open the Config database : $!\n" ; + +=head1 NAME + +esmith::FormMagick::Panels::mxbackup - useful panel functions + +=head1 SYNOPSIS + + use esmith::FormMagick::Panels::mxbackup + + my $panel = esmith::FormMagick::Panel::mxbackup->new(); + $panel->display(); + +=head1 DESCRIPTION + +This module is the backend to the mxbackup panel, responsible for +supplying all functions used by that panel. It is a subclass of +esmith::FormMagick itself, so it inherits the functionality of a FormMagick +object. + +=head2 new + +This is the class constructor. + +=cut + +sub new { + my $class = ref($_[0]) || $_[0]; + my $self = esmith::FormMagick->new(); + bless $self, $class; + # Uncomment the following line for debugging. + #$self->debug(TRUE); + return $self; +} + +=head2 show_mx_backup + +This method displays the hosts or domains for witch we currently +act as an MX Backup + +=cut + +sub show_mx_backup { + my $self = shift ; + my $q = $self->cgi ; + + my $MX = $mdb->get('mxbackup') + or ($self->error('ERR_NO_MXBACKUP_RECORD') and return undef) ; + my $empty = 0 ; + my %MXValues = split /,/, $MX->prop('name') ; + my $MXStatus = 0 ; + $MXStatus = 1 if ( ( $MX->prop('status') || 'disabled' ) eq 'enabled' ) ; + $empty = 1 if not %MXValues ; + + # this was a good idea to put an enable button... + # But now, the 'unless' test has to be done 2 time ! + unless ($empty) { + print $q->start_table({-class => 'sme-border'}), "\n "; + if ( $MXStatus ) { + my $button = "" ; + $button .= $self->localise('BUTTON_LABEL_STOP_SERVICE') ; + $button .= "" ; + print $q->Tr( + esmith::cgi::genSmallCell( $q, + "\""localise('ENABLED') . "\">" ) , + esmith::cgi::genSmallCell( $q, + $self->localise('SERVICE_RUNNING') ), " ", + esmith::cgi::genSmallCell( $q, + $button ),"\n ", + ),"\n" ; + } else { + my $button = "" ; + $button .= $self->localise('BUTTON_LABEL_START_SERVICE') ; + $button .= "" ; + print $q->Tr( + esmith::cgi::genSmallCell( $q, + "\""localise('DISABLED') . "\">" ) , + esmith::cgi::genSmallCell( $q, + $self->localise('SERVICE_STOPPED') ), " ", + esmith::cgi::genSmallCell( $q, + $button ),"\n ", + ),"\n" ; + } + } + # the 'create button should ever be here ;-) + print $q->end_table,"\n"; + print $q->Tr( + $q->td({-colspan => 2 }, + $q->p(" "), + ), + ),"\n" ; + print $q->Tr( + $q->td({-colspan => 2 }, + $q->p("" , + $self->localise('BUTTON_LABEL_CREATE') , + ""))),"\n" ; + + unless ($empty) { + print $q->Tr( + $q->td({-colspan => 2}, + $q->p($self->localise('SHOW_MXBACKUP')))),"\n"; + + my $q = $self->{cgi}; + print ""; + print $q->start_table({-class => 'sme-border'}), "\n "; + print $q->Tr( + esmith::cgi::genSmallCell( + $q, + $self->localise('LABEL_NAME'), + "header" + ), " ", + esmith::cgi::genSmallCell( + $q, + $self->localise('LABEL_HOST_DOMAIN'), + "header", + ), " ", + esmith::cgi::genSmallCell( + $q, + $self->localise('ACTION'), + "header", + ), "\n ", + ); + foreach my $name ( sort { ( join ( "\.", reverse( split /\./, $a) ) ) + cmp + ( join( "\.", reverse( split /\./, $b ) ) ) } + keys %MXValues ) { + my $dom = $self->localise('HOST') ; + $dom = $self->localise('DOMAIN') if ( $MXValues{ $name } ) ; + print $q->Tr( + esmith::cgi::genSmallCell($q, $name), + " ", + esmith::cgi::genSmallCell($q, $dom || ' '), + " ", + esmith::cgi::genSmallCell( + $q, + $q->a({href => $q->url(-absolute => 1) + . "?page=3&Next=Next&name=$name&" + . "host_domain=$dom"}, + $self->localise('REMOVE')) + ), + "\n ", + ); + } + print $q->end_table,"\n"; + print ''; + + } + else { + print '
' . + $self->localise('NO_MXBACKUP') . + ''; + } + return undef; + +} + + +=head2 validate_name + +This method try to validate the name of domains 'MX Backuped' + +=cut + +sub validate_name { + my $self = shift ; + my $name = $self->{cgi}->param('name') ; + if ( ! ( $name =~ /^([a-z0-9\-]+\.){1,4}[a-z]{2,5}$/i ) ) { + # A valid name is 1 to four word + dot, then a word between 2 and 5 characters + $self->debug_msg("the name $name don't seems to be a valid host or domain name"); + return $self->localise('ERR_BADNAME'); + } + else + { return 'OK'; } +} + +=head2 mxbackup_enable_disable + +This method change the status of MXBackup + +=cut + +sub mxbackup_enable_disable { + my $self = shift ; + $self->debug_msg("Start of sub 'mxbackup_enable_disable'.") ; + my $current = $self->{cgi}->param('Current') ; + $self->debug_msg("'mxbackup_enable_disable' : \$current = $current") ; + my $MX = $mdb->get('mxbackup') + || ($self->error('ERR_NO_MXBACKUP_RECORD') and return undef); + if ( $current ) { + $MX->set_prop("status", "disabled") ; + $self->debug_msg("'mxbackup_enable_disable' : mxbackup disabled.") ; + } else { + $MX->set_prop("status", "enabled") ; + $self->debug_msg("'mxbackup_enable_disable' : mxbackup enabled.") ; + } + esmith::templates::processTemplate + ( { + TEMPLATE_PATH => "/var/qmail/control/rcpthosts", + PERMS => 0644, + UID => "root", + GID => "root", + } ); + $self->debug_msg("'mxbackup_enable_disable' : rcpthost file regenerated.") ; + + esmith::templates::processTemplate ( + { + TEMPLATE_PATH => "/var/qmail/control/smtproutes", + PERMS => 0644, + UID => "root", + GID => "root", + } ); + $self->debug_msg("'mxbackup_enable_disable' : smtproutes file regenerated.") ; + # arg ! ugly ! I should do that all by an action... how bad ! + # but it's a 'q&d patch' : the whole must be changed in a sme7 mode. + if ( -e "/var/service/qpsmtpd/config/goodrcptto" ) { #SME 7 server + esmith::templates::processTemplate + ( { + TEMPLATE_PATH => "/var/service/qpsmtpd/config/goodrcptto", + } ); + $self->debug_msg("'mxbackup_enable_disable' : goodrcptto file regenerated.") ; + } + $self->debug_msg("'mxbackup_enable_disable' : \$self->wherenext(\"Finished\");") ; + $self->wherenext("Finished"); + $self->debug_msg("'mxbackup_enable_disable' : \$self->success();") ; + $self->success(); + return undef ; +} + +=head2 display_summary_create + +This is a wrapper for the display_summary method, to call it in create mode. + +=cut + +sub display_summary_create { + my $self = shift; + $self->display_summary('create'); +} + +=head2 display_summary_remove + +This is a wrapper for the display_summary method, to call it in remove mode. + +=cut + +sub display_summary_remove { + my $self = shift; + $self->display_summary('remove'); +} + +=head2 display_summary + +This method's purpose is to display a summary of the rule about to be added. + +=cut + +sub display_summary { + my $self = shift; + my $mode = shift; + my $save = $self->localise('SAVE'); + my $cancel = $self->localise('CANCEL'); + my $output = ""; + my $q = $self->{cgi}; + $self->debug_msg("start of method"); + + print ""; + + my $description = ""; + if ($mode eq 'create') { + $description = $self->localise('SUMMARY_ADD_DESC'); + } + elsif ($mode eq 'remove') { + $description = $self->localise('SUMMARY_REMOVE_DESC'); + } + else { + $self->error('ERR_UNSUPPORTED_MODE'); + return undef; + } + + print $q->p($description); + + print $q->start_table({-class => 'sme-border'}); + foreach my $tablearrayref ( + [$self->localise('LABEL_NAME') + => $q->param('name')], + [$self->localise('LABEL_HOST_DOMAIN') + => $self->localise($q->param('host_domain'))] + ) + { + print $q->Tr($q->td({-class => 'sme-border-right'}, $tablearrayref->[0]), + esmith::cgi::genSmallCell($q, $tablearrayref->[1]), + "\n " + ); + } + print $q->end_table, "\n"; + if ($mode eq 'create') { + print $q->table({-width => '100%'}, $q->Tr($q->th({-class => 'sme-layout'}, + $q->submit(-name => 'apply', + -value => $self->localise('APPLY')), + ' ', + $q->submit(-name => 'cancel', + -value => $self->localise('CANCEL'))))); + } + elsif ($mode eq 'remove') { + print $q->table({-width => '100%'}, $q->Tr($q->th({-class => 'sme-layout'}, + $q->submit( -name => 'remove', + -value => $self->localise('REMOVE')), + ' ', + $q->submit( -name => 'cancel', + -value => $self->localise('CANCEL'))))); + } + else { + $self->error('ERR_UNSUPPORTED_MODE'); + return undef; + } + $self->debug_msg("returning"); + + print ""; + return undef; +} + +=head2 remove_rule + +This method is a remove wrapper for the modify method. + +=cut + +sub remove_rule { + my $self = shift; + $self->modify('remove'); +} + +=head2 create_new + +This method is a create wrapper for the modify method. + +=cut + +sub create_new { + my $self = shift; + $self->modify('create'); +} + +=head2 modify + +This method's purpose is to add or remove rules from the database, and then +cause the firewall rules to update. + +=cut + +sub modify { + no strict 'refs'; + my $self = shift; + my $mode = shift; + my $q = $self->{cgi}; + $self->debug_msg("at start of modify method"); + + # If the cancel button was pressed, just go back to the start page. + if ($q->param("cancel")) { + $self->debug_msg("the cancel button was pressed"); + $self->wherenext("Front"); + } + else { + # Save the changes. + my $name = $q->param('name'); + my $host_domain = $q->param('host_domain'); + my $tpe = 0 ; + $tpe = 1 if ($host_domain eq 'DOMAIN' ); + + $self->debug_msg("name is $name"); + $self->debug_msg("tpe is $tpe"); + $self->debug_msg("host_domain is $host_domain"); + + my $MX = $mdb->get('mxbackup') + || ($self->error('ERR_NO_MXBACKUP_RECORD') and return undef); + $self->debug_msg("fetching name property from mxbackup record"); + my %MXValues = split /,/, $MX->prop("name"); + $self->debug_msg("the db property is " . join ( ",", %MXValues ) ); + + if ($mode eq 'create') { + $self->debug_msg("we are in create mode"); + my $newrule = "$name,$tpe"; + $self->debug_msg("new rule is $newrule"); + $MXValues{ $name } = $tpe ; + $self->debug_msg("MXValues now contains : " . join ( ",", %MXValues ) ); + } + elsif ($mode eq 'remove') { + $self->debug_msg("we are in remove mode"); + if ( exists $MXValues{ $name } ) { + delete $MXValues{ $name } + } + } + + $self->debug_msg("We're now writing : " . join ( ",", %MXValues ) ); + $MX->set_prop("name", ( join ",", %MXValues ) ); + # if %MXValues is empty, disable the MX Backup feature, enable otherwise + if ( ( join ",", %MXValues ) eq "" ) { + $MX->set_prop("status", "disabled") + } else { + $MX->set_prop("status", "enabled") + } + esmith::templates::processTemplate + ( { + TEMPLATE_PATH => "/var/qmail/control/rcpthosts", + PERMS => 0644, + UID => "root", + GID => "root", + } ); + $self->debug_msg("rcpthost file regenerated.") ; + + esmith::templates::processTemplate ( + { + TEMPLATE_PATH => "/var/qmail/control/smtproutes", + PERMS => 0644, + UID => "root", + GID => "root", + } ); + $self->debug_msg("smtproutes file regenerated.") ; + # arg ! ugly ! I should do that all by an action... how bad ! + # but it's a 'q&d patch' : the whole must be changed in a sme7 mode. + if ( -e "/var/service/qpsmtpd/config/goodrcptto" ) { #SME 7 server + esmith::templates::processTemplate + ( { + TEMPLATE_PATH => "/var/service/qpsmtpd/config/goodrcptto", + } ); + $self->debug_msg("'mxbackup_enable_disable' : goodrcptto file regenerated.") ; + } + + $self->wherenext("Finished"); + $self->success(); + } + $self->debug_msg("at end of modify method"); + return undef; +} + +1; diff --git a/smeserver-mxbackup.spec b/smeserver-mxbackup.spec new file mode 100644 index 0000000..fe9ec3e --- /dev/null +++ b/smeserver-mxbackup.spec @@ -0,0 +1,154 @@ +Summary: MX Backup configuration panel for SME Server +%define name smeserver-mxbackup +Name: %{name} +%define version 0.3 +%define release 4 +Version: %{version} +Release: %{release} +License: GPL +Group: Networking/Daemons +Source: %{name}-%{version}.tar.xz +Packager: Pascal Schirrmann +BuildRoot: /var/tmp/%{name}-%{version}-%{release}-buildroot +BuildRequires: e-smith-devtools +BuildArchitectures: noarch +Requires: smeserver-release >= 10 +Requires: e-smith-email >= 5.6.0 +Requires: e-smith-formmagick >= 2.6.0 +Requires: e-smith-base +Requires: e-smith-qmail >= 2.6.0 +AutoReqProv: no + +%description +Adds a MX Backup Configuration panel to the SME server-manager. + +%changelog +* Sat Sep 07 2024 cvs2git.sh aka Brian Read 0.3-4.sme +- Roll up patches and move to git repo [SME: 12338] + +* Sat Sep 07 2024 BogusDateBot +- Eliminated rpmbuild "bogus date" warnings due to inconsistent weekday, + by assuming the date is correct and changing the weekday. + +* Fri Sep 06 2024 Terry Fage 0.3-3.sme +- apply local 2024-09-06.patch + +* Fri Nov 11 2022 Jean-Philippe Pialasse 0.3-2.sme +- apply local 2022-11-11 patch + +* Wed Aug 31 2022 John Crisp 0.3-1.sme +- First import to Koozali SME v10 [SME: 12162] + +* Tue Jan 28 2020 John Crisp 0.2-1.sme +- Update createlinks file +- Remove unnecessary apostrophe +- Updated readme +- Comment out debugging in pm file +- Updating for v9 +- Dropped the UTF-8 +- Modify the vendor_perl directory + +* Sun Apr 20 2008 Pascal Schirrmann +- This is a fork of smeserver-mxbackup, with utf-8 charset. + As long as the two versions will exist, the sequence number will stay the same. + I just increment the version number for the tracker. +[0.1.0-03] +* Wed Apr 26 2006 Pascal Schirrmann +- Change default to host for any new creation +[0.1.0-02] +* Wed Apr 26 2006 Pascal Schirrmann +- Fast port to SME 7 : a qpsmtpd configuration file need + to be altered to accept incoming mails for mx-backuped domains +[0.1.0-01] +* Tue May 11 2004 Pascal Schirrmann +- New : if the MX-Backup server use a 'smart host' it + still use DNS for the 'MX-Backuped Domains' +[0.1.0-00] +* Thu Apr 22 2004 Pascal Schirrmann +- Unable to set a domain containing a Zero !!! +[0.0.4-00] +* Mon Mar 08 2004 Pascal Schirrmann +- This RPM can only work on SME 6.0 and later, adds a + require in the 'spec' file +[0.0.3-01] +* Sun Mar 07 2004 Pascal Schirrmann +- Add some nice stuff, ligths and so on... + Sounds are awaited for a far future release ;-) +[0.0.3-00] +* Sat Mar 06 2004 Pascal Schirrmann +- My database conception was not very 'SME-aware' + majors change in the database storage modes. +[0.0.2-00] +* Wed Mar 03 2004 Pascal Schirrmann +- some cosmetics change on the package name to be nearer + of contribs.org naming systems +[0.0.1-01] +* Fri Feb 27 2004 Pascal Schirrmann +- initial release +[0.0.1-00] + +%prep +%setup + +%build +perl createlinks + +%install +rm -rf $RPM_BUILD_ROOT +(cd root ; find . -depth -print | cpio -dump $RPM_BUILD_ROOT) +rm -f e-smith-%{version}-filelist +/sbin/e-smith/genfilelist $RPM_BUILD_ROOT > %{name}-%{version}-filelist + +%clean +cd .. +rm -rf %{name}-%{version} + +%files -f %{name}-%{version}-filelist +%defattr(-,root,root) + +%pre + +%post +# SME 6 comes with a 'left panel cache' to improve the server panel display speed +# But I haven't found a nice way to update this cache +# So I chose to do this update here. +if [ -x /etc/e-smith/events/actions/navigation-conf ] +then + echo "Rebuilding Web Server Manager Left Panel Cache ... Can take up to a minute." + /etc/e-smith/events/actions/navigation-conf + echo "Done." +fi +if [ -x /etc/e-smith/events/actions/initialize-default-databases ] +then + echo "Setting defaults values in SME configuration database, if needed. Don't change any existing configuration." + /etc/e-smith/events/actions/initialize-default-databases + echo "Done." +fi +# regenerate the rcpthosts file, in case of an upgrade +# If this is a new install, this will change nothing, because +# status = disabled +echo "Regenerating the config file..." +/sbin/e-smith/expand-template /var/qmail/control/rcpthosts +/sbin/e-smith/expand-template /var/qmail/control/smtproutes +if [ -e /var/service/qpsmtpd/config/goodrcptto ] +then + /sbin/e-smith/expand-template /var/service/qpsmtpd/config/goodrcptto +fi +# moving 'light' in correct place. +# these lights cannot be installed by the RPM : in case someone +# installs the same lights, there will be a conflict. +/bin/mv -f /etc/e-smith/GreenLight.jpg /etc/e-smith/web/common/ +/bin/mv -f /etc/e-smith/RedLight.jpg /etc/e-smith/web/common/ +echo "Installation finished." + +%preun + +%postun +# rollback the rcpthosts without mxbackup entries +echo "Revert the system as a non MX Backup system." +/sbin/e-smith/expand-template /var/qmail/control/rcpthosts +/sbin/e-smith/expand-template /var/qmail/control/smtproutes +if [ -e /var/service/qpsmtpd/config/goodrcptto ] +then + /sbin/e-smith/expand-template /var/service/qpsmtpd/config/goodrcptto +fi