Jump to content
Froxlor Forum

hmpfreally

Members
  • Content Count

    36
  • Joined

  • Last visited

Community Reputation

0 Neutral

About hmpfreally

  • Rank
    Advanced Froxie
  1. Erstmal vielen Dank für die ausführliche Antwort. Die FPM Version konnte ich bereits erfolgreich anpassen, das hat funktioniert. Der Cron wurde ebenfalls neu konfiguriert von mir (Nach Froxlor) und neu gestartet. Ich habe die Folgenden Konfigurationsschritte in Froxlor befolgt Debian Jessie (8.x) » Others (System) » libnss-mysql (required for FCGID/php-fpm/mpm-itk) Diese waren für /etc/libnss-mysql-root.cfg /etc/libnss-mysql.cfg /etc/nsswitch.conf Wenn ich es richtig verstanden habe. Was mir allerdings gerade auffällt ist, dass ich Debian Jessie (8.x) » Others (System) » PHP-FPM (alternative to mod_php) nicht nachgegangen bin, da diese Schritte ja im Github Wiki dabei sind. php5 wurde erfolgreich deaktiviert. Ich werde erstmal versuchen mich in Debian 10 einzulesen, vielen Dank nochmal für die Hilfe.
  2. Erstmal einen schönen Abend in die Runde. Vorerst muss ich zugeben, dass ich mich erst wieder in meinen vServer mit Debian 8 und Froxlor reinarbeite und kein Profi bin, allerdings möchte ich hier gerne mein Wissen erweitern. Vielleicht zuerst zu meinem System, ich nutze: Debian 8 Apache/2.4.10 (Debian) php Version: 5.6.40-0+deb8u4 mit Froxlor und möchte PHP-FPM aktivieren/einrichten. Nach der Anleitung hier --> https://github.com/Froxlor/Froxlor/wiki/apache2-with-php-fpm gelang es mir fpm zu aktivieren. Soweit sah alles gut aus, doch einige Fragen bleiben offen und letztlich habe ich ein Problem mit php Datein. Auch nach mehreren Tagen des Testens und Googlens bin ich nicht auf die Lösung gestoßen, bitte kann mir jemand weiter helfen? Zu erst gehe ich davon aus, dass der Cronjob nicht automatisch ausgeführt wird, da das Kundenverzeichnis in /var/customers/webs nicht automatisch angelegt wurde. Nach einigen Nachforschungen fand ich heraus, dass ich den Cron auf jeden Fall erstmal manuell starten sollte, mittels: php /var/www/froxlor/scripts/froxlor_master_cronjob.php --force --debug Leider habe ich keine Cronjobs mehr offen um zu checken, ob ich das Problem erfolgreich beheben konnte. Dabei ist mir allerdings direkt das nächste Problem aufgefallen und zwar spuckt er mir dabei unter anderem die folgene Zeile aus: [information] apache::reload: running service php7.0-fpm restart Failed to restart php7.0-fpm.service: Unit php7.0-fpm.service failed to load: No such file or directory. Da ich php version 5.6 benutze gehe ich hier schon von einem Fehler aus, habe die Konfiguration dazu aber nicht finden können. Trotzdem sollte das ganze ja eigentlich funktionieren, da ich den Apache schon manuell neu gestartet habe, liege ich da richtig? Wenn ich nun auf meine Seite: http://in-effect.de zugreifen möchte (auf php Datein), dann bekomme ich den Forbidden Error. Forbidden You don't have permission to access /fastcgiphp/index.php on this server. In den Customer Logs konnte ich dazu volgendens finden: (ine heißt mein angelegter Kunde) /var/customers/logs/ine-error.log [Sun Jul 14 20:34:45.579606 2019] [authz_core:error] [pid 1663] [client 91.12.206.1:49364] AH01630: client denied by server configuration: /etc/php5/fpm/pool.d/ine/in-effect.de/fpm.external Allerdings kann ich unter /etc/php5/fpm/pool.d/ine/in-effect.de/ nichts finden. Des weiteren Frage ich mich ob ich in den fpm Einstellungen die Einstellung für: "Default PHP configuration for new domains" auf vHost stellen soll statt default? Nach nun fast einer Woche des Suchens und Versuchens bin ich am Ende angekommen und würde mich sehr freuen wenn hier jemand eine Idee für mich hätte. Vielen Dank für eure Hilfe im vorraus, mit freundlichen Grüßen HmpfReally EDIT: Zumindest konnte ich das Problem anscheinend erfolgreich beheben. Wobei ich mir noch nicht ganz sicher über die richtige Konfiguration bin. Ich habe einen Screenshot angehängt. [information] apache::reload: running service php7.0-fpm restart Failed to restart php7.0-fpm.service: Unit php7.0-fpm.service failed to load: No such file or directory. Auch nach diesem Beitrag bekomme ich immer noch das Forbidden Problem. Ich gehe von einer fehlerhaften Konfiguration aus, kann aber aus meiner Fehlermeldung im Log nichts näheres schließen /var/customers/logs/ine-error.log [Sun Jul 14 20:34:45.579606 2019] [authz_core:error] [pid 1663] [client 91.12.206.1:49364] AH01630: client denied by server configuration: /etc/php5/fpm/pool.d/ine/in-effect.de/fpm.external Falls jemand eine Idee hat würde ich mich sehr freuen.
  3. Ich werde verr?ckt. Ich habe es nun an einem anderen PC getestet und es funktioniert. Vielen Dank, ich werde wohl ein Fehler bei mir haben. (Merkw?rdig war, dass es sowohl am PC als auch am Smartphone nicht funktionierte)
  4. Wie bereits erw?hnt lief der Server damit 1 1/2 Jahre problemlos, der Support vom vServer m?chte damit nichts zu tun haben (da meine Vermutung inzwischen ist, dass es nicht am vServer liegt) (Ist jedoch auch ein "Testserver" - eine bessere Beschreibung f?llt mir nicht ein, l?uft aber bisher immer ohne Probleme) Vielen Dank f?r die nette Hilfe, ich werde es im Laufe des Tages machen.
  5. authdaemonrc ##VERSION: $Id: authdaemonrc.in,v 1.8 2001/10/07 02:16:22 mrsam Exp $ # # Copyright 2000-2001 Double Precision, Inc. See COPYING for # distribution information. # # authdaemonrc created from authdaemonrc.dist by sysconftool # # Do not alter lines that begin with ##, they are used when upgrading # this configuration. # # This file configures authdaemond, the resident authentication daemon. # # Comments in this file are ignored. Although this file is intended to # be sourced as a shell script, authdaemond parses it manually, so # the acceptable syntax is a bit limited. Multiline variable contents, # with the \ continuation character, are not allowed. Everything must # fit on one line. Do not use any additional whitespace for indentation, # or anything else. ##NAME: authmodulelist:0 # # The authentication modules that are linked into authdaemond. The # default list is installed. You may selectively disable modules simply # by removing them from the following list. The available modules you # can use are: authcustom authcram authuserdb authldap authmysql authpam authmodulelist="authmysql" ##NAME: authmodulelistorig:1 # # This setting is used by Couriers webadmin module, and should be left # alone authmodulelistorig="authcustom authcram authuserdb authldap authmysql authpam" ##NAME: daemons:0 # # The number of daemon processes that are started. authdaemon is typically # installed where authentication modules are relatively expensive: such # as authldap, or authmysql, so its better to have a number of them running. # PLEASE NOTE: Some platforms may experience a problem if theres more than # one daemon. Specifically, SystemV derived platforms that use TLI with # socket emulation. Im suspicious of TLIs ability to handle multiple # processes accepting connections on the same filesystem domain socket. # # You may need to increase daemons if as your system load increases. Symptoms # include sporadic authentication failures. If you start getting # authentication failures, increase daemons. However, the default of 5 # SHOULD be sufficient. Bumping up daemon count is only a short-term # solution. The permanent solution is to add more resources: RAM, faster # disks, faster CPUs... daemons=5 ##NAME: version:0 # # When you have multiple versions of authdaemond.* installed, authdaemond # just picks the first one it finds. Set version to override that. # For example: version=authdaemond.plain version="" ##NAME: authdaemonvar:0 # # authdaemonvar is here, but is not used directly by authdaemond. Its # used by various configuration and build scripts, so dont touch it! authdaemonvar=/var/run/courier/authdaemon DEBUG_LOGIN=2 authmysqlrc MYSQL_SERVER 127.0.0.1 MYSQL_USERNAME froxlor MYSQL_PASSWORD DasrichtigePasswort MYSQL_PORT 3306 MYSQL_DATABASE froxlor MYSQL_USER_TABLE mail_users MYSQL_CRYPT_PWFIELD password_enc MYSQL_UID_FIELD uid MYSQL_GID_FIELD gid MYSQL_LOGIN_FIELD username MYSQL_HOME_FIELD homedir MYSQL_MAILDIR_FIELD maildir MYSQL_QUOTA_FIELD (quota*1024*1024) MYSQL_AUXOPTIONS_FIELD CONCAT("allowimap=",imap,",allowpop3=",pop3) imapd ##VERSION: $Id: imapd.dist.in 159 2011-11-14 02:07:00Z mrsam $ # # imapd created from imapd.dist by sysconftool # # Do not alter lines that begin with ##, they are used when upgrading # this configuration. # # Copyright 1998 - 2008 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: LOGGEROPTS:0 # # courierlogger(1) options. # LOGGEROPTS="-name=imapd" ##NAME: DEFDOMAIN:0 # # Optional default domain. If the username does not contain the # first character of DEFDOMAIN, then it is appended to the username. # If DEFDOMAIN and DOMAINSEP are both set, then DEFDOMAIN is appended # only if the username does not contain any character from DOMAINSEP. # You can set different default domains based on the the interface IP # address using the -access and -accesslocal options of couriertcpd(1). #DEFDOMAIN="@example.com" ##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, CRAM-SHA1, or # CRAM-SHA256 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 AUTH=CRAM-SHA256 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=2 also enables custom IMAP keywords, but uses a slower # algorithm. Use this setting if keyword-related problems occur when # multiple IMAP clients are updating keywords on the same message. IMAP_KEYWORDS=1 ##NAME: ACL_CAPABILITY:0 # # IMAP_ACL=1 enables IMAP ACL extension. Set this option to 0 to # disable ACL capabilities announce. IMAP_ACL=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:2 # # For use by webadmin IMAP_CAPABILITY_ORIG="IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA AUTH=CRAM-MD5 AUTH=CRAM-SHA1 AUTH=CRAM-SHA256 IDLE" ##NAME: IMAP_PROXY:0 # # Enable proxying. See README.proxy IMAP_PROXY=0 ##NAME: PROXY_HOSTNAME:0 # # Override value from gethostname() when checking if a proxy connection is # required. # # PROXY_HOSTNAME= ##NAME: IMAP_PROXY_FOREIGN:0 # # Proxying to non-Courier servers. Re-sends the CAPABILITY command after # logging in to the remote server. May not work with all IMAP clients. IMAP_PROXY_FOREIGN=0 ##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_MAILBOX_SANITY_CHECK:0 # # Sanity check -- make sure home directory and maildir's ownership matches # the IMAP server's effective uid and gid IMAP_MAILBOX_SANITY_CHECK=1 ##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_UMASK:0 # # IMAP_UMASK sets the umask of the server process. The value of IMAP_UMASK is # simply passed to the "umask" command. The default value is 022. # # This feature is mostly useful for shared folders, where the file permissions # of the messages may be important. IMAP_UMASK=022 ##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=131072 ##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: IMAP_LOG_DELETIONS:0 # # # Set IMAP_LOG_DELETIONS to log all message deletions to syslog. # # IMAP_LOG_DELETIONS=1 ##NAME: IMAPDEBUGFILE:0 # # IMAPDEBUGFILE="imaplog.dat" # # Generate diagnostic logging of IMAP commands. # # Set this globally, restart the server. Touch this file in an account's # maildir directory, and Courier-IMAP will append all IMAP commands received # for new sessions for this account. NOTE: existing IMAP sessions are not # affected, only new IMAP logins. ##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: OUTBOX_MULTIPLE_SEND:0 # # Remove the following comment to allow a COPY of more than one message to # the Outbox, at a time. # # OUTBOX_MULTIPLE_SEND=1 ##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
  6. Vielen Dank f?r die Idee, aber Imap ist f?r die Domain aktiviert. Der Dienst scheint auch zu laufen, Telenet Verbindung funktioniert auch und mit den E-Mail Clients ist auch der richtige Port zu finden (auch wenn dieser als Standart belassen wurde) Das merkw?rdige ist, dass der Server nicht ver?ndert wurde und es auf einmal nicht mehr ging. Zudem wurde er danach komplett neu aufgesetzt mit vorkonfigurierten Froxlor und es besteht der gleiche Fehler. Bin ratlos und am verzweifeln
  7. Der DeBug Login hat mich leider nicht weitergebracht. Alle Infos die ich daraus beziehen kann sind: imapd: Disconnected, ip=[::ffff:Meine.IP], time=14 imapd: Connection, ip=[::ffff:Meine.IP] Pop3 funktioniert jedoch (Auch der Login wird mir angezeigt im Log)
  8. Vielen Dank f?r deine Antwort. Die MySQL Daten stimmen ?berein (Benutzer Froxlor und das Froxlor MySQL Passwort) Mit dem Debug habe ich mich noch nicht besch?ftigt, reicht es DEBUG_LOGIN=2 einzutragen, oder w?hre dies entsprechend MYSQL_DEBUG_LOGIN 2? Die Neuinstallation belief sich vielmehr darauf, dass viele "Dienste und etc." ?ber l?ngeren Zeitraum nicht mehr genutzt wurden und nicht vollst?ndig vom System entfernt wurden (Zeitmangel). Da der Server nur noch nebenbei als Hobby betrieben wird, bot sich Weezy an, da es vorconfiguriert angeboten wird und ich somit Fehler meinerseits ausschlie?en wollte.
  9. Hallo Community, seit kurzem funktioniert mein "Mail System" auf meinem vServer nicht mehr. Bisher habe ich Debian Squeeze mit Froxlor eingerichtet gehabt und bis dato lief das System ohne Ver?nderungen einwandfrei (ca 1 1/2 Jahre lang). Auf einmal bekomme ich, wenn ich meine Emails ?ber IMAP mit einem Clienten (aktuell Thunderbird, funktioniert bei alternativer Software leider auch nicht), die Fehlermeldung, dass die Authentifizierung (Benutzername / Passwort) fehlgeschlagen ist. Am Server wurde nichts ver?ndert in diesem Zeitraum. Die Postfix / Courier Dienste laufen (imap; pop; authentification) und ?ber telenet bekomme ich auch eine Verbindung. In den Logs steht leider nur "Login failed / Disconnected" Der Server / die Dienste wurden bereits neu gestartet, E-Mail Konto wurde (im Client) neu eingerichetet, das Passwort wurde ge?ndert -> Kein Erfolg. (Bei der Neueinrichtung im Clienten kommt der Hinweis ob der Benutzername oder das Passwort falsch w?re) Da ich seit geraumer Zeit meinen vServer eine Neu-Installation g?nnen wollte, nahm ich dies als Anlass, da mich meine bisherige Fehlersuche nicht weiterbrachte. (Davor gab es immer Gr?nde mich davor zu dr?cken, auch da fcgi(d) wieder neu eingerichtet werden muss (sollte) ) Nun zum Problem: Mit einer Neu-Installation (Debian Squeeze mit Froxlor (Image)) bekomme ich genau den gleichen Fehler. (E-Mail Konto wurde dem Benutzer eingerichtet) Woran k?nnte dies liegen? Ich wei? leider nicht mehr weiter und bitte um Hilfe. Hat jemand eine Idee? Vielen Dank im voraus
×
×
  • Create New...