Top Menu

Jump to content
Home
    • Projects
    • Work packages
    • News
    • Getting started
    • Introduction video
      Welcome to OpenProject Community
      Get a quick overview of project management and team collaboration with OpenProject. You can restart this video from the help menu.

    • Help and support
    • User guides
    • Videos
    • Shortcuts
    • Community forum
    • Professional support

    • Additional resources
    • Data privacy and security policy
    • Digital accessibility (DE)
    • OpenProject website
    • Security alerts / Newsletter
    • OpenProject blog
    • Release notes
    • Report a bug
    • Development roadmap
    • Add and edit translations
    • API documentation
  • Sign in
      Forgot your password?
      Create a new account

      or sign in with your existing account

      Google

Side Menu

  • Overview
  • Activity
  • Roadmap
  • Work packages
  • Calendars
  • Team planners
  • Boards
  • Forums
  • Wiki
    • Table of contents
      • Expanded. Click to collapseCollapsed. Click to showDeveloper
        • Hierarchy leafAccessibility Checklist
        • Hierarchy leafCode Review Guidelines
        • Expanded. Click to collapseCollapsed. Click to showContribution
          • Hierarchy leafGit Workflow
          • Hierarchy leafTranslations
        • Expanded. Click to collapseCollapsed. Click to showDeveloping Plugins
          • Hierarchy leafDeveloping an OmniAuth Authentication Plugin
        • Hierarchy leafRelease Process
        • Hierarchy leafReport a bug
        • Hierarchy leafSecurity
        • Hierarchy leafSetting up an OpenLDAP server for testing
        • Hierarchy leafTheme Features
      • Hierarchy leafDownload
      • Expanded. Click to collapseCollapsed. Click to showFeature tour
        • Hierarchy leafRelease Notes OpenProject 30
        • Expanded. Click to collapseCollapsed. Click to showRelease Notes OpenProject 30 - Overview
          • Hierarchy leafGlossary
          • Hierarchy leafRelease Notes - Accessibility
          • Hierarchy leafRelease Notes - Accessibility changes
          • Hierarchy leafRelease Notes - Add work package queries as menu items to sidebar
          • Hierarchy leafRelease Notes - Copy projects based on Templates
          • Hierarchy leafRelease Notes - Design changes
          • Hierarchy leafRelease Notes - Fixed Bugs
          • Hierarchy leafRelease Notes - Keyboard Shortcuts
          • Hierarchy leafRelease Notes - Project settings
          • Hierarchy leafRelease Notes - Ruby&Rails Update
          • Hierarchy leafRelease Notes - Security
          • Hierarchy leafRelease Notes - Timelines
          • Hierarchy leafRelease Notes - Work packages
      • Hierarchy leafHowto create animated gifs
      • Hierarchy leafMigration Squashing
      • Hierarchy leafMod security
      • Hierarchy leafNew work package page
      • Hierarchy leafOP3 to OP4 Debian upgrade
      • Hierarchy leafOP4 Ubuntu1404 Stable with MySQL in production
      • Hierarchy leafOpenProject 40 Development Setup
      • Expanded. Click to collapseCollapsed. Click to showOpenProject Foundation
        • Hierarchy leafBoards
        • Hierarchy leafMembers
        • Hierarchy leafOPF-Meetings
        • Hierarchy leafStatutes
      • Expanded. Click to collapseCollapsed. Click to showRelease Notes
        • Hierarchy leafOpenProject released on Bitnami
      • Expanded. Click to collapseCollapsed. Click to showRelease Notes OpenProject 40 - Overview
        • Hierarchy leafRelease Notes OpenProject 40 - Accessibility improvements
        • Hierarchy leafRelease Notes OpenProject 40 - Column header functions in work package table
        • Hierarchy leafRelease Notes OpenProject 40 - Improved Design
        • Hierarchy leafRelease Notes OpenProject 40 - Integrated query title on work package page
        • Hierarchy leafRelease Notes OpenProject 40 - Integrated toolbar on work package page
        • Hierarchy leafRelease Notes OpenProject 40 - OmniAuth integration for OpenProject
        • Hierarchy leafRelease Notes OpenProject 40 - Work package details pane
      • Expanded. Click to collapseCollapsed. Click to showSecurity and privacy
        • Hierarchy leafFAQ
      • Expanded. Click to collapseCollapsed. Click to showSupport
        • Expanded. Click to collapseCollapsed. Click to showDownload and Installation
          • Hierarchy leafInstallation MacOS
          • Expanded. Click to collapseCollapsed. Click to showInstallation OpenProject 3 0
            • Hierarchy leafDebian Stable with MySQL in production
            • Hierarchy leafInstallation Ubuntu
            • Hierarchy leafInstallation Windows
            • Hierarchy leafInstallation on Centos 65 x64 with Apache and PostgreSQL 93
          • Expanded. Click to collapseCollapsed. Click to showInstallation OpenProject 40
            • Hierarchy leafOP4 Debian Stable with MySQL in production
          • Expanded. Click to collapseCollapsed. Click to showMigration paths
            • Hierarchy leafFrom Chilliproject to OpenProject
            • Hierarchy leafMigration 15 to 30
            • Hierarchy leafMigration 24 to 30
            • Hierarchy leafMigration Redmine 2x › OpenProject 30
            • Hierarchy leafOpenProject 3 Migration
          • Hierarchy leafOpenProject 40
        • Expanded. Click to collapseCollapsed. Click to showNews
          • Hierarchy leafNew OpenProject Translations Plugin
          • Hierarchy leafNew Plugin on OpenProjectorg Local Avatars
          • Hierarchy leafNew design for OpenProject
          • Hierarchy leafNews Accessibility workshop for OpenProject
          • Hierarchy leafNews Glossary for OpenProject
          • Hierarchy leafNews Heartbleed fixed
          • Hierarchy leafNews Icon Fonts
          • Hierarchy leafNews OpenProject 30 Release
          • Hierarchy leafNews Release GitHub Integration Plugin
          • Hierarchy leafNews Success Story Deutsche Telekom
          • Hierarchy leafNews Timelines
          • Hierarchy leafOpenProject 3013 released
          • Hierarchy leafOpenProject 3017 released
          • Hierarchy leafOpenProject 40 released
          • Hierarchy leafOpenProject 40 will be coming soon
          • Hierarchy leafOpenProject 405 released
          • Hierarchy leafOpenProject and pkgrio
          • Hierarchy leafOpenProject news moved to a new blog
          • Hierarchy leafOpenProjectBitnami
          • Hierarchy leafPackager version with plugins released ("Community edition")
          • Hierarchy leafRegistration OpenProject-Foundation
          • Hierarchy leafRelease OpenProject AuthPlugins
          • Hierarchy leafUpdates on OpenProject
          • Hierarchy leafWe need your feedback for the the new fullscreen view for work packages
        • Hierarchy leafOpenProject Plug-Ins
      • Hierarchy leafWiki
