Mail server using Postfix, Dovecot, Mysql... Postfix virtual maps doesn't work??

[tarasbuljba]

I have followed this guide

http://www.howtoforge.com/virtual-users-and-domains-postfix-dovecot-mysql-centos4.5

I change a little at me and edited custom postfix file as it is there, dovecot work, squiremail work and postfix work when i have no virtual aliases! When i add virtual things to postfix then it doesn't send/receive mail

In my configuration when i have this commented out all work fine and no errors, when it is use then postfix doesn't work

#virtual_mailbox_domains = mysql:$config_directory/mysql_virtual_domains_maps.cf
#virtual_mailbox_base = /var/vmail
#virtual_mailbox_maps = mysql:$config_directory/mysql_virtual_mailbox_maps.cf
#virtual_alias_maps = mysql:$config_directory/mysql_virtual_alias_maps.cf
#virtual_minimum_uid = 5000
#virtual_uid_maps = static:5000
#virtual_gid_maps = static:5000
#virtual_maildir_limit_message = "The user you are trying to reach is over quota."
#virtual_overquota_bounce = yes
#virtual_mailbox_extended = yes
#virtual_create_maildirsize = yes

Files i use for it are from that guide i posted link above... does anyone have any idea about why is this like that? I spent hours and hours trying all ways... Now i have dovecot and other running for nothing as this doesn't work :(

Thanks!

[topdog]

What do you see in the logs when postfix stops working ?

[tarasbuljba]

No no, postfix doesn't stop working, it loads normal as like without virtual things, and logs are empty...

I tested a bit more and it seems that problem is in virtual_mailbox_domains, virtual_alias_maps, virtual_mailbox_maps files because only they are commented now and postfix work, other i didn't comment... now i dunno if it is files from that guide or something wrong in that line? :O

EDIT: I forgot to add, when i have that virtual stuff mails seems to stay in quote on serv, when i comment them out later and restart postfix i receive emails sent by eg. forum on serv

[topdog]

You can run strace to see what is actually happening what is causing postfix to hung and not deliver.

[tarasbuljba]

I get this for strace -p on main master pid

