Postfix wiki

I'm trying to install postfix+webmail following the instructions in the arch wiki:
http://wiki.archlinux.org/index.php/PostFix_Howto
but at the step: Install Courier IMAP
pacman -Sy courier-imap courier-imap-mysql
fails with 'courier-imap-mysql: not found in sync db'
Anyone knows anything about that package?
Regards

courier-authlib provides courier-imap-mysql now (ran into the same problem myself.)
[root@raid marco]# pacman -Qi courier-authlib
Name : courier-authlib
Version : 0.58-2
Groups : None
Packager : Tobias Kieslich <tobias>
URL : http://courier-mta.org/authlib/
License : None
Architecture : i686
Size : 725617
Build Date : Mon Jan 23 22:20:47 2006 UTC
Install Date : Wed Mar 29 17:28:20 2006 UTC
Install Script : Yes
Reason: : installed as a dependency for another package
Provides : courier-imap-ldap courier-imap-mysql courier-imap-pgsql
Depends On : db>=4.3 libtool openssl perl
Required By : courier-imap
Conflicts With : courier-imap-ldap courier-imap-mysql courier-imap-pgsql
Description : Authentification library for the courier mailserver(s)

Similar Messages

Complete newbie to postfix, some guidance?

What I'm aiming for is a mailserver that will allow me to send/receive mail both locally and through the Internet. I will be ending my hosting with my provider (money issues) and need to transfer all my existing stuff to my home box, with DynDNS giving me a hostname to cover my dynamic IP. I plan on routing my existing domain name to the DynDNS hostname, since they offer dynamic IP services. So the actual route will be sporkbox.us -> sporkbox.ath.cx -> my dynamic IP. Convoluted? Yes. Optimum? No. The only way for this to work? As far as I know, yes.
I've looked around at a few guides but it's all very complicated. If there are any good resources out there that make understanding feasible, please link me to them. I've searched this forum but didn't find anything very helpful.
I have no idea where to begin to fix this up, since currently the mailserver is... odd.
http://codepad.org/WAOfJbFJ <--- /etc/postfix/main.cf
http://codepad.org/hf3tZ3Zv <--- ~/.mutt/muttrc
Any hope for the clueless?

Yes, most guides assume you'll be installing procmail+spamassasin+squirrel+courier-imap+...
Anyway, these are the few straightforward guides I've found:
* For setting up a ssl encrypted connection to a relay (say, sending email through google) - http://ubuntu-tutorials.com/2008/11/11/ … tpgmailcom
* Couple that with the local mail host delivery article - [wiki]Local Mail Delivery with Postfix[/wiki].
After you have a local setup, read on the guides I've linked below, but only pay attention to fetchmail and redirections based on local/foreign recipient and maps; e.g., [email protected] -> [email protected]
Once you have postfix+fetchmail, you'll probably want to enhance the setup with at least with procmail to divide your mail into various maildirs. If you rather not run postfix + procmail, look into exim. But remember, you do not need anything else to have a mail setup. Postfix + fetchmail are the bare basics!
Nice advanced guides that happen to include fetchmail setup:
http://www.hypexr.org/linux_mail_server.php (this one is done by an arch user and he's alsu using dyndns)
http://www.syntheticzero.com/howto/vmail.php
http://freshmeat.net/articles/gmail-on- … -fetchmail
A few things while reading these:
* the archlinux postfix package has sasl, no need to recompile
* using cat /certfile.crt > /etc/postfix/cert.pem is unnecessary:
smtp_tls_CAfile = /usr/share/ca-certificates/mozilla/Equifax_Secure_CA.crt
*you do not need .forward files in root or anyone's $HOME, just write this in
the aliases file:
root: andresp

Sending email from the shell

I'd like to send trivial emails to my external email addy via POP3 (just text, no attachments) from the shell. Is postfix my best bet? Is there something lighter? The postfix wiki page seems rather involved for what I want to do.
Thanks for the suggestions!
EDIT: Found sendEmail which is pretty nice. Other suggestions are still welcomed!
Last edited by graysky (2010-05-27 19:50:31)

Install msmtp and make a basic config file in ~/.msmtprc, for example:
account gmail
host smtp.gmail.com
port 587
protocol smtp
auth on
from [email protected]
user [email protected]
password password
tls on
tls_starttls on
tls_trust_file /usr/share/ca-certificates/mozilla/Equifax_Secure_CA.crt
account default : gmail
Make sure no one else can read or write to that file ('chmod 600 ~/.msmtprc'). Then double-check that mailx is installed (it's in base) and add the following line to ~/.mailrc:
set sendmail="/usr/bin/msmtp"
Everythings all set up! Now just pipe your message to mailx, like karol mentioned earlier:
$ echo "message" | mail -s subject [email protected]
Last edited by fflarex (2010-05-27 22:48:49)

[SOLVED]Issue with Postfix sending to external mail addresses

I'm having a very silly issue with Postfix. I followed the wiki article at [link]https://wiki.archlinux.org/index.php/Postfix[/link], and everything seems to work properly, however I cannot send to emails outside of my domain.
I get the error:
550 5.1.1 <[email protected]>: Recipient address rejected: Local delivery only!
Here is what the logs say:
May 08 16:05:12 my.dns.stuff.org postfix/smtpd[31464]: connect from localhost.localdomain[127.0.0.1]
May 08 16:05:12 my.dns.stuff.org postfix/smtpd[31464]: 091E011E3C: client=localhost.localdomain[127.0.0.1]
May 08 16:05:12 my.dns.stuff.org postfix/smtpd[31464]: 091E011E3C: reject: RCPT from localhost.localdomain[127.0.0.1]: 550 5.1.1 <[email protected]>: Recipient address rejected: Local delivery only!; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<sendingdomain.com>
May 08 16:05:12 my.dns.stuff.org postfix/smtpd[31464]: lost connection after RCPT from localhost.localdomain[127.0.0.1]
May 08 16:05:12 my.dns.stuff.org postfix/smtpd[31464]: disconnect from localhost.localdomain[127.0.0.1]
May 08 16:05:14 my.dns.stuff.org sudo[31476]: me : TTY=pts/0 ; PWD=/etc/postfix ; USER=root ; COMMAND=/usr/bin/journalctl
main.cf
# 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/BASIC_CONFIGURATION_README.html etc.
# 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/bin
# 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/lib/postfix
# The data_directory parameter specifies the location of Postfix-writable
# data files (caches, random numbers). This directory must be owned
# by the mail_owner account (see below).
data_directory = /var/lib/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 = mail.sendingdomain.com
# 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 = www.sendingdomain.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
# [email protected].
# 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
append_dot_mydomain = no
# 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 = loopback-only
#inet_interfaces = $myhostname
#inet_interfaces = $myhostname, 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
#mydestination = localhost
# 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 [email protected] 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]
default_transport = error: Local delivery only!
# 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 [email protected] 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 = hash:/etc/postfix/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
alias_database = $alias_maps
# 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".
# Cyrus IMAP over LMTP. Specify ``lmtpunix cmd="lmtpd"
# listen="/var/imap/socket/lmtp" prefork=0'' in cyrus.conf.
#mailbox_transport = lmtp:unix:/var/imap/socket/lmtp
# Cyrus IMAP via command line. Uncomment the "cyrus...pipe" and
# subsequent line in master.cf.
#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 = [email protected]
#luser_relay = [email protected]
#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
ddd $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/bin/sendmail
# 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
# mailq_path: The full pathname of the Postfix mailq command. This
# is the Sendmail-compatible mail queue listing command.
mailq_path = /usr/bin/mailq
# 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 = /etc/postfix/sample
# readme_directory: The location of the Postfix README files.
readme_directory = /usr/share/doc/postfix
inet_protocols = ipv4
#virtual_mailbox_domains = sendingdomain.com
virtual_alias_maps = hash:/etc/postfix/virtual_alias, mysql:/etc/postfix/mysql_virtual_forwards.cf
virtual_mailbox_domains = mysql:/etc/postfix/mysql_virtual_domains.cf
virtual_mailbox_maps = mysql:/etc/postfix/mysql_virtual_mailboxes.cf
virtual_mailbox_base = /home/vmailer
virtual_uid_maps = static:5003
virtual_gid_maps = static:5003
virtual_minimum_uid = 5003
virtual_mailbox_limit = 51200000
Any help would be appreciated. Thank you.
Last edited by nadman10 (2014-05-14 14:36:10)

Your main.cf seems redundant.
For example:
if you specify:
virtual_alias_maps = hash:/etc/postfix/virtual_alias, mysql:/etc/postfix/mysql_virtual_forwards.cf
you don't need this:
alias_maps = hash:/etc/postfix/aliases
and i think you have a lot of more options you don't need.
This is my main.cf on my vps and everything works great (sending and receiving emails from/to most common mail server: gmail, hotmail etc etc)
smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
biff = no
# appending .domain is the MUA's job.
append_dot_mydomain = no
readme_directory = no
# TLS parameters
smtpd_tls_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem
smtpd_tls_key_file=/etc/ssl/private/ssl-cert-snakeoil.key
smtpd_use_tls=yes
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
message_size_limit = 4194304
virtual_mailbox_domains = mysql:/etc/postfix/mysql-virtual-mailbox-domains.cf
virtual_mailbox_maps = mysql:/etc/postfix/mysql-virtual-mailbox-maps.cf
virtual_alias_maps = mysql:/etc/postfix/mysql-virtual-alias-maps.cf
virtual_transport = dovecot
dovecot_destination_recipient_limit = 1
it is very simple (no dkim, no forced tls, no mailbox limits and so on) and it can be improved but it works..
as I suggested you just try spending some hour wiping postfix installation and giving a look to this guide

HT5697 How do i configure os x server wiki to use the external web server?

I have a Mac mini Server with OS X 10.10 and Server 4.0 running in a DMZ behind a firewall. The firewall passes a select few ports through to this server, exposing services to the Internet.
I use two domains, one dummy domain only available on my local networks, and one proper domain available globally. Lets call them «example.lan» and «example.com». These domains are not hosted on the Mac mini, btw.
In the external domain, I have «server.example.com» registered on my firewalls official IP address.
In my internal domain, I have «server.example.lan» registered to my Mac mini internal (rfc1918) IP address.
Server 4.0 -> Websites seem to work as expected. I have three servers configured: «Server Website - All IP addresses», port 80 + 443. These serve the local networks. Then there is «server.example.com», port 443, serving the internet.
Now to my question: How to I control which of these websites we Wiki uses?
When I activate the Wiki, it is published on «server.example.lan/wiki», which seems rather pointless. In order for the wiki to be available to the internet, it needs to be published on «server.example.com/wiki», but I see no way of doing this. What am I missing here?
Regards,
Gakke

it does look like you can add virtual domains in the GUI of Server.app on at least some versions, but I don't have an OS X Server 10.8 version handy to check.
I'd encourage spending some time to learn the command line. In general, the payoff for learning the command line will be worth the effort expended. You're running a mail server here and sooner or later the capabilities of the GUI will fail you. This whether due to a configuration omission in the GUI itself, or due to the need to troubleshoot a malfunctioning mail server, a need to automate one or more of the Postfix-related sequences, or some other IT-related task. Entirely FWIW, of course.
Here's a cut-and-paste of the sequence just used to test the command line access to the Postfix configuration, first fetching the current value, appending example.com as the second domain, then displaying the new value, then restarting the Postfix server. Don't enter the dollar signs; just the postconf command and following. Adjust example.com to match your domain...
$ postconf mydestination
mydestination = $myhostname, localhost.$mydomain, localhost
$ sudo postconf -e 'mydestination = $myhostname, localhost.$mydomain, localhost, example.com'
Password: {your admin password here}
$ postconf mydestination
mydestination = $myhostname, localhost.$mydomain, localhost, example.com
$ sudo postfix reload
The Postfix and Postconf commands work irrespective of the OS X Server version; the tools reference the data files as needed.

How to add text to the start of the subject for email sent to wiki mail

When an email is sent to the group wiki email address (groupname-wiki@serverurl), I would like for the subject of the email to have \[groupname-wiki\] added to the beginning of the text. Can anyone suggest to me how to do this? What configuration file do I need to be looking at?
Thank you.
Message was edited by: Ixitar
Message was edited by: Ixitar

This sort of thing can be done with procmail which is included with the SLS. However, the section for these aliases in /etc/aliases is auto-generated, and it gets reset if you mess with it. I think it's not possible to change it directly.
What you could do, though, is leave the auto-generated stuff alone, and ignore the main address of the mailing list, and put your own alias in first, that rewrites the subject line before forwarding to the main wiki alias. Then tell people to use the list that you want to have them use.
For example, two lines in /etc/aliases that you'd use:
================
acmegroup: "| /usr/bin/procmail -m /opt/postfix/procmail-tag.rc {acmegroup} acmegroup-wiki"
### DO NOT MANUALLY EDIT THIS SECTION ###
# This section is automatically generated
acmegroup-wiki: , teamsserver@localhost, [email protected]
================
You need to learn how to write procmail code, but for this example, the tag.rc file you'd save in /opt/postfix looks like:
http://assets.cogley.info/procmail-tag.rc

[SOLVED] Help needed to configure postfix

I aim to be able to manage myself my mailserver.
For now i just need help in order to configure postfix so i can send an email from my postfix configured mail to my gmail account.
I've read the following wiki pages :
https://wiki.archlinux.org/index.php/postfix
https://wiki.archlinux.org/index.php/Si … ail_System
Wich are really not informative.
I've my own domain name, wich can be pinged, i will call it : domain.free.fr
Here is what i've done so far :
Install postfix :
sudo pacman -S postfix
Configure myhostname in /etc/postfix/main.cf
myhostname = domain.free.fr
Configure the username in /etc/postfix/aliases
root: glow
Reload aliases and postfix
newaliases
postfix reload
postfix status
postfix/postfix-script: the Postfix mail system is running: PID: 11706
Then i've tried to use sendmail to send an email to my gmail adress :
sendmail [email protected]
Test
Nothing coming in my mail.
What do i do wrong ?
Ican't find any log about postfix, /var/log/mail.log do not exist, is this normal ?
Last edited by GloW_on_dub (2014-03-31 15:45:54)

mailq
-Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient-------
CCD29FF253 262 Mon Mar 31 16:58:37 [email protected]
(delivery temporarily suspended: connect to alt4.gmail-smtp-in.l.google.com[74.125.25.27]:25: Connection timed out)
[email protected]
-- 0 Kbytes in 1 Request.
My mail is in the queue, but cannot be delivered
Last edited by GloW_on_dub (2014-03-31 15:03:51)

Mailman + Postfix - User unknown

Hi all, I'm having some trouble installing mailman (who doesn't?) right now.
I tried everything. I followed EXACTLY what is said on our wiki (https://wiki.archlinux.org/index.php/Mailman) but still it's not working.
Actually the only thing that is not working is 'sending an email to the mailing list'. And this is quite important for a mailing list, I guess.
After spending hours trying, here is my current status:
I created a mailing list called pynochio, with [email protected] as the mailing list address.
Postfix reads my /var/lib/mailman/data/virtual-mailman file and applies the mapping. I'm sure about that because I changed the content of virtual-mailman (and then hashed it using postmap command) and the email postfix was trying to authenticate changed. (so there is no permission issue from this side)
But then postfix concludes that the user doesn't exist. Here are fresh logs from journalctl, just for you:
Mar 20 19:59:53 ks3100290 postfix/qmgr[26527]: 128382077C: from=<[email protected]>, size=1775, nrcpt=2 (queue active)
Mar 20 19:59:53 ks3100290 postfix/trivial-rewrite[26562]: warning: do not list domain too.gy in BOTH mydestination and virtual_mailbox_domains
Mar 20 19:59:53 ks3100290 postfix/trivial-rewrite[26562]: warning: do not list domain too.gy in BOTH mydestination and virtual_mailbox_domains
Mar 20 19:59:53 ks3100290 postfix/virtual[26567]: 128382077C: to=<[email protected]>, relay=virtual, delay=0.74, delays=0.65/0.03/0/0.07, dsn=5.1.1, status=bounced (unknown user: "[email protected]")
Mar 20 19:59:53 ks3100290 postfix/virtual[26567]: 128382077C: to=<[email protected]>, relay=virtual, delay=0.78, delays=0.65/0.03/0/0.1, dsn=2.0.0, status=sent (delivered to maildir)
This warning appears because in the tutorial we are said to put `too.gy` (our domain) in mydestination and because in my postfix database inside the `domain` table, `too.gy` is said to be virtual (transport=virtual). I don't know if it should be that way.
My problem is that I don't really know how postfix and mailman are supposed to communicate. Postfix is supposed to let mailman handle things since [email protected] is a list address but it doesn't.
I read some tutorials (on other distribs) and they are using lists.too.gy domain for their lists address (it seems easier) but it looks like there's a better way to do it and in the archlinux mailman documentation, we are not using such subdomain for our lists. So I want to do it the right, archlinux way.
There is `postfix_to_mailman.py` transport script thing but I read it's a bad practice...
Here is the output of `postconf -n` (which respects the mailman tutorial, once again):
alias_database = $alias_maps
alias_maps = hash:/etc/postfix/aliases, hash:/var/lib/mailman/data/aliases
broken_sasl_auth_clients = yes
command_directory = /usr/bin
config_directory = /etc/postfix
daemon_directory = /usr/lib/postfix
data_directory = /var/lib/postfix
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
html_directory = no
inet_protocols = ipv4
local_recipient_maps = $alias_maps
local_transport = virtual
mail_owner = postfix
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
mydestination = localhost, too.gy
mydomain = too.gy
myhostname = mail.too.gy
mynetworks_style = host
myorigin = $mydomain
newaliases_path = /usr/bin/newaliases
queue_directory = /var/spool/postfix
readme_directory = /usr/share/doc/postfix
recipient_delimiter = +
relay_recipient_maps = hash:/var/lib/mailman/data/virtual-mailman
sample_directory = /etc/postfix/sample
sendmail_path = /usr/bin/sendmail
setgid_group = postdrop
smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination
smtpd_relay_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination
smtpd_sasl_auth_enable = yes
smtpd_sasl_local_domain = $mydomain
smtpd_sasl_path = /var/run/dovecot/auth-client
smtpd_sasl_security_options = noanonymous
smtpd_sasl_tls_security_options = $smtpd_sasl_security_options
smtpd_sasl_type = dovecot
smtpd_tls_auth_only = yes
smtpd_tls_cert_file = /etc/ssl/private/server.crt
smtpd_tls_key_file = /etc/ssl/private/server.key
smtpd_tls_loglevel = 1
transport_maps = hash:/etc/postfix/transport
unknown_local_recipient_reject_code = 550
virtual_alias_maps = hash:/etc/postfix/virtual, proxy:mysql:/etc/postfix/virtual_alias_maps.cf, hash:/var/lib/mailman/data/virtual-mailman
virtual_gid_maps = static:5000
virtual_mailbox_base = /home/vmail
virtual_mailbox_domains = proxy:mysql:/etc/postfix/virtual_domains_maps.cf
virtual_mailbox_limit = 512000000
virtual_mailbox_maps = proxy:mysql:/etc/postfix/virtual_mailbox_maps.cf
virtual_minimum_uid = 5000
virtual_transport = virtual
virtual_uid_maps = static:5000
Any help appreciated. I'm on it since 10 hours, I don't want to kill myself.
EDIT: Forgot my `/etc/mailman/mm_cfg.py` >
# -*- python -*-
from Defaults import *
DEFAULT_URL_HOST = 'lists.too.gy'
DEFAULT_EMAIL_HOST = 'too.gy'
MTA = 'Postfix'
VIRTUAL_HOSTS.clear()
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['too.gy']
DEFAULT_URL_PATTERN = 'http://%s/'
PUBLIC_ARCHIVE_URL = 'http://%(hostname)s/archives/%(listname)s'
MAILMAN_SITE_LIST = 'mailman'
Last edited by toogy (2014-03-20 19:23:23)

AlanNYC wrote:
If I turn off local recipient checking, will I actually get my mail?
Yes, all email properly addressed should be delivered to you without problems.
The line only affects improperly addressed email, in this case allowing them to be accepted instead of rejected.
Since you are running Spamassassin and an IMAP server, I suggest also using the line
luser=[email protected]
which will send all improperly addressed mail to the address specified by "[email protected]". This is what I meant by "catch-all" address.
If you find postfix giving you problems after adding the lines, simply delete them or comment them out by adding a hash mark to the front of the line, e.g.
#localrecipientmaps =
Alternatively, you can simply make no changes and allow the log messages to accumulate. The messages mean that postfix is doing its job by rejecting email addressed to users that don't exist. The above steps allow you to receive mail addressed to [email protected], where "anything" is any string allowed in an email address.
I assume you're testing your changes using a separate email account, but in case you're not: sign up for a free email account with any of a number of free email services (Gmail, Yahoo) and test your postfix install as you make changes using the free account.

WGM - Does it still write to postfix/aliases?

I've done a reinstall from scratch of OSX Server 10.5.5 with the latest updates.
My question is, when creating/modifying new groups in WGM, shouldn't it be writing to the /etc/postfix/aliases file? My previous installation wrote something like this to the aliases file.
groupshortname: [email protected], [email protected]
If this is still the case, perhaps my issue is one of permissions.
What are the permissions supposed to be on the aliases file?
Any other ideas why a new WGM created group, with a valid active email receiving user is not able to receive email to that group address?
Email sent to [email protected] from [email protected] (or my gmail account, etc) gets bounced.
groupshortname
services enabled for this group on: this-host
wiki and blog - checked
Web calendar - checked
Mailing list web archive - checked
Allow group members only to write to these services
Allow group members only to view these services
Any ideas or things to check most welcome. Thanks.

Nevermind. In typical Apple fashion they just started working.
The only thing I did was use the Directory.app to try to edit the group previously created in WGM. Now my postfix/aliases file has the proper entries.

ArchWiki and ArchServer wiki

Well, first a short introduction for thoses who don't know ArchServer yet. It is Arch Linux but less bleeding edge, more secure, and more stable (or at least we're trying to make it so ).
We have our own wiki : ArchServer Wiki
I would like to start a cross-thread discussion about the duplication of the documentation, a thing we're trying to avoid. The begining of the discussion can be found here : http://bbs.archserver.org/viewtopic.php?id=13
I believe most of the people behind ArchServer have an account here, it is probably easier to continue in this thread. I would like hear opinions about what should be in ArchServer Wiki, what should be in ArchWiki, since it's a matter that concerne both projects.

