Linux - NewbieThis 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
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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.
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
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
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
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.
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.
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.
@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.
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.
@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.
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.
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
