I just tagged the 0.92 release of qpsmtpd-dev.
It can be downloaded by clicking the Tags button on the github project page at
https://github.com/qpsmtpd-dev/qpsmtpd-dev. The changes are listed below.
Matt
0.92 Apr 20, 2013
new plugins: dmarc, fcrdns
new feature: DKIM message signing
k.
>
> Should one add plugins? Perhaps as placeholder files referring to
> where to get the genuine article, to reduce the possibility of naming
> collisions?
Using placeholders is one way to avoid collisions.
Another is to have a plugin registry, like this one:
https://github.com/q
> Calling all forks.
>
> If you have a fork of QP and would like to become much less forked, or
> perhaps even be able to use QP without being forked at all, this would be a
> great time to bring out your fork.
Should one add plugins? Perhaps as placeholder files referring to
where to get the ge
mployers
>>> to put most of our codebase at your disposal to do this. Even if the
>>> result wasn't something we could use, and we had to remain forked... at
>>> least it would be useful to _someone_ :)
>>
>> https://github.com/qpsmtpd-dev/qpsmtpd-dev
&g
disposal to do this. Even if the
>> result wasn't something we could use, and we had to remain forked... at
>> least it would be useful to _someone_ :)
>
> https://github.com/qpsmtpd-dev/qpsmtpd-dev
OK, as promised, I've asked my employers to put most of our codebase
>> I hereby propose the creation of qpsmtpd-dev.
>>
>> The primary aim is merging the forks maintained by myself, Steve, Chris,
>> Jared, and others. I am willing to do much of the work to accomplish this.
>> I believe there is much to be gained by doing so, not the least
> I am to the point where I need to deploy. I was hoping that I could get my
> changes merged into the main branch, but that appears impossible. I hate
> the prospect of forking, but I see few alternatives.
>
> I hereby propose the creation of qpsmtpd-dev.
>
> The primary aim
I totally agree with you.
A qpsmtpd-dev branch will speed tests allot.
José Borges Ferreira
PS: the log parser looks really good.
On Fri, Jun 22, 2012 at 10:14 AM, Matt Simerson wrote:
>
> http://www.nntp.perl.org/group/perl.qpsmtpd/2009/01/msg8376.html
>
> This thread almo
rking, but I see few alternatives.
I hereby propose the creation of qpsmtpd-dev.
The primary aim is merging the forks maintained by myself, Steve, Chris, Jared,
and others. I am willing to do much of the work to accomplish this. I believe
there is much to be gained by doing so, not the least o
