The maintainer is missing.

[tommy3001]

Where is Alexandre Cesaro?
The chief of go-gomail.

[ivy]

Are there any active forks of gomail that anyone's aware of? If no one is able to reach @alexcesaro perhaps we can merge some of these pull requests somewhere else?

[pedromorgan]

@ivy Snag is that "go" needs the import path github.com/go-gomail/gomail`. Merging elsewhere will require changes to all the import paths.

Maybe @alexcesaro should add a couple of maintainers

[ivy]

@pedromorgan We might not have any other choice. It looks like @alexcesaro hasn't been active on GitHub since mid-2016:

I sent him an email to see what we can do.

[ivy]

Now what? 😕

[pedromorgan]

How about https://github.com/go-mail/gomail as new location.. ??

Need to add a few active members to the organisation, and change the imports

[ivy]

@pedromorgan Thanks for the org invite. Could you also turn on issue tracking? Also, if we rename the repo from "gomail" to just "mail" we can shorten the gopkg.in import to: gopkg.in/mail.v2

[pedromorgan]

@ivy The only snag with renaming to mail, is the namespace changes, and now I have to change imports and code. Prefer as gomail (and reading go.pkg docs)

[ivy]

If you're going to move to a fork, it isn't that big of a deal is it? Understood however.

[ivy]

I would add however that your import line could just as easily be:

import gomail "gopkg.in/mail.v2"

[pedromorgan]

import  "gopkg.in/go-mail/gomail.v2"

should work instead, see http://labix.org/gopkg.in#SupportedURLs

[pedromorgan]

@ivy have changed it back for now

I want to get some of the pull requests merged etc first, and then we should be able to break. Hope that's ok

[pedromorgan]

I am suprised @ivy #104

• I first even research other forks first.... cos an olde.darker.shade of grey hacker
• I created the go-mail org from our frustration/realisation, to try and move things forward, as maintainer missing The maintainer is missing.  #104
• I forked it, into new "project/org", and then setup travis etc all..

And then I added @ivy as an "owner" moving forward..

• Adding you @ivy as owner was a bad idea in hindsight, maybe
• cos after a chat on gitter also.. but we agree idea is to maintain+future

once i was away..

• you removed me from gh-organisation, of go-mail and moving forward
• So "go-mail" is now completely yours, thanks for the hijack Thankz..
• I am reminded in future to avoid @ivy

So now you have gone off onto your own planet... which is fine..

• such as renaming namespace, big snag that one
• and renaming a project+function is not good et all..

But good luck, keep up with the rest of us and this project is now exactly what the original problem was.

Irony

• "owner" missing/uncontactable et all = @alexcesaro
• two owners and moving forward, need more
• @ivy removed owners, thanks.. Never been evicted before ;-)))

Good luck on your new independent maintainable fork,

• have fun and goodbye u hijacker and backstabber

[pedromorgan]

go-mail#16

[ivy]

Cross posting from go-mail#16:

@pedromorgan Thank you for coming forward to talk about this. I appreciate that you care about this project. However, as it stands, gomail has been essentially dormant for the last two years. So far, I’ve made good progress in tackling some of the small the issues, but there's still a lot of work to be done. Removing you from the team was a difficult decision, however it wasn’t without reason. In just a couple hours you managed to break backwards compatibility, ruin perfectly good documentation, and trashed continuous integration so that every build was testing against Go 1.7 only.

Yes, I renamed the package. No, I don't believe it breaks compatibility. I've asked you a few times now to explain your reasoning and I'd still like to hear your justification now.

I also want to be clear that I'm not taking your project away from you. It isn't yours. It's the community's and if you still want to be involved I'll be more than happy to continue working with you.

I respect your feelings, and I realize now that the situation could've been handled more considerately. I would also like you to know that this wasn't personal, and it wasn't done with malicious intent. This project has a lot of potential and I want it to have its best chance to survive.

Sincerely,
Ivy

[pedromorgan]

go-mail#16

[pedromorgan]

- However, as it stands, gomail has been essentially dormant for the last two years. 
- So far, I’ve made good progress in tackling some of the small the issues
- but there's still a lot of work to be done. 
- Removing you from the team was a difficult decision
- because @pedromorgan broke things...WTF!!!

Whaw.. Is @ivy a droid ??

[pedromorgan]

go-mail#16

[pedromorgan]

go-mail#16

[ghost]

So who has taken over and what's the new url ?

[ivy]

@gedw99 Sorry for the confusion. I'm still continuing maintenance on gomail at go-mail/mail.

[arundudeemmt]

@ivy @pedromorgan i am using QOR (https://github.com/qor/qor) which uses https://github.com/go-gomail/gomail/ internally , so applied a fix for same under , do i submit same fix again or it can be picked/cherry-picked from there #123 ?

[fredmenez]

Maintainer has left this world, details in #182.

[Neustradamus]

Dear all, it is possible to change your code?
Change from here:

• https://github.com/go-gomail/gomail
• Where to Report Vulnerabilities? #188
• https://github.com/go-mail/mail
• https://github.com/Shopify/gomail
• Where can I report vulnerabilities? Shopify/gomail#59
• https://github.com/ory/mail

It has been unmaintained and maybe one or more vulnerabilities :/

There are:

• https://github.com/xhit/go-simple-mail from @xhit
• https://github.com/wneessen/go-mail from @wneessen

Linked to:

• Maintainer has left this world #182
• This seems to be unmaintained, here is an alternative #163
• Project unmaintained #142
• == Active Forks == #108
• The maintainer is missing.  #104
• ### Forked to github.com/go-mail/gomail ### #105
• New Release Please #94
• why the master code not updated? go-mail/mail#78
• Fork? go-mail/mail#73
• Project maintenance state go-mail/mail#61