Project status

[mindrunner]

What is the status of this project. I do not see a lot of activity and a lot of open tickets / PRs.

Is this the way to go, or are there other open implementations of this standard out there?

[kurta]

There are several other open implementations, depending on your language preference (Perl, Go). I suspect that the open tickets here have mostly been addressed, but just not cleaned out.

…

--Kurt Andersen

On Thu, Jan 2, 2020, 13:39 lukas ***@***.***> wrote: What is the status of this project. I do not see a lot of activity and a lot of open tickets / PRs. Is this the way to go, or are there other open implementations of this standard out there? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#123?email_source=notifications&email_token=AAGU3SOEBOARLFXUQ2QSDATQ3ZNHPA5CNFSM4KCG6RR2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IDYLDJA>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGU3SKW45Z2B3RODLNPJDTQ3ZNHPANCNFSM4KCG6RRQ> .

[mindrunner]

Thanks for the clarification. It's not really about language. I want to implement ARC into docker-mailserver and I am looking for the best and most stable solution. Can you point me to the other implementations and/or give recommendations?

See here

[kurta]

How do you currently support DKIM? Using a matching ARC implementation would probably be the lowest friction (I'll look up the other implementations any send along links later today).

…

--Kurt

On Thu, Jan 2, 2020, 19:44 lukas ***@***.***> wrote: Thanks for the clarification. It's not really about language. I want to implement ARC into (docker-mailserver)[ https://github.com/tomav/docker-mailserver/] and I am looking for the best and most stable solution. Can you point me to the other implementations and/or give recommendations? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#123?email_source=notifications&email_token=AAGU3SKJUK2OWH4JWM27R6DQ32YDPA5CNFSM4KCG6RR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIAGMDY#issuecomment-570451471>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGU3SO6VIELE4O4ZECD6MLQ32YDPANCNFSM4KCG6RRQ> .

[mindrunner]

Hi Kurt! Thanks for jumping in! :)

docker-mailserver is using OpenDKIM. Does that answer the question?

Not sure how related this is, but docker-mailserver does not use rspamd (yet). See docker-mailserver/docker-mailserver#975

I am mentioning this, because I saw Mailu implemented ARC by using rspamd. Seemed quite simple there. The patch is tiny.

[kurta]

Yes, rspamd has had ARC support for quite some time. OpenARC is pretty much the counterpart for OpenDKIM. You can find a list of the other implementations at http://arc-spec.org/?page_id=79 and I know from earlier correspondence that there is also a recent Golang implementation published at https://github.com/Viruthagiri/go-emailauth/blob/master/README.md

…

--Kurt

On Fri, Jan 3, 2020 at 9:05 AM lukas ***@***.***> wrote: Hi Kurt! Thanks for jumping in! :) docker-mailserver <https://github.com/tomav/docker-mailserver> is using OpenDKIM <http://www.opendkim.org/>. Does that answer the question? Not sure how related this is, but docker-mailserver <https://github.com/tomav/docker-mailserver> does not use rspamd <https://www.rspamd.com/> (yet). See docker-mailserver/docker-mailserver#975 <docker-mailserver/docker-mailserver#975> I am mentioning this, because I saw Mailu <https://mailu.io/> implemented ARC by using rspamd <https://www.rspamd.com/>. Seemed quite simple there. The patch <Mailu/Mailu#616> is tiny. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#123?email_source=notifications&email_token=AAGU3SMIK4OWHXAL45CUT53Q35V5DA5CNFSM4KCG6RR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIBS4TA#issuecomment-570633804>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGU3SNVRKN4NVFREJGS6TDQ35V5DANCNFSM4KCG6RRQ> .

[mindrunner]

Alright, thanks. So I suppose I have to / should go with OpenARC if we are already using OpenDKIM, right?

I feel a little bit lost and the documentation seems quite thin. Any poke to the right starting point?

[kurta]

That's probably reasonable. Try sending a query to [email protected] - there may be a few people there with starter guidance readily at hand. Adding that into the repo sounds like it would be a good addition :-)

…

--Kurt

On Fri, Jan 3, 2020 at 4:30 PM lukas ***@***.***> wrote: Alright, thanks. So I suppose I have to / should go with OpenARC if we are already using OpenDKIM, right? I feel a little bit lost and the documentation seems quite thin. Any poke to the right starting point? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#123?email_source=notifications&email_token=AAGU3SPY5LOFX3NTSQMLQP3Q37KBVA5CNFSM4KCG6RR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEICMO3A#issuecomment-570738540>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGU3SNNCDS2N5ECK2IGZOTQ37KBVANCNFSM4KCG6RRQ> .

[mindrunner]

Found this: #120

@AntiFreeze any chance, we can merge some of the open PRs? :)

[flowerysong]

I would currently be wary of using OpenARC unless you're planning to maintain your own custom builds and watch for available patches; if I were relying on upstream releases to address major interoperability issues like #121 we would evidently still be waiting and a huge chunk of our traffic would be handled incorrectly.

[mindrunner]

Yes, I fully agree. This is why I created this thread. But what are my options?

[AntiFreeze]

@mindrunner this project is still active, thank you for reaching out.

The availability of the primary developers was dramatically reduced last year, which slowed down responses to new issues. We've been working on expanding coverage so that new issues/PRs/bugs/etc. are all dealt with in a timely manner. We're not quite there yet, though.

I'll check with @mskucherawy, but I thought issues like #121 were resolved a while ago, and if all we need is a new release and some packages to help people deploy this widely, we'll get on that ASAP.

[mindrunner]

Hi @AntiFreeze
Thank you for answering! I am happy to hear, this is making progress and I can/will help wherever I can! :)

I started working on the integration into docker-mailserver and it looks quite good so far.

Let's get the open PRs merged and tickets cleaned up. That would be great. Also official builds deb/rpm/tar.gz will be really helpful. :)

We've been working on expanding coverage

What does that mean in specific? Are you hiring people?

[flowerysong]

@AntiFreeze It's now been two months since your comment claiming this project is active, and a total of six months since #121 was opened. This is a one-line change that fixes parsing of seals generated by Microsoft (and possibly other implementations), and no maintainer has cared enough to merge it, let alone cut a new release.

The project might not be dead, but it's definitely not active.

[mindrunner]

+1

[kroeckx]

Which seems to be about the same state as OpenDMARC and OpenDKIM, which are also from The Trusted Domain Project . OpenDMARC had it's last commit and release 3 years ago while it has several unfixed security issues. OpenDKIM had it's last release 5 years ago, with single commit that fixed a typo 3 years ago.

[martinbogo]

And we're up and running again. I'm the maintainer, and Murray and I are working on new releases. Beta2 is up with a minor documentation fix and I'm doing code merges and regression testing on a number of issues on OpenARC/DMARC/DKIM to bring it in line with the requirements of the downstream integrators.

Closing this issue.