You are here:
  • Forums
  • General discussion

Content

email setup without authentication

Added by Tamas Csabina almost 9 years ago

Hi,

Is it possible to configure the email-engine not authenticate at all?
I have an internal smtp server that is configured to alloy relaying. I want to use this smtp server to send emails.

My configuration.yml looks like:
@
default:
email_delivery_method: :smtp
smtp_address: smtp.company
smtp_port: 25
@

I haven’t added the smtp_authentication: entry, as I don’t need one.

But the emails are not being delivered.

My questions:

- is it possible at all not to use an smtp-auth?
- how can I troubleshoot the email delivery (logfiles, trace, etc)? Is the config ok? Is the smtp server being reached? Is the smtp server refuses to deliver? Is the config+smtp_server is fine, and there are issues somewhere else?

Thanks in advance for any tips.

Tamas


Replies (5)

RE: email setup without authentication - Added by Christoph Opwis almost 9 years ago

Hi Tamas,

first, you should post things like this in the forum for “installation” topics.

- is it possible at all not to use an smtp-auth?

Yes. I am not the expert on this, but in our environment we also use an internal SMTP server without authentication and without encryption.

Our settings in configuration.yml are like this:

default:
  email_delivery_method: "smtp"
  smtp_adress: "smtp.mydomain.de"
  smtp_port: 25
  smtp_domain: "hostname-of-openproject-server.mydomain.de"

Everything else (smtp_authentication=, smtp_user_name=,..etc.) is not necessary, we disabled these by adding # at the beginning of the line.

