[DRE-commits] [schleuder] 07/52: New upstream version 3.0.0~beta9
Georg Faerber
georg-alioth-guest at moszumanska.debian.org
Mon Feb 6 11:21:18 UTC 2017
This is an automated email from the git hooks/post-receive script.
georg-alioth-guest pushed a commit to branch master
in repository schleuder.
commit 06e4218e96fe16da41c362c92656b7d4413b5d23
Author: Georg Faerber <georg at riseup.net>
Date: Tue Dec 6 19:16:27 2016 +0100
New upstream version 3.0.0~beta9
---
.gitignore | 1 +
.travis.yml | 2 +
CHANGELOG.md | 94 +++++
CONTRIBUTING.md | 14 +
LICENSE.txt | 674 ++++++++++++++++++++++++++++++++++
README.md | 32 +-
Rakefile | 61 +--
etc/schleuder.yml | 3 +
gems/schleuder-3.0.0.beta8.tar.gz | Bin 0 -> 154626 bytes
gems/schleuder-3.0.0.beta8.tar.gz.sig | Bin 0 -> 564 bytes
lib/schleuder.rb | 2 +-
lib/schleuder/cli.rb | 24 +-
lib/schleuder/conf.rb | 6 +-
lib/schleuder/list.rb | 2 +-
lib/schleuder/listlogger.rb | 3 +-
lib/schleuder/mail/message.rb | 11 +-
man/schleuder-api-daemon.8 | 68 ++++
man/schleuder-api-daemon.8.ron | 61 +++
man/schleuder.8 | 187 ++++------
man/schleuder.8.ron | 23 +-
schleuder.gemspec | 6 +-
spec/schleuder/list_spec.rb | 16 +-
spec/schleuder/subscription_spec.rb | 4 +-
23 files changed, 1107 insertions(+), 187 deletions(-)
diff --git a/.gitignore b/.gitignore
index 00ada9b..fde347c 100644
--- a/.gitignore
+++ b/.gitignore
@@ -3,3 +3,4 @@ vendor
*.swp
db/*.sqlite3
testmails/*
+.pc/
diff --git a/.travis.yml b/.travis.yml
index 7a9f875..6eaad2b 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -1,5 +1,7 @@
language: ruby
rvm:
+ - 2.1
+ - 2.2
- 2.3
before_install:
- gem install bundler
diff --git a/CHANGELOG.md b/CHANGELOG.md
new file mode 100644
index 0000000..c737725
--- /dev/null
+++ b/CHANGELOG.md
@@ -0,0 +1,94 @@
+Change Log
+==========
+
+This project adheres to [Semantic Versioning](http://semver.org/).
+
+The format of this file is based on [Keep a Changelog](http://keepachangelog.com/).
+
+## [Unreleased]
+
+### Added
+
+ * Include tarball into release.
+ * Make basedir of list-logs configurable (`listlogs_dir`). No operational change with the default value.
+
+### Changed
+
+ * Improved documentation.
+
+## [3.0.0.beta8] / 2016-11-27
+
+### Changed
+
+ * Add network and local-filesystem as dependencies in systemd-unit-file.
+ * Improved documentation.
+
+### Fixed
+
+ * Declare dependency on thin.
+
+
+## [3.0.0.beta7] / 2016-11-23
+
+### Added
+
+ * `man`-page for schleuder(8).
+ * schleuder-api-daemon: optionally use TLS.
+ * schleuder-api-daemon: authenticate client by API-key if TLS is used.
+
+### Changed
+
+ * Sign git-tags, gems, and tarballs as 0xB3D190D5235C74E1907EACFE898F2C91E2E6E1F3.
+ * Rename schleuderd to schleuder-api-daemon.
+ * schleuder-api-daemon: bind to `localhost` by default.
+ * schleuder-api-daemon: changed name of `bind` config option to `host`.
+ * schleuder-api-daemon: return 204 if not content is being sent along.
+ * Refactor and improve model validations.
+
+### Fixed
+
+ * Fixed creating lists.
+ * Fixed default config.
+ * Log errors to syslog-logger in case of problems with list-dir.
+
+
+## [3.0.0.beta6] / 2016-11-13
+
+### Added
+
+ * Add `-v`, `--version` arguments to CLI.
+ * New model validators.
+ * Translations (de, en) and better wording for validation error messages.
+ * Specs (test-cases) for the list model.
+ * Use Travis to automate testing.
+ * Test listname to be a valid email address before creating list.
+ * A simple contribution guide.
+ * Check that GnuPG >= 2.0 is being used.
+ * Enable to specify path to gpg-executable in GPGBIN environment variable.
+ * A simple schleuder-only MTA to help with development.
+
+### Changed
+
+ * schleuderd: use GET instead of OPTIONS to work around bug in ruby 2.1.
+ * Allow "inline"-pgp for request-messages (mail-gpg 0.2.7 fixed their issue).
+
+### Fixed
+
+ * Fix testing nested messages for emptiness.
+ * Fix bouncing a message if it was found to be empty.
+ * Fix truncated 'adding UID failed' message (transported via HTTP-headers).
+
+## ...
+
+---------
+
+Template, please ignore:
+
+## [x.x.x] / YYYY-MM-DD
+### Added
+### Changed
+### Deprecated
+### Removed
+### Fixed
+### Security
+
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
new file mode 100644
index 0000000..f2d2a03
--- /dev/null
+++ b/CONTRIBUTING.md
@@ -0,0 +1,14 @@
+Contributing
+============
+
+To contribute please follow this workflow:
+
+1. Talk to us! E.g. create an issue about your idea or problem.
+2. Fork the repository and work in a meaningful named branch that is based off of our "master".
+3. Commit in rather small chunks but don't split depending code across commits. Please write sensible commit messages.
+4. If in doubt request feedback from us!
+5. When finished create a merge request.
+
+
+Thank you for your interest!
+
diff --git a/LICENSE.txt b/LICENSE.txt
new file mode 100644
index 0000000..94a9ed0
--- /dev/null
+++ b/LICENSE.txt
@@ -0,0 +1,674 @@
+ GNU GENERAL PUBLIC LICENSE
+ Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+ Preamble
+
+ The GNU General Public License is a free, copyleft license for
+software and other kinds of works.
+
+ The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works. By contrast,
+the GNU General Public License is intended to guarantee your freedom to
+share and change all versions of a program--to make sure it remains free
+software for all its users. We, the Free Software Foundation, use the
+GNU General Public License for most of our software; it applies also to
+any other work released this way by its authors. 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
+them 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 prevent others from denying you
+these rights or asking you to surrender the rights. Therefore, you have
+certain responsibilities if you distribute copies of the software, or if
+you modify it: responsibilities to respect the freedom of others.
+
+ For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must pass on to the recipients the same
+freedoms that you received. 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.
+
+ Developers that use the GNU GPL protect your rights with two steps:
+(1) assert copyright on the software, and (2) offer you this License
+giving you legal permission to copy, distribute and/or modify it.
+
+ For the developers' and authors' protection, the GPL clearly explains
+that there is no warranty for this free software. For both users' and
+authors' sake, the GPL requires that modified versions be marked as
+changed, so that their problems will not be attributed erroneously to
+authors of previous versions.
+
+ Some devices are designed to deny users access to install or run
+modified versions of the software inside them, although the manufacturer
+can do so. This is fundamentally incompatible with the aim of
+protecting users' freedom to change the software. The systematic
+pattern of such abuse occurs in the area of products for individuals to
+use, which is precisely where it is most unacceptable. Therefore, we
+have designed this version of the GPL to prohibit the practice for those
+products. If such problems arise substantially in other domains, we
+stand ready to extend this provision to those domains in future versions
+of the GPL, as needed to protect the freedom of users.
+
+ Finally, every program is threatened constantly by software patents.
+States should not allow patents to restrict development and use of
+software on general-purpose computers, but in those that do, we wish to
+avoid the special danger that patents applied to a free program could
+make it effectively proprietary. To prevent this, the GPL assures that
+patents cannot be used to render the program non-free.
+
+ The precise terms and conditions for copying, distribution and
+modification follow.
+
+ TERMS AND CONDITIONS
+
+ 0. Definitions.
+
+ "This License" refers to version 3 of the GNU General Public License.
+
+ "Copyright" also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.
+
+ "The Program" refers to any copyrightable work licensed under this
+License. Each licensee is addressed as "you". "Licensees" and
+"recipients" may be individuals or organizations.
+
+ To "modify" a work means to copy from or adapt all or part of the work
+in a fashion requiring copyright permission, other than the making of an
+exact copy. The resulting work is called a "modified version" of the
+earlier work or a work "based on" the earlier work.
+
+ A "covered work" means either the unmodified Program or a work based
+on the Program.
+
+ To "propagate" a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for
+infringement under applicable copyright law, except executing it on a
+computer or modifying a private copy. Propagation includes copying,
+distribution (with or without modification), making available to the
+public, and in some countries other activities as well.
+
+ To "convey" a work means any kind of propagation that enables other
+parties to make or receive copies. Mere interaction with a user through
+a computer network, with no transfer of a copy, is not conveying.
+
+ An interactive user interface displays "Appropriate Legal Notices"
+to the extent that it includes a convenient and prominently visible
+feature that (1) displays an appropriate copyright notice, and (2)
+tells the user that there is no warranty for the work (except to the
+extent that warranties are provided), that licensees may convey the
+work under this License, and how to view a copy of this License. If
+the interface presents a list of user commands or options, such as a
+menu, a prominent item in the list meets this criterion.
+
+ 1. Source Code.
+
+ The "source code" for a work means the preferred form of the work
+for making modifications to it. "Object code" means any non-source
+form of a work.
+
+ A "Standard Interface" means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of
+interfaces specified for a particular programming language, one that
+is widely used among developers working in that language.
+
+ The "System Libraries" of an executable work include anything, other
+than the work as a whole, that (a) is included in the normal form of
+packaging a Major Component, but which is not part of that Major
+Component, and (b) serves only to enable use of the work with that
+Major Component, or to implement a Standard Interface for which an
+implementation is available to the public in source code form. A
+"Major Component", in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to
+produce the work, or an object code interpreter used to run it.
+
+ The "Corresponding Source" for a work in object code form means all
+the source code needed to generate, install, and (for an executable
+work) run the object code and to modify the work, including scripts to
+control those activities. However, it does not include the work's
+System Libraries, or general-purpose tools or generally available free
+programs which are used unmodified in performing those activities but
+which are not part of the work. For example, Corresponding Source
+includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require,
+such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+ The Corresponding Source need not include anything that users
+can regenerate automatically from other parts of the Corresponding
+Source.
+
+ The Corresponding Source for a work in source code form is that
+same work.
+
+ 2. Basic Permissions.
+
+ All rights granted under this License are granted for the term of
+copyright on the Program, and are irrevocable provided the stated
+conditions are met. This License explicitly affirms your unlimited
+permission to run the unmodified Program. The output from running a
+covered work is covered by this License only if the output, given its
+content, constitutes a covered work. This License acknowledges your
+rights of fair use or other equivalent, as provided by copyright law.
+
+ You may make, run and propagate covered works that you do not
+convey, without conditions so long as your license otherwise remains
+in force. You may convey covered works to others for the sole purpose
+of having them make modifications exclusively for you, or provide you
+with facilities for running those works, provided that you comply with
+the terms of this License in conveying all material for which you do
+not control copyright. Those thus making or running the covered works
+for you must do so exclusively on your behalf, under your direction
+and control, on terms that prohibit them from making any copies of
+your copyrighted material outside their relationship with you.
+
+ Conveying under any other circumstances is permitted solely under
+the conditions stated below. Sublicensing is not allowed; section 10
+makes it unnecessary.
+
+ 3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+ No covered work shall be deemed part of an effective technological
+measure under any applicable law fulfilling obligations under article
+11 of the WIPO copyright treaty adopted on 20 December 1996, or
+similar laws prohibiting or restricting circumvention of such
+measures.
+
+ When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such circumvention
+is effected by exercising rights under this License with respect to
+the covered work, and you disclaim any intention to limit operation or
+modification of the work as a means of enforcing, against the work's
+users, your or third parties' legal rights to forbid circumvention of
+technological measures.
+
+ 4. Conveying Verbatim Copies.
+
+ You may convey 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;
+keep intact all notices stating that this License and any
+non-permissive terms added in accord with section 7 apply to the code;
+keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
+
+ You may charge any price or no price for each copy that you convey,
+and you may offer support or warranty protection for a fee.
+
+ 5. Conveying Modified Source Versions.
+
+ You may convey a work based on the Program, or the modifications to
+produce it from the Program, in the form of source code under the
+terms of section 4, provided that you also meet all of these conditions:
+
+ a) The work must carry prominent notices stating that you modified
+ it, and giving a relevant date.
+
+ b) The work must carry prominent notices stating that it is
+ released under this License and any conditions added under section
+ 7. This requirement modifies the requirement in section 4 to
+ "keep intact all notices".
+
+ c) You must license the entire work, as a whole, under this
+ License to anyone who comes into possession of a copy. This
+ License will therefore apply, along with any applicable section 7
+ additional terms, to the whole of the work, and all its parts,
+ regardless of how they are packaged. This License gives no
+ permission to license the work in any other way, but it does not
+ invalidate such permission if you have separately received it.
+
+ d) If the work has interactive user interfaces, each must display
+ Appropriate Legal Notices; however, if the Program has interactive
+ interfaces that do not display Appropriate Legal Notices, your
+ work need not make them do so.
+
+ A compilation of a covered work with other separate and independent
+works, which are not by their nature extensions of the covered work,
+and which are not combined with it such as to form a larger program,
+in or on a volume of a storage or distribution medium, is called an
+"aggregate" if the compilation and its resulting copyright are not
+used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit. Inclusion of a covered work
+in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
+
+ 6. Conveying Non-Source Forms.
+
+ You may convey a covered work in object code form under the terms
+of sections 4 and 5, provided that you also convey the
+machine-readable Corresponding Source under the terms of this License,
+in one of these ways:
+
+ a) Convey the object code in, or embodied in, a physical product
+ (including a physical distribution medium), accompanied by the
+ Corresponding Source fixed on a durable physical medium
+ customarily used for software interchange.
+
+ b) Convey the object code in, or embodied in, a physical product
+ (including a physical distribution medium), accompanied by a
+ written offer, valid for at least three years and valid for as
+ long as you offer spare parts or customer support for that product
+ model, to give anyone who possesses the object code either (1) a
+ copy of the Corresponding Source for all the software in the
+ product that is covered by this License, on a durable physical
+ medium customarily used for software interchange, for a price no
+ more than your reasonable cost of physically performing this
+ conveying of source, or (2) access to copy the
+ Corresponding Source from a network server at no charge.
+
+ c) Convey individual copies of the object code with a copy of the
+ written offer to provide the Corresponding Source. This
+ alternative is allowed only occasionally and noncommercially, and
+ only if you received the object code with such an offer, in accord
+ with subsection 6b.
+
+ d) Convey the object code by offering access from a designated
+ place (gratis or for a charge), and offer equivalent access to the
+ Corresponding Source in the same way through the same place at no
+ further charge. You need not require recipients to copy the
+ Corresponding Source along with the object code. If the place to
+ copy the object code is a network server, the Corresponding Source
+ may be on a different server (operated by you or a third party)
+ that supports equivalent copying facilities, provided you maintain
+ clear directions next to the object code saying where to find the
+ Corresponding Source. Regardless of what server hosts the
+ Corresponding Source, you remain obligated to ensure that it is
+ available for as long as needed to satisfy these requirements.
+
+ e) Convey the object code using peer-to-peer transmission, provided
+ you inform other peers where the object code and Corresponding
+ Source of the work are being offered to the general public at no
+ charge under subsection 6d.
+
+ A separable portion of the object code, whose source code is excluded
+from the Corresponding Source as a System Library, need not be
+included in conveying the object code work.
+
+ A "User Product" is either (1) a "consumer product", which means any
+tangible personal property which is normally used for personal, family,
+or household purposes, or (2) anything designed or sold for incorporation
+into a dwelling. In determining whether a product is a consumer product,
+doubtful cases shall be resolved in favor of coverage. For a particular
+product received by a particular user, "normally used" refers to a
+typical or common use of that class of product, regardless of the status
+of the particular user or of the way in which the particular user
+actually uses, or expects or is expected to use, the product. A product
+is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent
+the only significant mode of use of the product.
+
+ "Installation Information" for a User Product means any methods,
+procedures, authorization keys, or other information required to install
+and execute modified versions of a covered work in that User Product from
+a modified version of its Corresponding Source. The information must
+suffice to ensure that the continued functioning of the modified object
+code is in no case prevented or interfered with solely because
+modification has been made.
+
+ If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as
+part of a transaction in which the right of possession and use of the
+User Product is transferred to the recipient in perpetuity or for a
+fixed term (regardless of how the transaction is characterized), the
+Corresponding Source conveyed under this section must be accompanied
+by the Installation Information. But this requirement does not apply
+if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has
+been installed in ROM).
+
+ The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or updates
+for a work that has been modified or installed by the recipient, or for
+the User Product in which it has been modified or installed. Access to a
+network may be denied when the modification itself materially and
+adversely affects the operation of the network or violates the rules and
+protocols for communication across the network.
+
+ Corresponding Source conveyed, and Installation Information provided,
+in accord with this section must be in a format that is publicly
+documented (and with an implementation available to the public in
+source code form), and must require no special password or key for
+unpacking, reading or copying.
+
+ 7. Additional Terms.
+
+ "Additional permissions" are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions.
+Additional permissions that are applicable to the entire Program shall
+be treated as though they were included in this License, to the extent
+that they are valid under applicable law. If additional permissions
+apply only to part of the Program, that part may be used separately
+under those permissions, but the entire Program remains governed by
+this License without regard to the additional permissions.
+
+ When you convey a copy of a covered work, you may at your option
+remove any additional permissions from that copy, or from any part of
+it. (Additional permissions may be written to require their own
+removal in certain cases when you modify the work.) You may place
+additional permissions on material, added by you to a covered work,
+for which you have or can give appropriate copyright permission.
+
+ Notwithstanding any other provision of this License, for material you
+add to a covered work, you may (if authorized by the copyright holders of
+that material) supplement the terms of this License with terms:
+
+ a) Disclaiming warranty or limiting liability differently from the
+ terms of sections 15 and 16 of this License; or
+
+ b) Requiring preservation of specified reasonable legal notices or
+ author attributions in that material or in the Appropriate Legal
+ Notices displayed by works containing it; or
+
+ c) Prohibiting misrepresentation of the origin of that material, or
+ requiring that modified versions of such material be marked in
+ reasonable ways as different from the original version; or
+
+ d) Limiting the use for publicity purposes of names of licensors or
+ authors of the material; or
+
+ e) Declining to grant rights under trademark law for use of some
+ trade names, trademarks, or service marks; or
+
+ f) Requiring indemnification of licensors and authors of that
+ material by anyone who conveys the material (or modified versions of
+ it) with contractual assumptions of liability to the recipient, for
+ any liability that these contractual assumptions directly impose on
+ those licensors and authors.
+
+ All other non-permissive additional terms are considered "further
+restrictions" within the meaning of section 10. If the Program as you
+received it, or any part of it, contains a notice stating that it is
+governed by this License along with a term that is a further
+restriction, you may remove that term. If a license document contains
+a further restriction but permits relicensing or conveying under this
+License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does
+not survive such relicensing or conveying.
+
+ If you add terms to a covered work in accord with this section, you
+must place, in the relevant source files, a statement of the
+additional terms that apply to those files, or a notice indicating
+where to find the applicable terms.
+
+ Additional terms, permissive or non-permissive, may be stated in the
+form of a separately written license, or stated as exceptions;
+the above requirements apply either way.
+
+ 8. Termination.
+
+ You may not propagate or modify a covered work except as expressly
+provided under this License. Any attempt otherwise to propagate or
+modify it is void, and will automatically terminate your rights under
+this License (including any patent licenses granted under the third
+paragraph of section 11).
+
+ However, if you cease all violation of this License, then your
+license from a particular copyright holder is reinstated (a)
+provisionally, unless and until the copyright holder explicitly and
+finally terminates your license, and (b) permanently, if the copyright
+holder fails to notify you of the violation by some reasonable means
+prior to 60 days after the cessation.
+
+ Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+ Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License. If your rights have been terminated and not permanently
+reinstated, you do not qualify to receive new licenses for the same
+material under section 10.
+
+ 9. Acceptance Not Required for Having Copies.
+
+ You are not required to accept this License in order to receive or
+run a copy of the Program. Ancillary propagation of a covered work
+occurring solely as a consequence of using peer-to-peer transmission
+to receive a copy likewise does not require acceptance. However,
+nothing other than this License grants you permission to propagate or
+modify any covered work. These actions infringe copyright if you do
+not accept this License. Therefore, by modifying or propagating a
+covered work, you indicate your acceptance of this License to do so.
+
+ 10. Automatic Licensing of Downstream Recipients.
+
+ Each time you convey a covered work, the recipient automatically
+receives a license from the original licensors, to run, modify and
+propagate that work, subject to this License. You are not responsible
+for enforcing compliance by third parties with this License.
+
+ An "entity transaction" is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations. If propagation of a covered
+work results from an entity transaction, each party to that
+transaction who receives a copy of the work also receives whatever
+licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if
+the predecessor has it or can get it with reasonable efforts.
+
+ You may not impose any further restrictions on the exercise of the
+rights granted or affirmed under this License. For example, you may
+not impose a license fee, royalty, or other charge for exercise of
+rights granted under this License, and you may not initiate litigation
+(including a cross-claim or counterclaim in a lawsuit) alleging that
+any patent claim is infringed by making, using, selling, offering for
+sale, or importing the Program or any portion of it.
+
+ 11. Patents.
+
+ A "contributor" is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based. The
+work thus licensed is called the contributor's "contributor version".
+
+ A contributor's "essential patent claims" are all patent claims
+owned or controlled by the contributor, whether already acquired or
+hereafter acquired, that would be infringed by some manner, permitted
+by this License, of making, using, or selling its contributor version,
+but do not include claims that would be infringed only as a
+consequence of further modification of the contributor version. For
+purposes of this definition, "control" includes the right to grant
+patent sublicenses in a manner consistent with the requirements of
+this License.
+
+ Each contributor grants you a non-exclusive, worldwide, royalty-free
+patent license under the contributor's essential patent claims, to
+make, use, sell, offer for sale, import and otherwise run, modify and
+propagate the contents of its contributor version.
+
+ In the following three paragraphs, a "patent license" is any express
+agreement or commitment, however denominated, not to enforce a patent
+(such as an express permission to practice a patent or covenant not to
+sue for patent infringement). To "grant" such a patent license to a
+party means to make such an agreement or commitment not to enforce a
+patent against the party.
+
+ If you convey a covered work, knowingly relying on a patent license,
+and the Corresponding Source of the work is not available for anyone
+to copy, free of charge and under the terms of this License, through a
+publicly available network server or other readily accessible means,
+then you must either (1) cause the Corresponding Source to be so
+available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner
+consistent with the requirements of this License, to extend the patent
+license to downstream recipients. "Knowingly relying" means you have
+actual knowledge that, but for the patent license, your conveying the
+covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that
+country that you have reason to believe are valid.
+
+ If, pursuant to or in connection with a single transaction or
+arrangement, you convey, or propagate by procuring conveyance of, a
+covered work, and grant a patent license to some of the parties
+receiving the covered work authorizing them to use, propagate, modify
+or convey a specific copy of the covered work, then the patent license
+you grant is automatically extended to all recipients of the covered
+work and works based on it.
+
+ A patent license is "discriminatory" if it does not include within
+the scope of its coverage, prohibits the exercise of, or is
+conditioned on the non-exercise of one or more of the rights that are
+specifically granted under this License. You may not convey a covered
+work if you are a party to an arrangement with a third party that is
+in the business of distributing software, under which you make payment
+to the third party based on the extent of your activity of conveying
+the work, and under which the third party grants, to any of the
+parties who would receive the covered work from you, a discriminatory
+patent license (a) in connection with copies of the covered work
+conveyed by you (or copies made from those copies), or (b) primarily
+for and in connection with specific products or compilations that
+contain the covered work, unless you entered into that arrangement,
+or that patent license was granted, prior to 28 March 2007.
+
+ Nothing in this License shall be construed as excluding or limiting
+any implied license or other defenses to infringement that may
+otherwise be available to you under applicable patent law.
+
+ 12. No Surrender of Others' Freedom.
+
+ If 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 convey a
+covered work so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you may
+not convey it at all. For example, if you agree to terms that obligate you
+to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this
+License would be to refrain entirely from conveying the Program.
+
+ 13. Use with the GNU Affero General Public License.
+
+ Notwithstanding any other provision of this License, you have
+permission to link or combine any covered work with a work licensed
+under version 3 of the GNU Affero General Public License into a single
+combined work, and to convey the resulting work. The terms of this
+License will continue to apply to the part which is the covered work,
+but the special requirements of the GNU Affero General Public License,
+section 13, concerning interaction through a network will apply to the
+combination as such.
+
+ 14. Revised Versions of this License.
+
+ The Free Software Foundation may publish revised and/or new versions of
+the GNU 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 that a certain numbered version of the GNU General
+Public License "or any later version" applies to it, you have the
+option of following the terms and conditions either of that numbered
+version or of any later version published by the Free Software
+Foundation. If the Program does not specify a version number of the
+GNU General Public License, you may choose any version ever published
+by the Free Software Foundation.
+
+ If the Program specifies that a proxy can decide which future
+versions of the GNU General Public License can be used, that proxy's
+public statement of acceptance of a version permanently authorizes you
+to choose that version for the Program.
+
+ Later license versions may give you additional or different
+permissions. However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
+
+ 15. Disclaimer of Warranty.
+
+ 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.
+
+ 16. Limitation of Liability.
+
+ IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
+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.
+
+ 17. Interpretation of Sections 15 and 16.
+
+ If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
+
+ 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
+state the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+ <one line to give the program's name and a brief idea of what it does.>
+ Copyright (C) <year> <name of author>
+
+ 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 3 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, see <http://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper mail.
+
+ If the program does terminal interaction, make it output a short
+notice like this when it starts in an interactive mode:
+
+ <program> Copyright (C) <year> <name of author>
+ This program 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, your program's commands
+might be different; for a GUI interface, you would use an "about box".
+
+ You should also get your employer (if you work as a programmer) or school,
+if any, to sign a "copyright disclaimer" for the program, if necessary.
+For more information on this, and how to apply and follow the GNU GPL, see
+<http://www.gnu.org/licenses/>.
+
+ The GNU 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 Lesser General
+Public License instead of this License. But first, please read
+<http://www.gnu.org/philosophy/why-not-lgpl.html>.
diff --git a/README.md b/README.md
index a68a0a0..028697d 100644
--- a/README.md
+++ b/README.md
@@ -44,7 +44,7 @@ Installing Schleuder
1. Download [the gem](https://git.codecoop.org/schleuder/schleuder3/raw/master/gems/schleuder-3.0.0.beta8.gem) and [the OpenPGP-signature](https://git.codecoop.org/schleuder/schleuder3/raw/master/gems/schleuder-3.0.0.beta8.gem.sig) and verify:
```
- gpg --recv-key 0x75C9B62688F93AC6574BDE7ED8A6EF816E1C6F25
+ gpg --recv-key 0xB3D190D5235C74E1907EACFE898F2C91E2E6E1F3
gpg --verify schleuder-3.0.0.beta8.gem.sig
```
@@ -60,6 +60,9 @@ Installing Schleuder
This creates neccessary directories, copies example configs, etc. If you see errors about missing write permissions please follow the advice given.
+For further information on setup and configuration please read <https://schleuder.nadir.org/docs/#setup>.
+
+
Command line usage
-----------------
@@ -77,14 +80,14 @@ E.g.:
List administration
-------------------
-You probably want to install
-[schleuder-cli](https://git.codecoop.org/schleuder/schleuder-cli), too.
-Otherwise you'd need to edit the database-records manually to change
-list-settings, subscribe addresses, etc.
+Please use
+[schleuder-cli](https://git.codecoop.org/schleuder/schleuder-cli) to create and
+manage lists from the command line.
Optionally consider installing
[schleuder-web](https://git.codecoop.org/schleuder/schleuder-web), the web
-interface for schleuder.
+interface for schleuder. It enables list-admins to manage their lists through
+the web instead of using [request-keywords](https://schleuder.nadir.org/docs/#subscription-and-key-management).
@@ -103,13 +106,16 @@ Testing
Contributing
------------
-To contribute please follow this workflow:
+Please see [CONTRIBUTING.md](CONTRIBUTING.md).
+
+
+License
+-------
+
+GNU GPL 3.0. Please see [LICENSE.txt](LICENSE.txt).
-1. Talk to us! E.g. create an issue about your idea or problem.
-2. Fork the repository and work in a meaningful named branch that is based off of our "master".
-3. Commit in rather small chunks but don't split depending code across commits. Please write sensible commit messages.
-4. If in doubt request feedback from us!
-5. When finished create a merge request.
+Alternative Download
+--------------------
-Thank you for your interest!
+Alternatively to the gem-files you can download the latest release as [a tarball](https://git.codecoop.org/schleuder/schleuder3/raw/master/gems/schleuder-3.0.0.beta8.tar.gz) and [its OpenPGP-signature](https://git.codecoop.org/schleuder/schleuder3/raw/master/gems/schleuder-3.0.0.beta8.tar.gz.sig).
diff --git a/Rakefile b/Rakefile
index fbdd31f..07b8297 100644
--- a/Rakefile
+++ b/Rakefile
@@ -1,10 +1,9 @@
project = 'schleuder'
require_relative "lib/#{project}.rb"
-version = Schleuder::VERSION
-tagname = "#{project}-#{version}"
-gpguid = 'schleuder at nadir.org'
-tarball = "#{tagname}.tar.gz"
+ at version = Schleuder::VERSION
+ at tagname = "#{project}-#{@version}"
+ at gpguid = 'schleuder at nadir.org'
load "active_record/railties/databases.rake"
@@ -20,24 +19,26 @@ end
# ActiveRecord requires this task to be present
Rake::Task.define_task("db:environment")
+def move_sign_and_add(file)
+ `mv -iv #{file} gems/`
+ `cd gems && gpg -u #{@gpguid} -b #{file}`
+ `git add gems/#{file}*`
+end
+
task :console do
exec "irb -r #{File.dirname(__FILE__)}/lib/schleuder.rb"
end
-desc 'Release a new version of schleuder.'
-task :release => [:git_tag, :gem, :publish_gem, :tarball, :wiki]
-
-task :gem => :check_version
+task :publish_gem => :website
task :git_tag => :check_version
-task :tarball => :check_version
desc "Build new version: git-tag and gem-file"
-task :new_version => [:gem, :edit_readme, :git_commit_version, :git_tag] do
+task :new_version => [:check_version, :gem, :tarball, :edit_readme, :git_commit_version, :git_tag] do
end
desc "Edit README"
task :edit_readme do
- puts "Please edit the README to refer to version #{version}"
+ puts "Please edit the README to refer to version #{@version}"
if system('gvim -f README.md')
`git add README.md`
else
@@ -47,40 +48,44 @@ end
desc 'git-tag HEAD as new version'
task :git_tag do
- `git tag -u #{gpguid} -s -m "Version #{version}" #{tagname}`
+ `git tag -u #{@gpguid} -s -m "Version #{@version}" #{@tagname}`
end
desc "Commit changes as new version"
task :git_commit_version do
`git add lib/#{project}/version.rb`
- `git commit -m "Version #{version} (README, gems)"`
+ `git commit -m "Version #{@version} (README, gems)"`
end
desc 'Build, sign and commit a gem-file.'
task :gem do
- gemfile = "#{tagname}.gem"
+ gemfile = "#{@tagname}.gem"
`gem build #{project}.gemspec`
- `mv -iv #{gemfile} gems/`
- `cd gems && gpg -u #{gpguid} -b #{gemfile}`
- `git add gems/#{gemfile}*`
+ move_sign_and_add(gemfile)
end
desc 'Publish gem-file to rubygems.org'
task :publish_gem do
- `gem push #{tagname}.gem`
+ puts "Really push #{@tagname}.gem to rubygems.org? [yN]"
+ if gets.match(/^y/i)
+ puts "Pushing..."
+ `gem push #{@tagname}.gem`
+ else
+ puts "Not pushed."
+ end
end
desc 'Build and sign a tarball'
task :tarball do
- `git archive --format tar.gz --prefix "#{tagname}/" -o #{tarball} #{tagname}`
- `gpg -u schleuder2 at nadir.org --detach-sign #{tarball}`
+ tarball = "#{@tagname}.tar.gz"
+ `git archive --format tar.gz --prefix "#{@tagname}/" -o #{tarball} #{@tagname}`
+ move_sign_and_add(tarball)
end
-desc 'Describe manual wiki-related release-tasks'
-task :wiki do
+desc 'Describe manual release-tasks'
+task :website do
puts "Please update the website:
- * Upload tarball+signature.
- * Edit download- and changelog-pages.
+ * Update changelog.
* Publish release-announcement.
"
end
@@ -88,11 +93,11 @@ end
desc 'Check if version-tag already exists'
task :check_version do
# Check if Schleuder::VERSION has been updated since last release
- if `git tag`.include?(tagname)
- $stderr.puts "Warning: Tag '#{tagname}' already exists. Did you forget to update #{project}/version.rb?"
- $stderr.print "Continue? [yN] "
+ if `git tag`.include?(@tagname)
+ $stderr.puts "Warning: Tag '#{@tagname}' already exists. Did you forget to update #{project}/version.rb?"
+ $stderr.print "Delete tag to continue? [yN] "
if $stdin.gets.match(/^y/i)
- `git tag -d #{tagname}`
+ `git tag -d #{@tagname}`
else
exit 1
end
diff --git a/etc/schleuder.yml b/etc/schleuder.yml
index 0a482eb..d2cad54 100644
--- a/etc/schleuder.yml
+++ b/etc/schleuder.yml
@@ -1,6 +1,9 @@
# Where are the list-directories stored (contain log-files and GnuPG-keyrings).
lists_dir: /var/schleuder/lists
+# Where to write list-logs. The actual log-file will be <lists_logs_base_dir>/<hostname>/<listname>/list.log.
+listlogs_dir: /var/schleuder/lists
+
# Schleuder reads plugins also from this directory.
plugins_dir: /etc/schleuder/plugins
diff --git a/gems/schleuder-3.0.0.beta8.tar.gz b/gems/schleuder-3.0.0.beta8.tar.gz
new file mode 100644
index 0000000..9336f84
Binary files /dev/null and b/gems/schleuder-3.0.0.beta8.tar.gz differ
diff --git a/gems/schleuder-3.0.0.beta8.tar.gz.sig b/gems/schleuder-3.0.0.beta8.tar.gz.sig
new file mode 100644
index 0000000..a7ed52e
Binary files /dev/null and b/gems/schleuder-3.0.0.beta8.tar.gz.sig differ
diff --git a/lib/schleuder.rb b/lib/schleuder.rb
index cfb452d..fe097c6 100644
--- a/lib/schleuder.rb
+++ b/lib/schleuder.rb
@@ -64,7 +64,7 @@ GPGME::Ctx.check_gpg_version
require Schleuder::Conf.database['adapter']
# TODO: Test if database is writable if sqlite.
-ActiveRecord::Base.establish_connection(Schleuder::Conf.databases[ENV["SCHLEUDER_ENV"]])
+ActiveRecord::Base.establish_connection(Schleuder::Conf.database)
ActiveRecord::Base.logger = Schleuder.logger
Mail.defaults do
diff --git a/lib/schleuder/cli.rb b/lib/schleuder/cli.rb
index aa55524..7a3ebe7 100644
--- a/lib/schleuder/cli.rb
+++ b/lib/schleuder/cli.rb
@@ -65,7 +65,10 @@ module Schleuder
desc 'install', "Set-up or update Schleuder environment (create folders, copy files, fill the database)."
def install
- %w[/var/schleuder/lists /etc/schleuder].each do |dir|
+ config_dir = Pathname.new(ENV['SCHLEUDER_CONFIG']).dirname
+ root_dir = Pathname.new(ENV['SCHLEUDER_ROOT'])
+
+ [Conf.lists_dir, config_dir].each do |dir|
dir = Pathname.new(dir)
if ! dir.exist?
if dir.dirname.writable?
@@ -76,8 +79,8 @@ module Schleuder
end
end
- Pathname.glob(Pathname.new(root_dir).join("etc").join("*.yml")).each do |file|
- target = Pathname.new("/etc/schleuder/").join(file.basename)
+ Pathname.glob(root_dir.join("etc").join("*.yml")).each do |file|
+ target = config_dir.join(file.basename)
if ! target.exist?
if target.dirname.writable?
FileUtils.cp file, target
@@ -87,6 +90,17 @@ module Schleuder
end
end
+ chmod_files = [
+ ENV['SCHLEUDER_CONFIG'],
+ ENV['SCHLEUDER_LIST_DEFAULTS'],
+ Conf.lists_dir
+ ]
+ if Conf.database['adapter'].match(/sqlite/)
+ chmod_files << Conf.database['database']
+ end
+
+ FileUtils.chmod_R('o-rwx', chmod_files)
+
if ActiveRecord::SchemaMigration.table_exists?
say `cd #{root_dir} && rake db:migrate`
else
@@ -239,10 +253,6 @@ Please notify the users and admins of this list of these changes.
KEYWORDS[keyword.downcase]
end.compact
end
-
- def root_dir
- Pathname.new(__FILE__).dirname.dirname.dirname.realpath
- end
end
end
end
diff --git a/lib/schleuder/conf.rb b/lib/schleuder/conf.rb
index dc8c197..da56984 100644
--- a/lib/schleuder/conf.rb
+++ b/lib/schleuder/conf.rb
@@ -16,6 +16,10 @@ module Schleuder
instance.config['lists_dir']
end
+ def self.listlogs_dir
+ instance.config['listlogs_dir']
+ end
+
def self.plugins_dir
instance.config['plugins_dir']
end
@@ -89,7 +93,7 @@ module Schleuder
def self.load_defaults(basename)
file = Pathname.new(ENV['SCHLEUDER_ROOT']).join("etc/#{basename}.yml")
if ! file.readable?
- raise RuntimError, "Error: '#{file}' is not a readable file."
+ raise RuntimeError, "Error: '#{file}' is not a readable file."
end
load_config_file(file)
end
diff --git a/lib/schleuder/list.rb b/lib/schleuder/list.rb
index 814b836..212ad6e 100644
--- a/lib/schleuder/list.rb
+++ b/lib/schleuder/list.rb
@@ -74,7 +74,7 @@ module Schleuder
end
def logfile
- @logfile ||= File.join(self.listdir, 'list.log')
+ @logfile ||= File.join(Conf.listlogs_dir, self.email.split('@').reverse, 'list.log')
end
def logger
diff --git a/lib/schleuder/listlogger.rb b/lib/schleuder/listlogger.rb
index 67939cd..8c4f281 100644
--- a/lib/schleuder/listlogger.rb
+++ b/lib/schleuder/listlogger.rb
@@ -2,7 +2,8 @@ module Schleuder
class Listlogger < ::Logger
include LoggerNotifications
def initialize(list)
- super(list.logfile, 'daily')
+ file = File.open(list.logfile, File::WRONLY | File::APPEND | File::CREAT, 0640)
+ super(file, 'daily')
@from = list.email
@adminaddresses = list.admins.map(&:email)
@level = ::Logger.const_get(list.log_level.upcase)
diff --git a/lib/schleuder/mail/message.rb b/lib/schleuder/mail/message.rb
index 923e9aa..8b59225 100644
--- a/lib/schleuder/mail/message.rb
+++ b/lib/schleuder/mail/message.rb
@@ -11,6 +11,11 @@ module Mail
def setup(recipient, list)
if self.encrypted?
new = self.decrypt(verify: true)
+ # Test if there's a signed multipart inside the ciphertext
+ # ("encapsulated" format of pgp/mime).
+ if new.signed?
+ new = new.verify
+ end
elsif self.signed?
new = self.verify
else
@@ -58,10 +63,6 @@ module Mail
Mail::Gpg.encrypted?(original_message)
end
- def was_encrypted_mime?
- Mail::Gpg.encrypted_mime?(original_message)
- end
-
def signature
# Theoretically there might be more than one signing key, in practice this is neglectable.
signatures.try(:first)
@@ -268,7 +269,7 @@ module Mail
else
# Test parts recursively. E.g. Thunderbird with activated
# memoryhole-headers send nested parts that might still be empty.
- return self.parts.reduce { |result, part| result && part.empty? }
+ return parts.inject(true) { |result, part| result && part.empty? }
end
else
return self.body.empty?
diff --git a/man/schleuder-api-daemon.8 b/man/schleuder-api-daemon.8
new file mode 100644
index 0000000..c7170df
--- /dev/null
+++ b/man/schleuder-api-daemon.8
@@ -0,0 +1,68 @@
+.\" generated with Ronn/v0.7.3
+.\" https://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "SCHLEUDER\-API\-DAEMON" "8" "November 2016" "" ""
+.
+.SH "SYNOPSIS"
+\fBschleuder\-api\-daemon\fR
+.
+.SH "DESCRIPTION"
+schleuder\-api\-daemon provides the HTTP\-API of Schleuder(8) to clients\.
+.
+.SH "ENVIRONMENT"
+.
+.SS "Configuration"
+\fBschleuder\-api\-daemon\fR reads configuration out of the \fBapi\fR section of \fBschleuder\fR\'s configuration\. Please see \fBschleuder\fR(8) for details about the configuration file\.
+.
+.P
+The available options are:
+.
+.TP
+\fBhost\fR
+The hostname/IP to listen at\. This is overwritten with \'localhost\' unless \fBuse_tls\fR is true\.
+.
+.TP
+\fBport\fR
+The port to listen at\. Default: 4443\.
+.
+.TP
+\fBuse_tls\fR
+Serve the API via HTTPS? Default: false\. Requires a usable certificate and key specified as \fBtls_cert_file\fR and \fBtls_key_file\fR\.
+.
+.TP
+\fBtls_cert_file\fR
+Path to the file that contains the TLS\-certificate to use for HTTPS\. You can generate a new one with \fBschleuder cert generate\fR\.
+.
+.TP
+\fBtls_key_file\fR
+Path to the file that contains the TLS\-key to use for HTTPS\.
+.
+.TP
+\fBvalid_api_keys\fR
+List of api_keys to allow access to the API\.
+.
+.SS "Clients"
+Available clients using the API are \fBschleuder\-cli\fR(8) and \fBschleuder\-web\fR\. URLs to their websites are listed in \fISEE ALSO\fR\.
+.
+.SH "BUGS"
+Known bugs are listed on the Schleuder bugtracker at \fIhttps://codecoop\.org/schleuder/schleuder3\fR
+.
+.SH "SEE ALSO"
+\fBschleuder\fR(8), \fBschleuder\-cli\fR(8)
+.
+.TP
+Website of \fBschleuder\fR
+\fIhttps://schleuder\.nadir\.org/\fR
+.
+.TP
+More extensive documentation for \fBschleuder\fR
+\fIhttps://schleuder\.nadir\.org/docs/\fR
+.
+.TP
+\fBschleuder\-cli\fR, the command line interface for list\-management
+\fIhttps://codecoop\.org/schleuder/schleuder\-cli/\fR
+.
+.TP
+\fBschleuder\-web\fR, the web interface for list\-management
+\fIhttps://codecoop\.org/schleuder/schleuder\-web/\fR
+
diff --git a/man/schleuder-api-daemon.8.ron b/man/schleuder-api-daemon.8.ron
new file mode 100644
index 0000000..0e3a088
--- /dev/null
+++ b/man/schleuder-api-daemon.8.ron
@@ -0,0 +1,61 @@
+schleuder-api-daemon(8)
+=======================
+
+## SYNOPSIS
+
+`schleuder-api-daemon`
+
+
+## DESCRIPTION
+
+schleuder-api-daemon provides the HTTP-API of `schleuder(8)` to clients.
+
+## ENVIRONMENT
+
+### Configuration
+
+`schleuder-api-daemon` reads configuration out of the `api` section of `schleuder`'s configuration. Please see `schleuder`(8) for details about the configuration file.
+
+The available options are:
+
+ * `host`:
+ The hostname/IP to listen at. This is overwritten with 'localhost' unless `use_tls` is true.
+ * `port`:
+ The port to listen at. Default: 4443.
+ * `use_tls`:
+ Serve the API via HTTPS? Default: false. Requires a usable certificate and key specified as `tls_cert_file` and `tls_key_file`.
+ * `tls_cert_file`:
+ Path to the file that contains the TLS-certificate to use for HTTPS. You can generate a new one with `schleuder cert generate`.
+ * `tls_key_file`:
+ Path to the file that contains the TLS-key to use for HTTPS.
+ * `valid_api_keys`:
+ List of api_keys to allow access to the API.
+
+
+### Clients
+
+Available clients using the API are `schleuder-cli`(8) and `schleuder-web`. URLs to their websites are listed below ([SEE ALSO][]).
+
+
+## BUGS
+
+Known bugs are listed on the Schleuder bugtracker at
+<https://codecoop.org/schleuder/schleuder3>
+
+## SEE ALSO
+
+`schleuder`(8),
+`schleuder-cli`(8)
+
+ * Website of `schleuder`:
+ <https://schleuder.nadir.org/>
+
+ * More extensive documentation for `schleuder`:
+ <https://schleuder.nadir.org/docs/>
+
+ * `schleuder-cli`, the command line interface for list-management:
+ <https://codecoop.org/schleuder/schleuder-cli/>
+
+ * `schleuder-web`, the web interface for list-management:
+ <https://codecoop.org/schleuder/schleuder-web/>
+
diff --git a/man/schleuder.8 b/man/schleuder.8
index c0eea90..ed99bbf 100644
--- a/man/schleuder.8
+++ b/man/schleuder.8
@@ -1,7 +1,7 @@
.\" generated with Ronn/v0.7.3
.\" http://github.com/rtomayko/ronn/tree/0.7.3
.
-.TH "SCHLEUDER" "8" "November 2016" "" ""
+.TH "SCHLEUDER" "8" "December 2016" "" ""
.
.SH "NAME"
\fBschleuder\fR \- an email hub for groups
@@ -10,10 +10,16 @@
\fBschleuder\fR work \fIlistaddress\fR < \fIemail\fR
.
.P
+\fBschleuder\fR help
+.
+.P
\fBschleuder\fR \fIother\-command\fR [<\.\.\.>]
.
.P
-For other commands see OPTIONS\.
+For descriptions of the other commands see the output of the \fIhelp\fR\-command\.
+.
+.P
+This manual page is written for system administrators\. For other information please read the Schleuder documentation online (\fISEE ALSO\fR)\.
.
.SH "DESCRIPTION"
Schleuder is an email hub for groups\. Subscribers can communicate encryptedly and pseudonymously among themselves, receive emails from non\-subscribers and send emails to non\-subscribers via the list\.
@@ -24,129 +30,91 @@ Schleuder takes care of all de\- and encryption, stripping of headers, formattin
.P
Email cryptography is handled by using GnuPG\.
.
-.P
-schleuder(8) is usually called in delivery mode by a \fIMail Transport Agent\fR with an incoming email piped to its standard input\. For more informations on how to integrate Schleuder with your existing mail setup, please look at the Schleuder website: \fIhttp://schleuder\.nadir\.org/\fR
-.
-.SH "GETTING THE PUBLIC KEY OF A LIST"
-Each Schleuder\-list replies with its public key to any email sent to \fIlistname\-sendkey at hostname\fR\. E\.g\. to receive the key for the contact address of the Schleuder project write an email to
-.
-.br
-\fIschleuder\-sendkey at nadir\.org\fR\.
-.
-.SH "EMAIL COMMANDS"
-Schleuder knows some special keywords that trigger different behaviour\. You can e\.g\. subscribe someone, or resend an email to a non\-subscriber using keywords\. See a list of available keywords below\.
+.SH "ENVIRONMENT"
.
-.P
-Keywords require that:
+.SS "Configuration"
+Schleuder reads its basic settings from a file that it by default expects at </etc/schleuder/schleuder\.yml>\. To make Schleuder read a different file set the environment variable \fISCHLEUDER_CONFIG\fR to the path to your file when running schleuder\. E\.g\.:
.
-.IP "\(bu" 4
-they start the line and begin with "x\-",
+.IP "" 4
.
-.IP "\(bu" 4
-they are written into the beginning of the \fIfirst text\-part\fR of the email (usually that’s just the normal body of the email),
+.nf
+
+SCHLEUDER_CONFIG=/usr/local/etc/schleuder\.yml /path/to/bin/schleuder \.\.\.
.
-.IP "\(bu" 4
-possible arguments must be written \fIon the same line\fR as the keyword (exceptions are mentioned in the descriptions below),
-.
-.IP "\(bu" 4
-the email must be \fIencrypted and signed\fR by a list\-member’s key\.
+.fi
.
.IP "" 0
.
.P
-Keywords can be repeated within one email at will\. Letter case doesn’t matter\.
+For explanations of the possible settings read the default config file\.
.
.P
-There are two types of keywords: those to enhance messages sent over the list (“list\-keywords”), and those to request something from Schleuder (“request\-keywords”)\.
+The default settings for new lists are read from another config file\. By default Schleuder looks at </etc/schleuder/list\-defaults\.yml>\. To make Schleuder read a different file set the environment variable \fISCHLEUDER_LIST_DEFAULTS\fR analogous to above\. The possible settings are explained in the default config file\.
.
-.SS "Resending"
-The resending\-keywords must be included in messages sent to the normal list\-address: \fIlistname at hostname\fR\.
+.SS "Connect to MTA"
+Schleuder behaves like an email\-filter: it reads email from standard\-input, and reports errors to standard\-error\. If all goes well Schleuder closes the initial connection to the Mail Transport Agent (MTA) only after it sent out all outgoing emails\.
.
-.TP
-\fBx\-resend:\fR \fIsomeone at example\.org\fR
-Send the message to the given address, encrypted if possible, otherwise in the clear\.
-.
-.TP
-\fBx\-resend\-encrypted\-only:\fR \fIsomeone at example\.org\fR
-Send the message to the given address only if it could be encrypted\.
+.P
+In case of an error the MTA is expected to include Schleuder\'s error message into a bounce\-email that is sent back to the sender (this is default behaviour of most MTAs)\.
.
-.SS "Subscription and key management"
-These keywords must be send to \fIlistname\-request at hostname\fR\. They are used to get information about the list, its subscribers and keys, or to change that information\.
+.P
+To connect the MTA with Schleuder it must pipe the incoming message into Schleuder\'s STDIN, and give it two arguments: first one: "work", second one: the full recipients email address\.
.
-.TP
-\fBx\-list\-subscriptions\fR
-List all subscriptions\.
+.P
+For more information on how to integrate Schleuder with your existing mail setup, please read the Schleuder documentation online (\fISEE ALSO\fR)\.
.
-.TP
-\fBx\-subscribe:\fR \fIperson at example\.org\fR \fI12345678DEADBEEF12345678DEADBEEF12345678\fR
-Subscribe the given address and assign it the given OpenPGP\-fingerprint\.
+.SS "Data storage"
+The keyrings for each list are standard GnuPG keyrings and sit in the filesystem under \fIlists_dir\fR/\fIhostname\fR/\fIlistname\fR/ (\fIlists_dir\fR is read from schleuder\.yml, by default it is </var/schleuder/lists>)\. They can be used manually using gpg2\. Please be careful to maintain proper file permissions if you touch the files\.
.
-.TP
-\fBx\-unsubscribe:\fR \fIperson at example\.org\fR
-Unsubscribe the given address\.
+.P
+In the list\-directory there’s also a list specific log\-file (might be missing if the log\-level is high and no error occurred yet)\.
.
-.TP
-\fBx\-set\-fingerprint:\fR \fI12345678DEADBEEF12345678DEADBEEF12345678\fR
-Assign the key with the given fingerprint to your subscription\.
+.P
+Other logging is sent to syslog\. Where that ends up depends on the operating system and the system administration\.
.
-.TP
-\fBx\-set\-fingerprint:\fR \fIperson at example\.org\fR \fI12345678DEADBEEF12345678DEADBEEF12345678\fR
-Assign the key with the given fingerprint to the given subscription\. This variant of this command may only be used by list\-admins\.
+.P
+All other list\-related data is stored in the SQL\-database\. Most data is unserialized, only some values are JSON\-encoded\.
.
-.TP
-\fBx\-list\-keys:\fR
-Lists all public keys known to the list\.
+.SH "SPECIAL FEATURES"
+Schleuder features some special funtionality\. For more detailed information read the Schleuder documentation online (\fISEE ALSO\fR)\.
.
-.TP
-\fBx\-add\-key:\fR
-Import the \fIrest of the email\-body\fR into the list\'s keyring\. Write the ascii\-armored key\-block below this keyword\.
+.SS "Getting the public key of a list"
+Each Schleuder\-list replies with its public key to any email sent to \fIlistname\-sendkey at hostname\fR\. E\.g\. to receive the key for the contact address of the Schleuder project write an email to
.
.br
-\fINote:\fR This command reads the whole body of the email\. If you want to use other keywords within the same email, \fIthis must be the last one!\fR
-.
-.TP
-\fBx\-delete\-key:\fR \fI12345678DEADBEEF12345678DEADBEEF12345678\fR
-Delete the key with the given fingerprint from the list\'s keyring\.
+\fIschleuder\-sendkey at nadir\.org\fR\.
.
-.TP
-\fBx\-get\-key:\fR \fI12345678DEADBEEF12345678DEADBEEF12345678\fR
-Export the key with the given fingerprint from the list\'s keyring\.
+.SS "Email commands"
+Schleuder knows some special keywords that trigger different behaviour\. You can e\.g\. subscribe someone, or resend an email to a non\-subscriber using keywords\.
.
-.TP
-\fBx\-fetch\-key:\fR \fI12345678DEADBEEF12345678DEADBEEF12345678\fR
-Fetch the key with the given fingerprint from a keyserver and import it into the list\'s keyring\. (This works only if a keyserver has been configured by the provider\.)
+.P
+Keywords require that:
.
-.SS "Other"
-Must also be sent to the request\-address: \fIlistname\-request at hostname\fR\.
+.IP "\(bu" 4
+they start the line and begin with "x\-",
.
-.TP
-\fBx\-sign\-this:\fR
-Sign the remaining contents of the email body or the attachments with the list\'s key\. Use this e\.g\. to provide GnuPG\-signatures for things you are publishing\.
+.IP "\(bu" 4
+they are written into the beginning of the \fIfirst text\-part\fR of the email (usually that’s just the normal body of the email),
.
-.br
-\fINote:\fR This command reads the whole body of the email\. If you want to use other keywords within the same email, \fIthis must be the last one!\fR
+.IP "\(bu" 4
+possible arguments must be written \fIon the same line\fR as the keyword (exceptions are mentioned in the descriptions below),
.
-.SH "CONTACT LIST\-OWNER"
-Write to \fIlistname\-owner at hostname\fR to contact the list\-owner(s) even if you don\'t know who they are\. Use the list\'s key to encrypt the email!
+.IP "\(bu" 4
+the email must be \fIencrypted and signed\fR by a list\-member’s key\.
.
-.SH "OPTIONS"
-Other sub\-commands of schleuder:
+.IP "" 0
.
-.TP
-\fBschleuder help\fR
-Display usage and exit\.
+.P
+Keywords can be repeated within one email at will\. Letter case doesn’t matter\.
.
-.TP
-\fBschleuder version\fR
-Display version and exit\.
+.P
+There are two types of keywords: those to enhance messages sent over the list (“list\-keywords”), and those to request something from Schleuder (“request\-keywords”)\.
.
-.TP
-\fBschleuder install\fR
-Creates neccessary directories, copies example configs, etc\. If you see errors about missing write permissions please follow the advice given\.
+.P
+Find detailed descriptions of all available keywords in the Schleuder documentation online (\fISEE ALSO\fR)\.
.
-.TP
-\fBschleuder generate_api_key\fR
-Generate a new key to be used by clients to speak to the API\.
+.SS "Contact list\-owner"
+Write to \fIlistname\-owner at hostname\fR to contact the list\-owner(s) even if you don\'t know who they are\. Use the list\'s key to encrypt the email!
.
.SH "EXIT STATUS"
.
@@ -160,21 +128,22 @@ Internal failure in incoming email processing\.
.
.SH "FILES"
.
-.TP
-\fB/etc/schleuder/schleuder\.yml\fR
-global Schleuder configuration
+.IP "\(bu" 4
+\fB/etc/schleuder/schleuder\.yml\fR: default path of global Schleuder configuration
.
-.TP
-\fB/etc/schleuder/list\-defaults\.yml\fR
-default list settings
+.IP "\(bu" 4
+\fB/etc/schleuder/list\-defaults\.yml\fR: default path of default list settings
.
-.TP
-\fB/var/schleuder/lists/\fR\fIhostname\fR\fB/\fR\fIlistname\fR
-list internal data
+.IP "\(bu" 4
+\fB/var/schleuder/\fR default path of lists_dir
.
-.TP
-\fB/var/schleuder/lists/\fR\fIhostname\fR\fB/\fR\fIlistname\fR\fB/list\.log\fR
-log\-file for list
+.IP "\(bu" 4
+\fB<lists_dir>\fR/\fB<hostname>\fR/`\fIlistname\fR: list internal data
+.
+.IP "\(bu" 4
+\fB<lists_dir>\fR/\fB<hostname>\fR/\fB<listname>\fR/list\.log`: log\-file for list
+.
+.IP "" 0
.
.P
All configuration files are formatted as YAML\. See \fIhttp://www\.yaml\.org/\fR for more details\.
@@ -187,13 +156,17 @@ Known bugs are listed on the Schleuder bugtracker at \fIhttps://codecoop\.org/sc
.
.TP
Website of \fBschleuder\fR
-\fIhttp://schleuder\.nadir\.org/\fR
+\fIhttps://schleuder\.nadir\.org/\fR
+.
+.TP
+More extensive documentation for \fBschleuder\fR
+\fIhttps://schleuder\.nadir\.org/docs/\fR
.
.TP
\fBschleuder\-cli\fR, the command line interface for list\-management
-\fIhttp://codecoop\.org/schleuder/schleuder\-cli/\fR
+\fIhttps://codecoop\.org/schleuder/schleuder\-cli/\fR
.
.TP
\fBschleuder\-web\fR, the web interface for list\-management
-\fIhttp://codecoop\.org/schleuder/schleuder\-web/\fR
+\fIhttps://codecoop\.org/schleuder/schleuder\-web/\fR
diff --git a/man/schleuder.8.ron b/man/schleuder.8.ron
index af8a799..328ce7d 100644
--- a/man/schleuder.8.ron
+++ b/man/schleuder.8.ron
@@ -42,12 +42,12 @@ In case of an error the MTA is expected to include Schleuder's error message int
To connect the MTA with Schleuder it must pipe the incoming message into Schleuder's STDIN, and give it two arguments: first one: "work", second one: the full recipients email address.
-For more informations on how to integrate Schleuder with your existing mail
+For more information on how to integrate Schleuder with your existing mail
setup, please read the Schleuder documentation online ([SEE ALSO][]).
### Data storage
-The keyrings for each list are standard GnuPG keyrings and sit in the filesystem under $lists_dir/$hostname/$listname/ ($lists_dir is read from schleuder.yml, by default it is </var/schleuder/lists>). They can be used manually using gpg2. Please be careful to maintain proper file permissions if you touch the files.
+The keyrings for each list are standard GnuPG keyrings and sit in the filesystem under <lists_dir>/<hostname>/<listname>/ (<lists_dir> is read from schleuder.yml, by default it is </var/schleuder/lists>). They can be used manually using gpg2. Please be careful to maintain proper file permissions if you touch the files.
In the list-directory there’s also a list specific log-file (might be missing if the log-level is high and no error occurred yet).
@@ -99,15 +99,18 @@ Write to <listname-owner at hostname> to contact the list-owner(s) even if you don'
## FILES
* `/etc/schleuder/schleuder.yml`:
- global Schleuder configuration
+ default path of global Schleuder configuration
* `/etc/schleuder/list-defaults.yml`:
- default list settings
+ default path of default list settings
- * `/var/schleuder/lists/`<hostname>`/`<listname>:
+ * `/var/schleuder/`
+ default path of lists_dir
+
+ * `<lists_dir>`/`<hostname>`/`<listname>:
list internal data
- * `/var/schleuder/lists/`<hostname>`/`<listname>`/list.log`:
+ * `<lists_dir>`/`<hostname>`/`<listname>`/list.log`:
log-file for list
All configuration files are formatted as YAML. See
@@ -124,13 +127,13 @@ Known bugs are listed on the Schleuder bugtracker at
`gnupg`(7).
* Website of `schleuder`:
- <http://schleuder.nadir.org/>
+ <https://schleuder.nadir.org/>
* More extensive documentation for `schleuder`:
- <http://schleuder.nadir.org/docs/>
+ <https://schleuder.nadir.org/docs/>
* `schleuder-cli`, the command line interface for list-management:
- <http://codecoop.org/schleuder/schleuder-cli/>
+ <https://codecoop.org/schleuder/schleuder-cli/>
* `schleuder-web`, the web interface for list-management:
- <http://codecoop.org/schleuder/schleuder-web/>
+ <https://codecoop.org/schleuder/schleuder-web/>
diff --git a/schleuder.gemspec b/schleuder.gemspec
index b78c430..708f686 100644
--- a/schleuder.gemspec
+++ b/schleuder.gemspec
@@ -6,9 +6,9 @@ require 'schleuder/version'
Gem::Specification.new do |s|
s.name = "schleuder"
s.version = Schleuder::VERSION
- s.authors = %w(lunar ng paz)
- s.email = "schleuder2 at nadir.org"
- s.homepage = "http://schleuder.nadir.org/"
+ s.authors = 'schleuder dev team'
+ s.email = "schleuder at nadir.org"
+ s.homepage = "https://schleuder.nadir.org/"
s.summary = "Schleuder is a gpg-enabled mailinglist with remailing-capabilities."
s.description = "Schleuder is a group's email-gateway: subscribers can exchange encrypted emails among themselves, receive emails from non-subscribers and send emails to non-subscribers via the list.\n\nSchleuder takes care of all decryption and (re-)encryption, stripping of headers, and more. Schleuder can also send out its own public key upon request and process administrative commands by email."
s.files = `git ls-files lib locales etc db/schema.rb README.md Rakefile`.split
diff --git a/spec/schleuder/list_spec.rb b/spec/schleuder/list_spec.rb
index 52ba846..db2762d 100644
--- a/spec/schleuder/list_spec.rb
+++ b/spec/schleuder/list_spec.rb
@@ -111,8 +111,8 @@ describe Schleuder::List do
list = Schleuder::List.new(
email: "foo at bar.org",
fingerprint: "aaaadddd0000999",
- "#{list_attribute}": nil
)
+ list[list_attribute] = nil
expect(list).not_to be_valid
expect(list.errors.messages[list_attribute]).to include("must be true or false")
@@ -122,8 +122,8 @@ describe Schleuder::List do
list = Schleuder::List.new(
email: "foo at bar.org",
fingerprint: "aaaadddd0000999",
- "#{list_attribute}": ""
)
+ list[list_attribute] = ""
expect(list).not_to be_valid
expect(list.errors.messages[list_attribute]).to include("must be true or false")
@@ -135,8 +135,8 @@ describe Schleuder::List do
list = Schleuder::List.new(
email: "foo at bar.org",
fingerprint: "aaaadddd0000999",
- "#{list_attribute}": ["$from", "to", "date", "cc"],
)
+ list[list_attribute] =["$from", "to", "date", "cc"]
expect(list).not_to be_valid
expect(list.errors.messages[list_attribute]).to include("contains invalid characters")
@@ -146,8 +146,8 @@ describe Schleuder::List do
list = Schleuder::List.new(
email: "foo at bar.org",
fingerprint: "aaaadddd0000999",
- "#{list_attribute}": ["foobar"],
)
+ list[list_attribute] = ["foobar"]
expect(list).to be_valid
end
@@ -157,7 +157,7 @@ describe Schleuder::List do
list = Schleuder::List.new(
email: "foo at bar.org",
fingerprint: "aaaadddd0000999",
- bounces_drop_on_headers: {"$": "%"},
+ bounces_drop_on_headers: {"$" => "%"},
)
expect(list).not_to be_valid
@@ -169,8 +169,8 @@ describe Schleuder::List do
list = Schleuder::List.new(
email: "foo at bar.org",
fingerprint: "aaaadddd0000999",
- "#{list_attribute}": "Foo\nbar",
)
+ list[list_attribute] = "Foo\nbar"
expect(list).not_to be_valid
expect(list.errors.messages[list_attribute]).to include("must not include line-breaks")
@@ -180,8 +180,8 @@ describe Schleuder::List do
list = Schleuder::List.new(
email: "foo at bar.org",
fingerprint: "aaaadddd0000999",
- "#{list_attribute}": nil,
)
+ list[list_attribute] = nil
expect(list).to be_valid
end
@@ -203,8 +203,8 @@ describe Schleuder::List do
list = Schleuder::List.new(
email: "foo at bar.org",
fingerprint: "aaaadddd0000999",
- "#{list_attribute}": 0,
)
+ list[list_attribute] = 0
expect(list).not_to be_valid
expect(list.errors.messages[list_attribute]).to include("must be a number greater than zero")
diff --git a/spec/schleuder/subscription_spec.rb b/spec/schleuder/subscription_spec.rb
index 9a2f4be..f5d2f10 100644
--- a/spec/schleuder/subscription_spec.rb
+++ b/spec/schleuder/subscription_spec.rb
@@ -106,8 +106,8 @@ describe Schleuder::Subscription do
list_id: @list.id,
email: "foo at bar.org",
fingerprint: nil,
- "#{subscription_attribute}": nil
)
+ subscription[subscription_attribute] = nil
expect(subscription).not_to be_valid
expect(subscription.errors.messages[subscription_attribute]).to include("must be true or false")
@@ -118,8 +118,8 @@ describe Schleuder::Subscription do
list_id: @list.id,
email: "foo at bar.org",
fingerprint: nil,
- "#{subscription_attribute}": ""
)
+ subscription[subscription_attribute] = ""
expect(subscription).not_to be_valid
expect(subscription.errors.messages[subscription_attribute]).to include("must be true or false")
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-ruby-extras/schleuder.git
More information about the Pkg-ruby-extras-commits
mailing list