Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in
M
mailinabox
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Administrator
  • mailinabox
  • Repository

Switch branch/tag
  • mailinabox
  • conf
  • zpush
  • backend_caldav.php
Find file
BlameHistoryPermalink
  • Joshua Tauberer's avatar
    use "127.0.0.1" throughout rather than mixing use of an IP address and "localhost" · 6d259a6e
    Joshua Tauberer authored May 06, 2016
    On some machines localhost is defined as something other than 127.0.0.1, and if we mix "127.0.0.1" and "localhost" then some connections won't be to to the address a service is actually running on.
    
    This was the case with DKIM: It was running on "localhost" but Postfix was connecting to it at 127.0.0.1. (https://discourse.mailinabox.email/t/opendkim-is-not-running-port-8891/1188/12.)
    
    I suppose "localhost" could be an alias to an IPv6 address? We don't really want local services binding on IPv6, so use "127.0.0.1" to be explicit and don't use "localhost" to be sure we get an IPv4 address.
    
    Fixes #797
    6d259a6e
backend_caldav.php 487 Bytes
EditWeb IDE

Replace backend_caldav.php

Attach a file by drag & drop or click to upload


Cancel
A new branch will be created in your fork and a new merge request will be started.

Technounit-GROUP 2023