NavigationUser loginSpam?See spam posts on this site? If so, please don't reply to the spam! Instead, just report the URL to the webmaster. |
Email receiving problemsI am working with a test box trying to get a test environment running to I am having a problem with my email. I am running 'Postfix' SMTP Anyone have an idea of what I did wrong? Thanks Kelly -- |
Email receiving problems
On Mon, Feb 19, 2007 at 09:35:37PM -0600, Kelly wrote:
> I am working with a test box trying to get a test environment running to
> switch from Solaris to Debian.
>
> I am having a problem with my email. I am running 'Postfix' SMTP
> server. I am running the 'Courier IMAP' server. I can send email just
> fine. When I am receiving email there is a problem. The email is
> supposed to go to the 'maildirs' directory in the home folders for the
> users. Problem is the email goes to the /var/mail/$username directory.
>
> Anyone have an idea of what I did wrong?
>
Well, the contents of your postfix and courier config files might enable
some useful suggestions.
Regards,
-Roberto
--
Roberto C. Sanchez
http://people.connexer.com/~roberto
http://www.connexer.com
Email receiving problems
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02/19/07 22:01, Roberto C. Sanchez wrote:
> On Mon, Feb 19, 2007 at 09:35:37PM -0600, Kelly wrote:
>> I am working with a test box trying to get a test environment running to
>> switch from Solaris to Debian.
>>
>> I am having a problem with my email. I am running 'Postfix' SMTP
>> server. I am running the 'Courier IMAP' server. I can send email just
>> fine. When I am receiving email there is a problem. The email is
>> supposed to go to the 'maildirs' directory in the home folders for the
>> users. Problem is the email goes to the /var/mail/$username directory.
>>
>> Anyone have an idea of what I did wrong?
Yes. You aren't (properly) telling postfix where to deliver email.
> Well, the contents of your postfix and courier config files might enable
> some useful suggestions.
I'm not sure if they do. The postfix -doc package will, though, as
does Google.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFF2n7LS9HxQb37XmcRAhVeAKCNasDD3r4VXNij5aAblQ/zK83vCgCgvI64
4XQF/V1QbXEiQIJ243jj+Q0=
=tWcY
-----END PGP SIGNATURE-----
--
RE: Email receiving problems
Ron thanks for the reply,
I added the command 'mailbox_command = /usr/bin/maildrop' to the main.cf
file. I sent a test email and the email did not go through at all. I
got this in reply:
_________________________________
Command died with status 1:
"/usr/bin/maildrop"
_________________________________
I looked in the directory /usr/bin/maildrop and it does not exist on
this box. I did a search and came up with a maildrop here:
/var/spool/postfix/maildrop. I tried it and got the same reply.
Thanks for your help.
Kelly
> -------- Original Message --------
> Subject: Re: Email receiving problems
> From: "Ron Johnson"
> Date: Tue, February 20, 2007 10:04 am
> To:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I wonder if you need this in main.cf?
>
> mailbox_command = /usr/bin/maildrop
> mailbox_size_limit = 0
>
> On 02/20/07 09:35, Kelly D Kennedy wrote:
> > Thanks for the reply David,
> >
> > The directive 'home_mailbox = Maildir/' is already in the main.cf file.
> >
> > ___________________________________________________________________________________________________________
> >
> > Here is the main.cf file contents:
> >
> > # See /usr/share/postfix/main.cf.dist for a commented, more complete
> > version
> > smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
> > biff = no
> >
> > # appending .domain is the MUA's job.
> > append_dot_mydomain = no
> >
> > # Uncomment the next line to generate "delayed mail" warnings
> > #delay_warning_time = 4h
> >
> > myhostname = www.boredomhost.com
> > alias_maps = hash:/etc/aliases
> > alias_database = hash:/etc/aliases
> > myorigin = /etc/mailname
> > relayhost =
> > mynetworks = 127.0.0.0/8
> > mailbox_command = procmail -a "$EXTENSION"
> > mailbox_size_limit = 0
> > recipient_delimiter = @
> > smtpd_sasl_local_domain =
> > smtpd_sasl_auth_enable = yes
> > smtpd_sasl_security_options = noanonymous
> > broken_sasl_auth_clients = yes
> > smtpd_recipient_restrictions =
> > permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination
> > smtpd_tls_auth_only = no
> > smtp_use_tls = yes
> > smtpd_use_tls = yes
> > smtp_tls_note_starttls_offer = yes
> > smtpd_tls_key_file = /etc/postfix/ssl/smtpd.key
> > smtpd_tls_cert_file = /etc/postfix/ssl/smtpd.crt
> > smtpd_tls_CAfile = /etc/postfix/ssl/cacert.pem
> > smtpd_tls_loglevel = 1
> > smtpd_tls_received_header = yes
> > smtpd_tls_session_cache_timeout = 3600s
> > tls_random_source = dev:/dev/urandom
> > home_mailbox = Maildir/
> > virtual_maps = hash:/etc/postfix/virtusertable
> > mydestination = boredomhost.com
> > virtual_alias_maps = hash:/etc/postfix/virtual
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFF2xwKS9HxQb37XmcRAhd1AJ9g5WJ+6+Jz0re9AG5sI9Wl3Fc2VgCgh9I1
> c6PcWBZRH31op5zpXIacdf0=
> =hIDY
> -----END PGP SIGNATURE-----
--
Email receiving problems
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02/20/07 11:00, Kelly wrote:
> Ron thanks for the reply,
>
> I added the command 'mailbox_command = /usr/bin/maildrop' to the main.cf
> file. I sent a test email and the email did not go through at all. I
> got this in reply:
> _________________________________
> Command died with status 1:
> "/usr/bin/maildrop"
> _________________________________
>
> I looked in the directory /usr/bin/maildrop and it does not exist on
> this box. I did a search and came up with a maildrop here:
> /var/spool/postfix/maildrop. I tried it and got the same reply.
>
> Thanks for your help.
Guess I should have mentioned that you need to install maildrop.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFF2ziDS9HxQb37XmcRAnOnAJ9Np6NjHj7VdDbdvhWvTbRFq291XACgwc08
mkJXBMAYg7jG3YeEDl/jiQY=
=cQxf
-----END PGP SIGNATURE-----
--
Email receiving problems
On Mon 2007-02-19 21:35:37 -0600 Kelly wrote:
> I am working with a test box trying to get a test environment running to
> switch from Solaris to Debian.
>
> I am having a problem with my email. I am running 'Postfix' SMTP
> server. I am running the 'Courier IMAP' server. I can send email just
> fine. When I am receiving email there is a problem. The email is
> supposed to go to the 'maildirs' directory in the home folders for the
> users. Problem is the email goes to the /var/mail/$username directory.
>
> Anyone have an idea of what I did wrong?
Without seeing your configuration I can only guess but, if you haven't
changed the default configuration, you should only need to add
'home_mailbox = Maildir/' to main.cf. Change 'Maildir' to suit the name
of the users home mail directory. Note the trailing forward slash on
the mailbox name as this tells postfix to deliver in maildir format.
If this doesn't work, post the output of the command 'postconf -n' which
will show where your config deviates from default.
--
David Hart
--
RE: Email receiving problems
Thanks for the reply David,
The directive 'home_mailbox = Maildir/' is already in the main.cf file.
___________________________________________________________________________________________________________
Here is the main.cf file contents:
# See /usr/share/postfix/main.cf.dist for a commented, more complete
version
smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
biff = no
# appending .domain is the MUA's job.
append_dot_mydomain = no
# Uncomment the next line to generate "delayed mail" warnings
#delay_warning_time = 4h
myhostname = www.boredomhost.com
alias_maps = hash:/etc/aliases
alias_database = hash:/etc/aliases
myorigin = /etc/mailname
relayhost =
mynetworks = 127.0.0.0/8
mailbox_command = procmail -a "$EXTENSION"
mailbox_size_limit = 0
recipient_delimiter = @
smtpd_sasl_local_domain =
smtpd_sasl_auth_enable = yes
smtpd_sasl_security_options = noanonymous
broken_sasl_auth_clients = yes
smtpd_recipient_restrictions =
permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination
smtpd_tls_auth_only = no
smtp_use_tls = yes
smtpd_use_tls = yes
smtp_tls_note_starttls_offer = yes
smtpd_tls_key_file = /etc/postfix/ssl/smtpd.key
smtpd_tls_cert_file = /etc/postfix/ssl/smtpd.crt
smtpd_tls_CAfile = /etc/postfix/ssl/cacert.pem
smtpd_tls_loglevel = 1
smtpd_tls_received_header = yes
smtpd_tls_session_cache_timeout = 3600s
tls_random_source = dev:/dev/urandom
home_mailbox = Maildir/
virtual_maps = hash:/etc/postfix/virtusertable
mydestination = boredomhost.com
virtual_alias_maps = hash:/etc/postfix/virtual
___________________________________________________________________________________________________________
Here is the file contents for IMAPD:
##VERSION: $Id: imapd.dist.in,v 1.29 2004/04/18 15:54:39 mrsam Exp $
#
# imapd created from imapd.dist by sysconftool
#
# Do not alter lines that begin with ##, they are used when upgrading
# this configuration.
#
# Copyright 1998 - 2004 Double Precision, Inc. See COPYING for
# distribution information.
#
# This configuration file sets various options for the Courier-IMAP
server
# when used with the couriertcpd server.
# A lot of the stuff here is documented in the manual page for
couriertcpd.
#
# NOTE - do not use \ to split long variable contents on multiple
lines.
# This will break the default imapd.rc script, which parses this file.
#
##NAME: ADDRESS:0
#
# Address to listen on, can be set to a single IP address.
#
# ADDRESS=127.0.0.1
ADDRESS=0
##NAME: PORT:1
#
# Port numbers that connections are accepted on. The default is 143,
# the standard IMAP port.
#
# Multiple port numbers can be separated by commas. When multiple port
# numbers are used it is possible to select a specific IP address for a
# given port as "ip.port". For example, "127.0.0.1.900,192.68.0.1.900"
# accepts connections on port 900 on IP addresses 127.0.0.1 and
192.68.0.1
# The previous ADDRESS setting is a default for ports that do not have
# a specified IP address.
PORT=143
##NAME: AUTHSERVICE:0
#
# It's possible to authenticate using a different 'service' parameter
# depending on the connection's port. This only works with
authentication
# modules that use the 'service' parameter, such as PAM. Example:
#
# AUTHSERVICE143=imap
# AUTHSERVICE993=imaps
##NAME: MAXDAEMONS:0
#
# Maximum number of IMAP servers started
#
MAXDAEMONS=40
##NAME: MAXPERIP:0
#
# Maximum number of connections to accept from the same IP address
MAXPERIP=20
##NAME: PIDFILE:0
#
# File where couriertcpd will save its process ID
#
PIDFILE=/var/run/courier/imapd.pid
##NAME: TCPDOPTS:0
#
# Miscellaneous couriertcpd options that shouldn't be changed.
#
TCPDOPTS="-nodnslookup -noidentlookup"
##NAME: AUTHMODULES:0
#
# Authentication modules. Here's the default list:
#
# authdaemon
#
# The default is set during the initial configuration.
#
# If this is currently set to AUTHMODULES="authdaemon", DO NOT CHANGE
IT.
# Instead, change the parameter authmodulelist in authdaemonrc.
AUTHMODULES="authdaemon"
##NAME: AUTHMODULES_ORIG:0
#
# For use by webadmin
AUTHMODULES_ORIG="authdaemon"
##NAME: DEBUG_LOGIN:0
#
# Dump additional login diagnostics to syslog
#
# DEBUG_LOGIN=0 - turn off login debugging
# DEBUG_LOGIN=1 - turn on login debugging
# DEBUG_LOGIN=2 - turn on login debugging + log passwords too
#
# Note that most information is sent to syslog at level 'debug', so
# you may need to modify your /etc/syslog.conf to be able to see it.
DEBUG_LOGIN=0
##NAME: IMAP_CAPABILITY:1
#
# IMAP_CAPABILITY specifies what most of the response should be to the
# CAPABILITY command.
#
# If you have properly configured Courier to use CRAM-MD5 or CRAM-SHA1
# authentication (see INSTALL), set IMAP_CAPABILITY as follows:
#
# IMAP_CAPABILITY="IMAP4rev1 UIDPLUS CHILDREN NAMESPACE
THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA AUTH=CRAM-MD5
AUTH=CRAM-SHA1 IDLE"
#
IMAP_CAPABILITY="IMAP4rev1 UIDPLUS CHILDREN NAMESPACE
THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE"
##NAME: KEYWORDS_CAPABILITY:0
#
# IMAP_KEYWORDS=1 enables custom IMAP keywords. Set this option to 0 to
# disable custom keywords.
IMAP_KEYWORDS=1
##NAME: SMAP1_CAPABILITY:0
#
# EXPERIMENTAL
#
# To enable the experimental "Simple Mail Access Protocol" extensions,
# uncomment the following setting.
#
# SMAP_CAPABILITY=SMAP1
##NAME: IMAP_CAPABILITY_ORIG:1
#
# For use by webadmin
IMAP_CAPABILITY_ORIG="IMAP4rev1 UIDPLUS CHILDREN NAMESPACE
THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA AUTH=CRAM-MD5
AUTH=CRAM-SHA1 IDLE"
##NAME: IMAP_IDLE_TIMEOUT:0
#
# This setting controls how often
# the server polls for changes to the folder, in IDLE mode (in seconds).
IMAP_IDLE_TIMEOUT=60
##NAME: IMAP_CAPABILITY_TLS:0
#
# The following setting will advertise SASL PLAIN authentication after
# STARTTLS is established. If you want to allow SASL PLAIN
authentication
# with or without TLS then just comment this out, and add AUTH=PLAIN to
# IMAP_CAPABILITY
IMAP_CAPABILITY_TLS="$IMAP_CAPABILITY AUTH=PLAIN"
##NAME: IMAP_TLS_ORIG:0
#
# For use by webadmin
IMAP_CAPABILITY_TLS_ORIG="$IMAP_CAPABILITY_ORIG AUTH=PLAIN"
##NAME: IMAP_DISABLETHREADSORT:0
#
# Set IMAP_DISABLETHREADSORT to disable the THREAD and SORT commands -
# server side sorting and threading.
#
# Those capabilities will still be advertised, but the server will
reject
# them. Set this option if you want to disable all the extra load from
# server-side threading and sorting. Not advertising those capabilities
# will simply result in the clients reading the entire folder, and
sorting
# it on the client side. That will still put some load on the server.
# advertising these capabilities, but rejecting the commands, will stop
this
# silliness.
#
IMAP_DISABLETHREADSORT=0
##NAME: IMAP_CHECK_ALL_FOLDERS:0
#
# Set IMAP_CHECK_ALL_FOLDERS to 1 if you want the server to check for
new
# mail in every folder. Not all IMAP clients use the IMAP's new mail
# indicator, but some do. Normally new mail is checked only in INBOX,
# because it is a comparatively time consuming operation, and it would
be
# a complete waste of time unless mail filters are used to deliver
# mail directly to folders.
#
# When IMAP clients are used which support new mail indication, and when
# mail filters are used to sort incoming mail into folders, setting
# IMAP_CHECK_ALL_FOLDERS to 1 will allow IMAP clients to announce new
# mail in folders. Note that this will result in slightly more load on
the
# server.
#
IMAP_CHECK_ALL_FOLDERS=0
##NAME: IMAP_OBSOLETE_CLIENT:0
#
# Set IMAP_OBSOLETE_CLIENT if your IMAP client expects \\NoInferiors to
mean
# what \\HasNoChildren really means.
IMAP_OBSOLETE_CLIENT=0
##NAME: IMAP_ULIMITD:0
#
# IMAP_ULIMITD sets the maximum size of the data segment of the server
# process. The value of IMAP_ULIMITD is simply passed to the "ulimit
-d"
# command (or ulimit -v). The argument to ulimi sets the upper limit on
the
# size of the data segment of the server process, in kilobytes. The
default
# value of 65536 sets a very generous limit of 64 megabytes, which
should
# be more than plenty for anyone.
#
# This feature is used as an additional safety check that should stop
# any potential denial-of-service attacks that exploit any kind of
# a memory leak to exhaust all the available memory on the server.
# It is theoretically possible that obscenely huge folders will also
# result in the server running out of memory when doing server-side
# sorting (by my calculations you have to have at least 100,000 messages
# in a single folder, for that to happen).
IMAP_ULIMITD=65536
##NAME: IMAP_USELOCKS:0
#
# Setting IMAP_USELOCKS to 1 will use dot-locking to support concurrent
# multiple access to the same folder. This incurs slight additional
# overhead. Concurrent multiple access will still work without this
setting,
# however occasionally a minor race condition may result in an IMAP
client
# downloading the same message twice, or a keyword update will fail.
#
# IMAP_USELOCKS=1 is strongly recommended when shared folders are used.
IMAP_USELOCKS=1
##NAME: IMAP_SHAREDINDEXFILE:0
#
# The index of all accessible folders. Do not change this setting
unless
# you know what you're doing. See README.sharedfolders for additional
# information.
IMAP_SHAREDINDEXFILE=/etc/courier/shared/index
##NAME: IMAP_ENHANCEDIDLE:0
#
# If Courier was compiled with the File Alteration Monitor, setting
# IMAP_ENHANCEDIDLE to 1 enables enhanced IDLE mode, where multiple
# clients may open the same folder concurrently, and receive updates to
# folder contents in realtime. See the imapd(8) man page for additional
# information.
#
# IMPORTANT: IMAP_USELOCKS *MUST* also be set to 1, and IDLE must be
included
# in the IMAP_CAPABILITY list.
#
IMAP_ENHANCEDIDLE=0
##NAME: IMAP_TRASHFOLDERNAME:0
#
# The name of the magic trash Folder. For MSOE compatibility,
# you can set IMAP_TRASHFOLDERNAME="Deleted Items".
#
# IMPORTANT: If you change this, you must also change IMAP_EMPTYTRASH
IMAP_TRASHFOLDERNAME=Trash
##NAME: IMAP_EMPTYTRASH:0
#
# The following setting is optional, and causes messages from the given
# folder to be automatically deleted after the given number of days.
# IMAP_EMPTYTRASH is a comma-separated list of folder:days. The default
# setting, below, purges 7 day old messages from the Trash folder.
# Another useful setting would be:
#
# IMAP_EMPTYTRASH=Trash:7,Sent:30
#
# This would also delete messages from the Sent folder (presumably
copies
# of sent mail) after 30 days. This is a global setting that is applied
to
# every mail account, and is probably useful in a controlled, corporate
# environment.
#
# Important: the purging is controlled by CTIME, not MTIME (the file
time
# as shown by ls). It is perfectly ordinary to see stuff in Trash
that's
# a year old. That's the file modification time, MTIME, that's
displayed.
# This is generally when the message was originally delivered to this
# mailbox. Purging is controlled by a different timestamp, CTIME, which
is
# changed when the file is moved to the Trash folder (and at other times
too).
#
# You might want to disable this setting in certain situations - it
results
# in a stat() of every file in each folder, at login and logout.
#
IMAP_EMPTYTRASH=Trash:7
##NAME: IMAP_MOVE_EXPUNGE_TO_TRASH:0
#
# Set IMAP_MOVE_EXPUNGE_TO_TRASH to move expunged messages to Trash.
This
# effectively allows an undo of message deletion by fishing the deleted
# mail from trash. Trash can be manually expunged as usually, and mail
# will get automatically expunged from Trash according to
IMAP_EMPTYTRASH.
#
# NOTE: shared folders are still expunged as usual. Shared folders are
# not affected.
#
IMAP_MOVE_EXPUNGE_TO_TRASH=0
##NAME: OUTBOX:0
#
# The next set of options deal with the "Outbox" enhancement.
# Uncomment the following setting to create a special folder, named
# INBOX.Outbox
#
# OUTBOX=.Outbox
##NAME: SENDMAIL:0
#
# If OUTBOX is defined, mail can be sent via the IMAP connection by
copying
# a message to the INBOX.Outbox folder. For all practical matters,
# INBOX.Outbox looks and behaves just like any other IMAP folder. If
this
# folder doesn't exist it must be created by the IMAP mail client, just
# like any other IMAP folder. The kicker: any message copied or moved
to
# this folder is will be E-mailed by the Courier-IMAP server, by running
# the SENDMAIL program. Therefore, messages copied or moved to this
# folder must be well-formed RFC-2822 messages, with the recipient list
# specified in the To:, Cc:, and Bcc: headers. Courier-IMAP relies on
# SENDMAIL to read the recipient list from these headers (and delete the
Bcc:
# header) by running the command "$SENDMAIL -oi -t -f $SENDER", with the
# message piped on standard input. $SENDER will be the return address
# of the message, which is set by the authentication module.
#
# DO NOT MODIFY SENDMAIL, below, unless you know what you're doing.
#
SENDMAIL=/usr/sbin/sendmail
##NAME: HEADERFROM:0
#
# For administrative and oversight purposes, the return address, $SENDER
# will also be saved in the X-IMAP-Sender mail header. This header gets
# added to the sent E-mail (but it doesn't get saved in the copy of the
# message that's saved in the folder)
#
# WARNING - By enabling OUTBOX above, *every* IMAP mail client will
receive
# the magic OUTBOX treatment. Therefore advance LARTing is in order for
# _all_ of your lusers, until every one of them is aware of this.
Otherwise if
# OUTBOX is left at its default setting - a folder name that might be
used
# accidentally - some people may be in for a rude surprise. You can
redefine
# the name of the magic folder by changing OUTBOX, above. You should do
that
# and pick a less-obvious name. Perhaps brand it with your
organizational
# name ( OUTBOX=.WidgetsAndSonsOutbox )
HEADERFROM=X-IMAP-Sender
##NAME: IMAPDSTART:0
#
# IMAPDSTART is not used directly. Rather, this is a convenient flag to
# be read by your system startup script in /etc/rc.d, like this:
#
# . /etc/courier/imapd
#
# case x$IMAPDSTART in
# x[yY]*)
# /usr/lib/courier/imapd.rc start
# ;;
# esac
#
# The default setting is going to be NO, so you'll have to manually flip
# it to yes.
IMAPDSTART=YES
##NAME: MAILDIRPATH:0
#
# MAILDIRPATH - directory name of the maildir directory.
#
MAILDIRPATH=Maildir
___________________________________________________________________________________________________________
Here is the output of postconf -n:
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
append_dot_mydomain = no
biff = no
broken_sasl_auth_clients = yes
config_directory = /etc/postfix
home_mailbox = Maildir/
mailbox_command = procmail -a "$EXTENSION"
mailbox_size_limit = 0
mydestination = boredomhost.com
myhostname = www.boredomhost.com
mynetworks = 127.0.0.0/8
myorigin = /etc/mailname
recipient_delimiter = @
relayhost =
smtp_tls_note_starttls_offer = yes
smtp_use_tls = yes
smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
smtpd_recipient_restrictions =
permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination
smtpd_sasl_auth_enable = yes
smtpd_sasl_local_domain =
smtpd_sasl_security_options = noanonymous
smtpd_tls_CAfile = /etc/postfix/ssl/cacert.pem
smtpd_tls_auth_only = no
smtpd_tls_cert_file = /etc/postfix/ssl/smtpd.crt
smtpd_tls_key_file = /etc/postfix/ssl/smtpd.key
smtpd_tls_loglevel = 1
smtpd_tls_received_header = yes
smtpd_tls_session_cache_timeout = 3600s
smtpd_use_tls = yes
tls_random_source = dev:/dev/urandom
virtual_alias_maps = hash:/etc/postfix/virtual
Thanks Again
Kelly
> -------- Original Message --------
> Subject: Re: Email receiving problems
> From: "David Hart"
> Date: Tue, February 20, 2007 4:53 am
> To:
>
> On Mon 2007-02-19 21:35:37 -0600 Kelly wrote:
>
> > I am working with a test box trying to get a test environment running to
> > switch from Solaris to Debian.
> >
> > I am having a problem with my email. I am running 'Postfix' SMTP
> > server. I am running the 'Courier IMAP' server. I can send email just
> > fine. When I am receiving email there is a problem. The email is
> > supposed to go to the 'maildirs' directory in the home folders for the
> > users. Problem is the email goes to the /var/mail/$username directory.
> >
> > Anyone have an idea of what I did wrong?
>
> Without seeing your configuration I can only guess but, if you haven't
> changed the default configuration, you should only need to add
> 'home_mailbox = Maildir/' to main.cf. Change 'Maildir' to suit the name
> of the users home mail directory. Note the trailing forward slash on
> the mailbox name as this tells postfix to deliver in maildir format.
>
> If this doesn't work, post the output of the command 'postconf -n' which
> will show where your config deviates from default.
>
> --
> David Hart
--
Email receiving problems
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I wonder if you need this in main.cf?
mailbox_command = /usr/bin/maildrop
mailbox_size_limit = 0
On 02/20/07 09:35, Kelly D Kennedy wrote:
> Thanks for the reply David,
>
> The directive 'home_mailbox = Maildir/' is already in the main.cf file.
>
> ___________________________________________________________________________________________________________
>
> Here is the main.cf file contents:
>
> # See /usr/share/postfix/main.cf.dist for a commented, more complete
> version
> smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
> biff = no
>
> # appending .domain is the MUA's job.
> append_dot_mydomain = no
>
> # Uncomment the next line to generate "delayed mail" warnings
> #delay_warning_time = 4h
>
> myhostname = www.boredomhost.com
> alias_maps = hash:/etc/aliases
> alias_database = hash:/etc/aliases
> myorigin = /etc/mailname
> relayhost =
> mynetworks = 127.0.0.0/8
> mailbox_command = procmail -a "$EXTENSION"
> mailbox_size_limit = 0
> recipient_delimiter = @
> smtpd_sasl_local_domain =
> smtpd_sasl_auth_enable = yes
> smtpd_sasl_security_options = noanonymous
> broken_sasl_auth_clients = yes
> smtpd_recipient_restrictions =
> permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination
> smtpd_tls_auth_only = no
> smtp_use_tls = yes
> smtpd_use_tls = yes
> smtp_tls_note_starttls_offer = yes
> smtpd_tls_key_file = /etc/postfix/ssl/smtpd.key
> smtpd_tls_cert_file = /etc/postfix/ssl/smtpd.crt
> smtpd_tls_CAfile = /etc/postfix/ssl/cacert.pem
> smtpd_tls_loglevel = 1
> smtpd_tls_received_header = yes
> smtpd_tls_session_cache_timeout = 3600s
> tls_random_source = dev:/dev/urandom
> home_mailbox = Maildir/
> virtual_maps = hash:/etc/postfix/virtusertable
> mydestination = boredomhost.com
> virtual_alias_maps = hash:/etc/postfix/virtual
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFF2xwKS9HxQb37XmcRAhd1AJ9g5WJ+6+Jz0re9AG5sI9Wl3Fc2VgCgh9I1
c6PcWBZRH31op5zpXIacdf0=
=hIDY
-----END PGP SIGNATURE-----
--
Email receiving problems
On Tue, 20 Feb 2007 10:04:26 -0600
Ron Johnson wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I wonder if you need this in main.cf?
>
> mailbox_command = /usr/bin/maildrop
It can be done like this as well, but the OP needs to uncomment the
relevant line in /etc/maildroprc
Regards,
Andrei
--
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)
--
[solved]Email receiving problems
adding the command in main.cf and uncommented the line in maildroprc and
it is now working.
Thanks
Kelly
Andrei Popescu wrote:
> On Tue, 20 Feb 2007 10:04:26 -0600
> Ron Johnson wrote:
>
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> I wonder if you need this in main.cf?
>>
>> mailbox_command = /usr/bin/maildrop
>>
>
> It can be done like this as well, but the OP needs to uncomment the
> relevant line in /etc/maildroprc
>
> Regards,
> Andrei
>
--
Email receiving problems
Am 2007-02-19 21:35:37, schrieb Kelly:
> I am working with a test box trying to get a test environment running to
> switch from Solaris to Debian.
>
> I am having a problem with my email. I am running 'Postfix' SMTP
> server. I am running the 'Courier IMAP' server. I can send email just
> fine. When I am receiving email there is a problem. The email is
> supposed to go to the 'maildirs' directory in the home folders for the
> users. Problem is the email goes to the /var/mail/$username directory.
>
> Anyone have an idea of what I did wrong?
apt-get install courier-mta-ssl
and the error go magicaly. :-)
Thanks, Greetings and nice Day
Michelle Konzack
Systemadministrator
Tamay Dogan Network
Debian GNU/Linux Consultant
--
Linux-User #280138 with the Linux Counter, http://counter.li.org/
##################### Debian GNU/Linux Consultant #####################
Michelle Konzack Apt. 917 ICQ #328449886
50, rue de Soultz MSM LinuxMichi
0033/6/61925193 67100 Strasbourg/France IRC #Debian (irc.icq.com)
Email receiving problems
Am 2007-02-19 21:35:37, schrieb Kelly:
> I am having a problem with my email. I am running 'Postfix' SMTP
> server. I am running the 'Courier IMAP' server. I can send email just
> fine. When I am receiving email there is a problem. The email is
> supposed to go to the 'maildirs' directory in the home folders for the
> users. Problem is the email goes to the /var/mail/$username directory.
>
> Anyone have an idea of what I did wrong?
I use ~/.Maildir for mail and have "home_mailbox = .Maildir/"
in /etc/postfix/main.cf, perhaps you need it set to "Maildir/"?
--