-
Notifications
You must be signed in to change notification settings - Fork 371
Auth support #92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Sorry for the late reply. Sure, pull request welcome. |
Where is the code? |
Hello Good day Does go-guerrilla support plain authentication. I'm new to developing smtp sever, so my apologies. |
@flashmob I'm looking to develop this. I'll send across a pull request from my fork. |
Hi,
Thanks for your interest!
At present, major development work is being done on
#135
It has changed a lot of code, so it may be better to work off that branch.
Although there are changes that would need to be documented in there, so
you'd probably need to wait until it's done before you can work on it.
Question: Does Auth support require database access? Could you please link
to the code that does this in your fork?
…On Sat, 11 Jul 2020 at 19:18, Agnibha ***@***.***> wrote:
@flashmob <https://github.com/flashmob> I'm looking to develop this. I'll
send across a pull request from my fork.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#92 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAE6MP4ZSDP4KEK7THJQUN3R3A4A3ANCNFSM4EC27LSA>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I implemented auth support (CRAM-MD5 and LOGIN) in my fork, so I'd like to know whether you'd be interested in such functionality and I can create a pull request for that.
The text was updated successfully, but these errors were encountered: