LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 03-10-2017, 08:01 AM   #1
redssr
Member
 
Registered: Oct 2013
Location: Dist Nasik MH State Country India
Distribution: Linux
Posts: 108

Rep: Reputation: Disabled
Dovecot with haproxy


Dear Friends,

Whenever i tries to configure dovecot with haproxy parameters i gets below error while restarting dovecot

Code:
root@ip-172-31-21-162 dovecot]# systemctl status dovecot -l
● dovecot.service - Dovecot IMAP/POP3 email server
   Loaded: loaded (/usr/lib/systemd/system/dovecot.service; disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Fri 2017-03-10 13:55:28 UTC; 6s ago
  Process: 5890 ExecStart=/usr/sbin/dovecot -F (code=exited, status=89)
  Process: 5887 ExecStartPre=/usr/libexec/dovecot/prestartscript (code=exited, status=0/SUCCESS)
 Main PID: 5890 (code=exited, status=89)

Mar 10 13:55:28 ip-172-31-21-162.us-west-2.compute.internal systemd[1]: Starting Dovecot IMAP/POP3 email server...
Mar 10 13:55:28 ip-172-31-21-162.us-west-2.compute.internal systemd[1]: Started Dovecot IMAP/POP3 email server.
Mar 10 13:55:28 ip-172-31-21-162.us-west-2.compute.internal dovecot[5890]: doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 89: Unknown setting: haproxy_trusted_networks
Mar 10 13:55:28 ip-172-31-21-162.us-west-2.compute.internal systemd[1]: dovecot.service: main process exited, code=exited, status=89/n/a
Mar 10 13:55:28 ip-172-31-21-162.us-west-2.compute.internal dovecot[5890]: doveconf: Error: managesieve-login: dump-capability process returned 89
Mar 10 13:55:28 ip-172-31-21-162.us-west-2.compute.internal dovecot[5890]: doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 89: Unknown setting: haproxy_trusted_networks
Mar 10 13:55:28 ip-172-31-21-162.us-west-2.compute.internal systemd[1]: Unit dovecot.service entered failed state.
Mar 10 13:55:28 ip-172-31-21-162.us-west-2.compute.internal systemd[1]: dovecot.service failed
i followed these urls https://dovecot.org/list/dovecot/201...er/102236.html
http://wiki2.dovecot.org/HAProxy
http://dovecot.2317879.n4.nabble.com...50.html#a51179

but no succeess I am confused now that Does dovecot support HAproxy or not.

Regards,
Redssr
 
Old 03-10-2017, 08:28 AM   #2
TB0ne
LQ Guru
 
Registered: Jul 2003
Location: Birmingham, Alabama
Distribution: SuSE, RedHat, Slack,CentOS
Posts: 23,806

Rep: Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973
Quote:
Originally Posted by redssr View Post
Dear Friends,
Whenever i tries to configure dovecot with haproxy parameters i gets below error while restarting dovecot
Code:
root@ip-172-31-21-162 dovecot]# systemctl status dovecot -l
● dovecot.service - Dovecot IMAP/POP3 email server
   Loaded: loaded (/usr/lib/systemd/system/dovecot.service; disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Fri 2017-03-10 13:55:28 UTC; 6s ago
  Process: 5890 ExecStart=/usr/sbin/dovecot -F (code=exited, status=89)
  Process: 5887 ExecStartPre=/usr/libexec/dovecot/prestartscript (code=exited, status=0/SUCCESS)
 Main PID: 5890 (code=exited, status=89)

Mar 10 13:55:28 ip-172-31-21-162.us-west-2.compute.internal systemd[1]: Starting Dovecot IMAP/POP3 email server...
Mar 10 13:55:28 ip-172-31-21-162.us-west-2.compute.internal systemd[1]: Started Dovecot IMAP/POP3 email server.
Mar 10 13:55:28 ip-172-31-21-162.us-west-2.compute.internal dovecot[5890]: doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 89: Unknown setting: haproxy_trusted_networks
Mar 10 13:55:28 ip-172-31-21-162.us-west-2.compute.internal systemd[1]: dovecot.service: main process exited, code=exited, status=89/n/a
Mar 10 13:55:28 ip-172-31-21-162.us-west-2.compute.internal dovecot[5890]: doveconf: Error: managesieve-login: dump-capability process returned 89
Mar 10 13:55:28 ip-172-31-21-162.us-west-2.compute.internal dovecot[5890]: doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 89: Unknown setting: haproxy_trusted_networks
Mar 10 13:55:28 ip-172-31-21-162.us-west-2.compute.internal systemd[1]: Unit dovecot.service entered failed state.
Mar 10 13:55:28 ip-172-31-21-162.us-west-2.compute.internal systemd[1]: dovecot.service failed
i followed these urls https://dovecot.org/list/dovecot/201...er/102236.html
http://wiki2.dovecot.org/HAProxy
http://dovecot.2317879.n4.nabble.com...50.html#a51179

but no succeess I am confused now that Does dovecot support HAproxy or not.
Yes it does, but it's telling you very plainly that you have an error on line 89 in your configuration file. Either you specified the wrong syntax, or have a mistake(s) elsewhere in your config. Since you don't show us your config, we can't help...and you provide no other details either, such as version/distro of Linux, versions of software you're using, environment, etc. Based on what you posted, you have an error in your config file. Short answer: fix it.

Longer answer: post relevant details, and read the "Question Guidelines" link in my posting signature. Also, is this the same "bulk email server" you mentioned before here: http://www.linuxquestions.org/questi...ps-4175592099/

Because I don't think many people are going to help you be a spammer.
 
Old 03-10-2017, 08:49 AM   #3
redssr
Member
 
Registered: Oct 2013
Location: Dist Nasik MH State Country India
Distribution: Linux
Posts: 108

Original Poster
Rep: Reputation: Disabled
No dear i am not setting it for bulk email setup. Its already completed. This is totally new project. I was successfully able to configure postfix but dovecot is giving above error
Code:
Unknown setting: haproxy_trusted_networks
I just copy pasted the line from http://wiki2.dovecot.org/HAProxy link and restarted the dovecot

here is the added line in dovecot.conf file

Code:
[root@ip-172-31-21-162 dovecot]# grep -nri haproxy dovecot.conf
89:haproxy_trusted_networks = 127.0.0.1
Linux distro
Code:
[root@ip-172-31-21-162 ~]# cat /etc/*release
CentOS Linux release 7.3.1611 (Core)
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"

CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"

CentOS Linux release 7.3.1611 (Core)
CentOS Linux release 7.3.1611 (Core
dovecot version

Code:
[root@ip-172-31-21-162 ~]# rpm -qa|grep dovecot
dovecot-mysql-2.2.10-7.el7.x86_64
dovecot-pigeonhole-2.2.10-7.el7.x86_64
dovecot-devel-2.2.10-7.el7.x86_64
dovecot-2.2.10-7.el7.x86_64
Regards,
Redssr

Last edited by redssr; 03-10-2017 at 09:04 AM.
 
Old 03-10-2017, 09:35 AM   #4
TB0ne
LQ Guru
 
Registered: Jul 2003
Location: Birmingham, Alabama
Distribution: SuSE, RedHat, Slack,CentOS
Posts: 23,806

Rep: Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973
Quote:
Originally Posted by redssr View Post
No dear i am not setting it for bulk email setup. Its already completed. This is totally new project. I was successfully able to configure postfix but dovecot is giving above error
Code:
Unknown setting: haproxy_trusted_networks
Yeah...
Quote:
I just copy pasted the line from http://wiki2.dovecot.org/HAProxy link and restarted the dovecot here is the added line in dovecot.conf file
Code:
[root@ip-172-31-21-162 dovecot]# grep -nri haproxy dovecot.conf
89:haproxy_trusted_networks = 127.0.0.1
Did you look carefully at that line??? Did you see how you have not followed the same syntax as the ones in the examples?
 
Old 03-10-2017, 10:37 AM   #5
redssr
Member
 
Registered: Oct 2013
Location: Dist Nasik MH State Country India
Distribution: Linux
Posts: 108

Original Poster
Rep: Reputation: Disabled
Hello,

let me post the whole conf file here. I had added the line as same as in http://wiki2.dovecot.org/HAProxy
here is my whole dovecot.conf file details

Code:
[centos@ip-172-31-21-162 ~]$ cat /etc/dovecot/dovecot.conf
## Dovecot configuration file

# If you're in a hurry, see http://wiki2.dovecot.org/QuickConfiguration

# "doveconf -n" command gives a clean output of the changed settings. Use it
# instead of copy&pasting files when posting to the Dovecot mailing list.

# '#' character and everything after it is treated as comments. Extra spaces
# and tabs are ignored. If you want to use either of these explicitly, put the
# value inside quotes, eg.: key = "# char and trailing whitespace  "

# Most (but not all) settings can be overridden by different protocols and/or
# source/destination IPs by placing the settings inside sections, for example:
# protocol imap { }, local 127.0.0.1 { }, remote 10.0.0.0/8 { }

# Default values are shown for each setting, it's not required to uncomment
# those. These are exceptions to this though: No sections (e.g. namespace {})
# or plugin settings are added by default, they're listed only as examples.
# Paths are also just examples with the real defaults being based on configure
# options. The paths listed here are for configure --prefix=/usr
# --sysconfdir=/etc --localstatedir=/var

# Protocols we want to be serving.
#protocols = imap pop3 lmtp

# A comma separated list of IPs or hosts where to listen in for connections.
# "*" listens in all IPv4 interfaces, "::" listens in all IPv6 interfaces.
# If you want to specify non-default ports or anything more complex,
# edit conf.d/master.conf.
#listen = *, ::

# Base directory where to store runtime data.
#base_dir = /var/run/dovecot/

# Name of this instance. In multi-instance setup doveadm and other commands
# can use -i <instance_name> to select which instance is used (an alternative
# to -c <config_path>). The instance name is also added to Dovecot processes
# in ps output.
#instance_name = dovecot

# Greeting message for clients.
#login_greeting = Dovecot ready.

# Space separated list of trusted network ranges. Connections from these
# IPs are allowed to override their IP addresses and ports (for logging and
# for authentication checks). disable_plaintext_auth is also ignored for
# these networks. Typically you'd specify your IMAP proxy servers here.
#login_trusted_networks =

# Space separated list of login access check sockets (e.g. tcpwrap)
#login_access_sockets =

# With proxy_maybe=yes if proxy destination matches any of these IPs, don't do
# proxying. This isn't necessary normally, but may be useful if the destination
# IP is e.g. a load balancer's IP.
#auth_proxy_self =

# Show more verbose process titles (in ps). Currently shows user name and
# IP address. Useful for seeing who are actually using the IMAP processes
# (eg. shared mailboxes or if same uid is used for multiple accounts).
#verbose_proctitle = no

# Should all processes be killed when Dovecot master process shuts down.
# Setting this to "no" means that Dovecot can be upgraded without
# forcing existing client connections to close (although that could also be
# a problem if the upgrade is e.g. because of a security fix).
#shutdown_clients = yes

# If non-zero, run mail commands via this many connections to doveadm server,
# instead of running them directly in the same process.
#doveadm_worker_count = 0
# UNIX socket or host:port used for connecting to doveadm server
#doveadm_socket_path = doveadm-server

# Space separated list of environment variables that are preserved on Dovecot
# startup and passed down to all of its child processes. You can also give
# key=value pairs to always set specific settings.
#import_environment = TZ

##
## Dictionary server settings
##

# Dictionary can be used to store key=value lists. This is used by several
# plugins. The dictionary can be accessed either directly or though a
# dictionary server. The following dict block maps dictionary names to URIs
# when the server is used. These can then be referenced using URIs in format
# "proxy::<name>".
haproxy_trusted_networks = 127.0.0.1

dict {
  #quota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext
  #expire = sqlite:/etc/dovecot/dovecot-dict-sql.conf.ext
}

# Most of the actual configuration gets included below. The filenames are
# first sorted by their ASCII value and parsed in that order. The 00-prefixes
# in filenames are intended to make it easier to understand the ordering.
!include conf.d/*.conf

# A config file can also tried to be included without giving an error if
# it's not found:
!include_try local.conf
I think this will be right output of my dovecot.conf for you to understand my problem

Regards,
Redssr
 
Old 03-10-2017, 11:29 AM   #6
TB0ne
LQ Guru
 
Registered: Jul 2003
Location: Birmingham, Alabama
Distribution: SuSE, RedHat, Slack,CentOS
Posts: 23,806

Rep: Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973
Quote:
Originally Posted by redssr View Post
Hello,
let me post the whole conf file here. I had added the line as same as in http://wiki2.dovecot.org/HAProxy here is my whole dovecot.conf file details
Code:
[centos@ip-172-31-21-162 ~]$ cat /etc/dovecot/dovecot.conf
## Dovecot configuration file

# If you're in a hurry, see http://wiki2.dovecot.org/QuickConfiguration

# "doveconf -n" command gives a clean output of the changed settings. Use it
# instead of copy&pasting files when posting to the Dovecot mailing list.

# '#' character and everything after it is treated as comments. Extra spaces
# and tabs are ignored. If you want to use either of these explicitly, put the
# value inside quotes, eg.: key = "# char and trailing whitespace  "

# Most (but not all) settings can be overridden by different protocols and/or
# source/destination IPs by placing the settings inside sections, for example:
# protocol imap { }, local 127.0.0.1 { }, remote 10.0.0.0/8 { }

# Default values are shown for each setting, it's not required to uncomment
# those. These are exceptions to this though: No sections (e.g. namespace {})
# or plugin settings are added by default, they're listed only as examples.
# Paths are also just examples with the real defaults being based on configure
# options. The paths listed here are for configure --prefix=/usr
# --sysconfdir=/etc --localstatedir=/var

# Protocols we want to be serving.
#protocols = imap pop3 lmtp

# A comma separated list of IPs or hosts where to listen in for connections.
# "*" listens in all IPv4 interfaces, "::" listens in all IPv6 interfaces.
# If you want to specify non-default ports or anything more complex,
# edit conf.d/master.conf.
#listen = *, ::

# Base directory where to store runtime data.
#base_dir = /var/run/dovecot/

# Name of this instance. In multi-instance setup doveadm and other commands
# can use -i <instance_name> to select which instance is used (an alternative
# to -c <config_path>). The instance name is also added to Dovecot processes
# in ps output.
#instance_name = dovecot

# Greeting message for clients.
#login_greeting = Dovecot ready.

# Space separated list of trusted network ranges. Connections from these
# IPs are allowed to override their IP addresses and ports (for logging and
# for authentication checks). disable_plaintext_auth is also ignored for
# these networks. Typically you'd specify your IMAP proxy servers here.
#login_trusted_networks =

# Space separated list of login access check sockets (e.g. tcpwrap)
#login_access_sockets =

# With proxy_maybe=yes if proxy destination matches any of these IPs, don't do
# proxying. This isn't necessary normally, but may be useful if the destination
# IP is e.g. a load balancer's IP.
#auth_proxy_self =

# Show more verbose process titles (in ps). Currently shows user name and
# IP address. Useful for seeing who are actually using the IMAP processes
# (eg. shared mailboxes or if same uid is used for multiple accounts).
#verbose_proctitle = no

# Should all processes be killed when Dovecot master process shuts down.
# Setting this to "no" means that Dovecot can be upgraded without
# forcing existing client connections to close (although that could also be
# a problem if the upgrade is e.g. because of a security fix).
#shutdown_clients = yes

# If non-zero, run mail commands via this many connections to doveadm server,
# instead of running them directly in the same process.
#doveadm_worker_count = 0
# UNIX socket or host:port used for connecting to doveadm server
#doveadm_socket_path = doveadm-server

# Space separated list of environment variables that are preserved on Dovecot
# startup and passed down to all of its child processes. You can also give
# key=value pairs to always set specific settings.
#import_environment = TZ

##
## Dictionary server settings
##

# Dictionary can be used to store key=value lists. This is used by several
# plugins. The dictionary can be accessed either directly or though a
# dictionary server. The following dict block maps dictionary names to URIs
# when the server is used. These can then be referenced using URIs in format
# "proxy::<name>".
haproxy_trusted_networks = 127.0.0.1

dict {
  #quota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext
  #expire = sqlite:/etc/dovecot/dovecot-dict-sql.conf.ext
}

# Most of the actual configuration gets included below. The filenames are
# first sorted by their ASCII value and parsed in that order. The 00-prefixes
# in filenames are intended to make it easier to understand the ordering.
!include conf.d/*.conf

# A config file can also tried to be included without giving an error if
# it's not found:
!include_try local.conf
I think this will be right output of my dovecot.conf for you to understand my problem
I understood your problem when you posted it, but you are not understanding the answer.

AGAIN, you are not putting the correct syntax in on that line; if you actually read two of the links you, yourself, posted, you'd see the syntactical difference. You need more than an IP address, and specifying localhost is pointless, since that is ONLY ON ONE MACHINE.
 
Old 03-10-2017, 11:46 AM   #7
redssr
Member
 
Registered: Oct 2013
Location: Dist Nasik MH State Country India
Distribution: Linux
Posts: 108

Original Poster
Rep: Reputation: Disabled
Ok dear

I quit my way, can you please post your syntax here so that i can coy paste it?

Regards,
Redssr
 
Old 03-10-2017, 12:31 PM   #8
TB0ne
LQ Guru
 
Registered: Jul 2003
Location: Birmingham, Alabama
Distribution: SuSE, RedHat, Slack,CentOS
Posts: 23,806

Rep: Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973
Quote:
Originally Posted by redssr View Post
Ok dear
I quit my way, can you please post your syntax here so that i can coy paste it?
No, thanks. The documentation that YOU POSTED has the examples in it...if you don't feel like reading it, I'm not going to read it for you, so you can copy/paste things, rather than read and learn on your own. Here's a hint: its in the third link you posted. And AGAIN, using localhost for HAPROXY has ZERO effect and purpose.

Especially since you're wanting help with your spam server.

Last edited by TB0ne; 03-10-2017 at 12:34 PM.
 
Old 03-11-2017, 12:39 AM   #9
redssr
Member
 
Registered: Oct 2013
Location: Dist Nasik MH State Country India
Distribution: Linux
Posts: 108

Original Poster
Rep: Reputation: Disabled
Hello,

Dear,

As per your suggestion i replaced the localhost with real server ip but still i am getting the same error
here is my new config file
Code:
[root@ip-172-31-21-162 dovecot]# cat dovecot.conf
haproxy_trusted_networks = 52.42.141.89
dict {
}

!include conf.d/*.conf

!include_try local.conf
[root@ip-172-31-21-162 dovecot]#
And the error below

Code:
[root@ip-172-31-21-162 dovecot]# systemctl status dovecot -l
● dovecot.service - Dovecot IMAP/POP3 email server
   Loaded: loaded (/usr/lib/systemd/system/dovecot.service; disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Sat 2017-03-11 06:34:23 UTC; 3min 25s ago
  Process: 25387 ExecStart=/usr/sbin/dovecot -F (code=exited, status=89)
  Process: 25384 ExecStartPre=/usr/libexec/dovecot/prestartscript (code=exited, status=0/SUCCESS)
 Main PID: 25387 (code=exited, status=89)

Mar 11 06:34:23 ip-172-31-21-162.us-west-2.compute.internal systemd[1]: Starting Dovecot IMAP/POP3 email server...
Mar 11 06:34:23 ip-172-31-21-162.us-west-2.compute.internal systemd[1]: Started Dovecot IMAP/POP3 email server.
Mar 11 06:34:23 ip-172-31-21-162.us-west-2.compute.internal dovecot[25387]: doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 1: Unknown setting: haproxy_trusted_networks
Mar 11 06:34:23 ip-172-31-21-162.us-west-2.compute.internal systemd[1]: dovecot.service: main process exited, code=exited, status=89/n/a
Mar 11 06:34:23 ip-172-31-21-162.us-west-2.compute.internal dovecot[25387]: doveconf: Error: managesieve-login: dump-capability process returned 89
Mar 11 06:34:23 ip-172-31-21-162.us-west-2.compute.internal dovecot[25387]: doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 1: Unknown setting: haproxy_trusted_networks
Mar 11 06:34:23 ip-172-31-21-162.us-west-2.compute.internal systemd[1]: Unit dovecot.service entered failed state.
Mar 11 06:34:23 ip-172-31-21-162.us-west-2.compute.internal systemd[1]: dovecot.service failed.
[root@ip-172-31-21-162 dovecot]#
I entered exactly what is given in the doc http://wiki2.dovecot.org/HAProxy.

Regards,
Redssr
 
Old 03-11-2017, 08:52 AM   #10
TB0ne
LQ Guru
 
Registered: Jul 2003
Location: Birmingham, Alabama
Distribution: SuSE, RedHat, Slack,CentOS
Posts: 23,806

Rep: Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973
Quote:
Originally Posted by redssr View Post
As per your suggestion i replaced the localhost with real server ip but still i am getting the same error here is my new config file
Code:
[root@ip-172-31-21-162 dovecot]# cat dovecot.conf
haproxy_trusted_networks = 52.42.141.89
dict {
}

!include conf.d/*.conf

!include_try local.conf
[root@ip-172-31-21-162 dovecot]#
And the error below
Code:
[root@ip-172-31-21-162 dovecot]# systemctl status dovecot -l
● dovecot.service - Dovecot IMAP/POP3 email server
   Loaded: loaded (/usr/lib/systemd/system/dovecot.service; disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Sat 2017-03-11 06:34:23 UTC; 3min 25s ago
  Process: 25387 ExecStart=/usr/sbin/dovecot -F (code=exited, status=89)
  Process: 25384 ExecStartPre=/usr/libexec/dovecot/prestartscript (code=exited, status=0/SUCCESS)
 Main PID: 25387 (code=exited, status=89)

Mar 11 06:34:23 ip-172-31-21-162.us-west-2.compute.internal systemd[1]: Starting Dovecot IMAP/POP3 email server...
Mar 11 06:34:23 ip-172-31-21-162.us-west-2.compute.internal systemd[1]: Started Dovecot IMAP/POP3 email server.
Mar 11 06:34:23 ip-172-31-21-162.us-west-2.compute.internal dovecot[25387]: doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 1: Unknown setting: haproxy_trusted_networks
Mar 11 06:34:23 ip-172-31-21-162.us-west-2.compute.internal systemd[1]: dovecot.service: main process exited, code=exited, status=89/n/a
Mar 11 06:34:23 ip-172-31-21-162.us-west-2.compute.internal dovecot[25387]: doveconf: Error: managesieve-login: dump-capability process returned 89
Mar 11 06:34:23 ip-172-31-21-162.us-west-2.compute.internal dovecot[25387]: doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 1: Unknown setting: haproxy_trusted_networks
Mar 11 06:34:23 ip-172-31-21-162.us-west-2.compute.internal systemd[1]: Unit dovecot.service entered failed state.
Mar 11 06:34:23 ip-172-31-21-162.us-west-2.compute.internal systemd[1]: dovecot.service failed.
[root@ip-172-31-21-162 dovecot]#
I entered exactly what is given in the doc http://wiki2.dovecot.org/HAProxy.
AGAIN, you are not paying attention to what you're being told. YOU posted a link in your original post....you were told that post #3 in what you posted had the syntax, as did the others. And the only thing you changed was the IP address, and apparently STILL haven't bothered to read the very docs you say you've read.

AGAIN, read what you have already posted: http://dovecot.2317879.n4.nabble.com...50.html#a51179

...and try to find the difference. Not going to get much help with your spam server, thanks.
 
Old 03-11-2017, 10:18 AM   #11
bathory
LQ Guru
 
Registered: Jun 2004
Location: Piraeus
Distribution: Slackware
Posts: 12,840

Rep: Reputation: 1868Reputation: 1868Reputation: 1868Reputation: 1868Reputation: 1868Reputation: 1868Reputation: 1868Reputation: 1868Reputation: 1868Reputation: 1868Reputation: 1868
@OP
Quote:
rpm -qa|grep dovecot
dovecot-mysql-2.2.10-7.el7.x86_64
dovecot-pigeonhole-2.2.10-7.el7.x86_64
dovecot-devel-2.2.10-7.el7.x86_64
dovecot-2.2.10-7.el7.x86_64
Unfortunately dovecot support for haproxy is implemented on 2.2.19 version. So you need to upgrade to a more recent version.

Regards
 
1 members found this post helpful.
Old 03-11-2017, 10:34 AM   #12
TB0ne
LQ Guru
 
Registered: Jul 2003
Location: Birmingham, Alabama
Distribution: SuSE, RedHat, Slack,CentOS
Posts: 23,806

Rep: Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973
Quote:
Originally Posted by bathory View Post
@OP
Unfortunately dovecot support for haproxy is implemented on 2.2.19 version. So you need to upgrade to a more recent version.
Good catch...TOTALLY missed that, but the OP has been working on his spam server for quite some time. Assumed they had correct software installed...that's what I get for assuming.
 
Old 03-11-2017, 11:05 AM   #13
bathory
LQ Guru
 
Registered: Jun 2004
Location: Piraeus
Distribution: Slackware
Posts: 12,840

Rep: Reputation: 1868Reputation: 1868Reputation: 1868Reputation: 1868Reputation: 1868Reputation: 1868Reputation: 1868Reputation: 1868Reputation: 1868Reputation: 1868Reputation: 1868
@TB0ne
Quote:
Originally Posted by TB0ne View Post
Good catch...TOTALLY missed that, but the OP has been working on his spam server for quite some time. Assumed they had correct software installed...that's what I get for assuming.
I can't tell if OP is trying to setup a spam server, because dovecot is an IMAP/POP3 server not smtp.
Perhaps he's just building a mailserver for a big corporation so it needs a haproxy to serve clients.

Cheeers
 
Old 03-11-2017, 11:10 AM   #14
TB0ne
LQ Guru
 
Registered: Jul 2003
Location: Birmingham, Alabama
Distribution: SuSE, RedHat, Slack,CentOS
Posts: 23,806

Rep: Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973Reputation: 6973
Quote:
Originally Posted by bathory View Post
@TB0ne
I can't tell if OP is trying to setup a spam server, because dovecot is an IMAP/POP3 server not smtp. Perhaps he's just building a mailserver for a big corporation so it needs a haproxy to serve clients.
Please see: http://www.linuxquestions.org/questi...ps-4175592099/
Quote:
Originally Posted by redssr
I had one email marketing domain abc.com. Basically i want to setup bulk email server. I already had 10 different IP assigned to the server.
Now my problem is how to configure to use multiple IP for single domain so that my domain/Ip should not get blacklisted.
While the OP *SAYS* this isn't for a spam server...I'd certainly be highly suspicious.
 
Old 03-11-2017, 11:30 AM   #15
bathory
LQ Guru
 
Registered: Jun 2004
Location: Piraeus
Distribution: Slackware
Posts: 12,840

Rep: Reputation: 1868Reputation: 1868Reputation: 1868Reputation: 1868Reputation: 1868Reputation: 1868Reputation: 1868Reputation: 1868Reputation: 1868Reputation: 1868Reputation: 1868
Quote:
Originally Posted by TB0ne View Post
Please see: http://www.linuxquestions.org/questi...ps-4175592099/

While the OP *SAYS* this isn't for a spam server...I'd certainly be highly suspicious.
I've seen that thread, but as i told you, dovecot cannot be used to spam people, as it's an IMAP/POP3 server.
If it was for postfix or other smtp server I certainly refrain.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
HAProxy Redirect prash.devops Linux - Software 3 07-29-2016 12:01 PM
dovecot-auth: pam_succeed_if(dovecot:auth): error retrieving information about user karsel Linux - Newbie 0 12-11-2012 07:44 AM
Dovecot 1.x to Dovecot 2.x mbox to Maildir best transfer program silent_wumpus Linux - Server 0 09-05-2012 02:59 PM
/usr/local/libexec/dovecot/dovecot-lda - IS MISSING ?!? snowweb Linux - Server 1 08-14-2012 07:05 AM
haproxy agarwalpranay Linux - Newbie 4 06-19-2010 01:31 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 10:00 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration