From 724d877995dfcc10c462a18dcb4ea6c8b60c2d03 Mon Sep 17 00:00:00 2001 From: Sam Chudnick Date: Sun, 2 Jul 2023 19:04:30 -0400 Subject: initial commit --- LICENSE | 674 +++++++++++++++++++++ README.md | 56 ++ group_vars/all/vars.yml | 8 + inventory.yml | 8 + roles/dovecot/defaults/main.yml | 0 roles/dovecot/files/conf.d/10-auth.conf | 10 + roles/dovecot/files/conf.d/10-director.conf | 60 ++ roles/dovecot/files/conf.d/10-logging.conf | 109 ++++ roles/dovecot/files/conf.d/10-mail.conf | 10 + roles/dovecot/files/conf.d/10-master.conf | 22 + roles/dovecot/files/conf.d/10-tcpwrapper.conf | 14 + roles/dovecot/files/conf.d/15-lda.conf | 4 + roles/dovecot/files/conf.d/15-mailboxes.conf | 25 + roles/dovecot/files/conf.d/20-imap.conf | 2 + roles/dovecot/files/conf.d/90-acl.conf | 19 + roles/dovecot/files/conf.d/90-plugin.conf | 11 + roles/dovecot/files/conf.d/90-quota.conf | 83 +++ .../dovecot/files/conf.d/90-sieve-extprograms.conf | 44 ++ roles/dovecot/files/conf.d/90-sieve.conf | 6 + .../files/conf.d/auth-checkpassword.conf.ext | 21 + roles/dovecot/files/conf.d/auth-deny.conf.ext | 15 + roles/dovecot/files/conf.d/auth-dict.conf.ext | 16 + roles/dovecot/files/conf.d/auth-master.conf.ext | 16 + .../dovecot/files/conf.d/auth-passwdfile.conf.ext | 20 + roles/dovecot/files/conf.d/auth-sql.conf.ext | 30 + roles/dovecot/files/conf.d/auth-static.conf.ext | 24 + roles/dovecot/files/conf.d/auth-system.conf.ext | 74 +++ roles/dovecot/files/default.sieve | 22 + roles/dovecot/files/dovecot.conf | 16 + roles/dovecot/files/dovecot_pam | 8 + roles/dovecot/handlers/main.yml | 0 roles/dovecot/tasks/main.yml | 67 ++ roles/dovecot/templates/10-ssl.conf.j2 | 20 + roles/opendkim/defaults/main.yml | 0 roles/opendkim/handlers/main.yml | 0 roles/opendkim/tasks/main.yml | 57 ++ roles/opendkim/templates/opendkim.conf.j2 | 21 + roles/opendmarc/defaults/main.yml | 0 roles/opendmarc/files/opendmarc.conf | 11 + roles/opendmarc/handlers/main.yml | 0 roles/opendmarc/tasks/main.yml | 39 ++ roles/policyd_spf/defaults/main.yml | 0 roles/policyd_spf/files/policyd-spf.conf | 8 + roles/policyd_spf/handlers/main.yml | 0 roles/policyd_spf/tasks/main.yml | 13 + roles/postfix/defaults/main.yml | 0 roles/postfix/files/body_checks | 2 + roles/postfix/files/header_checks | 11 + roles/postfix/handlers/main.yml | 0 roles/postfix/tasks/main.yml | 84 +++ roles/postfix/templates/aliases | 3 + roles/postfix/templates/local_maps | 1 + roles/postfix/templates/login_maps | 1 + roles/postfix/templates/main.cf.j2 | 69 +++ roles/postfix/templates/master.cf.j2 | 84 +++ roles/postgrey/defaults/main.yml | 0 roles/postgrey/files/postgrey | 2 + roles/postgrey/handlers/main.yml | 0 roles/postgrey/tasks/main.yml | 24 + roles/spamassassin/defaults/main.yml | 0 roles/spamassassin/files/defaults | 9 + roles/spamassassin/handlers/main.yml | 0 roles/spamassassin/tasks/main.yml | 40 ++ roles/spamassassin/templates/local.cf.j2 | 18 + run.yml | 79 +++ 65 files changed, 2090 insertions(+) create mode 100644 LICENSE create mode 100644 README.md create mode 100644 group_vars/all/vars.yml create mode 100644 inventory.yml create mode 100644 roles/dovecot/defaults/main.yml create mode 100644 roles/dovecot/files/conf.d/10-auth.conf create mode 100644 roles/dovecot/files/conf.d/10-director.conf create mode 100644 roles/dovecot/files/conf.d/10-logging.conf create mode 100644 roles/dovecot/files/conf.d/10-mail.conf create mode 100644 roles/dovecot/files/conf.d/10-master.conf create mode 100644 roles/dovecot/files/conf.d/10-tcpwrapper.conf create mode 100644 roles/dovecot/files/conf.d/15-lda.conf create mode 100644 roles/dovecot/files/conf.d/15-mailboxes.conf create mode 100644 roles/dovecot/files/conf.d/20-imap.conf create mode 100644 roles/dovecot/files/conf.d/90-acl.conf create mode 100644 roles/dovecot/files/conf.d/90-plugin.conf create mode 100644 roles/dovecot/files/conf.d/90-quota.conf create mode 100644 roles/dovecot/files/conf.d/90-sieve-extprograms.conf create mode 100644 roles/dovecot/files/conf.d/90-sieve.conf create mode 100644 roles/dovecot/files/conf.d/auth-checkpassword.conf.ext create mode 100644 roles/dovecot/files/conf.d/auth-deny.conf.ext create mode 100644 roles/dovecot/files/conf.d/auth-dict.conf.ext create mode 100644 roles/dovecot/files/conf.d/auth-master.conf.ext create mode 100644 roles/dovecot/files/conf.d/auth-passwdfile.conf.ext create mode 100644 roles/dovecot/files/conf.d/auth-sql.conf.ext create mode 100644 roles/dovecot/files/conf.d/auth-static.conf.ext create mode 100644 roles/dovecot/files/conf.d/auth-system.conf.ext create mode 100644 roles/dovecot/files/default.sieve create mode 100644 roles/dovecot/files/dovecot.conf create mode 100644 roles/dovecot/files/dovecot_pam create mode 100644 roles/dovecot/handlers/main.yml create mode 100644 roles/dovecot/tasks/main.yml create mode 100644 roles/dovecot/templates/10-ssl.conf.j2 create mode 100644 roles/opendkim/defaults/main.yml create mode 100644 roles/opendkim/handlers/main.yml create mode 100644 roles/opendkim/tasks/main.yml create mode 100644 roles/opendkim/templates/opendkim.conf.j2 create mode 100644 roles/opendmarc/defaults/main.yml create mode 100644 roles/opendmarc/files/opendmarc.conf create mode 100644 roles/opendmarc/handlers/main.yml create mode 100644 roles/opendmarc/tasks/main.yml create mode 100644 roles/policyd_spf/defaults/main.yml create mode 100644 roles/policyd_spf/files/policyd-spf.conf create mode 100644 roles/policyd_spf/handlers/main.yml create mode 100644 roles/policyd_spf/tasks/main.yml create mode 100644 roles/postfix/defaults/main.yml create mode 100644 roles/postfix/files/body_checks create mode 100644 roles/postfix/files/header_checks create mode 100644 roles/postfix/handlers/main.yml create mode 100644 roles/postfix/tasks/main.yml create mode 100644 roles/postfix/templates/aliases create mode 100644 roles/postfix/templates/local_maps create mode 100644 roles/postfix/templates/login_maps create mode 100644 roles/postfix/templates/main.cf.j2 create mode 100644 roles/postfix/templates/master.cf.j2 create mode 100644 roles/postgrey/defaults/main.yml create mode 100644 roles/postgrey/files/postgrey create mode 100644 roles/postgrey/handlers/main.yml create mode 100644 roles/postgrey/tasks/main.yml create mode 100644 roles/spamassassin/defaults/main.yml create mode 100644 roles/spamassassin/files/defaults create mode 100644 roles/spamassassin/handlers/main.yml create mode 100644 roles/spamassassin/tasks/main.yml create mode 100644 roles/spamassassin/templates/local.cf.j2 create mode 100644 run.yml diff --git a/LICENSE b/LICENSE new file mode 100644 index 0000000..94a9ed0 --- /dev/null +++ b/LICENSE @@ -0,0 +1,674 @@ + GNU GENERAL PUBLIC LICENSE + Version 3, 29 June 2007 + + Copyright (C) 2007 Free Software Foundation, Inc. + 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. + + + Copyright (C) + + 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 . + +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: + + Copyright (C) + 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 +. + + 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 +. diff --git a/README.md b/README.md new file mode 100644 index 0000000..eb23991 --- /dev/null +++ b/README.md @@ -0,0 +1,56 @@ +# ansible-mailserver +ansible-mailserver is an Ansible playbook to deploy a simple postfix/dovecot mail server. + +## Features +Simple one-command installation and configuration of your very own mail server. + +Includes a host of defenses needed when dealing with the world of internet mail: +- postscreen - inbound SMTP connection filtering +- postgrey - greylisting utility +- policyd-spf - SPF validation +- spamassassin - spam filter +- opendkim - DKIM signing and verification +- opendmarc - DMARC verification + +## Usage + +### Prerequisites +Before running the playbook you will need to have the following: +- An A record for your base domain +- An A record for the `mail` subdomain +- A PTR record for your mail server + +### Clone the repository +``` +git clone https://git.chudnick.com/ansible-mailserver +``` + +### Modify the inventory +Modify the inventory.yml for your deployment. +At a minimum, change `mail.example.com` to the FQDN of your mail server and +change `ansible_user` and `remote_user` to the name of your account on the +mail server. + +### Modify vars.yml +Modify group\_vars/all/vars.yml for your deployment. +Below is a list of the variables and there function: +- `domain` - base domain +- `mail_domain` - hostname of your mail server and common name on the TLS certificate +- `dkim_selector` - selector for your DKIM keys +- `spam_score` - SpamAssassin score required for mail to be considered spam +- `sa_locales` - locales which SpamAssassin expects to receive mail in - any locale not listed is considered spam +- `cert_email` - the email used to get a LetsEncrypt certificate + +You must modify `domain` with your domain name. All other changes are optional. + +### Run the playbook +From the repo root directory run: +``` +ansible-playbook run.yml -i inventory.yml --ask-become-pass +``` +If you have passwordless sudo configured --ask-become-pass is not necessary. + +### Set DNS records +The playbook finishes by generating the DNS records required for mail verification. +You can find these records under /home/root/dns\_records once the playbook finishes. +The records are in BIND9 format but the values can be extracted for use on any platform. diff --git a/group_vars/all/vars.yml b/group_vars/all/vars.yml new file mode 100644 index 0000000..7d8f440 --- /dev/null +++ b/group_vars/all/vars.yml @@ -0,0 +1,8 @@ +domain: "example.com" +mail_domain: "mail.{{ domain }}" +dkim_selector: "mail" + +spam_score: "5.0" +sa_locales: "en" + +cert_email: "contact@{{ domain }}" diff --git a/inventory.yml b/inventory.yml new file mode 100644 index 0000000..9abd208 --- /dev/null +++ b/inventory.yml @@ -0,0 +1,8 @@ +all: + hosts: + children: + mail_server: + hosts: + mail.example.com: + ansible_user: admin + remote_user: admin diff --git a/roles/dovecot/defaults/main.yml b/roles/dovecot/defaults/main.yml new file mode 100644 index 0000000..e69de29 diff --git a/roles/dovecot/files/conf.d/10-auth.conf b/roles/dovecot/files/conf.d/10-auth.conf new file mode 100644 index 0000000..7ac1eee --- /dev/null +++ b/roles/dovecot/files/conf.d/10-auth.conf @@ -0,0 +1,10 @@ +# Authentication +disable_plaintext_auth = yes +auth_username_format = %n +auth_mechanisms = plain +userdb { + driver = passwd +} +passdb { + driver = pam +} diff --git a/roles/dovecot/files/conf.d/10-director.conf b/roles/dovecot/files/conf.d/10-director.conf new file mode 100644 index 0000000..073d8a8 --- /dev/null +++ b/roles/dovecot/files/conf.d/10-director.conf @@ -0,0 +1,60 @@ +## +## Director-specific settings. +## + +# Director can be used by Dovecot proxy to keep a temporary user -> mail server +# mapping. As long as user has simultaneous connections, the user is always +# redirected to the same server. Each proxy server is running its own director +# process, and the directors are communicating the state to each others. +# Directors are mainly useful with NFS-like setups. + +# List of IPs or hostnames to all director servers, including ourself. +# Ports can be specified as ip:port. The default port is the same as +# what director service's inet_listener is using. +#director_servers = + +# List of IPs or hostnames to all backend mail servers. Ranges are allowed +# too, like 10.0.0.10-10.0.0.30. +#director_mail_servers = + +# How long to redirect users to a specific server after it no longer has +# any connections. +#director_user_expire = 15 min + +# How the username is translated before being hashed. Useful values include +# %Ln if user can log in with or without @domain, %Ld if mailboxes are shared +# within domain. +#director_username_hash = %Lu + +# To enable director service, uncomment the modes and assign a port. +service director { + unix_listener login/director { + #mode = 0666 + } + fifo_listener login/proxy-notify { + #mode = 0666 + } + unix_listener director-userdb { + #mode = 0600 + } + inet_listener { + #port = + } +} + +# Enable director for the wanted login services by telling them to +# connect to director socket instead of the default login socket: +service imap-login { + #executable = imap-login director +} +service pop3-login { + #executable = pop3-login director +} +service submission-login { + #executable = submission-login director +} + +# Enable director for LMTP proxying: +protocol lmtp { + #auth_socket_path = director-userdb +} diff --git a/roles/dovecot/files/conf.d/10-logging.conf b/roles/dovecot/files/conf.d/10-logging.conf new file mode 100644 index 0000000..bcd6dea --- /dev/null +++ b/roles/dovecot/files/conf.d/10-logging.conf @@ -0,0 +1,109 @@ +## +## Log destination. +## + +# Log file to use for error messages. "syslog" logs to syslog, +# /dev/stderr logs to stderr. +#log_path = syslog + +# Log file to use for informational messages. Defaults to log_path. +#info_log_path = +# Log file to use for debug messages. Defaults to info_log_path. +#debug_log_path = + +# Syslog facility to use if you're logging to syslog. Usually if you don't +# want to use "mail", you'll use local0..local7. Also other standard +# facilities are supported. +#syslog_facility = mail + +## +## Logging verbosity and debugging. +## + +# Log filter is a space-separated list conditions. If any of the conditions +# match, the log filter matches (i.e. they're ORed together). Parenthesis +# are supported if multiple conditions need to be matched together. +# Supported conditions are: +# event: - Match event name. '*' and '?' wildcards supported. +# source:[:] - Match source code filename [and line] +# field:= - Match field key to a value. Can be specified +# multiple times to match multiple keys. +# cat[egory]: - Match a category. Can be specified multiple times to +# match multiple categories. +# For example: event:http_request_* (cat:error cat:storage) + +# Filter to specify what debug logging to enable. This will eventually replace +# mail_debug and auth_debug settings. +#log_debug = + +# Crash after logging a matching event. For example category:error will crash +# any time an error is logged, which can be useful for debugging. +#log_core_filter = + +# Log unsuccessful authentication attempts and the reasons why they failed. +#auth_verbose = no + +# In case of password mismatches, log the attempted password. Valid values are +# no, plain and sha1. sha1 can be useful for detecting brute force password +# attempts vs. user simply trying the same password over and over again. +# You can also truncate the value to n chars by appending ":n" (e.g. sha1:6). +#auth_verbose_passwords = no + +# Even more verbose logging for debugging purposes. Shows for example SQL +# queries. +#auth_debug = no + +# In case of password mismatches, log the passwords and used scheme so the +# problem can be debugged. Enabling this also enables auth_debug. +#auth_debug_passwords = no + +# Enable mail process debugging. This can help you figure out why Dovecot +# isn't finding your mails. +#mail_debug = no + +# Show protocol level SSL errors. +#verbose_ssl = no + +# mail_log plugin provides more event logging for mail processes. +plugin { + # Events to log. Also available: flag_change append + #mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename + # Available fields: uid, box, msgid, from, subject, size, vsize, flags + # size and vsize are available only for expunge and copy events. + #mail_log_fields = uid box msgid size +} + +## +## Log formatting. +## + +# Prefix for each line written to log file. % codes are in strftime(3) +# format. +#log_timestamp = "%b %d %H:%M:%S " + +# Space-separated list of elements we want to log. The elements which have +# a non-empty variable value are joined together to form a comma-separated +# string. +#login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c + +# Login log format. %s contains login_log_format_elements string, %$ contains +# the data we want to log. +#login_log_format = %$: %s + +# Log prefix for mail processes. See doc/wiki/Variables.txt for list of +# possible variables you can use. +#mail_log_prefix = "%s(%u)<%{pid}><%{session}>: " + +# Format to use for logging mail deliveries: +# %$ - Delivery status message (e.g. "saved to INBOX") +# %m / %{msgid} - Message-ID +# %s / %{subject} - Subject +# %f / %{from} - From address +# %p / %{size} - Physical size +# %w / %{vsize} - Virtual size +# %e / %{from_envelope} - MAIL FROM envelope +# %{to_envelope} - RCPT TO envelope +# %{delivery_time} - How many milliseconds it took to deliver the mail +# %{session_time} - How long LMTP session took, not including delivery_time +# %{storage_id} - Backend-specific ID for mail, e.g. Maildir filename +#deliver_log_format = msgid=%m: %$ diff --git a/roles/dovecot/files/conf.d/10-mail.conf b/roles/dovecot/files/conf.d/10-mail.conf new file mode 100644 index 0000000..683c5e9 --- /dev/null +++ b/roles/dovecot/files/conf.d/10-mail.conf @@ -0,0 +1,10 @@ +# Mail location +mail_location = maildir:~/Mail:INBOX=~/Mail/Inbox:LAYOUT=fs +namespace inbox { + type = private + prefix = + separator = / + inbox = yes + subscriptions = yes + list = yes +} diff --git a/roles/dovecot/files/conf.d/10-master.conf b/roles/dovecot/files/conf.d/10-master.conf new file mode 100644 index 0000000..c2c9493 --- /dev/null +++ b/roles/dovecot/files/conf.d/10-master.conf @@ -0,0 +1,22 @@ +# Master Configuration +service imap-login { + # Run login processes in high-security mode (see: LoginProcess.txt in dovecot docs) + service_count = 1 + # Disable unencrypted IMAP by setting port for plain IMAP to 0 + inet_listener imap { + port = 0 + } + inet_listener imaps { + port = 993 + ssl = yes + } +} + +# Allow postfix to user dovecot SASL +service auth { + unix_listener /var/spool/postfix/private/auth { + mode = 0660 + user = postfix + group = postfix + } +} diff --git a/roles/dovecot/files/conf.d/10-tcpwrapper.conf b/roles/dovecot/files/conf.d/10-tcpwrapper.conf new file mode 100644 index 0000000..b237d96 --- /dev/null +++ b/roles/dovecot/files/conf.d/10-tcpwrapper.conf @@ -0,0 +1,14 @@ +# 10-tcpwrapper.conf +# +# service name for hosts.{allow|deny} are those defined as +# inet_listener in master.conf +# +#login_access_sockets = tcpwrap +# +#service tcpwrap { +# unix_listener login/tcpwrap { +# group = $default_login_user +# mode = 0600 +# user = $default_login_user +# } +#} diff --git a/roles/dovecot/files/conf.d/15-lda.conf b/roles/dovecot/files/conf.d/15-lda.conf new file mode 100644 index 0000000..8538f79 --- /dev/null +++ b/roles/dovecot/files/conf.d/15-lda.conf @@ -0,0 +1,4 @@ +# Local Delivery Agent +protocol lda { + mail_plugins = $mail_plugins sieve +} diff --git a/roles/dovecot/files/conf.d/15-mailboxes.conf b/roles/dovecot/files/conf.d/15-mailboxes.conf new file mode 100644 index 0000000..4de88b0 --- /dev/null +++ b/roles/dovecot/files/conf.d/15-mailboxes.conf @@ -0,0 +1,25 @@ +# Mailboxes +namespace inbox { + mailbox Sent { + special_use = \Sent + auto = subscribe + } + mailbox Trash { + special_use = \Trash + auto = create + autoexpunge = 30d + } + mailbox Drafts { + special_use = \Drafts + auto = subscribe + } + mailbox Spam { + special_use = \Junk + auto = create + autoexpunge = 30d + } + mailbox Archive { + special_use = \Archive + auto = create + } +} diff --git a/roles/dovecot/files/conf.d/20-imap.conf b/roles/dovecot/files/conf.d/20-imap.conf new file mode 100644 index 0000000..0e7d4ae --- /dev/null +++ b/roles/dovecot/files/conf.d/20-imap.conf @@ -0,0 +1,2 @@ +# IMAP +imap_capability = +SPECIAL-USE diff --git a/roles/dovecot/files/conf.d/90-acl.conf b/roles/dovecot/files/conf.d/90-acl.conf new file mode 100644 index 0000000..f0c0e7a --- /dev/null +++ b/roles/dovecot/files/conf.d/90-acl.conf @@ -0,0 +1,19 @@ +## +## Mailbox access control lists. +## + +# vfile backend reads ACLs from "dovecot-acl" file from mail directory. +# You can also optionally give a global ACL directory path where ACLs are +# applied to all users' mailboxes. The global ACL directory contains +# one file for each mailbox, eg. INBOX or sub.mailbox. cache_secs parameter +# specifies how many seconds to wait between stat()ing dovecot-acl file +# to see if it changed. +plugin { + #acl = vfile:/etc/dovecot/global-acls:cache_secs=300 +} + +# To let users LIST mailboxes shared by other users, Dovecot needs a +# shared mailbox dictionary. For example: +plugin { + #acl_shared_dict = file:/var/lib/dovecot/shared-mailboxes +} diff --git a/roles/dovecot/files/conf.d/90-plugin.conf b/roles/dovecot/files/conf.d/90-plugin.conf new file mode 100644 index 0000000..8c8fccf --- /dev/null +++ b/roles/dovecot/files/conf.d/90-plugin.conf @@ -0,0 +1,11 @@ +## +## Plugin settings +## + +# All wanted plugins must be listed in mail_plugins setting before any of the +# settings take effect. See for list of plugins and +# their configuration. Note that %variable expansion is done for all values. + +plugin { + #setting_name = value +} diff --git a/roles/dovecot/files/conf.d/90-quota.conf b/roles/dovecot/files/conf.d/90-quota.conf new file mode 100644 index 0000000..3308c05 --- /dev/null +++ b/roles/dovecot/files/conf.d/90-quota.conf @@ -0,0 +1,83 @@ +## +## Quota configuration. +## + +# Note that you also have to enable quota plugin in mail_plugins setting. +# + +## +## Quota limits +## + +# Quota limits are set using "quota_rule" parameters. To get per-user quota +# limits, you can set/override them by returning "quota_rule" extra field +# from userdb. It's also possible to give mailbox-specific limits, for example +# to give additional 100 MB when saving to Trash: + +plugin { + #quota_rule = *:storage=1G + #quota_rule2 = Trash:storage=+100M + + # LDA/LMTP allows saving the last mail to bring user from under quota to + # over quota, if the quota doesn't grow too high. Default is to allow as + # long as quota will stay under 10% above the limit. Also allowed e.g. 10M. + #quota_grace = 10%% + + # Quota plugin can also limit the maximum accepted mail size. + #quota_max_mail_size = 100M +} + +## +## Quota warnings +## + +# You can execute a given command when user exceeds a specified quota limit. +# Each quota root has separate limits. Only the command for the first +# exceeded limit is executed, so put the highest limit first. +# The commands are executed via script service by connecting to the named +# UNIX socket (quota-warning below). +# Note that % needs to be escaped as %%, otherwise "% " expands to empty. + +plugin { + #quota_warning = storage=95%% quota-warning 95 %u + #quota_warning2 = storage=80%% quota-warning 80 %u +} + +# Example quota-warning service. The unix listener's permissions should be +# set in a way that mail processes can connect to it. Below example assumes +# that mail processes run as vmail user. If you use mode=0666, all system users +# can generate quota warnings to anyone. +#service quota-warning { +# executable = script /usr/local/bin/quota-warning.sh +# user = dovecot +# unix_listener quota-warning { +# user = vmail +# } +#} + +## +## Quota backends +## + +# Multiple backends are supported: +# dirsize: Find and sum all the files found from mail directory. +# Extremely SLOW with Maildir. It'll eat your CPU and disk I/O. +# dict: Keep quota stored in dictionary (eg. SQL) +# maildir: Maildir++ quota +# fs: Read-only support for filesystem quota + +plugin { + #quota = dirsize:User quota + #quota = maildir:User quota + #quota = dict:User quota::proxy::quota + #quota = fs:User quota +} + +# Multiple quota roots are also possible, for example this gives each user +# their own 100MB quota and one shared 1GB quota within the domain: +plugin { + #quota = dict:user::proxy::quota + #quota2 = dict:domain:%d:proxy::quota_domain + #quota_rule = *:storage=102400 + #quota2_rule = *:storage=1048576 +} diff --git a/roles/dovecot/files/conf.d/90-sieve-extprograms.conf b/roles/dovecot/files/conf.d/90-sieve-extprograms.conf new file mode 100644 index 0000000..17dcb77 --- /dev/null +++ b/roles/dovecot/files/conf.d/90-sieve-extprograms.conf @@ -0,0 +1,44 @@ +# Sieve Extprograms plugin configuration + +# Don't forget to add the sieve_extprograms plugin to the sieve_plugins setting. +# Also enable the extensions you need (one or more of vnd.dovecot.pipe, +# vnd.dovecot.filter and vnd.dovecot.execute) by adding these to the +# sieve_extensions or sieve_global_extensions settings. Restricting these +# extensions to a global context using sieve_global_extensions is recommended. + +plugin { + + # The directory where the program sockets are located for the + # vnd.dovecot.pipe, vnd.dovecot.filter and vnd.dovecot.execute extension + # respectively. The name of each unix socket contained in that directory + # directly maps to a program-name referenced from the Sieve script. + #sieve_pipe_socket_dir = sieve-pipe + #sieve_filter_socket_dir = sieve-filter + #sieve_execute_socket_dir = sieve-execute + + # The directory where the scripts are located for direct execution by the + # vnd.dovecot.pipe, vnd.dovecot.filter and vnd.dovecot.execute extension + # respectively. The name of each script contained in that directory + # directly maps to a program-name referenced from the Sieve script. + #sieve_pipe_bin_dir = /usr/lib/dovecot/sieve-pipe + #sieve_filter_bin_dir = /usr/lib/dovecot/sieve-filter + #sieve_execute_bin_dir = /usr/lib/dovecot/sieve-execute +} + +# An example program service called 'do-something' to pipe messages to +#service do-something { + # Define the executed script as parameter to the sieve service + #executable = script /usr/lib/dovecot/sieve-pipe/do-something.sh + + # Use some unprivileged user for executing the program + #user = dovenull + + # The unix socket located in the sieve_pipe_socket_dir (as defined in the + # plugin {} section above) + #unix_listener sieve-pipe/do-something { + # LDA/LMTP must have access + # user = vmail + # mode = 0600 + #} +#} + diff --git a/roles/dovecot/files/conf.d/90-sieve.conf b/roles/dovecot/files/conf.d/90-sieve.conf new file mode 100644 index 0000000..c7ef6c4 --- /dev/null +++ b/roles/dovecot/files/conf.d/90-sieve.conf @@ -0,0 +1,6 @@ +# Sieve Configuration +plugin { + sieve = ~/.dovecot.sieve + sieve_default = /var/lib/dovecot/sieve/default.sieve + sieve_global = /var/lib/dovecot/sieve/ +} diff --git a/roles/dovecot/files/conf.d/auth-checkpassword.conf.ext b/roles/dovecot/files/conf.d/auth-checkpassword.conf.ext new file mode 100644 index 0000000..b2fb13a --- /dev/null +++ b/roles/dovecot/files/conf.d/auth-checkpassword.conf.ext @@ -0,0 +1,21 @@ +# Authentication for checkpassword users. Included from 10-auth.conf. +# +# + +passdb { + driver = checkpassword + args = /usr/bin/checkpassword +} + +# passdb lookup should return also userdb info +userdb { + driver = prefetch +} + +# Standard checkpassword doesn't support direct userdb lookups. +# If you need checkpassword userdb, the checkpassword must support +# Dovecot-specific extensions. +#userdb { +# driver = checkpassword +# args = /usr/bin/checkpassword +#} diff --git a/roles/dovecot/files/conf.d/auth-deny.conf.ext b/roles/dovecot/files/conf.d/auth-deny.conf.ext new file mode 100644 index 0000000..ce3f1cf --- /dev/null +++ b/roles/dovecot/files/conf.d/auth-deny.conf.ext @@ -0,0 +1,15 @@ +# Deny access for users. Included from 10-auth.conf. + +# Users can be (temporarily) disabled by adding a passdb with deny=yes. +# If the user is found from that database, authentication will fail. +# The deny passdb should always be specified before others, so it gets +# checked first. + +# Example deny passdb using passwd-file. You can use any passdb though. +passdb { + driver = passwd-file + deny = yes + + # File contains a list of usernames, one per line + args = /etc/dovecot/deny-users +} diff --git a/roles/dovecot/files/conf.d/auth-dict.conf.ext b/roles/dovecot/files/conf.d/auth-dict.conf.ext new file mode 100644 index 0000000..0be4847 --- /dev/null +++ b/roles/dovecot/files/conf.d/auth-dict.conf.ext @@ -0,0 +1,16 @@ +# Authentication via dict backend. Included from 10-auth.conf. +# +# + +passdb { + driver = dict + + # Path for dict configuration file, see + # example-config/dovecot-dict-auth.conf.ext + args = /etc/dovecot/dovecot-dict-auth.conf.ext +} + +userdb { + driver = dict + args = /etc/dovecot/dovecot-dict-auth.conf.ext +} diff --git a/roles/dovecot/files/conf.d/auth-master.conf.ext b/roles/dovecot/files/conf.d/auth-master.conf.ext new file mode 100644 index 0000000..2cf128f --- /dev/null +++ b/roles/dovecot/files/conf.d/auth-master.conf.ext @@ -0,0 +1,16 @@ +# Authentication for master users. Included from 10-auth.conf. + +# By adding master=yes setting inside a passdb you make the passdb a list +# of "master users", who can log in as anyone else. +# + +# Example master user passdb using passwd-file. You can use any passdb though. +passdb { + driver = passwd-file + master = yes + args = /etc/dovecot/master-users + + # Unless you're using PAM, you probably still want the destination user to + # be looked up from passdb that it really exists. pass=yes does that. + pass = yes +} diff --git a/roles/dovecot/files/conf.d/auth-passwdfile.conf.ext b/roles/dovecot/files/conf.d/auth-passwdfile.conf.ext new file mode 100644 index 0000000..c89d28c --- /dev/null +++ b/roles/dovecot/files/conf.d/auth-passwdfile.conf.ext @@ -0,0 +1,20 @@ +# Authentication for passwd-file users. Included from 10-auth.conf. +# +# passwd-like file with specified location. +# + +passdb { + driver = passwd-file + args = scheme=CRYPT username_format=%u /etc/dovecot/users +} + +userdb { + driver = passwd-file + args = username_format=%u /etc/dovecot/users + + # Default fields that can be overridden by passwd-file + #default_fields = quota_rule=*:storage=1G + + # Override fields from passwd-file + #override_fields = home=/home/virtual/%u +} diff --git a/roles/dovecot/files/conf.d/auth-sql.conf.ext b/roles/dovecot/files/conf.d/auth-sql.conf.ext new file mode 100644 index 0000000..ccbea86 --- /dev/null +++ b/roles/dovecot/files/conf.d/auth-sql.conf.ext @@ -0,0 +1,30 @@ +# Authentication for SQL users. Included from 10-auth.conf. +# +# + +passdb { + driver = sql + + # Path for SQL configuration file, see example-config/dovecot-sql.conf.ext + args = /etc/dovecot/dovecot-sql.conf.ext +} + +# "prefetch" user database means that the passdb already provided the +# needed information and there's no need to do a separate userdb lookup. +# +#userdb { +# driver = prefetch +#} + +userdb { + driver = sql + args = /etc/dovecot/dovecot-sql.conf.ext +} + +# If you don't have any user-specific settings, you can avoid the user_query +# by using userdb static instead of userdb sql, for example: +# +#userdb { + #driver = static + #args = uid=vmail gid=vmail home=/var/vmail/%u +#} diff --git a/roles/dovecot/files/conf.d/auth-static.conf.ext b/roles/dovecot/files/conf.d/auth-static.conf.ext new file mode 100644 index 0000000..90890c5 --- /dev/null +++ b/roles/dovecot/files/conf.d/auth-static.conf.ext @@ -0,0 +1,24 @@ +# Static passdb. Included from 10-auth.conf. + +# This can be used for situations where Dovecot doesn't need to verify the +# username or the password, or if there is a single password for all users: +# +# - proxy frontend, where the backend verifies the password +# - proxy backend, where the frontend already verified the password +# - authentication with SSL certificates +# - simple testing + +#passdb { +# driver = static +# args = proxy=y host=%1Mu.example.com nopassword=y +#} + +#passdb { +# driver = static +# args = password=test +#} + +#userdb { +# driver = static +# args = uid=vmail gid=vmail home=/home/%u +#} diff --git a/roles/dovecot/files/conf.d/auth-system.conf.ext b/roles/dovecot/files/conf.d/auth-system.conf.ext new file mode 100644 index 0000000..dadb9f7 --- /dev/null +++ b/roles/dovecot/files/conf.d/auth-system.conf.ext @@ -0,0 +1,74 @@ +# Authentication for system users. Included from 10-auth.conf. +# +# +# + +# PAM authentication. Preferred nowadays by most systems. +# PAM is typically used with either userdb passwd or userdb static. +# REMEMBER: You'll need /etc/pam.d/dovecot file created for PAM +# authentication to actually work. +passdb { + driver = pam + # [session=yes] [setcred=yes] [failure_show_msg=yes] [max_requests=] + # [cache_key=] [] + #args = dovecot +} + +# System users (NSS, /etc/passwd, or similar). +# In many systems nowadays this uses Name Service Switch, which is +# configured in /etc/nsswitch.conf. +#passdb { + #driver = passwd + # [blocking=no] + #args = +#} + +# Shadow passwords for system users (NSS, /etc/shadow or similar). +# Deprecated by PAM nowadays. +# +#passdb { + #driver = shadow + # [blocking=no] + #args = +#} + +# PAM-like authentication for OpenBSD. +# +#passdb { + #driver = bsdauth + # [blocking=no] [cache_key=] + #args = +#} + +## +## User databases +## + +# System users (NSS, /etc/passwd, or similar). In many systems nowadays this +# uses Name Service Switch, which is configured in /etc/nsswitch.conf. +userdb { + # + driver = passwd + # [blocking=no] + #args = + + # Override fields from passwd + #override_fields = home=/home/virtual/%u +} + +# Static settings generated from template +#userdb { + #driver = static + # Can return anything a userdb could normally return. For example: + # + # args = uid=500 gid=500 home=/var/mail/%u + # + # LDA and LMTP needs to look up users only from the userdb. This of course + # doesn't work with static userdb because there is no list of users. + # Normally static userdb handles this by doing a passdb lookup. This works + # with most passdbs, with PAM being the most notable exception. If you do + # the user verification another way, you can add allow_all_users=yes to + # the args in which case the passdb lookup is skipped. + # + #args = +#} diff --git a/roles/dovecot/files/default.sieve b/roles/dovecot/files/default.sieve new file mode 100644 index 0000000..6709988 --- /dev/null +++ b/roles/dovecot/files/default.sieve @@ -0,0 +1,22 @@ +require ["fileinto", "mailbox"]; +/* +* Discard mail that has a spam score greater than or equal to 5 +*/ +if header :contains "X-Spam-Level" "*****" { + discard; + stop; +} +/* +* Discard messages marked as infected by virus scanner +*/ +if header :contains "X-Virus-Scan" "infected" { + discard; + stop; +} +/* +* If message is marked as spam (and falls below discard threshold) put into spam mailbox +*/ +if header :contains "X-Spam-Flag" "YES" { + fileinto "Spam"; +} + diff --git a/roles/dovecot/files/dovecot.conf b/roles/dovecot/files/dovecot.conf new file mode 100644 index 0000000..14a4cf0 --- /dev/null +++ b/roles/dovecot/files/dovecot.conf @@ -0,0 +1,16 @@ +# Enable installed protocols +!include_try /usr/share/dovecot/protocols.d/*.protocol + +dict { + #quota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext + #expire = sqlite:/etc/dovecot/dovecot-dict-sql.conf.ext +} + +# Most of the actual configuration gets included below. The filenames are +# first sorted by their ASCII value and parsed in that order. The 00-prefixes +# in filenames are intended to make it easier to understand the ordering. +!include conf.d/*.conf + +# A config file can also tried to be included without giving an error if +# it's not found: +!include_try local.conf diff --git a/roles/dovecot/files/dovecot_pam b/roles/dovecot/files/dovecot_pam new file mode 100644 index 0000000..af0e0dd --- /dev/null +++ b/roles/dovecot/files/dovecot_pam @@ -0,0 +1,8 @@ +#%PAM-1.0 + +@include common-auth +@include common-account +@include common-session + +auth required pam_unix.so +account required pam_unix.so diff --git a/roles/dovecot/handlers/main.yml b/roles/dovecot/handlers/main.yml new file mode 100644 index 0000000..e69de29 diff --git a/roles/dovecot/tasks/main.yml b/roles/dovecot/tasks/main.yml new file mode 100644 index 0000000..ce5eb2c --- /dev/null +++ b/roles/dovecot/tasks/main.yml @@ -0,0 +1,67 @@ +- name: install packages + package: + name: + - dovecot-imapd + - dovecot-sieve + state: latest + +- name: deploy dovecot.conf + copy: + src: dovecot.conf + dest: /etc/dovecot/dovecot.conf + owner: root + group: root + mode: '0644' + +- name: deploy dovecot configuration files + copy: + src: "{{ item }}" + dest: /etc/dovecot/conf.d/ + owner: root + group: root + mode: '0644' + with_fileglob: "files/conf.d/*" + +- name: deploy dovecot tls configuration file + template: + src: templates/10-ssl.conf.j2 + dest: /etc/dovecot/conf.d/10-ssl.conf + owner: root + group: root + mode: '0644' + +- name: create sieve dir + file: + path: /var/lib/dovecot/sieve + state: directory + +- name: deploy default sieve script + copy: + src: default.sieve + dest: /var/lib/dovecot/sieve/default.sieve + owner: root + group: root + mode: '0644' + +- name: compile default sieve script + command: + cmd: sievec /var/lib/dovecot/sieve/default.sieve + +- name: deploy dovecot PAM configuration + copy: + src: dovecot_pam + dest: /etc/pam.d/dovecot + owner: root + group: root + mode: '0644' + +- name: enable dovecot + systemd: + enabled: yes + masked: no + name: dovecot + +- name: restart dovecot + service: + name: dovecot + state: restarted diff --git a/roles/dovecot/templates/10-ssl.conf.j2 b/roles/dovecot/templates/10-ssl.conf.j2 new file mode 100644 index 0000000..8efa1d2 --- /dev/null +++ b/roles/dovecot/templates/10-ssl.conf.j2 @@ -0,0 +1,20 @@ +# SSL/TLS Configuration +ssl = required +ssl_key = "]*\.(exe|pif|com|dll|vbs|bat|sh|bash|so|zip|tar|gz|cpio)/ REJECT +# Block message/partial vulnerability +/message\/partial/ REJECT +# CVE-2022-1328 mitigation - block messages with uuencode +/^Content-Transfer-Encoding:.*uuencode.*/ REJECT +# Remove Received string that is created when spamassassin reinjects message into postfix +# This is to prevent leaking the userid of the spamassassin user +/^Received:.*userid.*/ IGNORE +# Remove User-Agent strings from headers +/^User-Agent: .*/ IGNORE diff --git a/roles/postfix/handlers/main.yml b/roles/postfix/handlers/main.yml new file mode 100644 index 0000000..e69de29 diff --git a/roles/postfix/tasks/main.yml b/roles/postfix/tasks/main.yml new file mode 100644 index 0000000..0b482ea --- /dev/null +++ b/roles/postfix/tasks/main.yml @@ -0,0 +1,84 @@ +- name: install packages + package: + name: + - postfix + state: latest + +- name: deploy postfix main.cf + template: + src: main.cf.j2 + dest: /etc/postfix/main.cf + owner: root + group: root + mode: '0644' + +- name: deploy postfix master.cf + template: + src: master.cf.j2 + dest: /etc/postfix/master.cf + owner: root + group: root + mode: '0644' + +- name: create mailadmin user + user: + name: mailadmin + shell: /usr/sbin/nologin + password_lock: yes + +- name: deploy aliases file + template: + src: aliases + dest: /etc/aliases + owner: root + group: root + mode: '0644' + +- name: deploy login_maps + template: + src: login_maps + dest: /etc/postfix/login_maps + owner: root + group: root + mode: '0644' + +- name: deploy local_maps + template: + src: local_maps + dest: /etc/postfix/local_maps + owner: root + group: root + mode: '0644' + +- name: update address databases + shell: | + newaliases + postmap /etc/postfix/login_maps + postmap /etc/postfix/local_maps + +- name: deploy header checks file + copy: + src: header_checks + dest: /etc/postfix/header_checks + owner: root + group: root + mode: '0644' + +- name: deploy body checks file + copy: + src: body_checks + dest: /etc/postfix/body_checks + owner: root + group: root + mode: '0644' + +- name: enable postfix + systemd: + enabled: yes + masked: no + name: postfix + +- name: restart postfix + service: + name: postfix + state: restarted diff --git a/roles/postfix/templates/aliases b/roles/postfix/templates/aliases new file mode 100644 index 0000000..6cb2ca6 --- /dev/null +++ b/roles/postfix/templates/aliases @@ -0,0 +1,3 @@ +postmaster: mailadmin +root: mailadmin +dmarc: mailadmin diff --git a/roles/postfix/templates/local_maps b/roles/postfix/templates/local_maps new file mode 100644 index 0000000..57592f9 --- /dev/null +++ b/roles/postfix/templates/local_maps @@ -0,0 +1 @@ +mailadmin mailadmin diff --git a/roles/postfix/templates/login_maps b/roles/postfix/templates/login_maps new file mode 100644 index 0000000..d3ace34 --- /dev/null +++ b/roles/postfix/templates/login_maps @@ -0,0 +1 @@ +mailadmin@{{ domain }} mailadmin diff --git a/roles/postfix/templates/main.cf.j2 b/roles/postfix/templates/main.cf.j2 new file mode 100644 index 0000000..8a2d767 --- /dev/null +++ b/roles/postfix/templates/main.cf.j2 @@ -0,0 +1,69 @@ +smtpd_banner = $myhostname ESMTP $mail_name +biff = no + +# appending .domain is the MUA's job. +append_dot_mydomain = no + +# Uncomment the next line to generate "delayed mail" warnings +#delay_warning_time = 4h + +readme_directory = no + +# See http://www.postfix.org/COMPATIBILITY_README.html -- default to 2 on +# fresh installs. +compatibility_level = 2 + +# TLS parameters +smtpd_tls_cert_file = /etc/letsencrypt/live/mail.{{ domain }}/fullchain.pem +smtpd_tls_key_file = /etc/letsencrypt/live/mail.{{ domain }}/privkey.pem +smtpd_tls_security_level = encrypt +smtp_tls_CApath=/etc/ssl/certs +smtp_tls_CAfile=/etc/ssl/certs/ca-certificates.crt +smtp_tls_security_level = encrypt +smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache + +smtpd_relay_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination +myhostname = {{ mail_domain }} +alias_maps = hash:/etc/aliases +alias_database = hash:/etc/aliases +myorigin = $mydomain +mydestination = $myhostname, $mydomain, localhost +relayhost = +mynetworks = 127.0.0.0/8 [::1]/128 +mailbox_size_limit = 0 +recipient_delimiter = + +inet_interfaces = all +inet_protocols = ipv4 +smtpd_tls_auth_only = yes +smtpd_tls_mandatory_protocols = !SSLv2, !SSLv3, !TLSv1, !TLSv1.1 +smtpd_tls_protocols = !SSLv2, !SSLv3, !TLSv1, !TLSv1.1 +smtp_tls_mandatory_protocols = !SSLv2, !SSLv3, !TLSv1, !TLSv1.1 +smtp_tls_protocols = !SSLv2, !SSLv3, !TLSv1, !TLSv1.1 +tls_preempt_cipherlist = yes +smtpd_tls_ciphers = high +smtpd_tls_mandatory_ciphers = high +smtp_tls_ciphers = high +smtp_tls_mandatory_ciphers = high +smtpd_tls_exclude_ciphers = aNULL, eNULL, EXP, LOW, MEDIUM, PSK, SRP, SHA1, kRSA, CAMELLIA, ARIA, DSS, RSA+AES, ADH, AECDH +smtp_tls_exclude_ciphers = aNULL, eNULL, EXP, LOW, MEDIUM, PSK, SRP, SHA1, kRSA, CAMELLIA, ARIA, DSS, RSA+AES, ADH, AECDH +smtpd_sasl_type = dovecot +smtpd_sasl_path = private/auth +smtpd_sasl_auth_enable = yes +smtpd_sasl_security_options = noanonymous, noplaintext +smtpd_sasl_tls_security_options = noanonymous +smtpd_helo_required = yes +smtpd_sender_login_maps = proxy:hash:/etc/postfix/login_maps +smtpd_helo_restrictions = reject_unknown_helo_hostname, reject_non_fqdn_helo_hostname +smtpd_sender_restrictions = reject_sender_login_mismatch, reject_non_fqdn_sender, reject_unknown_sender_domain +smtpd_recipient_restrictions = reject_non_fqdn_recipient, reject_unknown_recipient_domain, permit_sasl_authenticated, reject_unauth_destination, check_policy_service unix:private/postgrey, check_policy_service unix:private/policyd-spf, reject_rbl_client zen.spamhaus.org +smtpd_data_restrictions = reject_unauth_pipelining +disable_vrfy_command = yes +local_recipient_maps = proxy:hash:/etc/postfix/local_maps $alias_maps +home_mailbox = Mail/Inbox/ +mailbox_command = /usr/lib/dovecot/deliver +header_checks = regexp:/etc/postfix/header_checks +body_checks = regexp:/etc/postfix/body_checks +postscreen_dnsbl_sites = zen.spamhaus.org +postscreen_dnsbl_action = enforce +postscreen_greet_action = enforce +policyd-spf_time_limit = 3600 diff --git a/roles/postfix/templates/master.cf.j2 b/roles/postfix/templates/master.cf.j2 new file mode 100644 index 0000000..ea64537 --- /dev/null +++ b/roles/postfix/templates/master.cf.j2 @@ -0,0 +1,84 @@ +# ========================================================================== +# service type private unpriv chroot wakeup maxproc command + args +# (yes) (yes) (no) (never) (100) +# ========================================================================== +smtp inet n - y - 1 postscreen +pickup unix n - y 60 1 pickup +cleanup unix n - y - 0 cleanup +qmgr unix n - n 300 1 qmgr +tlsmgr unix - - y 1000? 1 tlsmgr +rewrite unix - - y - - trivial-rewrite +bounce unix - - y - 0 bounce +defer unix - - y - 0 bounce +trace unix - - y - 0 bounce +verify unix - - y - 1 verify +flush unix n - y 1000? 0 flush +proxymap unix - - n - - proxymap +proxywrite unix - - n - 1 proxymap +smtp unix - - y - - smtp +relay unix - - y - - smtp + -o syslog_name=postfix/$service_name +showq unix n - y - - showq +error unix - - y - - error +retry unix - - y - - error +discard unix - - y - - discard +local unix - n n - - local +virtual unix - n n - - virtual +lmtp unix - - y - - lmtp +anvil unix - - y - 1 anvil +scache unix - - y - 1 scache +postlog unix-dgram n - n - 1 postlogd + +# ==================================================================== +# Interfaces to non-Postfix software. Be sure to examine the manual +# pages of the non-Postfix software to find out what options it wants. +# +# Many of the following services use the Postfix pipe(8) delivery +# agent. See the pipe(8) man page for information about ${recipient} +# and other message envelope options. +# ==================================================================== +maildrop unix - n n - - pipe + flags=DRXhu user=vmail argv=/usr/bin/maildrop -d ${recipient} + +uucp unix - n n - - pipe + flags=Fqhu user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient) + +ifmail unix - n n - - pipe + flags=F user=ftn argv=/usr/lib/ifmail/ifmail -r $nexthop ($recipient) + +bsmtp unix - n n - - pipe + flags=Fq. user=bsmtp argv=/usr/lib/bsmtp/bsmtp -t$nexthop -f$sender $recipient + +scalemail-backend unix - n n - 2 pipe + flags=R user=scalemail argv=/usr/lib/scalemail/bin/scalemail-store ${nexthop} ${user} ${extension} + +mailman unix - n n - - pipe + flags=FRX user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py ${nexthop} ${user} + +smtpd pass - - y - - smtpd + -o content_filter=spamassassin + -o smtpd_milters=unix:opendkim/opendkim.sock,unix:opendmarc/opendmarc.sock +tlsproxy unix - - y - 0 tlsproxy + +dnsblog unix - - y - 0 dnsblog + +submissions inet n - y - - smtpd + -o smtpd_tls_wrappermode=yes + -o smtpd_tls_security_level=encrypt + -o smtpd_tls_auth_only=yes + -o smtpd_sasl_auth_enable=yes + -o smtpd_client_restrictions=permit_sasl_authenticated,permit_mynetworks,reject + -o smtpd_helo_restrictions= + -o smtpd_sender_restrictions=permit_mynetworks,reject_sender_login_mismatch + -o smtpd_recipient_restrictions=reject_non_fqdn_recipient,reject_unknown_recipient_domain,permit_sasl_authenticated,permit_mynetworks,reject + -o syslog_name=postfix/submissions + -o smtpd_tls_protocols=!SSLv2,!SSLv3,!TLSv1,!TLSv1.1,!TLSv1.2 + -o smtpd_tls_mandatory_protocols=!SSLv2,!SSLv3,!TLSv1,!TLSv1.1,!TLSv1.2 + -o smtpd_milters=unix:opendkim/opendkim.sock + +spamassassin unix - n n - - pipe user=debian-spamd + argv=/usr/bin/spamc --socket=/var/spool/postfix/spamd/spamd.sock -e /usr/sbin/sendmail -oi + -f ${sender} ${recipient} + +policyd-spf unix - n n - 0 spawn user=policyd-spf + argv=/usr/bin/policyd-spf diff --git a/roles/postgrey/defaults/main.yml b/roles/postgrey/defaults/main.yml new file mode 100644 index 0000000..e69de29 diff --git a/roles/postgrey/files/postgrey b/roles/postgrey/files/postgrey new file mode 100644 index 0000000..d9a79d5 --- /dev/null +++ b/roles/postgrey/files/postgrey @@ -0,0 +1,2 @@ +POSTGREY_OPTS="--unix=/var/spool/postfix/private/postgrey --privacy" +POSTGREY_TEXT="Greylisted - see https://www.greylisting.org" diff --git a/roles/postgrey/handlers/main.yml b/roles/postgrey/handlers/main.yml new file mode 100644 index 0000000..e69de29 diff --git a/roles/postgrey/tasks/main.yml b/roles/postgrey/tasks/main.yml new file mode 100644 index 0000000..7c0caa7 --- /dev/null +++ b/roles/postgrey/tasks/main.yml @@ -0,0 +1,24 @@ +- name: install packages + package: + name: + - postgrey + state: latest + +- name: deploy configuration + copy: + src: postgrey + dest: /etc/default/postgrey + owner: root + group: root + mode: '0644' + +- name: enable postgrey + systemd: + enabled: yes + masked: no + name: postgrey + +- name: restart postgrey + service: + name: postgrey + state: restarted diff --git a/roles/spamassassin/defaults/main.yml b/roles/spamassassin/defaults/main.yml new file mode 100644 index 0000000..e69de29 diff --git a/roles/spamassassin/files/defaults b/roles/spamassassin/files/defaults new file mode 100644 index 0000000..a38795c --- /dev/null +++ b/roles/spamassassin/files/defaults @@ -0,0 +1,9 @@ +OPTIONS="--listen /var/run/spamd.sock --max-children 5 --socketpath=/var/spool/postfix/spamd/spamd.sock --socketowner root --socketgroup root --socketmode 0666" + +PIDFILE=/var/run/spamd.pid + +# Cronjob +# Set to anything but 0 to enable the cron job to automatically update +# spamassassin's rules on a nightly basis +CRON=1 + diff --git a/roles/spamassassin/handlers/main.yml b/roles/spamassassin/handlers/main.yml new file mode 100644 index 0000000..e69de29 diff --git a/roles/spamassassin/tasks/main.yml b/roles/spamassassin/tasks/main.yml new file mode 100644 index 0000000..4c69be5 --- /dev/null +++ b/roles/spamassassin/tasks/main.yml @@ -0,0 +1,40 @@ +- name: install packages + package: + name: + - spamassassin + state: latest + +- name: make directory in postfix chroot + file: + path: /var/spool/postfix/spamd + owner: root + group: root + mode: '0755' + state: directory + +- name: deploy configuration + template: + src: local.cf.j2 + dest: /etc/spamassassin/local.cf + owner: root + group: root + mode: '0644' + +- name: deploy defaults file + copy: + src: defaults + dest: /etc/default/spamd + owner: root + group: root + mode: '0644' + +- name: enable spamassassin + systemd: + enabled: yes + masked: no + name: spamd + +- name: restart spamassassin + service: + name: spamd + state: restarted diff --git a/roles/spamassassin/templates/local.cf.j2 b/roles/spamassassin/templates/local.cf.j2 new file mode 100644 index 0000000..1fdc978 --- /dev/null +++ b/roles/spamassassin/templates/local.cf.j2 @@ -0,0 +1,18 @@ +# SpamAssassin Configuration +# Clearly indicate message is spam to user +rewrite_header Subject *****SPAM***** +rewrite_header From *****SPAM***** + +# Halves default spam score thus implementing a very strict spam policy +# Comment or edit as needed for your deployment +required_score {{ spam_score }} + +# Attach original messages as text/plain instead of message/rfc822 to spam reports +# This is basically a safety net to prevent mail clients from automatically loading +# attached spam messages. Note though that this makes the original message harder to recover +# If this is not something you are worried about, comment the next line to use the default. +report_safe 2 + +# This specifies languages considered OK for incoming mail +# If you expect to receive mail in non-western character sets, comment or edit as needed +ok_locales {{ sa_locales }} diff --git a/run.yml b/run.yml new file mode 100644 index 0000000..d461d30 --- /dev/null +++ b/run.yml @@ -0,0 +1,79 @@ +- name: setup + hosts: mail_server + become: yes + + tasks: + - name: set system hostname + hostname: + name: "{{ mail_domain }}" + + - name: install packages + package: + name: + - ufw + - gnupg + - certbot + state: latest + + - name: allow http for certificate challenges + ufw: + rule: allow + port: '80' + proto: tcp + + - name: allow smtp + ufw: + rule: allow + port: '25' + proto: tcp + + - name: allow smtps + become: yes + ufw: + rule: allow + port: '465' + proto: tcp + + - name: allow imaps + ufw: + rule: allow + port: '993' + proto: tcp + + - name: get certificate + command: + cmd: "certbot certonly --standalone -d {{ mail_domain }} -m {{ cert_email }} --non-interactive --agree-tos --no-eff-email" + +- name: configure services + hosts: mail_server + become: yes + roles: + - postfix + - dovecot + - opendkim + - opendmarc + - postgrey + - spamassassin + - policyd_spf + +- name: get dns recordV + hosts: mail_server + become: yes + + tasks: + - name: get dns entries + shell: | + pubkey="$(tr -d '\n' $HOME/dns_records + register: dns_result + + - name: inform where to get records + debug: + msg: "You can now find the DNS records you need to set at /home/root/dns_records" -- cgit v1.2.3