October 2018 - amavis-devel

Perl development styleguide
by Ralph Seichter 01 Nov '18

01 Nov '18

I use 'autopep8' for Python programming, and I wonder if there is an equivalent tool that enforces a Perl coding styleguide. Also, does such a styleguide actually exist? Perl's whole TMTOWTDI approach still makes me uncomfortable, to be honest. ;-) -Ralph

4 6

amavis or amavisd-new?
by Patrick Ben Koetter 25 Oct '18

25 Oct '18

In the beginning amavis was called amavis. Then the project was forked. Then there were three. Only amavisd-new survived. It is now hosted on amavis.org. I'd like to call amavisd-new amavis again. If we do so, I'd update the documentation accordingly. Opinions? p@rick -- [*] sys4 AG https://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG,80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief Aufsichtsratsvorsitzender: Florian Kirstein

4 3

Filing GitLab issues for merge requests
by Ralph Seichter 15 Oct '18

15 Oct '18

I'd like to suggest that a GitLab issue should be filed for our merge requests, and that merge requests should link to at least one issue. This would make it easier for non-contributors who wish to file any type of issue to see if somebody has already worked on that aspect. In my experience, this can avoid duplicates. From what I see, users with less technical aptitude tend to look more at the existing issues than at merge requests. Also, the issue can be used for discussions with non- contributors, leaving the pull request conversations more focused on technical aspects. See also: https://about.gitlab.com/2016/03/03/start-with-an-issue/ https://about.gitlab.com/2016/03/08/gitlab-tutorial-its-all-connected/ -Ralph

3 3

Rewriting amavisd.conf
by Patrick Ben Koetter 12 Oct '18

12 Oct '18

What's in amavis.conf and how it is (not) structured, is one of the biggest problems amavis users have. I've learned that in many amavis trainings I've given so far. What also adds is the fact, that amavisd.conf seems to be driven by a developers mindset/view and not an operators/admin one. I would like to come up with a completely new amavisd.conf. It should: - Add a section for general service option - Add sections that group parameters/options by content class (and not functionality) - Add a section for policy banks Opinions? Objections? p@rick -- [*] sys4 AG https://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG,80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief Aufsichtsratsvorsitzender: Florian Kirstein

3 6

Our next steps
by Alexander Wirt 12 Oct '18

12 Oct '18

Hi, as you maybe already know I am also one of the persons now responsible for amavisd-new (yai...). I maintained amavisd-new for more than a decade in Debian and I run amavisd-new for several customers since ~2002. We will need some time to properly setup the new amavisd-new project, but we plan to work on it at the weekend. We plan to work on the following things before the next release - establish a proper git and release workflow - organize the bugtracker - build website and documentation with gitlab ci/pages - split amavisd-new into proper perl modules (we can reassamble it for the release, but we really don't want to develop the monolothic binary) - my company (credativ) developed a test framework for amavisd-new and custom modules that we want to integrate into amavisd-new - setup CI jobs We need your help! If you are interested to work with us on amavisd-new, get in touch with us :). Thats it for now Alex (formorer)

2 2

Removing README.courier(-old)
by Patrick Ben Koetter 12 Oct '18

12 Oct '18

It has been years I've heard anyone asking questions about the courier mail server. I think it is of no relevance anymore. This said, I'd like to remove the documentation for Courier layed out in - README.courier - README.courier-old Any objections? p@rick -- [*] sys4 AG https://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG,80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief Aufsichtsratsvorsitzender: Florian Kirstein

3 4

README.banned: Purpose?
by Patrick Ben Koetter 12 Oct '18

12 Oct '18

What's the purpose of README.banned in the README_FILES directory? It contains log/output of message parts found by amavis. p@rick -- [*] sys4 AG https://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG,80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief Aufsichtsratsvorsitzender: Florian Kirstein

2 1

documentation: roadmap (draft)
by Patrick Ben Koetter 11 Oct '18

11 Oct '18

I'm not a Perl programmer, but I am good when it comes to write code that programs the human mind - documentation. Yeah, I know. Strange person… ;-) I really would like to get my hands dirty on amavis' documentation, but I need to plan carefully, as there are only a few cycles left to work on amavis at the moment. My current plan is to - research what gitlab provides/requires for a documentation build chain - define types of documentation amavis should deliver e.g. man-pages, INSTALL guide, documentation that describes what amavis is, how it gets to work and what it can do. - screen the existing documentation for content we can use to create the upper deliverables - separate content that isn't really a README_FILE, e.g. the SQL schemas - create missing documentation If you want to join me, either writing documentation yourself or proofreading what I wrote, you are more than welcome. p@rick -- [*] sys4 AG https://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG,80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief Aufsichtsratsvorsitzender: Florian Kirstein

1 0

Initial ML Setup... ;-)
by Patrick Ben Koetter 11 Oct '18

11 Oct '18

Hello everybody, if you received this mail, then the mailing list works (its been a while Ralf and I had a look a the MLM config). It also means you are somehow interested to contribute to amavis development in some way. That's good. amavis needs your help. We need to fix bugs, improve documentation and we need to think about the future of content filtering and how amavis can and should relate to that. But before that we will need to organize ourselves and the project a little bit. Not too much. Just enough to ensure our efforts will have effect. And hopefully not to religious. My primary goal is to get things done. Regarding this aspect I prefer leight weight organziation and a few, simple rules that work most of the time over the perfect thing. I've begun to add a few thoughts and ideas on organization to the issue tracker. Feel free to comment (if you own an account) or simply reply here in the list. Regards, p@rick -- [*] sys4 AG https://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG,80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief Aufsichtsratsvorsitzender: Florian Kirstein

2 3