That looks more or less similar to your configuration, but, it seems to me, that you did not use the right format. In .yml it is very important to keep the indenting! Only “default:” must be without indenting, everything beneath belonging to “default:” must be indented.

- how can I troubleshoot the email delivery (logfiles, trace, etc)?

For instance, if you just edit a user and change its password, by default an email is generated.
You did not provide us with information about your environment. In Debian or Ubuntu environments you can see all what happened in the openproject’s log directory - there are different logfiles for each environment.

Hope that helps, regards
Christoph

RE: email setup without authentication - Added by Tamas Csabina almost 9 years ago

Hi Christoph,

Thank you for your reply. I made some progress.

The .yml file’s indent was okay, but when I quoted it, that extra 2 spaces got lost.
I’ve modified the syntax a bit, based on your reply:

default:
  email_delivery_method: "smtp"
  smtp_address: "smtp.server"
  smtp_port: 25
  smtp_domain: "mycompany.com"

And with this, some emails are being delivered, some emails are not:
Whenever the admin is changing a password for example, an email is being delivered to the user.
Whenever a user makes a modification on a work package, there is no email is being sent, and this is what I see in the logs:
@
Sent mail to tamas@mycompany.com (25.8ms)
2014-04-04T08:45:24+0200: [Worker(delayed_job host:openproject pid:13049)] Class#work_package_updated failed with Net::SMTPSyntaxError: 501 Syntax: HELO hostname
- 2 failed attempts
@

This error (501 Syntax: HELO hostname) is coming from the smtp server. Whenever I make a telnet session on port 25 to the smtp server, and type “HELO”, this is the reply I got. If I use “helo myhost”, I got a proper reply, so I guess I’ve missed some host related configuration during OpenProject setup.
Will dive into this…

RE: email setup without authentication - Added by Tamas Csabina almost 9 years ago

Finally made this work.

As the password change task was generating an email, and the work package update was not generating it, I took a closer look on the differences.
The work package update email is being sent in a delayed_job. But the delayed_job queue was not properly update after I have modified the .yml file (I guess). Even apache restart hadn’t involved the queue cleanup, so I had to do it manually:
Stopped the queue with:
@
RAILS_ENV=production bundle exec script/delayed_job stop
@

Followed by:
@
RAILS_ENV=production bundle exec script/delayed_job start
@
to start the queue again.
After this email delivery for work package updates are working fine.

I hope this helps out someone…

RE: email setup without authentication - Added by Andrew Moore about 8 years ago

Tamas Csabina wrote:

Hi,

Is it possible to configure the email-engine not authenticate at all?
I have an internal smtp server that is configured to alloy relaying. I want to use this smtp server to send emails.

My configuration.yml looks like:
@
default:
email_delivery_method: :smtp
smtp_address: smtp.company
smtp_port: 25
@

I haven’t added the smtp_authentication: entry, as I don’t need one.

But the emails are not being delivered.

My questions:

- is it possible at all not to use an smtp-auth?
- how can I troubleshoot the email delivery (logfiles, trace, etc)? Is the config ok? Is the smtp server being reached? Is the smtp server refuses to deliver? Is the config+smtp_server is fine, and there are issues somewhere else?

Thanks in advance for any tips.

Tamas

I’m having the same issue. I went through the reconfiguration wizard to setup SMTP but there was not option for no authentication.

Test emails return “An error occurred while sending mail (SMTP-AUTH requested but missing user name)”

Here is my configuration.yml

default:
  email_delivery_method: "smtp"
  smtp_address: "mailout.myco.com"
  smtp_port: 25

production:
  email_delivery_method: "smtp"
  smtp_address: "mailout.myco.com"
  smtp_port: 25

RE: email setup without authentication - Added by Tamas Csabina about 8 years ago

Hi Andrew,

Sorry Andrew, but I cannot really help, as at the end it was all working fine for us (no auth required).

What might be the problem for you is that int the configuration.yml file there are multiple entries about the smtp auth. Maybe you have edited the beginning of the file but a the end of the file there is still an old value overwriting your changes? I am just guessing.
Maybe post the complete .yml file, but as I said, at the end we have no issues to run the smtp stuff without authentication.

Regards,
Tamas

  • (1 - 5/5)
Loading...