Current time: 11-16-2024, 12:43 PM Hello There, Guest! (LoginRegister)


Thread Closed 
Webmail im ispCP! Problem!
Author Message
shoxxweb Offline
Junior Member
*

Posts: 59
Joined: Feb 2008
Reputation: 0
Post: #11
RE: Webmail im ispCP! Problem!
Hey Leute,

Finde in meiner Imapd diesen Abschnitt nicht.
Hier die ganze imapd:

##VERSION: $Id: imapd,v 1.3 2003/08/08 14:12:58 lisp Exp $
#
# imapd created from imapd.dist by sysconftool
#
# Do not alter lines that begin with ##, they are used when upgrading
# this configuration.
#
# Copyright 1998 - 2002 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=4

##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.
#

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

DEBUG_LOGIN=1

##NAME: IMAP_CAPABILITY:0
#
# 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 CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA AUTH=CRAM-MD5 AUTH=CRAM-SHA1 IDLE"
#

IMAP_CAPABILITY="IMAP4rev1 CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE AUTH=LOGIN"

##NAME: IMAP_CAPABILITY_ORIG:0
#
# For use by webadmin

IMAP_CAPABILITY_ORIG="IMAP4rev1 CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT AUTH=CRAM-MD5 AUTH=CRAM-SHA1 IDLE AUTH=LOGIN"

##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.
#

IMAP_USELOCKS=0

##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.
#
# 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:
#
# . ${sysconfdir}/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


P.S Hoffe ihr könnt mir helfen!
02-07-2008 08:19 AM
Find all posts by this user
Thread Closed 


Messages In This Thread
Webmail im ispCP! Problem! - shoxxweb - 02-07-2008, 06:38 AM
RE: Webmail im ispCP! Problem! - BeNe - 02-07-2008, 06:47 AM
RE: Webmail im ispCP! Problem! - shoxxweb - 02-07-2008, 06:53 AM
RE: Webmail im ispCP! Problem! - BeNe - 02-07-2008, 06:57 AM
RE: Webmail im ispCP! Problem! - shoxxweb - 02-07-2008, 06:58 AM
RE: Webmail im ispCP! Problem! - shoxxweb - 02-07-2008, 07:40 AM
RE: Webmail im ispCP! Problem! - Rene - 02-07-2008, 07:42 AM
RE: Webmail im ispCP! Problem! - joximu - 02-07-2008, 07:46 AM
RE: Webmail im ispCP! Problem! - Rene - 02-07-2008, 07:55 AM
RE: Webmail im ispCP! Problem! - joximu - 02-07-2008, 08:02 AM
RE: Webmail im ispCP! Problem! - shoxxweb - 02-07-2008 08:19 AM
RE: Webmail im ispCP! Problem! - joximu - 02-07-2008, 08:27 AM
RE: Webmail im ispCP! Problem! - shoxxweb - 02-07-2008, 08:28 AM
RE: Webmail im ispCP! Problem! - joximu - 02-07-2008, 08:53 AM
RE: Webmail im ispCP! Problem! - shoxxweb - 02-07-2008, 09:07 AM
RE: Webmail im ispCP! Problem! - joximu - 02-07-2008, 09:11 AM
RE: Webmail im ispCP! Problem! - shoxxweb - 02-07-2008, 09:13 AM
RE: Webmail im ispCP! Problem! - joximu - 02-07-2008, 09:16 AM
RE: Webmail im ispCP! Problem! - shoxxweb - 02-07-2008, 09:18 AM
RE: Webmail im ispCP! Problem! - joximu - 02-07-2008, 09:24 AM
RE: Webmail im ispCP! Problem! - shoxxweb - 02-07-2008, 09:35 AM
RE: Webmail im ispCP! Problem! - joximu - 02-07-2008, 09:41 AM
RE: Webmail im ispCP! Problem! - shoxxweb - 02-07-2008, 08:06 PM
RE: Webmail im ispCP! Problem! - rbtux - 02-07-2008, 08:20 PM
RE: Webmail im ispCP! Problem! - shoxxweb - 02-07-2008, 08:23 PM
RE: Webmail im ispCP! Problem! - fulltilt - 02-07-2008, 08:35 PM
RE: Webmail im ispCP! Problem! - shoxxweb - 02-07-2008, 08:44 PM
RE: Webmail im ispCP! Problem! - fulltilt - 02-07-2008, 08:51 PM
RE: Webmail im ispCP! Problem! - shoxxweb - 02-07-2008, 08:54 PM
RE: Webmail im ispCP! Problem! - fulltilt - 02-07-2008, 09:03 PM
RE: Webmail im ispCP! Problem! - shoxxweb - 02-07-2008, 09:00 PM
RE: Webmail im ispCP! Problem! - rbtux - 02-07-2008, 09:09 PM
RE: Webmail im ispCP! Problem! - joximu - 02-08-2008, 01:26 AM
RE: Webmail im ispCP! Problem! - zpin - 02-07-2008, 09:02 PM
RE: Webmail im ispCP! Problem! - shoxxweb - 02-07-2008, 09:11 PM
RE: Webmail im ispCP! Problem! - fulltilt - 02-07-2008, 09:17 PM
RE: Webmail im ispCP! Problem! - shoxxweb - 02-07-2008, 09:12 PM
RE: Webmail im ispCP! Problem! - shoxxweb - 02-07-2008, 09:20 PM
RE: Webmail im ispCP! Problem! - joximu - 02-07-2008, 10:51 PM
RE: Webmail im ispCP! Problem! - fulltilt - 02-07-2008, 11:25 PM
RE: Webmail im ispCP! Problem! - joximu - 02-07-2008, 11:31 PM
RE: Webmail im ispCP! Problem! - fulltilt - 02-07-2008, 11:39 PM
RE: Webmail im ispCP! Problem! - rbtux - 02-08-2008, 12:58 AM
RE: Webmail im ispCP! Problem! - fulltilt - 02-08-2008, 01:13 AM
RE: Webmail im ispCP! Problem! - shoxxweb - 02-08-2008, 05:46 AM
RE: Webmail im ispCP! Problem! - BeNe - 02-08-2008, 04:48 PM

Forum Jump:


User(s) browsing this thread: 10 Guest(s)