On 10/7/18 4:09 PM, Dave McGuire wrote:
> On 10/07/2018 07:05 PM, Ralph Seichter wrote:
>>> Personally I rather like it when a piece of infrastructure software
>>> stops being a "moving target".
>>
>> I like to know if software currently used in production systems is
>> maintained, i.e. how
On 08.10.18 01:09, Dave McGuire wrote:
> are there any bugs in amavisd-new that anyone cares about at this
> point?
Yes, DKIM-related, see my original message. From what I can tell the
available patch does not fix everything. Because of this issue I have
disabled amavisd-new's DKIM-features
On 10/07/2018 07:05 PM, Ralph Seichter wrote:
>> Personally I rather like it when a piece of infrastructure software
>> stops being a "moving target".
>
> I like to know if software currently used in production systems is
> maintained, i.e. how likely it is that bugs will be fixed in a
>
On 07.10.18 23:35, Dave McGuire wrote:
> Personally I rather like it when a piece of infrastructure software
> stops being a "moving target".
I like to know if software currently used in production systems is
maintained, i.e. how likely it is that bugs will be fixed in a
reasonable amount of
On 10/07/2018 04:15 PM, Boris Gulay wrote:
>> Would that not only give a false sense of amavisd-new being maintained
>> after all? I still hope Mark Martinec will answer (I mailed him today)
> I've sent him a letter with some fixed more then two month ago. Still no
> reply.
> Just check when last
Boris Gulay skrev den 2018-10-07 21:24:
Benny Pedersen писал 2018-10-07 17:34:
Ralph Seichter skrev den 2018-10-07 14:48:
On 07.10.18 12:12, Alexander Dalloz wrote:
That's too a one man show?
See https://github.com/rspamd/rspamd/blob/master/AUTHORS.md
impresive that amavisd have less
Ralph Seichter писал 2018-10-07 15:44:
On 07.10.18 12:23, Bernhard Schmidt wrote:
Would that not only give a false sense of amavisd-new being maintained
after all? I still hope Mark Martinec will answer (I mailed him today)
I've sent him a letter with some fixed more then two month ago.
Benny Pedersen писал 2018-10-07 17:34:
Ralph Seichter skrev den 2018-10-07 14:48:
On 07.10.18 12:12, Alexander Dalloz wrote:
That's too a one man show?
See https://github.com/rspamd/rspamd/blob/master/AUTHORS.md
impresive that amavisd have less tickets
Because rspamd is actively
Ralph Seichter skrev den 2018-10-07 14:48:
On 07.10.18 12:12, Alexander Dalloz wrote:
That's too a one man show?
See https://github.com/rspamd/rspamd/blob/master/AUTHORS.md
impresive that amavisd have less tickets
On 07.10.18 12:12, Alexander Dalloz wrote:
> That's too a one man show?
See https://github.com/rspamd/rspamd/blob/master/AUTHORS.md
-Ralph
On 07.10.18 12:23, Bernhard Schmidt wrote:
> Not really merge them or even do a new release (which is a fork
> needing manpower and coordination to avoid fragmentation), but as a
> central point for known defects and patches floating around on the
> mailing list.
Would that not only give a false
Hi,
I think a good start would be to import the past amavisd-new releases into
Github / Gitlab and start collecting issues and pull requests for bugfixes. Not
really merge them or even do a new release (which is a fork needing manpower
and coordination to avoid fragmentation), but as a central
Am 07.10.2018 um 11:27 schrieb Ralf Hildebrandt:
We recently migrated away from amavisd-new and are now using rspamd.
That's too a one man show?
Alexander
We recently migrated away from amavisd-new and are now using rspamd.
Ralph Seichter wrote:
> On 07.10.18 00:26, Giovanni Bechis wrote:
>
>> I think that if Mark Martinek is not maintaining any more the
>> community should step up and fork the project.
>
> Are you volunteering? I've made some local modifications over time, but
> amavisd-new with its >35000 lines
Zimbra also comes with it. What will be zimbra's future? What about
spamtitan?
On Oct 7, 2018 4:46 AM, "Ralph Seichter" wrote:
> On 07.10.18 00:26, Giovanni Bechis wrote:
>
> > I think that if Mark Martinek is not maintaining any more the
> > community should step up and fork the project.
>
>
16 matches
Mail list logo