FC4 and postfix setup for multiple domains and POP3

How do i trouble shoot the delivery of email to multiple domains on this setup.  I have followed the instructions on the example but when it says test it and see new email appear in the folders i do not see any.  I need some help here.



D

Well, since you're carrying on with this question instead of creating a new one as suggested, I'll try to help by asking some questions.

1)  Prior to testing by sending email to addresses in the postfix virtual post offices, did you test the installation locally as recommended in the instructions, using telnet?

2)  Can you telnet to both port 110 and port 25, both locally and through the Internet?  If not, see next question.

3)  Have you verified that your ports are not blocked by iptables or by the config not set to listen on the interface (or all interfaces)?

4)  If you're sending mail to, for example, joe@abc.com, from an internet location like a Yahoo or hotmail account, are you getting any sort of undeliverable message back?

5)  Before attempting to send mail over the internet to this server, did you verify that there are MX records for those domains pointing to an A record that resolves to the public IP of this server?

After you answer those questions, maybe there will be more questions, but maybe you'll find your answer while answering those questions.

on question 1 all the instructions state is:

Restarting postfix and testing delivery

Our next task is to reload the configuration changes we've just made to postfix with:

#postfix reload

Keep an eye on your /var/log/maillog for any errors from the postfix daemons, in case there are simply typos or similar errors occurring.

Provide the reload occurred without error, test your setup by sending mail to your new virtual domains. If all looks well in /var/log/maillog, you should be able to look in your /var/spool/virtual/another-domain.com directory and see a new mailbox containing the mail you just sent.

If you get errors in /var/log/maillog you need to double check your directories, permissions, tables and don't forget if you didn't look in the master.cf file right back at the beginning that could be the cause of your trouble too. Most error messages from postfix are relatively helpful in narrowing down the point of failure.

Assuming that all worked, we can move onto setting up vm-pop3d.

and i can stop and start postfix without errors.  if i telnet in--

telnet localhost 25
Trying 127.0.0.1...
Connected to localhost (127.0.0.1).
Escape character is '^]'.

if i type  ehlo localhost it just hangs.

in main.cf i did not set up anything other than what was in the instructions.  

here is my main.cf

# Global Postfix configuration file. This file lists only a subset
# of all 300+ parameters. See the postconf(5) manual page for a
# complete list.
#
# The general format of each line is: parameter = value. Lines
# that begin with whitespace continue the previous line. A value can
# contain references to other $names or ${name}s.
#
# NOTE - 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 = host.domain.tld
#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 = domain.tld

# 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 = localhost

# 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, localhost
#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 = 550

# 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 = 168.100.189.0/28, 127.0.0.0/8
#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

# 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

# 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:/file/name
#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:/file/name
#fallback_transport = cyrus
#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)

# 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

# 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.2.2/samples

# readme_directory: The location of the Postfix README files.
#
readme_directory = /usr/share/doc/postfix-2.2.2/README_FILES
virtual_mailbox_base = /var/spool/virtual
virtual_mailbox_maps = hash:/etc/postfix/vmailbox
virtual_mailbox_domains = hash:/etc/postfix/vmaildomains
virtual_uid_maps = static:200
virtual_gid_maps = static:200
virtual_mailbox_lock = dotlock
virtual_minimum_uid = 200

See the last post in {http:Q_21985866.html}

The asker in that Question says they had to change main.cf inet_interface to "all interfaces" from "localhost" to get things to work.

You beat me to my post, and I see you already have it set to "all."

on the machine(using putty) i can type  telnet localhost 25  or   telnet 192.168.100.76 25 and then will be presented with

[root@mail2 ~]# telnet 192.168.100.76 25
Trying 192.168.100.76...
Connected to 192.168.100.76 (192.168.100.76).
Escape character is '^]'.



and then it hangs there.  

i can not telnet in from another computer on the network and that is with firewall off   lokkit  disabled