time(NULL) = 1203790938
read(10, "\0", 1) = 1
read(10, 0xbfca762b, 1) = -1 EAGAIN (Resource temporarily unavailable)
waitpid(-1, [{WIFEXITED(s) && WEXITSTATUS(s) == 1}], WNOHANG) = 22929
time(NULL) = 1203790938
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2917, ...}) = 0
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2917, ...}) = 0
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2917, ...}) = 0
send(3, "<20>Feb 23 19:22:18 postfix/mast"..., 120, MSG_NOSIGNAL) = 120
time(NULL) = 1203790938
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2917, ...}) = 0
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2917, ...}) = 0
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2917, ...}) = 0
send(3, "<20>Feb 23 19:22:18 postfix/mast"..., 123, MSG_NOSIGNAL) = 123
time(NULL) = 1203790938
waitpid(-1, 0xbfca7804, WNOHANG) = 0
alarm(333) = 333
time(NULL) = 1203790938
select(94, [10 11 12 15 18 21 23 24 27 29 30 32 33 35 36 38 39 41 42 44 45 47 48 50 51 53 54 56 57 59 60 62 63 65 66 68 69 71 72 74 75 77 78 80 81 83 84 86 87 89 90 92 93], [], [10 11 12 15 18 21 23 24 27 29 30 32 33 35 36 38 39 41 42 44 45 47 48 50 51 53 54 56 57 59 60 62 63 65 66 68 69 71 72 74 75 77 78 80 81 83 84 86 87 89 90 92 93], {34, 0}

I noticed something else, when i use that virtual things with grep postfix i get
root 22887 0.0 0.1 6704 1748 ? Ss 19:21 0:00 /usr/libexec/postfix/master
postfix 22889 0.0 0.1 6768 1736 ? S 19:21 0:00 pickup -l -t fifo -u
postfix 22890 0.0 0.1 6828 1828 ? S 19:21 0:00 qmgr -l -t fifo -u

And when i don't use them i get many more...
root 23114 0.0 0.1 6704 1748 ? Ss 19:26 0:00 /usr/libexec/postfix/master
postfix 23116 0.0 0.1 6772 1784 ? S 19:26 0:00 pickup -l -t fifo -u
postfix 23117 0.0 0.1 6828 1844 ? S 19:26 0:00 qmgr -l -t fifo -u
postfix 23118 0.0 0.1 6892 1888 ? S 19:26 0:00 cleanup -z -t unix -u
postfix 23119 0.0 0.1 6776 1736 ? S 19:26 0:00 trivial-rewrite -n rewrite -t unix -u
postfix 23120 0.0 0.2 6932 2304 ? S 19:26 0:00 smtp -t unix -u
postfix 23121 0.0 0.1 6764 1820 ? S 19:26 0:00 tlsmgr -l -t unix -u
postfix 23122 0.0 0.1 6892 1884 ? S 19:26 0:00 cleanup -z -t unix -u
postfix 23123 0.0 0.2 6936 2316 ? S 19:26 0:00 smtp -t unix -u
postfix 23124 0.0 0.2 6936 2316 ? S 19:26 0:00 smtp -t unix -u
postfix 23125 0.0 0.2 6936 2316 ? S 19:26 0:00 smtp -t unix -u

Now that is weird a bit :/

[topdog]

The master is unable to start the other processes that means something is hunging i cannot put my figure on it, I guess you need to run strace from when you start the process.

[tarasbuljba]

I don't know how to do that kind of strace really :(

But, i did some more starts and tests and i found this in logs!

Feb 24 08:14:06 server postfix/postfix-script: starting the Postfix mail system
Feb 24 08:14:06 server postfix/master[6211]: daemon started -- version 2.3.3, configuration /etc/postfix
Feb 24 08:14:06 server postfix/qmgr[6214]: C8D0122C8177: from=<apache@server.borgteam.com>, size=1249, nrcpt=2 (queue active)
Feb 24 08:14:06 server postfix/trivial-rewrite[6215]: fatal: unsupported dictionary type: mysql
Feb 24 08:14:07 server postfix/master[6211]: warning: process /usr/libexec/postfix/trivial-rewrite pid 6215 exit status 1
Feb 24 08:14:07 server postfix/master[6211]: warning: /usr/libexec/postfix/trivial-rewrite: bad command startup -- throttling
Feb 24 08:15:07 server postfix/trivial-rewrite[6305]: fatal: unsupported dictionary type: mysql
Feb 24 08:15:08 server postfix/master[6211]: warning: process /usr/libexec/postfix/trivial-rewrite pid 6305 exit status 1
Feb 24 08:15:08 server postfix/master[6211]: warning: /usr/libexec/postfix/trivial-rewrite: bad command startup -- throttling
Feb 24 08:15:25 server postfix/cleanup[6316]: fatal: unsupported dictionary type: mysql
Feb 24 08:15:26 server postfix/master[6211]: warning: process /usr/libexec/postfix/cleanup pid 6316 exit status 1
Feb 24 08:15:26 server postfix/master[6211]: warning: /usr/libexec/postfix/cleanup: bad command startup -- throttling

mysql is unsupported :/?

[topdog]

Yep your postfix was built without mysql support.

ldd `which postfix`

[tarasbuljba]

Third edit...

I go all to work now, virtual emails also work, i can send and receive emails, but... i hav eproblem with pop3 on windows mail when i add account

i can receive emails normal over windows mail but i can't send as i get relay reject message... over squiremail i can send...

I also tried to add imap account to windows mail and i get same error when i wanna send message... any ideas?

[topdog]

You need to add your network to the mynetworks option, or use smtp authentication.

[tarasbuljba]

What do you mean? :/

I have this there

inet_interfaces = all
mydestination = $myhostname, localhost.$mydomain, $transport_maps, mail.$mydomain
mynetworks = 85.17.200.115

:/

Dunno now what you mean

[falko]

mynetworks = 85.17.200.115
You should use this instead:
mynetworks = 127.0.0.0/8
and then enable "Server requires authentication" in your email client.

[tarasbuljba]

I did that, but now i can't send emails over webmail or any programs... i get this error on webmail

Transaction failed
Server replied: 554 5.7.1 <tarasbuljba@gmail.com>: Relay access denied

And in programs it only asks again and again for username/password

[topdog]

Point your webmail's smtp configuration to 127.0.0.1

[tarasbuljba]

I did

Now i get only this as error message in webmail

Server replied:

Below is configuration file i have if you can check it out and tell me what is wrong? :/ I have on my server two ip's, one is 85.17.200.71 and one is 85.17.200.115 (borgteam.com), when i use .71 ip i get same error as above said, when i use .115 then everything is fine...

# Global Postfix configuration file. This file lists only a subset
# of all parameters. For the syntax, and for a complete parameter
# list, see the postconf(5) manual page (command: "man 5 postconf").
#
# For common configuration examples, see BASIC_CONFIGURATION_README
# and STANDARD_CONFIGURATION_README. To find these documents, use
# the command "postconf html_directory readme_directory", or go to
# http://www.postfix.org/.
#
# For best results, change no more than 2-3 parameters at a time,
# and test if Postfix still works after every change.

# SOFT BOUNCE
#
# The soft_bounce parameter provides a limited safety net for
# testing. When soft_bounce is enabled, mail will remain queued that
# would otherwise bounce. This parameter disables locally-generated
# bounces, and prevents the SMTP server from rejecting mail permanently
# (by changing 5xx replies into 4xx replies). However, soft_bounce
# is no cure for address rewriting mistakes or mail routing mistakes.
#
#soft_bounce = no

# LOCAL PATHNAME INFORMATION
#
# The queue_directory specifies the location of the Postfix queue.
# This is also the root directory of Postfix daemons that run chrooted.
# See the files in examples/chroot-setup for setting up Postfix chroot
# environments on different UNIX systems.
#
queue_directory = /var/spool/postfix

# The command_directory parameter specifies the location of all
# postXXX commands.
#
command_directory = /usr/sbin

# The daemon_directory parameter specifies the location of all Postfix
# daemon programs (i.e. programs listed in the master.cf file). This
# directory must be owned by root.
#
daemon_directory = /usr/libexec/postfix

# QUEUE AND PROCESS OWNERSHIP
#
# The mail_owner parameter specifies the owner of the Postfix queue
# and of most Postfix daemon processes. Specify the name of a user
# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In
# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
# USER.
#
mail_owner = postfix

# The default_privs parameter specifies the default rights used by
# the local delivery agent for delivery to external file or command.
# These rights are used in the absence of a recipient user context.
# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
#
#default_privs = nobody

# INTERNET HOST AND DOMAIN NAMES
#
# The myhostname parameter specifies the internet hostname of this
# mail system. The default is to use the fully-qualified domain name
# from gethostname(). $myhostname is used as a default value for many
# other configuration parameters.
#
myhostname = server.85.17.200.71
#myhostname = virtual.domain.tld

# The mydomain parameter specifies the local internet domain name.
# The default is to use $myhostname minus the first component.
# $mydomain is used as a default value for many other configuration
# parameters.
#
mydomain = borgteam.com

# SENDING MAIL
#
# The myorigin parameter specifies the domain that locally-posted
# mail appears to come from. The default is to append $myhostname,
# which is fine for small sites. If you run a domain with multiple
# machines, you should (1) change this to $mydomain and (2) set up
# a domain-wide alias database that aliases each user to
# user@that.users.mailhost.
#
# For the sake of consistency between sender and recipient addresses,
# myorigin also specifies the default domain name that is appended
# to recipient addresses that have no @domain part.
#
myorigin = $myhostname
#myorigin = $mydomain

# RECEIVING MAIL

# The inet_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on. By default,
# the software claims all active interfaces on the machine. The
# parameter also controls delivery of mail to user@[ip.address].
#
# See also the proxy_interfaces parameter, for network addresses that
# are forwarded to us via a proxy or network address translator.
#
# Note: you need to stop/start Postfix when this parameter changes.
#
#inet_interfaces = all
#inet_interfaces = $myhostname
#inet_interfaces = $myhostname, localhost
inet_interfaces = all

# The proxy_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on by way of a
# proxy or network address translation unit. This setting extends
# the address list specified with the inet_interfaces parameter.
#
# You must specify your proxy/NAT addresses when your system is a
# backup MX host for other domains, otherwise mail delivery loops
# will happen when the primary MX host is down.
#
#proxy_interfaces =
#proxy_interfaces = 1.2.3.4

# The mydestination parameter specifies the list of domains that this
# machine considers itself the final destination for.
#
# These domains are routed to the delivery agent specified with the
# local_transport parameter setting. By default, that is the UNIX
# compatible delivery agent that lookups all recipients in /etc/passwd
# and /etc/aliases or their equivalent.
#
# The default is $myhostname + localhost.$mydomain. On a mail domain
# gateway, you should also include $mydomain.
#
# Do not specify the names of virtual domains - those domains are
# specified elsewhere (see VIRTUAL_README).
#
# Do not specify the names of domains that this machine is backup MX
# host for. Specify those names via the relay_domains settings for
# the SMTP server, or use permit_mx_backup if you are lazy (see
# STANDARD_CONFIGURATION_README).
#
# The local machine is always the final destination for mail addressed
# to user@[the.net.work.address] of an interface that the mail system
# receives mail on (see the inet_interfaces parameter).
#
# Specify a list of host or domain names, /file/name or type:table
# patterns, separated by commas and/or whitespace. A /file/name
# pattern is replaced by its contents; a type:table is matched when
# a name matches a lookup key (the right-hand side is ignored).
# Continue long lines by starting the next line with whitespace.
#
# See also below, section "REJECTING MAIL FOR UNKNOWN LOCAL USERS".
#
mydestination = $myhostname, localhost.$mydomain, $transport_maps, mail.$mydomain
#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain,
# mail.$mydomain, www.$mydomain, ftp.$mydomain

# REJECTING MAIL FOR UNKNOWN LOCAL USERS
#
# The local_recipient_maps parameter specifies optional lookup tables
# with all names or addresses of users that are local with respect
# to $mydestination, $inet_interfaces or $proxy_interfaces.
#
# If this parameter is defined, then the SMTP server will reject
# mail for unknown local users. This parameter is defined by default.
#
# To turn off local recipient checking in the SMTP server, specify
# local_recipient_maps = (i.e. empty).
#
# The default setting assumes that you use the default Postfix local
# delivery agent for local delivery. You need to update the
# local_recipient_maps setting if:
#
# - You define $mydestination domain recipients in files other than
# /etc/passwd, /etc/aliases, or the $virtual_alias_maps files.
# For example, you define $mydestination domain recipients in
# the $virtual_mailbox_maps files.
#
# - You redefine the local delivery agent in master.cf.
#
# - You redefine the "local_transport" setting in main.cf.
#
# - You use the "luser_relay", "mailbox_transport", or "fallback_transport"
# feature of the Postfix local delivery agent (see local(8)).
#
# Details are described in the LOCAL_RECIPIENT_README file.
#
# Beware: if the Postfix SMTP server runs chrooted, you probably have
# to access the passwd file via the proxymap service, in order to
# overcome chroot restrictions. The alternative, having a copy of
# the system passwd file in the chroot jail is just not practical.
#
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify a bare username, an @domain.tld
# wild-card, or specify a user@domain.tld address.
#
#local_recipient_maps = unix:passwd.byname $alias_maps
#local_recipient_maps = proxy:unix:passwd.byname $alias_maps
#local_recipient_maps =

# The unknown_local_recipient_reject_code specifies the SMTP server
# response code when a recipient domain matches $mydestination or
# ${proxy,inet}_interfaces, while $local_recipient_maps is non-empty
# and the recipient address or address local-part is not found.
#
# The default setting is 550 (reject mail) but it is safer to start
# with 450 (try again later) until you are certain that your
# local_recipient_maps settings are OK.
#
unknown_local_recipient_reject_code = 450

# TRUST AND RELAY CONTROL

# The mynetworks parameter specifies the list of "trusted" SMTP
# clients that have more privileges than "strangers".
#
# In particular, "trusted" SMTP clients are allowed to relay mail
# through Postfix. See the smtpd_recipient_restrictions parameter
# in postconf(5).
#
# You can specify the list of "trusted" network addresses by hand
# or you can let Postfix do it for you (which is the default).
#
# By default (mynetworks_style = subnet), Postfix "trusts" SMTP
# clients in the same IP subnetworks as the local machine.
# On Linux, this does works correctly only with interfaces specified
# with the "ifconfig" command.
#
# Specify "mynetworks_style = class" when Postfix should "trust" SMTP
# clients in the same IP class A/B/C networks as the local machine.
# Don't do this with a dialup site - it would cause Postfix to "trust"
# your entire provider's network. Instead, specify an explicit
# mynetworks list by hand, as described below.
#
# Specify "mynetworks_style = host" when Postfix should "trust"
# only the local machine.
#
#mynetworks_style = class
#mynetworks_style = subnet
#mynetworks_style = host

# Alternatively, you can specify the mynetworks list by hand, in
# which case Postfix ignores the mynetworks_style setting.
#
# Specify an explicit list of network/netmask patterns, where the
# mask specifies the number of bits in the network part of a host
# address.
#
# You can also specify the absolute pathname of a pattern file instead
# of listing the patterns here. Specify type:table for table-based lookups
# (the value on the table right-hand side is not used).
#
mynetworks = 85.17.200.115
#mynetworks = $config_directory/mynetworks
#mynetworks = hash:/etc/postfix/network_table

# The relay_domains parameter restricts what destinations this system will
# relay mail to. See the smtpd_recipient_restrictions description in
# postconf(5) for detailed information.
#
# By default, Postfix relays mail
# - from "trusted" clients (IP address matches $mynetworks) to any destination,
# - from "untrusted" clients to destinations that match $relay_domains or
# subdomains thereof, except addresses with sender-specified routing.
# The default relay_domains value is $mydestination.
#
# In addition to the above, the Postfix SMTP server by default accepts mail
# that Postfix is final destination for:
# - destinations that match $inet_interfaces or $proxy_interfaces,
# - destinations that match $mydestination
# - destinations that match $virtual_alias_domains,
# - destinations that match $virtual_mailbox_domains.
# These destinations do not need to be listed in $relay_domains.
#
# Specify a list of hosts or domains, /file/name patterns or type:name
# lookup tables, separated by commas and/or whitespace. Continue
# long lines by starting the next line with whitespace. A file name
# is replaced by its contents; a type:name table is matched when a
# (parent) domain appears as lookup key.
#
# NOTE: Postfix will not automatically forward mail for domains that
# list this system as their primary or backup MX host. See the
# permit_mx_backup restriction description in postconf(5).
#
#relay_domains = $mydestination

# INTERNET OR INTRANET

# The relayhost parameter specifies the default host to send mail to
# when no entry is matched in the optional transport(5) table. When
# no relayhost is given, mail is routed directly to the destination.
#
# On an intranet, specify the organizational domain name. If your
# internal DNS uses no MX records, specify the name of the intranet
# gateway host instead.
#
# In the case of SMTP, specify a domain, host, host:port, [host]:port,
# [address] or [address]:port; the form [host] turns off MX lookups.
#
# If you're connected via UUCP, see also the default_transport parameter.
#
#relayhost = $mydomain
#relayhost = [gateway.my.domain]
#relayhost = [mailserver.isp.tld]
#relayhost = uucphost
#relayhost = [an.ip.add.ress]

# REJECTING UNKNOWN RELAY USERS
#
# The relay_recipient_maps parameter specifies optional lookup tables
# with all addresses in the domains that match $relay_domains.
#
# If this parameter is defined, then the SMTP server will reject
# mail for unknown relay users. This feature is off by default.
#
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify an @domain.tld wild-card, or specify
# a user@domain.tld address.
#
#relay_recipient_maps = hash:/etc/postfix/relay_recipients

# INPUT RATE CONTROL
#
# The in_flow_delay configuration parameter implements mail input
# flow control. This feature is turned on by default, although it
# still needs further development (it's disabled on SCO UNIX due
# to an SCO bug).
#
# A Postfix process will pause for $in_flow_delay seconds before
# accepting a new message, when the message arrival rate exceeds the
# message delivery rate. With the default 100 SMTP server process
# limit, this limits the mail inflow to 100 messages a second more
# than the number of messages delivered per second.
#
# Specify 0 to disable the feature. Valid delays are 0..10.
#
#in_flow_delay = 1s

# ADDRESS REWRITING
#
# The ADDRESS_REWRITING_README document gives information about
# address masquerading or other forms of address rewriting including
# username->Firstname.Lastname mapping.

# ADDRESS REDIRECTION (VIRTUAL DOMAIN)
#
# The VIRTUAL_README document gives information about the many forms
# of domain hosting that Postfix supports.

# "USER HAS MOVED" BOUNCE MESSAGES
#
# See the discussion in the ADDRESS_REWRITING_README document.

# TRANSPORT MAP
#
# See the discussion in the ADDRESS_REWRITING_README document.

# ALIAS DATABASE
#
# The alias_maps parameter specifies the list of alias databases used
# by the local delivery agent. The default list is system dependent.
#
# On systems with NIS, the default is to search the local alias
# database, then the NIS alias database. See aliases(5) for syntax
# details.
#
# If you change the alias database, run "postalias /etc/aliases" (or
# wherever your system stores the mail alias file), or simply run
# "newaliases" to build the necessary DBM or DB file.
#
# It will take a minute or so before changes become visible. Use
# "postfix reload" to eliminate the delay.
#
#alias_maps = dbm:/etc/aliases
#alias_maps = hash:/etc/aliases
#alias_maps = hash:/etc/aliases, nis:mail.aliases
#alias_maps = netinfo:/aliases
alias_maps = $alias_database

# The alias_database parameter specifies the alias database(s) that
# are built with "newaliases" or "sendmail -bi". This is a separate
# configuration parameter, because alias_maps (see above) may specify
# tables that are not necessarily all under control by Postfix.
#
#alias_database = dbm:/etc/aliases
#alias_database = dbm:/etc/mail/aliases
#alias_database = hash:/etc/aliases
#alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases
alias_database = hash:/etc/postfix/aliases

# ADDRESS EXTENSIONS (e.g., user+foo)
#
# The recipient_delimiter parameter specifies the separator between
# user names and address extensions (user+foo). See canonical(5),
# local(8), relocated(5) and virtual(5) for the effects this has on
# aliases, canonical, virtual, relocated and .forward file lookups.
# Basically, the software tries user+foo and .forward+foo before
# trying user and .forward.
#
recipient_delimiter = +

# DELIVERY TO MAILBOX
#
# The home_mailbox parameter specifies the optional pathname of a
# mailbox file relative to a user's home directory. The default
# mailbox file is /var/spool/mail/user or /var/mail/user. Specify
# "Maildir/" for qmail-style delivery (the / is required).
#
#home_mailbox = Mailbox
#home_mailbox = Maildir/

# The mail_spool_directory parameter specifies the directory where
# UNIX-style mailboxes are kept. The default setting depends on the
# system type.
#
#mail_spool_directory = /var/mail
mail_spool_directory = /var/spool/mail

# The mailbox_command parameter specifies the optional external
# command to use instead of mailbox delivery. The command is run as
# the recipient with proper HOME, SHELL and LOGNAME environment settings.
# Exception: delivery for root is done as $default_user.
#
# Other environment variables of interest: USER (recipient username),
# EXTENSION (address extension), DOMAIN (domain part of address),
# and LOCAL (the address localpart).
#
# Unlike other Postfix configuration parameters, the mailbox_command
# parameter is not subjected to $parameter substitutions. This is to
# make it easier to specify shell syntax (see example below).
#
# Avoid shell meta characters because they will force Postfix to run
# an expensive shell process. Procmail alone is expensive enough.
#
# IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP AN
# ALIAS THAT FORWARDS MAIL FOR ROOT TO A REAL USER.
#
#mailbox_command = /some/where/procmail
#mailbox_command = /some/where/procmail -a "$EXTENSION"

# The mailbox_transport specifies the optional transport in master.cf
# to use after processing aliases and .forward files. This parameter
# has precedence over the mailbox_command, fallback_transport and
# luser_relay parameters.
#
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf. The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
#
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#
#mailbox_transport = lmtp:unix:/var/lib/imap/socket/lmtp

# If using the cyrus-imapd IMAP server deliver local mail to the IMAP
# server using LMTP (Local Mail Transport Protocol), this is prefered
# over the older cyrus deliver program by setting the
# mailbox_transport as below:
#
# mailbox_transport = lmtp:unix:/var/lib/imap/socket/lmtp
#
# The efficiency of LMTP delivery for cyrus-imapd can be enhanced via
# these settings.
#
# local_destination_recipient_limit = 300
# local_destination_concurrency_limit = 5
#
# Of course you should adjust these settings as appropriate for the
# capacity of the hardware you are using. The recipient limit setting
# can be used to take advantage of the single instance message store
# capability of Cyrus. The concurrency limit can be used to control
# how many simultaneous LMTP sessions will be permitted to the Cyrus
# message store.
#
# To use the old cyrus deliver program you have to set:
#mailbox_transport = cyrus

# The fallback_transport specifies the optional transport in master.cf
# to use for recipients that are not found in the UNIX passwd database.
# This parameter has precedence over the luser_relay parameter.
#
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf. The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
#
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#
#fallback_transport = lmtp:unix:/var/lib/imap/socket/lmtp
#fallback_transport =

# The luser_relay parameter specifies an optional destination address
# for unknown recipients. By default, mail for unknown@$mydestination,
# unknown@[$inet_interfaces] or unknown@[$proxy_interfaces] is returned
# as undeliverable.
#
# The following expansions are done on luser_relay: $user (recipient
# username), $shell (recipient shell), $home (recipient home directory),
# $recipient (full recipient address), $extension (recipient address
# extension), $domain (recipient domain), $local (entire recipient
# localpart), $recipient_delimiter. Specify ${name?value} or
# ${name:value} to expand value only when $name does (does not) exist.
#
# luser_relay works only for the default Postfix local delivery agent.
#
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must specify "local_recipient_maps =" (i.e. empty) in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#
#luser_relay = $user@other.host
#luser_relay = $local@other.host
#luser_relay = admin+$local

# JUNK MAIL CONTROLS
#
# The controls listed here are only a very small subset. The file
# SMTPD_ACCESS_README provides an overview.

# The header_checks parameter specifies an optional table with patterns
# that each logical message header is matched against, including
# headers that span multiple physical lines.
#
# By default, these patterns also apply to MIME headers and to the
# headers of attached messages. With older Postfix versions, MIME and
# attached message headers were treated as body text.
#
# For details, see "man header_checks".
#
#header_checks = regexp:/etc/postfix/header_checks

# FAST ETRN SERVICE
#
# Postfix maintains per-destination logfiles with information about
# deferred mail, so that mail can be flushed quickly with the SMTP
# "ETRN domain.tld" command, or by executing "sendmail -qRdomain.tld".
# See the ETRN_README document for a detailed description.
#
# The fast_flush_domains parameter controls what destinations are
# eligible for this service. By default, they are all domains that
# this server is willing to relay mail to.
#
#fast_flush_domains = $relay_domains

# SHOW SOFTWARE VERSION OR NOT
#
# The smtpd_banner parameter specifies the text that follows the 220
# code in the SMTP server's greeting banner. Some people like to see
# the mail version advertised. By default, Postfix shows no version.
#
# You MUST specify $myhostname at the start of the text. That is an
# RFC requirement. Postfix itself does not care.
#
#smtpd_banner = $myhostname ESMTP $mail_name
#smtpd_banner = $myhostname ESMTP $mail_name ($mail_version)
smtpd_banner = $myhostname

# PARALLEL DELIVERY TO THE SAME DESTINATION
#
# How many parallel deliveries to the same user or domain? With local
# delivery, it does not make sense to do massively parallel delivery
# to the same user, because mailbox updates must happen sequentially,
# and expensive pipelines in .forward files can cause disasters when
# too many are run at the same time. With SMTP deliveries, 10
# simultaneous connections to the same domain could be sufficient to
# raise eyebrows.
#
# Each message delivery transport has its XXX_destination_concurrency_limit
# parameter. The default is $default_destination_concurrency_limit for
# most delivery transports. For the local delivery agent the default is 2.

#local_destination_concurrency_limit = 2
#default_destination_concurrency_limit = 20

# DEBUGGING CONTROL
#
# The debug_peer_level parameter specifies the increment in verbose
# logging level when an SMTP client or server host name or address
# matches a pattern in the debug_peer_list parameter.
#
debug_peer_level = 2

# The debug_peer_list parameter specifies an optional list of domain
# or network patterns, /file/name patterns or type:name tables. When
# an SMTP client or server host name or address matches a pattern,
# increase the verbose logging level by the amount specified in the
# debug_peer_level parameter.
#
#debug_peer_list = 127.0.0.1
#debug_peer_list = some.domain

# The debugger_command specifies the external command that is executed
# when a Postfix daemon program is run with the -D option.
#
# Use "command .. & sleep 5" so that the debugger can attach before
# the process marches on. If you use an X-based debugger, be sure to
# set up your XAUTHORITY environment variable before starting Postfix.
#
#debugger_command =
# PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
# xxgdb $daemon_directory/$process_name $process_id & sleep 5
debugger_command =
PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
xxgdb $daemon_directory/$process_name $process_id & sleep 5

# If you can't use X, use this to capture the call stack when a
# daemon crashes. The result is in a file in the configuration
# directory, and is named after the process name and the process ID.
#
# debugger_command =
# PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont;
# echo where) | gdb $daemon_directory/$process_name $process_id 2>&1
# >$config_directory/$process_name.$process_id.log & sleep 5
#
# Another possibility is to run gdb under a detached screen session.
# To attach to the screen sesssion, su root and run "screen -r
# <id_string>" where <id_string> uniquely matches one of the detached
# sessions (from "screen -list").
#
# debugger_command =
# PATH=/bin:/usr/bin:/sbin:/usr/sbin; export PATH; screen
# -dmS $process_name gdb $daemon_directory/$process_name
# $process_id & sleep 1

# INSTALL-TIME CONFIGURATION INFORMATION
#
# The following parameters are used when installing a new Postfix version.
#
# sendmail_path: The full pathname of the Postfix sendmail command.
# This is the Sendmail-compatible mail posting interface.
#
sendmail_path = /usr/sbin/sendmail.postfix

# newaliases_path: The full pathname of the Postfix newaliases command.
# This is the Sendmail-compatible command to build alias databases.
#
newaliases_path = /usr/bin/newaliases.postfix

# mailq_path: The full pathname of the Postfix mailq command. This
# is the Sendmail-compatible mail queue listing command.
#
mailq_path = /usr/bin/mailq.postfix

# setgid_group: The group for mail submission and queue management
# commands. This must be a group name with a numerical group ID that
# is not shared with other accounts, not even with the Postfix account.
#
setgid_group = postdrop

# html_directory: The location of the Postfix HTML documentation.
#
html_directory = no

# manpage_directory: The location of the Postfix on-line manual pages.
#
manpage_directory = /usr/share/man

# sample_directory: The location of the Postfix sample configuration files.
# This parameter is obsolete as of Postfix 2.1.
#
sample_directory = /usr/share/doc/postfix-2.3.3/samples

# readme_directory: The location of the Postfix README files.
#
readme_directory = /usr/share/doc/postfix-2.3.3/README_FILES

smtpd_sasl_auth_enable = yes
smtpd_sasl_security_options = noanonymous
broken_sasl_auth_clients = yes
smtpd_sasl_local_domain =
smtpd_recipient_restriction = permit_sasl_authenticated, permit_mynetworks, reject_unauth_destination

smptpd_tls_cert_file = /etc/ssl/server/mail/smtpd.crt
smtpd_tls_key_file = /etc/ssl/server/mail/smtpd.key
smtpd_tls_CAfile = /etc/ssl/server/mail/cacert.pem
smtp_tls_auth_only = no
smtp_use_tls = yes
smtpd_use_tls = yes
smtpd_tls_received_header = no
smtp_tls_note_starttls_offer = yes
smtpd_tls_loglevel = 1
tls_random_source = dev:/dev/urandom
smtpd_tls_session_cache_timeout = 3600s
smtpd_tls_recieved_header = yes

virtual_mailbox_domains = mysql:/etc/postfix/mysql_virtual_domains_maps.cf
virtual_mailbox_base = /var/vmail
virtual_mailbox_maps = mysql:/etc/postfix/mysql_virtual_mailbox_maps.cf
virtual_alias_maps = mysql:/etc/postfix/mysql_virtual_alias_maps.cf
virtual_minimum_uid = 150
virtual_uid_maps = static:150
virtual_gid_maps = static:12
virtual_mailbox_limit_override = yes
virtual_maildir_limit_message = "The user you are trying to reach is over quota."
virtual_overquota_bounce = yes
virtual_mailbox_extended = yes
virtual_create_maildirsize = yes
transport_maps = mysql:/etc/postfix/mysql-virtual_transports.cf

[topdog]

115 works because $mynetworks is pointing to it

mynetworks = 85.17.200.115


For localhost and your other ip to be able to send mail through the server with out authenticating you need this


mynetworks = 127.0.0.1 85.17.200.115 85.17.200.71

[tarasbuljba]

Ok, i did that, webmail one works now... but one over Windows mail doesn't work and i can't send emails...

I tried for both incoming and outgoing mail to put mail.borgteam.com and borgteam.com...

Also i tried to check box that my serv require auth... It asks for username/password then but whatever i put its not good...

I dunno what else i can post which can help to solve problem :/

In /etc/hosts i have this

127.0.0.1 localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6
85.17.200.71 server.85.17.200.71 server
85.17.200.115 server.borgteam.com server

I have other domain pointing to first ip but i haven't set that as hostname on ip address as i don't really use that domain much.. i dunno if that have anything with it..

And here is error from windows http://img176.imageshack.us/img176/300/clipboard01co2.jpg

[topdog]

That seems like a client problem, i am guessing that the windows mail is brain dead and is not trying to authenticate at all its just trying to send the mail because that is what error 0x800CC79 indicates.

[topdog]

Test your server to see if the server is working fine.

Generate your base64 encoded username / password combo

perl -MMIME::Base64 -e 'print encode_base64("\0username\0password");'


Then connect and test


telnet server_ip 25
220 server.domain_name.com ESMTP Postfix
ehlo me
250-server_name.com
250-PIPELINING
250-SIZE 10240000
250-ETRN
250-AUTH PLAIN LOGIN
250 8BITMIME
AUTH PLAIN AHVzZXJuYW1lAHBhc3N3b3Jk
235 Authentication successful

[tarasbuljba]

Seems not :(

telnet 85.17.200.71 25
Trying 85.17.200.71...
Connected to server.85.17.200.71 (85.17.200.71).
Escape character is '^]'.
220 server.85.17.200.71
ehlo me
250-server.85.17.200.71
250-PIPELINING
250-SIZE 10240000
250-VRFY
250-ETRN
250-STARTTLS
250-AUTH LOGIN PLAIN
250-AUTH=LOGIN PLAIN
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 DSN
AUTH PLAIN AHVzZXJuYW1lAHBhc3N3b3Jk
535 5.7.0 Error: authentication failed: authentication failure

Just wondering... may this have anything with dovecot or it is just postfix?

[topdog]

NO No, the server may be working, you just used my username / password combination with out changing it,

You NEED to generate your own base64 encoded username / password. using a username and password that exist on the server.

[tarasbuljba]

O, oops :)

System user/pass or virtual one in mysql for email? :/

I used here system one

telnet 85.17.200.71 25
Trying 85.17.200.71...
Connected to server.85.17.200.71 (85.17.200.71).
Escape character is '^]'.
220 server.85.17.200.71
ehlo me
250-server.85.17.200.71
250-PIPELINING
250-SIZE 10240000
250-VRFY
250-ETRN
250-STARTTLS
250-AUTH LOGIN PLAIN
250-AUTH=LOGIN PLAIN
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 DSN
AUTH PLAIN AHRhcmEcYTBlYTBl
535 5.7.0 Error: authentication failed: bad protocol / cancel

That is when i changed user pass... but with other pass i use usually works well..

telnet 85.17.200.71 25
Trying 85.17.200.71...
Connected to server.85.17.200.71 (85.17.200.71).
Escape character is '^]'.
220 server.85.17.200.71
ehlo me
250-server.85.17.200.71
250-PIPELINING
250-SIZE 10240000
250-VRFY
250-ETRN
250-STARTTLS
250-AUTH LOGIN PLAIN
250-AUTH=LOGIN PLAIN
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 DSN
AUTH PLAIN AHRhcmE...
235 2.0.0 Authentication successful

[topdog]

So now you agree that it is the M$ mail client that is brain dead.

[tarasbuljba]

the M$??

So what should i do with it now... i really have no idea anymore what to do to it

[topdog]

the M$??

So what should i do with it now... i really have no idea anymore what to do to it

Well since you pay for the Licence anyway, its time to get your moneys worth, phone M$

[tarasbuljba]

I pay for license? Tell me which one

[topdog]

you have a windows licence so M$ must provide you with support

[tarasbuljba]

??????

What are you talking about, you make me confused really... have no idea what/how/etc

[topdog]

I am saying speak to M$ technical support and let they debug the problem.

[tarasbuljba]

So you say that i talk to provider where i rent dedicated server at? :/

Might it be my hostnames? I am all confused about it... On domain i have few A records for subdomains and www. and just domain, on ip reverse lookup i set server.***.com and for second ip server1.***.com

too much linux stuff for me to learn :( :)

[topdog]

So you say that i talk to provider where i rent dedicated server at? :/

Might it be my hostnames? I am all confused about it... On domain i have few A records for subdomains and www. and just domain, on ip reverse lookup i set server.***.com and for second ip server1.***.com

too much linux stuff for me to learn :( :)
The problem as you saw with your test is not the server, your server is working properly the only reason you cannot authenticate and send mail is because the windows mail client you are using is brain dead, if you want to continue using windows mail then talk to Microsoft to help you fix the client, our use something else.

But your server is fine as you can see that when you connect to it via telnet you can authenticate.

The problem is the client NOT the server.

[tarasbuljba]

Ooo, better :)

I will test some other client then.. maybe outlook on windows xp on my other pc and i might install thunderbird and test with it too, then i reply here...

Thx

Just a question, this is edit msg

Is this ok for dovecot...? It is different then in that guide because it didn't work before

auth default {
# Space separated list of wanted authentication mechanisms:
# plain login digest-md5 cram-md5 ntlm rpa apop anonymous gssapi
mechanisms = plain login

and this in dovecot-sql config

default_pass_scheme = PLAIN-MD5...

And one more thing about postfix i noticed, it says no tls in logs, but i have created certificates and path is ok

smptpd_tls_cert_file = /etc/ssl/server/mail/smtpd.crt
smtpd_tls_key_file = /etc/ssl/server/mail/smtpd.key
smtpd_tls_CAfile = /etc/ssl/server/mail/cacert.pem

this is from log: warning: No server certs available. TLS won't be enabled