The two big ones I can think of are: Postfix and SELinux. Neither of these are exclusively for a server but are usually used as such. SELinux (and it's packages in the AUR) are being regularly maintained by Nicky. SELinux documentation is still just the basics but does cover all the important parts. Since I don't use Postfix I'm not sure of the state for the Postfix documentation.

Wiki Mailing lists

I am having a problems with wiki mailing lists, they were working fine for about six months then one day stopped the issue seems to be that the automatically generated list in Postfix is not finding the email addresses for the group.
All members of the group have email address showing up in the info tab of the WGM but still nothing seems to be generated.
If any one can add any insight I would be very grateful.

So do I. We upgraded from 10.5 to 10.6.4. We have been using 'Mailing-Lists for groups' under 10.5 for years, and everything was easy. After migrating to 10.6 the radio-button in Server-Admin still exists, but it is not working any more. Strategic decission to feature the wiki system, without telling loyal migrators?
So we changed using the wiki-mailing-list function. Worked fine (though no welcome-messages for new users showed up, as promised, but who cares...) until we restarted the server for the first time. Messages went still straight to the wiki-site, but would not be delivered to the users any more.
After spending a week with '/etc/postfix/aliases', the 'newaliases command' and other fun stuff I discovered, that turning off or on 'Mailman-Mailing-List' in Server-Admin/Mail/Mailing-Lists does the job of refreshing the the '/etc/postfix/aliases' file that seams to be responsible to sending the wiki-emails to the defined users of the wiki.
Tell me if that does the job for you as well!
And yes I am talking about Mailman-Mailing-Lists to be turned *off or on*, and not about the Group- Mailing-Lists.
Regards
Robert

SOHO postfix

I made my own mail server (SOHO Postfix, http://wiki.archlinux.org/index.php/SOHO_Postfix ) but I just cant log in to check mail.
Almost everything works fine, just logging doesnt work. I tried to log in through mozilla thunderbird, but it fails. Same as with squirrelmail.
From mail.log:
Jan 18 09:13:05 hell imapd-ssl: Connection, ip=[::ffff:xxx.xxx.xxx.xxx]
Jan 18 09:13:08 hell imapd-ssl: LOGIN FAILED, method=PLAIN, ip=[::ffff:xxx.xxx.xxx.xxx]
Jan 18 09:13:13 hell imapd-ssl: LOGIN FAILED, user=ryne, ip=[::ffff:xxx.xxx.xxx.xxx]
Jan 18 09:13:20 hell imapd-ssl: LOGOUT, ip=[::ffff:xxx.xxx.xxx.xxx], rcvd=96, sent=512
I even turned off my firewall, but still nothing.

Ryne wrote:
Yes, I know that login is [email protected]
I'm using Courier-IMAP.
When I had imapd-ssl squirrelmail dont wanna even connect to imapd (I tried also to change port (143->993) in squirrelmail's config), but when I changed it to normal imapd (not ssl) it works fine.
Not really sure then...
Double-check and see if there are typos.
If you are having problems with squirrelmail. Postfix is setup to deliver from localhost w/o auth so you can accept default squirrelmail SMTP setting fine.
SMTP Settings
4. SMTP Server : localhost
5. SMTP Port : 25
6. POP before SMTP : false
7. SMTP Authentication : none
8. Secure SMTP (TLS) : disabled
9. Header encryption key :
A. Update IMAP Settings : localhost:993 (courier)
Last edited by quad3d@work (2008-01-18 23:25:26)

Postfix howto [solved]

I'm trying to install Postfix and Courier-IMAP to run a small intranet mail system. I went to the Postfix Howto in the Wiki, and following the instructions, got to setting up the mysql database. When I try to import the table structure indicated, I keep getting a syntax error on the part around
code.../code
I'm not fluent in mysql, and wondered if anyone who knows this could check out that page and let me know if it's ok. If so, it's something I'm doing.
I'm kind of cookbooking it through this for now.

which postfix howto.. there should be more than one...
cuz I wrote more than one..at one point..
EDIT: I see the problem..
http://wiki.archlinux.org/index.php/Pos … _structure.
the wiki migration yeilded a few "artifacts" in some of the code blocks. I will take a look at it..

[postfix/dovecot] setup a mailserver

Hi.
I followed this little tutorial (quite old, but seems to be still ok) : http://www.howtoforge.com/arch-linux-ma … nd-dovecot
I did all of it, all my daemons start well, but I don't know what to do; I've to say I didn't understand well when and how I created the accounts, I don't even know if I did it…
Thanks for any help or precision, I'm a bit lost here… :-)

Building a mail server could be a delicate task. So, go step by step.
Decide first, if you want to use VIRTUAL or UNIX users.
Make your SMTP installation work. Test it. Then test it again.
If it works, decide, if you need an IMAP/POP server too. Install it, make it work. Test it. Test it again.
I've had some adventures with postfix/courier-imap/cyrus-sasl lately. If you do not work slowly, nothing will work. Really.
And do not be afraid to read other distro's wiki pages too. It could be helpful.

Configuring KMail / Postfix

I have been setting up localmail according to this wiki article. https://wiki.archlinux.org/index.php/Postfix_Local_Mail
This is all great and works according to the wiki, however its when I try and get things working in KMail that I'm having trouble with. I may have run into something similar to what is described here, especially the last comment.
https://bugs.kde.org/show_bug.cgi?id=286793#c3
As described here the mail is received in Kmail, but I am unable to remove them. Sending and receiving mail using mail from the command line does work. I haven't even tried sending mail to a local user from KMail but that can wait until after I get this problem fixed.
Has anyone else run into this issue and is there a work around or solution for this behaviour?
Last edited by MikeW (2011-11-22 07:47:48)

MrHoffman, thank you for your response to my challenge to get the new test server working. This is a migration from Snow Leopard Server to Mountain Lion Server.
Here is the "checkhostname" test results:
blue:~ admin$ sudo changeip -checkhostname
Password:
Primary address     = 96.231.165.211
Current HostName    = blue.pderby.com
DNS HostName        = blue.pderby.com
The names match. There is nothing to change.
dirserv:success = "success"
blue:~ admin$
Here is the response from postconf -n
blue:~ admin$ postconf -n
biff = no
command_directory = /usr/sbin
config_directory = /etc/postfix
daemon_directory = /usr/libexec/postfix
data_directory = /var/lib/postfix
debug_peer_level = 2
debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin xxgdb $daemon_directory/$process_name $process_id & sleep 5
dovecot_destination_recipient_limit = 1
html_directory = /usr/share/doc/postfix/html
imap_submit_cred_file = /Library/Server/Mail/Config/postfix/submit.cred
inet_interfaces = loopback-only
inet_protocols = all
mail_owner = _postfix
mailbox_size_limit = 0
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
message_size_limit = 10485760
mydomain_fallback = localhost
newaliases_path = /usr/bin/newaliases
queue_directory = /Library/Server/Mail/Data/spool
readme_directory = /usr/share/doc/postfix
recipient_delimiter = +
sample_directory = /usr/share/doc/postfix/examples
sendmail_path = /usr/sbin/sendmail
setgid_group = _postdrop
smtpd_tls_ciphers = medium
smtpd_tls_exclude_ciphers = SSLv2, aNULL, ADH, eNULL
tls_random_source = dev:/dev/urandom
unknown_local_recipient_reject_code = 550
use_sacl_cache = yes
blue:~ admin$
I agree that I should change the LAN domain from .local to something like .internal or whatever.   I've been running with .local for 5 years on snow leopard server and never had any problems so that was a low priority.
I hope I'm just not seeing some obvious setting in main.cf

Postfix wiki

Similar Messages

Maybe you are looking for