Have you compared your main.cf and virtual and vmailbox files to what the asker posted at {http:Q_21985866.html#17527777}?

i copied it over and now im getting this error from  /var/log/maillog

Jan 31 11:15:22 mail2 postfix/trivial-rewrite[19114]: fatal: open database /etc/postfix/virtual.db: No such file or directory
Jan 31 11:15:23 mail2 postfix/master[12475]: warning: process /usr/libexec/postfix/trivial-rewrite pid 19114 exit status 1
Jan 31 11:15:23 mail2 postfix/master[12475]: warning: /usr/libexec/postfix/trivial-rewrite: bad command startup -- throttling

"copied it over" - ???

I was expecting you to desk-check your stuff against the stuff the other Asker posted to see what might be different, and adjust accordingly...  

If you had your virtual PO's all set and then changed the names/locations in your configs to whatever it says in his configuration, I would expect you to have new problems.

there is only  /etc/postfix/virtual    

there is no  /etc/postfix/virtual.db

in the directions i followed i do not see any instructions to do

#postmap virtula

in the /etc/postfix  directory.

You have to make sure you don't have references to anything in your main.cf that doesn't exist on the drive.  If you made paths and stuff for *your* virtual PO's but are now referencing the *other guy's* virtual PO's in your main.cf, you'll get the "no such file or directory" error.

i went back to the original main.cf

here are the differences between mine and the example you referenced

they have:
mydestination = virtual_mailbox_domains = localhost.$mydomain,virtual1.domain,virtual2.domain,abc.com
i have:
mydestination = $myhostname, localhost.$mydomain, localhost

they have:
alias_database = hash:/etc/postfix/aliases
I have:
alias_database = hash:/etc/aliases

I do not have an aliases file or an aliases.db file there.

they had
#mail_owner = postfix

i have
mail_owner = postfix

So you don't have virtual POs set up yet, then?

how are you determining that?

Dunno.

Usually when virtual POs are set up you have a virtual.db somewhere.  The "postmap virtual" command should create it, provided you created a "virtual" file with the 2 domains mapped to their directories.  The asker called it "virtual" which is why they would've had to have done "postmap virtual."

After you have the directories and users and whatnot defined, you need to do the postmap command somewhere along the line.  

The guy that posted the instructions at {http:Q_21985866.html#17509990} has you create a vmaildomains file and a vmailbox file and has you run "postmap vmaildomains" and "postmap vmailbox" using those files, instead of one called "virtual" for the virtual domains.  The default virtual domain config file is called "virtual" which is probably why the asker used "virtual."

Do you have your 2 domains and their target directories in the /etc./postfix/virtual file?  If so, run "postmap virtual" in the /etc/postfix/ directory to create your virtual.db and try again...

Hi knightdogs,

Just quick question how far have you got with postfix problem and what will you be using for pop Can help in step by step guide in setup postfix with cyrus-imapd?.

let me know.

Darren

I am now at the point where i am trying to telnet into it and getting the followning:
[root@mail3 ~]# telnet localhost 25
Trying 127.0.0.1...
Connected to localhost.localdomain (127.0.0.1).
Escape character is '^]'.

and it will just hang.  I have ran lokkit and disabled the firewall and it still just hangs there.  

have you tried to send mail to root from localhost ?
On command line as root user
----------------------------------
mail root
Subject: Test from localhost
Test #1
.
Cc:
-------------------------
check to see if mail server is getting mail locally if we get test mail for root we can look else where also just check have you got localhost.localdomain in your host file?

Darren

Darren,
thank you for that information.  I got that far late last night and was able to use that and send email to root, i went one step farther and sent it to admin@1stvirtualdomain and that worked it created the file in the var/spool/virtual/1stvirtualdomain folder.  I checked this morning and found out that more test email that i had sent to admin@1stvirtualdomain had now ben delivered ( about 48 hrs later).  also test email that i had sent to dennis@1stvirtauldomain and paul@1stvirtualdomain had been delivered.  email that i sent to admin@2ndvirtualdomain had not been delivered yet, and it was sent at the same time.  i went in and used telnet session to send email to admin@2ndvirtualdomain and it went, so i am waiting on it to see if the other emails i have sent will arrive.

i am monitoring the /var/log/maillog to see when it is attempting to deliver email.

i will now start on the second part of the documentation   http://www.sonicresolutions.com/tech/howto_postfix_vmpop3d.html  starting Configuring vm-pop3d  

will you be able to assist in this also?

Hi Knightdogs,

I am not familiar vmpop as i have never installed the software or run it on our linux servers.

We currently use postfix with cyrus-imapd as our pop server and we had no problems with virtual domain hosting we control the whole email server via webmin which has couple plugins called virtualmin and cyus admin to control user admins personally i would recommend this but it really is personal choice.
let me know if you would like any assistance in the future.

all the best

Darren,

yes please. i am using webmin also so you said the magic word.  I have installed vm-pop3d and it has been giving me a fit all day.  did you download the plugins from webmin.com?

Lets start from the begin download these packages and install with yum
yum -y install cyrus-imapd cyrus-imapd-utils cyrus-sasl cyrus-sasl-devel cyrus-sasl-md5 cyrus-sasl-plain perl-Cyrus

Then go to webmin and download virtualmin http://download.webmin.com/download/virtualmin/virtual-server-3.33.gpl.wbm.gz
then go here http://www.tecchio.net/webmin/cyrus/cyrus-imapd-mod-1.4.5.wbm.gz and download the cyrus admin module for webmin.

After that go to command prompt as root and type CPAN
here you will need to install Perl modules
install Encode
install HTML::Entities
install Cyrus::IMAP
install Mail::IMAPClient

You may need to setup cpan if you have never run before just follow screen defaults then you may want to run install Bundle::CPAN.

once you have completed this we will go on to the next step  to complete the postfix & cyrus install.

all the best
Darren

I guess the question first would be, does Cyrus imapd do multiple virtual POP3 servers like vm-pop3d is supposed to do?  If so, and it's easier to work with, go for it, but if not, travel the road you started on with vm-pop3d...

My 2 cents.

I have completed the cyrus installs with yum
it told me it installed 4 packages.
i am looking now for the commands to run to show installed packages to verify that the other packages were installed.

i have gone into Webmin and modules and installed the two modules for webmin

on CPAN i got the below error:
cpan> install Cyrus::IMAP
Warning: Cannot install Cyrus::IMAP, don't know what it is.
Try the command

    i /Cyrus::IMAP/

to find objects with matching identifiers.
 
all other installs gave me   install --ok

Ok go to webmin and select the other tab click on perl modules and see if Cyrus::IMAP is install from the perl-cyrus package which you install from yum.

you should see Cyrus::Imap listed in the install perl modules.

After that on the command line as root set cyrus-imapd password.
 run command  passwd cyrus
( just create your own cyrus password )

Then yon need to open up port 143 imap port on iptables.

then go to Cyrus IMAP Server module in webmin control panel and click on configure on top left menu enter in the password you created on the command line as root.

then go to virtualmin module  Configuration under the section
Actions upon server and user creation look for:

Notify other modules when updating server administrator Unix users?        

Notify other modules when updating mailbox Unix users?

Select the radio button to say yes and save the configuration.

Then open file manager on the webmin control panel and navigate to /etc/sysconfig/saslauthd click on edit tab above and change MECH=shadow  to read as MECH=pam

The navigate to /etc/imapd.conf and click edit and paste in below
-----------------------------------------------------------
reject8bit: no
autocreatequota: 512000
hashimapspool: 1
sasl_mech_list: PLAIN
virtdomains: 0
configdirectory: /var/lib/imap
admins: cyrus
sasl_pwcheck_method: saslauthd
imapidresponse: 0
timeout: 30
dracinterval: 0
poptimeout: 10
autocreatequota_units: 1048576
partition-default: /var/spool/imap
servername: your server name here
drachost: localhost
tls_cert_file: /usr/share/ssl/certs/cyrus-imapd.pem
tls_ca_file: /usr/share/ssl/certs/ca-bundle.crt
tls_key_file: /usr/share/ssl/certs/cyrus-imapd.pem
-------------------------------------------------------------------------------
Then open up postfix main.cf and paste this in
queue_directory = /var/spool/postfix
command_directory = /usr/sbin
daemon_directory = /usr/libexec/postfix
mail_owner = postfix
append_dot_mydomain = no
biff = no
inet_interfaces = all
notify_classes = resource, software
#myhostname = your hostname here
#mydomain =  your domain here
mydestination = $myhostname, $mydomain, localhost.$mydomain, mail.$mydomain, localhost, mail.hostnamehere, hostname here
smtpd_banner = $myhostname ESMTP $mail_name
myorigin = $mydomain
inet_interfaces = all
alias_database = hash:/etc/postfix/aliases
virtual_alias_domains = hash:/etc/postfix/virtual
$virtual_mailbox_domains = hash:/etc/postfix/virtual
virtual_alias_maps = hash:/etc/postfix/virtual
mailbox_transport = lmtp:unix:/var/lib/imap/socket/lmtp
unknown_local_recipient_reject_code = 450
mynetworks_style = host
alias_maps = hash:/etc/aliases
relay_domains = $mydestination
cyrus_destination_recipient_limit = 1
cyrus_destination_concurrency_limit = 2
debug_peer_level = 2
debug_peer_level = 2
debugger_command =
       PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
       ddd $daemon_directory/$process_name $process_id & sleep 5
sendmail_path = /usr/sbin/sendmail.postfix
newaliases_path = /usr/bin/newaliases.postfix
mailq_path = /usr/bin/mailq.postfix
setgid_group = postdrop
manpage_directory = /usr/share/man
sample_directory = /usr/share/doc/postfix-2.0.18/samples
readme_directory = /usr/share/doc/postfix-2.0.18/README_FILES
smtpd_sasl_auth_enable = yes
smtpd_sasl_security_options = noanonymous
smtpd_sasl_local_domain = $myhostname
smtpd_sasl_auth_enable = yes
smtpd_sasl_security_options = noanonymous
smtpd_sasl_local_domain = $myhostname
broken_sasl_auth_clients = yes
smtpd_recipient_restrictions =
   permit_sasl_authenticated,
   permit_mynetworks,
   reject_unauth_destination
   reject_invalid_hostname,
   reject_non_fqdn_hostname,
   reject_non_fqdn_sender,
   reject_non_fqdn_recipient,
   reject_unknown_sender_domain,
   reject_unknown_recipient_domain,
   reject_unauth_pipelining,
   permit_mynetworks,
   reject_rbl_client zen.spamhaus.org,
   reject_rbl_client opm.blitzed.org,
   reject_rbl_client list.dsbl.org,
   reject_rbl_client sbl.spamhaus.org,
   permit
----------------------------------------------------------------------
After this on the command line as root run command below
postfix reload
service cyrus-imapd restart
service saslauthd restart

let me know how you get on and if any problems  check your log files and post
so we can look at them all should be ok.

all the best
Darre

Darren,
thanks for this post and the instructions, please keep up the help.  I have followed what you said and  here is the results.

when i click on virtualmin virtual servers in the servers tab it states:

Virtualmin's configuration has not been checked since it was last updated. Click the button below to verify it now.

when i click on recheck and refresh configuration i get:

Checking Configuration       
The status of your system is being checked to ensure that all enabled features are available, that the mail server is properly configured, and that quotas are active ..

      BIND DNS server is installed.

      Mail server Postfix is installed and configured.

      Apache is installed.

      Webalizer is installed.

      MySQL does not appear to be installed and running on your system, or has not yet been set up properly in Webmin's MySQL Database module. If your system does not use MySQL, it should be disabled in Virtualmin's module configuration page.

.. your system is not ready for use by Virtualmin.



/var/log/maillog:

Feb  6 14:35:52 mail3 master[10073]: process started
Feb  6 14:35:52 mail3 master[10076]: about to exec /usr/lib/cyrus-imapd/ctl_cyrusdb
Feb  6 14:35:52 mail3 ctl_cyrusdb[10076]: recovering cyrus databases
Feb  6 14:35:52 mail3 ctl_cyrusdb[10076]: done recovering cyrus databases
Feb  6 14:35:52 mail3 master[10077]: about to exec /usr/lib/cyrus-imapd/idled
Feb  6 14:35:52 mail3 master[10073]: ready for work
Feb  6 14:35:52 mail3 master[10079]: about to exec /usr/lib/cyrus-imapd/ctl_cyrusdb
Feb  6 14:35:52 mail3 ctl_cyrusdb[10079]: checkpointing cyrus databases
Feb  6 14:35:52 mail3 ctl_cyrusdb[10079]: archiving database file: /var/lib/imap/annotations.db
Feb  6 14:35:52 mail3 master[10080]: about to exec /usr/lib/cyrus-imapd/imapd
Feb  6 14:35:52 mail3 master[10081]: about to exec /usr/lib/cyrus-imapd/imapd
Feb  6 14:35:52 mail3 master[10082]: about to exec /usr/lib/cyrus-imapd/pop3d
Feb  6 14:35:52 mail3 master[10083]: about to exec /usr/lib/cyrus-imapd/pop3d
Feb  6 14:35:52 mail3 master[10084]: about to exec /usr/lib/cyrus-imapd/lmtpd
Feb  6 14:35:52 mail3 master[10085]: about to exec /usr/lib/cyrus-imapd/imapd
Feb  6 14:35:52 mail3 master[10086]: about to exec /usr/lib/cyrus-imapd/imapd
Feb  6 14:35:52 mail3 ctl_cyrusdb[10079]: archiving log file: /var/lib/imap/db/log.0000000001
Feb  6 14:35:52 mail3 master[10087]: about to exec /usr/lib/cyrus-imapd/pop3d
Feb  6 14:35:52 mail3 master[10088]: about to exec /usr/lib/cyrus-imapd/pop3d
Feb  6 14:35:53 mail3 pop3[10082]: executed
Feb  6 14:35:53 mail3 pop3s[10083]: executed
Feb  6 14:35:53 mail3 pop3[10087]: executed
Feb  6 14:35:53 mail3 pop3s[10088]: executed
Feb  6 14:35:53 mail3 imap[10080]: executed
Feb  6 14:35:53 mail3 imaps[10081]: executed
Feb  6 14:35:53 mail3 imaps[10086]: executed
Feb  6 14:35:53 mail3 imap[10085]: executed
Feb  6 14:35:53 mail3 ctl_cyrusdb[10079]: archiving database file: /var/lib/imap/mailboxes.db
Feb  6 14:35:53 mail3 ctl_cyrusdb[10079]: archiving log file: /var/lib/imap/db/log.0000000001
Feb  6 14:35:53 mail3 ctl_cyrusdb[10079]: done checkpointing cyrus databases
Feb  6 14:35:53 mail3 master[10073]: process 10079 exited, status 0
Feb  6 14:35:53 mail3 master[10089]: about to exec /usr/lib/cyrus-imapd/imapd
Feb  6 14:35:53 mail3 imap[10089]: executed
Feb  6 14:35:53 mail3 master[10090]: about to exec /usr/lib/cyrus-imapd/pop3d
Feb  6 14:35:53 mail3 master[10091]: about to exec /usr/lib/cyrus-imapd/imapd
Feb  6 14:35:53 mail3 lmtpunix[10084]: executed
Feb  6 14:35:53 mail3 master[10092]: about to exec /usr/lib/cyrus-imapd/pop3d
Feb  6 14:35:53 mail3 pop3[10090]: executed
Feb  6 14:35:53 mail3 imap[10091]: executed
Feb  6 14:35:53 mail3 pop3[10092]: executed
Feb  6 14:35:55 mail3 master[10093]: about to exec /usr/lib/cyrus-imapd/imapd
Feb  6 14:35:55 mail3 imap[10093]: executed
Feb  6 14:35:55 mail3 master[10094]: about to exec /usr/lib/cyrus-imapd/imapd
Feb  6 14:35:55 mail3 master[10095]: about to exec /usr/lib/cyrus-imapd/imapd
Feb  6 14:35:55 mail3 imap[10095]: executed
Feb  6 14:35:55 mail3 master[10096]: about to exec /usr/lib/cyrus-imapd/pop3d
Feb  6 14:35:55 mail3 imap[10094]: executed
Feb  6 14:35:55 mail3 master[10097]: about to exec /usr/lib/cyrus-imapd/imapd
Feb  6 14:35:55 mail3 master[10098]: about to exec /usr/lib/cyrus-imapd/imapd
Feb  6 14:35:55 mail3 imap[10098]: executed
Feb  6 14:35:55 mail3 master[10099]: about to exec /usr/lib/cyrus-imapd/imapd
Feb  6 14:35:55 mail3 master[10100]: about to exec /usr/lib/cyrus-imapd/pop3d
Feb  6 14:35:55 mail3 pop3[10100]: executed
Feb  6 14:35:55 mail3 imap[10099]: executed
Feb  6 14:35:55 mail3 pop3[10096]: executed
Feb  6 14:35:55 mail3 imap[10097]: executed
Feb  6 14:35:55 mail3 master[10104]: about to exec /usr/lib/cyrus-imapd/imapd
Feb  6 14:35:55 mail3 imap[10085]: accepted connection
Feb  6 14:35:55 mail3 imap[10104]: executed
Feb  6 14:35:55 mail3 imap[10085]: badlogin: localhost.localdomain [127.0.0.1] plaintext cyrus SASL(-1): generic failure: checkpass failed
Feb  6 14:36:13 mail3 master[10114]: about to exec /usr/lib/cyrus-imapd/pop3d
Feb  6 14:36:13 mail3 pop3[10087]: accepted connection
Feb  6 14:36:13 mail3 pop3[10114]: executed
Feb  6 14:36:15 mail3 master[10073]: process 10087 exited, status 0
Feb  6 14:36:58 mail3 master[10073]: process 10085 exited, status 0
Feb  6 14:37:17 mail3 pop3[10092]: accepted connection
Feb  6 14:37:17 mail3 master[10148]: about to exec /usr/lib/cyrus-imapd/pop3d
Feb  6 14:37:17 mail3 pop3[10148]: executed
Feb  6 14:37:19 mail3 master[10073]: process 10092 exited, status 0
Feb  6 14:38:23 mail3 pop3[10100]: accepted connection
Feb  6 14:38:23 mail3 master[10286]: about to exec /usr/lib/cyrus-imapd/pop3d
Feb  6 14:38:23 mail3 pop3[10286]: executed
Feb  6 14:38:25 mail3 master[10073]: process 10100 exited, status 0
Feb  6 14:39:27 mail3 pop3[10114]: accepted connection
Feb  6 14:39:27 mail3 master[10368]: about to exec /usr/lib/cyrus-imapd/pop3d
Feb  6 14:39:27 mail3 pop3[10368]: executed
Feb  6 14:39:29 mail3 master[10073]: process 10114 exited, status 0
Feb  6 14:39:39 mail3 imap[10091]: accepted connection
Feb  6 14:39:39 mail3 master[10383]: about to exec /usr/lib/cyrus-imapd/imapd
Feb  6 14:39:39 mail3 imap[10383]: executed
Feb  6 14:39:39 mail3 imap[10091]: badlogin: localhost.localdomain [127.0.0.1] plaintext cyrus SASL(-1): generic failure: checkpass failed
Feb  6 14:40:31 mail3 pop3[10148]: accepted connection
Feb  6 14:40:31 mail3 master[10398]: about to exec /usr/lib/cyrus-imapd/pop3d
Feb  6 14:40:31 mail3 pop3[10398]: executed
Feb  6 14:40:33 mail3 master[10073]: process 10148 exited, status 0
Feb  6 14:40:42 mail3 master[10073]: process 10091 exited, status 0
Feb  6 14:41:35 mail3 pop3[10286]: accepted connection
Feb  6 14:41:35 mail3 master[10468]: about to exec /usr/lib/cyrus-imapd/pop3d
Feb  6 14:41:35 mail3 pop3[10468]: executed
Feb  6 14:41:37 mail3 master[10073]: process 10286 exited, status 0
Feb  6 14:42:39 mail3 pop3[10368]: accepted connection
Feb  6 14:42:39 mail3 master[10476]: about to exec /usr/lib/cyrus-imapd/pop3d
Feb  6 14:42:39 mail3 pop3[10476]: executed
Feb  6 14:42:41 mail3 master[10073]: process 10368 exited, status 0
Feb  6 14:43:43 mail3 pop3[10398]: accepted connection
Feb  6 14:43:43 mail3 master[10484]: about to exec /usr/lib/cyrus-imapd/pop3d
Feb  6 14:43:43 mail3 pop3[10484]: executed
Feb  6 14:43:45 mail3 master[10073]: process 10398 exited, status 0
Feb  6 14:44:47 mail3 pop3[10468]: accepted connection
Feb  6 14:44:47 mail3 master[10500]: about to exec /usr/lib/cyrus-imapd/pop3d
Feb  6 14:44:47 mail3 pop3[10500]: executed
Feb  6 14:44:49 mail3 master[10073]: process 10468 exited, status 0
Feb  6 14:45:51 mail3 pop3[10476]: accepted connection
Feb  6 14:45:51 mail3 master[10509]: about to exec /usr/lib/cyrus-imapd/pop3d
Feb  6 14:45:51 mail3 pop3[10509]: executed
Feb  6 14:45:53 mail3 master[10073]: process 10476 exited, status 0
Feb  6 14:46:55 mail3 pop3[10484]: accepted connection
Feb  6 14:46:55 mail3 master[10516]: about to exec /usr/lib/cyrus-imapd/pop3d
Feb  6 14:46:55 mail3 pop3[10516]: executed
Feb  6 14:46:57 mail3 master[10073]: process 10484 exited, status 0
Feb  6 14:47:59 mail3 pop3[10500]: accepted connection
Feb  6 14:47:59 mail3 master[10524]: about to exec /usr/lib/cyrus-imapd/pop3d
Feb  6 14:47:59 mail3 pop3[10524]: executed
Feb  6 14:48:01 mail3 master[10073]: process 10500 exited, status 0
Feb  6 14:49:03 mail3 pop3[10509]: accepted connection
Feb  6 14:49:03 mail3 master[10536]: about to exec /usr/lib/cyrus-imapd/pop3d
Feb  6 14:49:03 mail3 pop3[10536]: executed
Feb  6 14:49:05 mail3 master[10073]: process 10509 exited, status 0
Feb  6 14:50:07 mail3 pop3[10516]: accepted connection
Feb  6 14:50:07 mail3 master[10541]: about to exec /usr/lib/cyrus-imapd/pop3d
Feb  6 14:50:07 mail3 pop3[10541]: executed
Feb  6 14:50:09 mail3 master[10073]: process 10516 exited, status 0
Feb  6 14:50:48 mail3 postfix/postfix-script: refreshing the Postfix mail system
Feb  6 14:50:49 mail3 postfix/master[1881]: reload configuration /etc/postfix
Feb  6 14:51:07 mail3 master[10073]: exiting on SIGTERM/SIGINT
Feb  6 14:51:07 mail3 master[10629]: process started
Feb  6 14:51:07 mail3 master[10630]: about to exec /usr/lib/cyrus-imapd/ctl_cyrusdb
Feb  6 14:51:07 mail3 ctl_cyrusdb[10630]: recovering cyrus databases
Feb  6 14:51:07 mail3 ctl_cyrusdb[10630]: skiplist: recovered /var/lib/imap/mailboxes.db (0 records, 144 bytes) in 0 seconds
Feb  6 14:51:07 mail3 ctl_cyrusdb[10630]: skiplist: recovered /var/lib/imap/annotations.db (0 records, 144 bytes) in 0 seconds
Feb  6 14:51:07 mail3 ctl_cyrusdb[10630]: done recovering cyrus databases
Feb  6 14:51:07 mail3 master[10632]: about to exec /usr/lib/cyrus-imapd/idled
Feb  6 14:51:07 mail3 master[10629]: ready for work
Feb  6 14:51:07 mail3 master[10634]: about to exec /usr/lib/cyrus-imapd/ctl_cyrusdb
Feb  6 14:51:07 mail3 ctl_cyrusdb[10634]: checkpointing cyrus databases
Feb  6 14:51:07 mail3 ctl_cyrusdb[10634]: archiving database file: /var/lib/imap/annotations.db
Feb  6 14:51:07 mail3 master[10635]: about to exec /usr/lib/cyrus-imapd/imapd
Feb  6 14:51:07 mail3 imap[10635]: executed
Feb  6 14:51:07 mail3 master[10636]: about to exec /usr/lib/cyrus-imapd/imapd
Feb  6 14:51:07 mail3 imaps[10636]: executed
Feb  6 14:51:07 mail3 master[10637]: about to exec /usr/lib/cyrus-imapd/pop3d
Feb  6 14:51:07 mail3 ctl_cyrusdb[10634]: archiving log file: /var/lib/imap/db/log.0000000001
Feb  6 14:51:07 mail3 pop3[10637]: executed
Feb  6 14:51:08 mail3 master[10638]: about to exec /usr/lib/cyrus-imapd/pop3d
Feb  6 14:51:08 mail3 master[10639]: about to exec /usr/lib/cyrus-imapd/lmtpd
Feb  6 14:51:08 mail3 lmtpunix[10639]: executed
Feb  6 14:51:08 mail3 master[10640]: about to exec /usr/lib/cyrus-imapd/imapd
Feb  6 14:51:08 mail3 imap[10640]: executed
Feb  6 14:51:08 mail3 master[10641]: about to exec /usr/lib/cyrus-imapd/imapd
Feb  6 14:51:08 mail3 imaps[10641]: executed
Feb  6 14:51:08 mail3 master[10642]: about to exec /usr/lib/cyrus-imapd/pop3d
Feb  6 14:51:08 mail3 pop3s[10638]: executed
Feb  6 14:51:08 mail3 pop3[10642]: executed
Feb  6 14:51:08 mail3 master[10643]: about to exec /usr/lib/cyrus-imapd/pop3d
Feb  6 14:51:08 mail3 ctl_cyrusdb[10634]: archiving database file: /var/lib/imap/mailboxes.db
Feb  6 14:51:08 mail3 pop3s[10643]: executed
Feb  6 14:51:08 mail3 ctl_cyrusdb[10634]: archiving log file: /var/lib/imap/db/log.0000000001
Feb  6 14:51:08 mail3 ctl_cyrusdb[10634]: done checkpointing cyrus databases
Feb  6 14:51:08 mail3 master[10629]: process 10634 exited, status 0
Feb  6 14:51:08 mail3 master[10644]: about to exec /usr/lib/cyrus-imapd/imapd
Feb  6 14:51:08 mail3 imap[10644]: executed
Feb  6 14:51:08 mail3 master[10645]: about to exec /usr/lib/cyrus-imapd/pop3d
Feb  6 14:51:08 mail3 pop3[10645]: executed
Feb  6 14:51:08 mail3 master[10646]: about to exec /usr/lib/cyrus-imapd/imapd
Feb  6 14:51:08 mail3 imap[10646]: executed
Feb  6 14:51:08 mail3 master[10647]: about to exec /usr/lib/cyrus-imapd/pop3d
Feb  6 14:51:08 mail3 pop3[10647]: executed
Feb  6 14:51:10 mail3 master[10648]: about to exec /usr/lib/cyrus-imapd/imapd
Feb  6 14:51:10 mail3 master[10649]: about to exec /usr/lib/cyrus-imapd/imapd
Feb  6 14:51:10 mail3 imap[10649]: executed
Feb  6 14:51:10 mail3 master[10650]: about to exec /usr/lib/cyrus-imapd/imapd
Feb  6 14:51:10 mail3 master[10651]: about to exec /usr/lib/cyrus-imapd/pop3d
Feb  6 14:51:10 mail3 pop3[10651]: executed
Feb  6 14:51:10 mail3 master[10652]: about to exec /usr/lib/cyrus-imapd/imapd
Feb  6 14:51:10 mail3 imap[10650]: executed
Feb  6 14:51:10 mail3 master[10653]: about to exec /usr/lib/cyrus-imapd/imapd
Feb  6 14:51:10 mail3 master[10654]: about to exec /usr/lib/cyrus-imapd/imapd
Feb  6 14:51:10 mail3 imap[10654]: executed
Feb  6 14:51:10 mail3 master[10655]: about to exec /usr/lib/cyrus-imapd/pop3d
Feb  6 14:51:10 mail3 pop3[10655]: executed
Feb  6 14:51:10 mail3 imap[10648]: executed
Feb  6 14:51:10 mail3 imap[10652]: executed
Feb  6 14:51:10 mail3 imap[10653]: executed
Feb  6 14:51:11 mail3 pop3[10642]: accepted connection
Feb  6 14:51:11 mail3 master[10656]: about to exec /usr/lib/cyrus-imapd/pop3d
Feb  6 14:51:11 mail3 pop3[10656]: executed
Feb  6 14:51:13 mail3 master[10629]: process 10642 exited, status 0
Feb  6 14:52:15 mail3 pop3[10655]: accepted connection
Feb  6 14:52:15 mail3 master[10680]: about to exec /usr/lib/cyrus-imapd/pop3d
Feb  6 14:52:15 mail3 pop3[10680]: executed
Feb  6 14:52:17 mail3 master[10629]: process 10655 exited, status 0
Feb  6 14:53:19 mail3 pop3[10647]: accepted connection
Feb  6 14:53:19 mail3 master[10686]: about to exec /usr/lib/cyrus-imapd/pop3d
Feb  6 14:53:19 mail3 pop3[10686]: executed
Feb  6 14:53:21 mail3 master[10629]: process 10647 exited, status 0
Feb  6 14:54:26 mail3 pop3[10656]: accepted connection
Feb  6 14:54:26 mail3 master[10705]: about to exec /usr/lib/cyrus-imapd/pop3d
Feb  6 14:54:26 mail3 pop3[10705]: executed
Feb  6 14:54:28 mail3 master[10629]: process 10656 exited, status 0

what other log files and posts do we need to check now?

Dennis

"Then yon need to open up port 143 imap port on iptables."

Note that this is the IMAP port.  If you don't want to provide IMAP access to clients, only allow port 110 (POP).

i have gone into lokkit and added    143:IMAP

I think i would prefer to only offer POP though.

Yes, although the cyrus-imapd name implies it's an IMAP server, it does serve POP3 as well, so if you want it to only act as a POP3 server you should be able to disable IMAP in the config, using webmin, and only have POP enabled, which means you'd also want to go back in lokkit and turn off IMAP port.

Hi
the only reason is enabling 143 is for webmin imap admin to connect to cyrus thats all your mail users will be getting mail via the pop server not imap server.

Sorry for the delay but i was out and about i home now Have you verified all is working just enter command below
service cyrus-imapd status

make sure it rebuilds db file ok this should need no user input.
Your log files look ok to me seem cyrus is up and running.

Give some information on how far you have got also we need to create some Mail Aliases  and some mail box users to make sure every thing is handed over ok with webmin. We will complete this with webmin to control virtual websites and mail account for those websites.

As for checking usermin defaults we need to know what your server will be offering do you run MYSQL Database server for your clients?
If no disable mysql under configuration section usermin.

Enabled features for servers and select disable MYSQL set to No

We need to set user shell access under usermin configuration as below:
Defaults for new domains
Shell for mailbox users   = /dev/null
Shell for FTP users   =      /sbin/nologin
Shell for server Unix users  = /bin/sh

the click save and re check configuration this should be ready for usermin.

Then click on Server Templates  icon and need to make some small changes there
Under Default Settings template link click it and then click on drop down box and select mail for domain
navigate to Format for usernames that include domain and select
username-domain click save. the reason for doing this way i found that cyrus was picky sometimes when using username.domain as mail box structure under cyrus seperates them with a dot there is setting you can use for this for cyrus to seperate box with / but its not a big deal just to change users.

Once completed then go to usermin and create a domain
mydomin.com to just enter in domain name without the www and choose password etc I am sure you know this bit let usermin create the new domain.
if all is ok all services enabled uder usermin configuration should be configured and restarted by usermin. now lets check every thing is in the right place.

Do with have ne domain under apache ?
Do with have DNS entry in Bind ?
Do with have MYSQL Database ? (If Enabled)
Do with have domains and alias in virtual user table ?
Click on cyrus imap admin  do with have mailbox created for domain ?

I don't know if you have static IP address or registered domain name we need this so we can test mail from the outside world and the we can setup two account on outlook and to see if we can relay and get mail all ok.

Thats it for now do your checks and postback to me if all is ok then we can do how final checks and see if server is getting  external mail.

Bye for now
Darren

Darren,
I have completed everything up to this comment, with the following results for this last comment:

[root@mail3 ~]# service cyrus-imapd status
cyrus-master (pid 10629) is running...

make sure it rebuilds db file ok this should need no user input.
--how do i know this? where do i look?

As for checking usermin defaults we need to know what your server will be offering do you run MYSQL Database server for your clients?
If no disable mysql under configuration section usermin.
this server will not do mysql.
i have gone into webmin
webmin  tab
usermin configuration  icon
i dont see where you are saying to disable it at.


Enabled features for servers and select disable MYSQL set to No

i got lost here.  can you be a little more specific?

darren,
i found the configuration page, you said  

if no disable mysql under configuration section usermin. you mean the below right?

Configuration       
For module Virtualmin Virtual Servers (GPL)
Configurable options for Virtualmin Virtual Servers (GPL)
Enabled features for servers
Home directory creation enabled?       Always    Optionally  
Unix user creation enabled?       Always    Optionally  
BIND setup and configuration enabled?       Yes    Yes, but not by default    No  
Mailbox and alias configuration enabled?       Yes    Yes, but not by default    No  
Apache setup and configuration enabled?       Yes    Yes, but not by default    No  
Webalizer report generation enabled?       Yes    Yes, but not by default    No  
SSL website setup enabled?       Yes    Yes, but not by default    No  
MySQL setup and configuration enabled?       Yes    Yes, but not by default    No  

you mean right here, set this to no?



where is :

Enabled features for servers and select disable MYSQL set to No

Hi
Sorry sometimes i don't explain myself sorry for that go to http://www.protoolsuk.co.uk/webmin/Virtualmin.jpg iI down screenshot for you.

Let me know if all is ok
Darren

Hi Knightdogs,

make sure it rebuilds db file ok this should need no user input.
--how do i know this? where do i look?

For this section above this will done every time you start cyrus server you don't have to do anything sometimes the cyrus server will not start because it can not rebuild db database but not often if this does happen to you in the future you can navigate to /var/lib/imap and copy or remove all *.db files from this directory and then restart cyrus and should then rebuild the database files again. Just an extra bit of info beacuse it does happen.

Darren

I selected no -----

i changed this---

We need to set user shell access under usermin configuration as below:
Defaults for new domains
Shell for mailbox users   = /dev/null
Shell for FTP users   =      /sbin/nologin
Shell for server Unix users  = /bin/sh


and then told it to recheck. this is what it said:

The status of your system is being checked to ensure that all enabled features are available, that the mail server is properly configured, and that quotas are active ..

      BIND DNS server is installed.

      Mail server Postfix is installed and configured.

      Apache is installed.

      Webalizer is installed.

      Logrotate is installed.

      Using network interface eth0 for virtual IPs.

      Default IP address for virtual servers is 192.168.100.70.

      Quotas are not enabled on the filesystem / which contains home directories under /home and email files under /var/spool/mail. Quota editing has been disabled.

      All commands needed to create and restore backups are installed.

.. your system is ready for use by Virtualmin.

Updating all Webmin users with new settings..
.. done

next i did this----

Then click on Server Templates  icon and need to make some small changes there
Under Default Settings template link click it and then click on drop down box and select mail for domain
navigate to Format for usernames that include domain and select
username-domain click save. the reason for doing this way i found that cyrus was picky sometimes when using username.domain as mail box structure under cyrus seperates them with a dot there is setting you can use for this for cyrus to seperate box with / but its not a big deal just to change users.

then i am here------

Once completed then go to usermin and create a domain
mydomin.com to just enter in domain name without the www and choose password etc I am sure you know this bit let usermin create the new domain.
if all is ok all services enabled uder usermin configuration should be configured and restarted by usermin. now lets check every thing is in the right place.

I dont see where you mean to creat the domain at. here is what mine looks like---

http://www.knightdog.biz/usermin.jpg

Dennis
i have used webmin for about 6 months now, and up till now have never used usermin. sorry.  please bear with me on the learning curve.  thanks.

Sorry Dennis

Not usermin I ment  Virtualmin Virtual Servers (GPL) my mistake thats my brain I think but fingers do a different think very sorry.

Here we want to create a new Virtual domain so we can check every think is in the right place. If I don't make sense just tell me and i will do a screenshot pics are sometimes better.

Darren

Darren,
i have done this and created the domain in virtualmin.

Hi

Lets now check postfix do we have  entries in virtual aliases table for the domain you just created.

Go to Cyrus IMAP Server icon under webmin servers and check to see if virtualmin has created mail box storage for the new domain.

Let me know the out come

yes the domain is there

We also have storage ?

Now lets see if we can send and recieve mail form the outside world go to dnsreport.com and do check on your host name to see if we can connect to your mail server also do email test at the same place user@yourdomain.com or an alias postmaster@domian.com to see if the mailbox is ok.

If all is ok now create a user for that domain IE: darren@yourhost.com create the new mail user under virtualmin.

Darren

I went there and ran this test with the following address

postmaster@abc.com

Trying to connect to all mailservers:

   mail.abc.com. - xxx.xxx.xxx.xxx  [Successful connect: Got a good response [250 Ok]] (took 2.562 seconds)

now i created an account     admin

and tried the test again

Trying to connect to all mailservers:

   mail.abc.com. - xxx.xxx.xxx.xxx  [Could not connect: Could not receive data: Operation timed out.]
  [Note that if your mailserver takes over 30 seconds to respond, our test will timeout, even though real mailservers will wait longer]

darren, if you shoot me an email at  dknight<at>atlanticmcc<dot>com  i will give you the name and ip.

Dennis