Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #4866

Closed
Open
Created Aug 23, 2013 by Administrator@rootOwner

Mails do not get sent to users when exim is used as mail daemon (sendmail with -t command).

Created by: pspoerri

  1. Summary: Mails do not get sent to users when exim is used as mail daemon.

  2. Steps to reproduce: Setup gitlab (5.2 and 6.0) on linux with exim as sendmail client.

  3. Expected behavior: Mail should arrive at users location.

  4. Observed behavior: Gitlab will notify that a mail to $user has been sent but exim won't report that it sent a mail to $user. Exim will also report

    From: Mail Delivery System <[email protected]>
    Subject: Mail failure - no recipient addresses
    Date: 29. Juli 2013 13:51:23 MESZ
    To: <[email protected]>
    A message that you sent using the -t command line option contained no
    addresses that were not also on the command line, and were therefore
    suppressed. This left no recipient addresses, and so no delivery could
    be attempted.
  5. Output of checks

    • Results of GitLab [Application Check]

      # bundle exec rake gitlab:check RAILS_ENV=production
      Checking Environment ...
      Git configured for git user? ... yes
      Has python2? ... yes
      python2 is supported version? ... yes
      Checking Environment ... Finished
      Checking GitLab Shell ...
      GitLab Shell version >= 1.7.0 ? ... OK (1.7.0)
      Repo base directory exists? ... yes
      Repo base directory is a symlink? ... no
      Repo base owned by git:git? ... yes
      Repo base access is drwxrws---? ... yes
      post-receive hook up-to-date? ... yes
      post-receive hooks in repos are links: ...
      Checking GitLab Shell ... Finished
      Checking Sidekiq ...
      Running? ... yes
      Checking Sidekiq ... Finished
      Checking GitLab ...
      Database config exists? ... yes
      Database is SQLite ... no
      All migrations up? ... yes
      GitLab config exists? ... yes
      GitLab config outdated? ... no
      Log directory writable? ... yes
      Tmp directory writable? ... yes
      Init script exists? ... no
      Try fixing it:
      Install the init script
      For more information see:
      doc/install/installation.md in section "Install Init Script"
      Please fix the error above and rerun the checks.
      Init script up-to-date? ... can't check because of previous errors
      Projects have satellites? ...
      [...]
      Redis version >= 2.0.0? ... yes
      Your git bin path is "/usr/bin/git"
      Git version >= 1.7.10 ? ... no
      Try fixing it:
      Update your git to a version >= 1.7.10 from 1.7.9
      Please fix the error above and rerun the checks.

      I know that git has not been updated yet. But it doesn't have anything to do with gitlab email. Hence I'm leaving it there.

      • Sha1: 4c8f3699
    1. Possible fixes:
        diff --git a/config/application.rb b/config/application.rb
        index f7349fa..75eee2c 100644
        --- a/config/application.rb
        +++ b/config/application.rb
        @@ -11,6 +11,8 @@ end

         module Gitlab
           class Application < Rails::Application
        +    config.action_mailer.sendmail_settings = { :arguments => "-i" }
        +
             # Settings in config/environments/* take precedence over those specified he
             # Application configuration should go into files in config/initializers
             # -- all .rb files in that directory are automatically loaded.

This issue was also discussed in #3943 (closed). I thought to reopen it but since it was closed by the requestor. I thought it might be better to just create a new issue.

The issue is also discussed here: https://github.com/mikel/mail/issues/70

Assignee
Assign to
Time tracking