[GitHub] incubator-nifi pull request: NIFI-414 Add SMTP Username and Passwo...

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[GitHub] incubator-nifi pull request: NIFI-414 Add SMTP Username and Passwo...

JPercivall
GitHub user jamespowenjr opened a pull request:

    https://github.com/apache/incubator-nifi/pull/34

    NIFI-414 Add SMTP Username and Password Support to PutEmail Processor

    Fairly simple change to allow username and password as part of the SMTP settings. Both are not required. In addition, password is sensitive.
   
    I've tested this against an SMTP server that requires authentication (AWS SES, Simple Email Service) and it works as expected.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jamespowenjr/incubator-nifi NIFI-414

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-nifi/pull/34.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #34
   
----
commit 5450a5a2f00626b40b199c2ad551ac0c8cc610e5
Author: James Owen <[hidden email]>
Date:   2015-03-11T22:29:08Z

    Added username/password to PutEmail Processor

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|

[GitHub] incubator-nifi pull request: NIFI-414 Add SMTP Username and Passwo...

JPercivall
Github user asfgit closed the pull request at:

    https://github.com/apache/incubator-nifi/pull/34


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [hidden email] or file a JIRA ticket
with INFRA.
---