Mail Probleme

KayNoise · Feb 26, 2019

Hallo zusammen, und sorry erstmal bin noch realtiv neu im Linux/ Plesk Systemen und kenne mich noch nicht zu 100% aus. Aber dennoch hoffe ich Ihr könnt mir weiterhelfen. Ich habe ein Problem mit meinem Mail Server (QMail/ Dovecot) in Plesk 17.8.11 auf einem Ubuntu 16.04.
Folgender Fehler tritt auf, SMTP Server läuft und man kann sich auch verbinden, allerdings empfange und kann keine Mails mehr verschicken. Wenn ich mir selber eine Mail schicke bekomme ich folgendes zurück:

I'm sorry to have to inform you that your message could not
be delivered to one or more recipients.

<DOMAIN.XY>: host DOMAIN.XY[XXXX] said: 451 qq
temporary problem (#4.3.0) (in reply to end of DATA command)
Reporting-MTA: dns; XXX
X-Postfix-Queue-ID: D82AEAXXXX
X-Postfix-Sender: rfc822; DOMAIN.XY
Arrival-Date: Mon, 25 Feb 2019 08:47:19 +0000 (UTC)

Final-Recipient: rfc822; DOMAIN.XY
Original-Recipient: rfc822;DOMAIN.XY
Action: failed
Status: 4.0.0
Remote-MTA: dns; DOMAIN.XY
Diagnostic-Code: smtp; 451 qq temporary problem (#4.3.0)

Mail Log (/var/log)

Datei maillog:

Feb 26 05:39:01 XXXX qmail: 1551155941.043369 starting delivery 27: msg 330965087 to local XXXX
Feb 26 05:39:01 XXXX qmail: 1551155941.043413 status: local 1/10 remote 0/20
Feb 26 05:39:01 XXXX qmail: 1551155941.044995 delivery 27: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/
Feb 26 05:39:01 XXXX qmail: 1551155941.045008 status: local 0/10 remote 0/20
Feb 26 05:39:33 XXXX /var/qmail/bin/relaylock[15972]: /var/qmail/bin/relaylock: mail from 194.156.126.20:11438 (not defined)

Datei mail.log:

Feb 24 19:47:48 XXXX qmail: 1551034068.987031 starting delivery 20: msg 330957402 to local XXX
Feb 24 19:47:48 XXXX qmail: 1551034068.987077 status: local 1/10 remote 0/20
Feb 24 19:47:48 XXXX qmail: 1551034068.987170 delivery 20: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/
Feb 24 19:47:48 XXXX qmail: 1551034068.987181 status: local 0/10 remote 0/20
Feb 24 19:48:14 XXXX /var/qmail/bin/relaylock[11341]: /var/qmail/bin/relaylock: mail from 84.54.36.126:40776 (not defined)

Datei mail.err:

Feb 25 09:50:05 XXXX dovecot: Error: service=imap, user=XX@XX.eu, ip=[XXXX]. stat(/var/qmail/mailnames/kaynoise.eu/rooter/Maildir/.Entw&APw-rfe/tmp) failed: Permission denied (euid=30(popuser) egid=31(popuser) missing +x perm: /var/qmail/mailnames/XXXX/rooter/Maildir/.Entw&APw-rfe, dir owned by 0:2520 mode=0700)

Das sind nur ein Auszug aus den Logs, ich hoffe dort ist schon das richtige dabei. Falls nicht würde ich mich freuen wenn Ihr mir sagt was und wo ich es genau finden kann.
Ich hatte auch schon einmal versucht den Server aus zu schalten über Plesk und wieder zu starten, allerdings habe ich dann folgende Fehlermeldung erhalten (Bild im Anhang)
Dazu muss ich sagen das ich vor ca. 2 Wochen ein massives Rechte Probleme hatte daher vermute ich das es evtl. alles nur daran liegt.

Ich hoffe mir kann jemand da weiterhelfen und bedanke mich schonmal für eure Bemühungen.

PS: Plesk Repair habe ich schon versucht, hat nichts gebracht.

GwenDragon · Feb 26, 2019

Lass mal in der Shell laufen:
plesk repair installation

KayNoise · Feb 27, 2019

Guten Morgen, danke für die schnelle Info. Habe ich durchlaufen lassen.

===> Cumulative upgrade and repair of Plesk database (revertable stage) has been completed.
===> Plesk database scheme upgrade has been started.
Applying migrations from: /opt/psa/bootstrapper/pp17.8.11-bootstrapper/migrations/
===> Plesk database scheme upgrade has been completed.
===> Cumulative Plesk upgrade and repair (final stage) has been started.
===> Preparing Plesk upgrade (final stage).
Stopping sw_engine service... done
sed: can't read /etc/postfix/master.cf: No such file or directory
===> Plesk was not upgraded completely. See installation log for details.
Reconfiguring mail subsystem...
Reconfiguring Apache web server...
Reconfiguring ProFTPD FTP server...
===> Configuring ProFTPD server
Reconfiguring AWStats web statistics...
Reconfiguring WatchDog...
Restoring SELinux contexts...
Synchronizing state of sw-cp-server.service with SysV init with /lib/systemd/systemd-sysv-install...
Executing /lib/systemd/systemd-sysv-install enable sw-cp-server
Synchronizing state of sw-engine.service with SysV init with /lib/systemd/systemd-sysv-install...
Executing /lib/systemd/systemd-sysv-install enable sw-engine
Synchronizing state of qmail.service with SysV init with /lib/systemd/systemd-sysv-install...
Executing /lib/systemd/systemd-sysv-install enable qmail
Synchronizing state of dovecot.service with SysV init with /lib/systemd/systemd-sysv-install...
Executing /lib/systemd/systemd-sysv-install enable dovecot
Synchronizing state of psa.service with SysV init with /lib/systemd/systemd-sysv-install...
Executing /lib/systemd/systemd-sysv-install enable psa
Synchronizing state of networking.service with SysV init with /lib/systemd/systemd-sysv-install...
Executing /lib/systemd/systemd-sysv-install enable networking
Reconfiguring SSL ciphers and protocols...
Regenerating web servers' configuration files...
Cleaning active Panel sessions...
Fixing permissions on Panel packages files
WARNING:failed to get permissions for package diverts others to: /usr/lib/apache2/modules/mod_proxy.so.orig from package /var/cache/apt/archives/libapache2-mod-proxy-psa_2.4.18-ubuntu16.04.17100418_amd64.deb
WARNING:failed to get permissions for package diverts others to: /usr/lib/apache2/modules/mod_proxy_fcgi.so.orig from package /var/cache/apt/archives/libapache2-mod-proxy-psa_2.4.18-ubuntu16.04.17100418_amd64.deb
Creating non-existing directory '/run/fail2ban'
Changing permissions on /run/fail2ban to 0755
Creating non-existing directory '/run/lock/files'
Changing group on /run/lock/files to psaadm (1000)
Changing permissions on /run/lock/files to 0770
Changing owner on /var/qmail/bin/qmail-queue to mhandlers-user (31)
Changing group on /var/qmail/bin/qmail-queue to popuser (31)
Changing permissions on /var/qmail/bin/qmail-queue to 02511
Changing owner on /var/qmail/bin/qmail-remote to mhandlers-user (31)
Changing group on /var/qmail/bin/qmail-remote to popuser (31)
Changing permissions on /var/qmail/bin/qmail-remote to 02511

Bootstrapper repair finished.
Errors occurred while performing the following actions: cumulative Plesk upgrade and repair final stage, restore mail.
Check '/var/log/plesk/install/plesk_17.8.11_repair.log' and '/var/log/plesk/install/plesk_17.8.11_repair_problems.log' for details.
If you can't resolve the issue on your own, please address Plesk support.

exit status 1

Das sagt die Repair log:

START Bootstrapper 17.8.11 repair AT Sat Feb 23 21:15:49 CET 2019

**** Product repair started.

===> Checking for previous installation ... found.
Started bootstrapper repair procedure (fast mode). This may take a while.
Certain actions may be skipped if not applicable.

Trying to start service mysql... /usr/sbin/mysqld (pid 497) is running...
done
Trying to establish test connection... connected
done
Trying to find psa database... version is 017008011
Trying to backup MySQL database... done
MySQL databases are dumped to /var/lib/psa/dumps/mysql.preupgrade.17.8.11-17.8.11.20190223-211549.dump.gz
Finishing up upgrade procedures and rerunning previously failed upgrade actions...
Checking for the group 'lock-manager'...
Trying to add supplementary group 'lock-manager' for user 'psaadm'... already there
===> Cumulative APS controller database (apsc) upgrade and repair has been started.
Upgrade or repair for 'apsc' (stage 'prep') is not required
Trying to backup MySQL database... done
MySQL databases are dumped to /var/lib/psa/dumps/mysql.preupgrade.apsc.17.8.11-17.8.11.20190223-211556.dump.gz
===> Cumulative upgrade and repair of APS controller database has been completed.
Connection to APSC DB is possible
===> Cumulative APS controller upgrade and repair (final stage) has been started.
Upgrade or repair for 'apsc' (stage 'post') is not required
===> Cumulative upgrade and repair of APS controller (final stage) has been completed.
Trying to reset database user password for 'pma_LMhNK93_RAVY@'... done
===> Cumulative Plesk database upgrade and repair (revertable stage) has been started.
Upgrade or repair for 'core' (stage 'prep') is not required
===> Preparing Plesk database upgrade (revertable stage).

Trying to set psa database version to 017008011... done
===> Cumulative upgrade and repair of Plesk database (revertable stage) has been completed.
===> Plesk database scheme upgrade has been started.
===> Plesk database scheme upgrade has been completed.
done
===> Cumulative Plesk upgrade and repair (final stage) has been started.
===> Preparing Plesk upgrade (final stage).
After end of upgrade for 'core' (stage 'post') following actions are registered as failed: 20171214123200-set_recipient_address_mapper_17_8_9 20171214123200-set_recipient_address_mapper_17_8_9.
===> Plesk was not upgraded completely. See installation log for details.
Trying to upgrade and repair Horde webmail configuration... Upgrade or repair for 'horde' (stage 'files') is not required
done
Trying to upgrade and repair Fail2Ban configuration (bootstrapper-prep stage)... Upgrade or repair for 'fail2ban' (stage 'bootstrapper-prep') is not required
done
Trying to upgrade and repair Fail2Ban configuration (bootstrapper-post stage)... Upgrade or repair for 'fail2ban' (stage 'bootstrapper-post') is not required
done
Trying to upgrade and repair Firewall service configuration... Upgrade or repair for 'firewall' (stage 'post') is not required
done
Reconfiguring Apache web server...
Reconfiguring ProFTPD FTP server...
Reconfiguring AWStats web statistics...
Reconfiguring WatchDog...
Restoring SELinux contexts...
Trying to register service sw-cp-server... done
Trying to register service sw-engine... done
Trying to register service qmail... done
Trying to register service dovecot... done
Trying to register service psa... done
Trying to register service networking... done
Reconfiguring SSL ciphers and protocols...
Trying to configure SSL ciphers and protocols for: ... done
Cleaning active Panel sessions...
Fixing permissions on Panel packages files

Bootstrapper repair finished.
Errors occurred while performing the following actions: cumulative Plesk upgrade and repair final stage.
Check '/var/log/plesk/install/plesk_17.8.11_repair.log' and '/var/log/plesk/install/plesk_17.8.11_repair_problems.log' for details.
If you can't resolve the issue on your own, please address Plesk support.

**** Product repair completed successfully.

STOP Bootstrapper 17.8.11 repair AT Sat Feb 23 21:16:56 CET 2019
START Bootstrapper 17.8.11 repair AT Sat Feb 23 21:37:37 CET 2019
Started bootstrapper repair procedure (fast mode). This may take a while.
Certain actions may be skipped if not applicable.

/usr/sbin/mysqld (pid 479) is running...
Finishing up upgrade procedures and rerunning previously failed upgrade actions...
Trying to allow INNODB engine... done
Restarting mysql Trying to restart service mysql... done

**** Turn mysql-innodb VPS optimized aspect off: completed successfully.

===> Cumulative APS controller database (apsc) upgrade and repair has been started.
===> Cumulative upgrade and repair of APS controller database has been completed.
Connection to APSC DB is possible
===> Cumulative APS controller upgrade and repair (final stage) has been started.
===> Cumulative upgrade and repair of APS controller (final stage) has been completed.
===> Cumulative Plesk database upgrade and repair (revertable stage) has been started.
===> Preparing Plesk database upgrade (revertable stage).
===> Cumulative upgrade and repair of Plesk database (revertable stage) has been completed.
===> Plesk database scheme upgrade has been started.
===> Plesk database scheme upgrade has been completed.
===> Cumulative Plesk upgrade and repair (final stage) has been started.
===> Preparing Plesk upgrade (final stage).
===> Plesk was not upgraded completely. See installation log for details.
Reconfiguring Apache web server...
Reconfiguring ProFTPD FTP server...
Reconfiguring AWStats web statistics...
Reconfiguring WatchDog...
Restoring SELinux contexts...
Reconfiguring SSL ciphers and protocols...
Cleaning active Panel sessions...
Fixing permissions on Panel packages files

Bootstrapper repair finished.
Errors occurred while performing the following actions: cumulative Plesk upgrade and repair final stage.
Check '/var/log/plesk/install/plesk_17.8.11_repair.log' and '/var/log/plesk/install/plesk_17.8.11_repair_problems.log' for details.
If you can't resolve the issue on your own, please address Plesk support.
STOP Bootstrapper 17.8.11 repair AT Sat Feb 23 21:38:45 CET 2019
START Bootstrapper 17.8.11 repair AT Wed Feb 27 08:20:08 CET 2019

**** Product repair started.

===> Checking for previous installation ... found.
Started bootstrapper repair procedure. This may take a while.
Certain actions may be skipped if not applicable.

Trying to start service mysql... /usr/sbin/mysqld (pid 493) is running...
done
Trying to establish test connection... connected
done
Trying to find psa database... version is 017008011
Trying to backup MySQL database... done
MySQL databases are dumped to /var/lib/psa/dumps/mysql.preupgrade.17.8.11-17.8.11.20190227-082009.dump.gz
Finishing up upgrade procedures and rerunning previously failed upgrade actions...
Checking for the group 'lock-manager'...
Trying to add supplementary group 'lock-manager' for user 'psaadm'... already there
===> Cumulative APS controller database (apsc) upgrade and repair has been started.
Upgrade or repair for 'apsc' (stage 'prep') is not required
Trying to backup MySQL database... done
MySQL databases are dumped to /var/lib/psa/dumps/mysql.preupgrade.apsc.17.8.11-17.8.11.20190227-082015.dump.gz
===> Cumulative upgrade and repair of APS controller database has been completed.
Connection to APSC DB is possible
===> Cumulative APS controller upgrade and repair (final stage) has been started.
Upgrade or repair for 'apsc' (stage 'post') is not required
===> Cumulative upgrade and repair of APS controller (final stage) has been completed.
Trying to reset database user password for 'pma_LMhNK93_RAVY@'... done
===> Cumulative Plesk database upgrade and repair (revertable stage) has been started.
Upgrade or repair for 'core' (stage 'prep') is not required
===> Preparing Plesk database upgrade (revertable stage).

Trying to set psa database version to 017008011... done
===> Cumulative upgrade and repair of Plesk database (revertable stage) has been completed.
===> Plesk database scheme upgrade has been started.
===> Plesk database scheme upgrade has been completed.
done
===> Cumulative Plesk upgrade and repair (final stage) has been started.
===> Preparing Plesk upgrade (final stage).
After end of upgrade for 'core' (stage 'post') following actions are registered as failed: 20171214123200-set_recipient_address_mapper_17_8_9 20171214123200-set_recipient_address_mapper_17_8_9 20171214123200-set_recipient_address_mapper_17_8_9 20171214123200-set_recipient_address_mapper_17_8_9.
===> Plesk was not upgraded completely. See installation log for details.
Trying to upgrade and repair Horde webmail configuration... Upgrade or repair for 'horde' (stage 'files') is not required
done
Trying to upgrade and repair Fail2Ban configuration (bootstrapper-prep stage)... Upgrade or repair for 'fail2ban' (stage 'bootstrapper-prep') is not required
done
Trying to upgrade and repair Fail2Ban configuration (bootstrapper-post stage)... Upgrade or repair for 'fail2ban' (stage 'bootstrapper-post') is not required
done
Trying to upgrade and repair Firewall service configuration... Upgrade or repair for 'firewall' (stage 'post') is not required
done
Reconfiguring mail subsystem...
Trying to execute mail_restore to synchronize mail server settings and Plesk Database... ==> Checking for: mailsrv_conf_init... fail
Reconfiguring Apache web server...
Reconfiguring ProFTPD FTP server...
Reconfiguring AWStats web statistics...
Reconfiguring WatchDog...
Restoring SELinux contexts...
Trying to register service sw-cp-server... done
Trying to register service sw-engine... done
Trying to register service qmail... done
Trying to register service dovecot... done
Trying to register service psa... done
Trying to register service networking... done
Reconfiguring SSL ciphers and protocols...
Trying to configure SSL ciphers and protocols for: ... done
Regenerating web servers' configuration files...
Cleaning active Panel sessions...
Fixing permissions on Panel packages files

Bootstrapper repair finished.
Errors occurred while performing the following actions: cumulative Plesk upgrade and repair final stage, restore mail.
Check '/var/log/plesk/install/plesk_17.8.11_repair.log' and '/var/log/plesk/install/plesk_17.8.11_repair_problems.log' for details.
If you can't resolve the issue on your own, please address Plesk support.

**** Product repair completed successfully.

STOP Bootstrapper 17.8.11 repair AT Wed Feb 27 08:21:29 CET 2019

Leider kann ich meine Mails immer noch nicht abrufen und auch nichts versenden. Aber verbunden mit dem Server bin ich.

EDIT: jetzt kann ich mich wieder nicht verbinden. Fehler angehangen.

mr_brain · Feb 27, 2019

"Plesk was not upgraded completely"

Auf der Shell mal den "plesk-installer" laufen lassen und alles updaten.

GwenDragon · Feb 27, 2019

Ich weiß gerade nicht ob plesk repair fs bei deinem Rechteproblem helfen würde.

Ansonsten prüfe bitte mal deine Rechte im Mailverzeichnis.

Code:

/var/qmail/mailnames                    root:root 0755
/var/qmail/mailnames/DOMAIN.TLD            popupser:popuser 0750
/var/qmail/mailnames/DOMAIN.TLD/info    popupser:popuser 0700

KayNoise · Feb 27, 2019

mr_brain said:
"Plesk was not upgraded completely"

Auf der Shell mal den "plesk-installer" laufen lassen und alles updaten.

Danke dir erstmal für die Antwort.
Jetzt kurz zwei fragen, einfach in der Shell "plesk-installer" eingeben oder?
Dann noch eins, überschreibt er mir dann alle vorhandenen Informationen oder Installiert er einfach nur die Infos und übernimmt die Daten?

GwenDragon · Feb 27, 2019

Der Pleskinstaller löscht dir nichts an Daten.

Shell öffnen und jeweils:
plesk installer update
plesk installer upgrade

KayNoise · Feb 27, 2019

Guten Abend zusammen, also ich bin nun so weit das ich mich wieder verbinden kann, allerdings nichts synchronisiert wird oder abgerufen.
Ich habe einmal den Plesk Insaller laufen lassen und hatte danach einmal qmail gelöscht und wieder installiert.
Meine Vermutung liegt darin das entweder etwas mit dem SMTP Server oder mit den Rechten der Postfächer nicht stimmt.

mr_brain · Feb 27, 2019

Naja, dann hätteste eh auf gleich auf Postfix umstellen können. Meiner Meinung der besser SMTP ... ins besonders beim Debuggen bei Problemen.

KayNoise · Feb 27, 2019

mr_brain said:
Naja, dann hätteste eh auf gleich auf Postfix umstellen können. Meiner Meinung der besser SMTP ... ins besonders beim Debuggen bei Problemen.

hätte ich ja auch gemacht wenn nicht noch wichtige mails im Postfach wären die ich gerade nicht abrufen kann. Außer man kann das irgendwie komplett umziehen. Weil der Empfang von Mails hat teilweise ja funktioniert ich konnte sie nur nicht Syncen.

GwenDragon · Feb 27, 2019

KayNoise said:
bin nun so weit das ich mich wieder verbinden kann, allerdings nichts synchronisiert wird oder abgerufen.

Ja, aber das ist nicht viel Information.
Was zeigt das Log zu dem Zeitpunkt für qmail und dovecot?

mr_brain · Feb 27, 2019

KayNoise said:
hätte ich ja auch gemacht wenn nicht noch wichtige mails im Postfach wären die ich gerade nicht abrufen kann. Außer man kann das irgendwie komplett umziehen.

Ja, geht. Es sollten nur keine Emails in der mailq sein. https://support.plesk.com/hc/en-us/...n-the-server-with-Plesk-and-how-to-switch-it-

KayNoise · Feb 27, 2019

qMail:

Feb 27 20:38:38 XXX dovecot: imap-login: Login: user=<ipad@XXX.eu>, method=CRAM-MD5, rip=, lip=, mpid=1730, TLS, session=<yaL6UeWCUP9d9EW+>
Feb 27 20:38:38 XXX dovecot: imap-login: Login: user=<verleih@XXX.eu>, method=CRAM-MD5, rip=, lip=., mpid=1731, TLS, session=<gaf6UeWCUf9d9EW+>
Feb 27 20:38:38 XXX dovecot: imap-login: Login: user=<feedback@XXX.eu>, method=CRAM-MD5, rip=, lip=, mpid=1732, TLS, session=<Bar6UeWCVP9d9EW+>
Feb 27 20:38:38 XXX dovecot: imap-login: Login: user=<support@XXX.eu>, method=CRAM-MD5, rip=, lip=, mpid=1733, TLS, session=<v6n6UeWCU/9d9EW+>
Feb 27 20:38:38 XXX dovecot: imap-login: Login: user=<booking@XXX.eu>, method=CRAM-MD5, rip=, lip=, mpid=1734, TLS, session=<V/37UeWCXv9d9EW+>
Feb 27 20:38:38 XXX dovecot: imap-login: Login: user=<promo@XXX.eu>, method=CRAM-MD5, rip=, lip=, mpid=1735, TLS, session=<c/b7UeWCV/9d9EW+>
Feb 27 20:38:38 XXX dovecot: imap-login: Login: user=<nas@XXX.eu>, method=CRAM-MD5, rip=, lip=, mpid=1736, TLS, session=<DxT8UeWCWv9d9EW+>
Feb 27 20:38:38 XXX dovecot: imap-login: Login: user=<office@XXX.eu>, method=CRAM-MD5, rip=, lip=, mpid=1737, TLS, session=<Df37UeWCXf9d9EW+>
Feb 27 20:38:38 XXX dovecot: imap-login: Login: user=<rooter@XXX.eu>, method=CRAM-MD5, rip=, lip=, mpid=1738, TLS, session=<wfv7UeWCWf9d9EW+>
Feb 27 20:40:02 XXX /var/qmail/bin/relaylock[1821]: /var/qmail/bin/relaylock: mail from (not defined)
Feb 27 20:40:02 XXX smtp_auth[1822]: SMTP connect from unknown []
Feb 27 20:40:02 XXX smtp_auth[1822]: Invalid mail address 'julia'
Feb 27 20:40:02 XXX smtp_auth[1822]: FAILED: julia - password incorrect from (null) []
Feb 27 20:42:41 XXX /var/qmail/bin/relaylock[1838]: /var/qmail/bin/relaylock: mail from (not defined)
Feb 27 20:42:41 XXX smtp_auth[1839]: SMTP connect from unknown []
Feb 27 20:42:41 XXX smtp_auth[1839]: No such user 'office@stratoserver.net' in mail authorization database
Feb 27 20:42:41 XXX smtp_auth[1839]: FAILED: office@stratoserver.net - password incorrect from (null) []
Feb 27 20:44:09 XXX /var/qmail/bin/relaylock[1875]: /var/qmail/bin/relaylock: mail from ()
Feb 27 20:44:10 XXX qmail-queue-handlers[1880]: Handlers Filter before-queue for qmail started ...
Feb 27 20:44:10 XXX qmail-queue-handlers[1880]: from=XXX@icloud.com
Feb 27 20:44:10 XXX qmail-queue-handlers[1880]: to=XXX@XXX.eu
Feb 27 20:44:10 XXX check-quota[1881]: Starting the check-quota filter...
Feb 27 20:44:10 XXX qmail-queue-handlers[1880]: handlers_stderr: SKIP
Feb 27 20:44:10 XXX qmail-queue-handlers[1880]: SKIP during call 'check-quota' handler
Feb 27 20:44:10 XXX qmail-queue-handlers[1880]: starter: submitter[1882] exited normally
Feb 27 20:44:10 XXX qmail: 1551296650.569029 new msg 330957404
Feb 27 20:44:10 XXX qmail: 1551296650.569059 info msg 330957404: bytes 1777 from <XXX@icloud.com> qp 1882 uid 2020
Feb 27 20:44:10 XXX qmail: 1551296650.718517 starting delivery 4: msg 330957404 to local XXX.eu-XXX@XXX.eu
Feb 27 20:44:10 XXX qmail: 1551296650.718547 status: local 1/10 remote 0/20
Feb 27 20:44:10 XXX qmail-local-handlers[1883]: Handlers Filter before-local for qmail started ...
Feb 27 20:44:10 XXX qmail-local-handlers[1883]: from=XXX@icloud.com
Feb 27 20:44:10 XXX qmail-local-handlers[1883]: to=XXX@XXX.eu
Feb 27 20:44:10 XXX qmail-local-handlers[1883]: mailbox: /var/qmail/mailnames/XXX.eu/XXX
Feb 27 20:44:10 XXX qmail: 1551296650.791687 delivery 4: deferral: Uh-oh:_.qmail_has_prog_delivery_but_has_x_bit_set._(#4.7.0)/
Feb 27 20:44:10 XXX qmail: 1551296650.791713 status: local 0/10 remote 0/20
Feb 27 20:44:39 XXX /var/qmail/bin/relaylock[1906]: /var/qmail/bin/relaylock: mail from 185.234.217.220:49266 (not defined)
Feb 27 20:44:40 XXX smtp_auth[1929]: SMTP connect from unknown []
Feb 27 20:44:40 XXX smtp_auth[1929]: Invalid mail address 'maureen'
Feb 27 20:44:40 XXX smtp_auth[1929]: FAILED: maureen - password incorrect from (null) []
Feb 27 20:44:48 XXX dovecot: pop3-login: Aborted login (auth failed, 1 attempts in 2 secs): user=<support@XXX.eu>, method=PLAIN, rip=, lip=, session=<l0DsZ+WCTH5Z+Kw3>
Feb 27 20:45:46 XXX qmail: 1551296746.887046 starting delivery 5: msg 330957051 to local XXX.eu-XXX@XXX.eu
Feb 27 20:45:46 XXX qmail: 1551296746.887076 status: local 1/10 remote 0/20
Feb 27 20:45:46 XXX qmail-local-handlers[1948]: Handlers Filter before-local for qmail started ...
Feb 27 20:45:47 XXX qmail-local-handlers[1948]: from=XXX@icloud.com
Feb 27 20:45:47 XXX qmail-local-handlers[1948]: to=XXX@XXX.eu
Feb 27 20:45:47 XXX qmail-local-handlers[1948]: mailbox: /var/qmail/mailnames/XXX.eu/XXX
Feb 27 20:45:47 XXX qmail: 1551296747.034740 delivery 5: deferral: Uh-oh:_.qmail_has_prog_delivery_but_has_x_bit_set._(#4.7.0)/
Feb 27 20:45:47 XXX qmail: 1551296747.034768 status: local 0/10 remote 0/20
Feb 27 20:45:51 XXX qmail: 1551296751.038219 starting delivery 6: msg 330957404 to local XXX.eu-XXX@XXX.eu
Feb 27 20:45:51 XXX qmail: 1551296751.038251 status: local 1/10 remote 0/20
Feb 27 20:45:51 XXX qmail-local-handlers[1949]: Handlers Filter before-local for qmail started ...
Feb 27 20:45:51 XXX qmail-local-handlers[1949]: from=XXX@icloud.com
Feb 27 20:45:51 XXX qmail-local-handlers[1949]: to=XXX@XXX.eu
Feb 27 20:45:51 XXX qmail-local-handlers[1949]: mailbox: /var/qmail/mailnames/XXX.eu/XXX
Feb 27 20:45:51 XXX qmail: 1551296751.134289 delivery 6: deferral: Uh-oh:_.qmail_has_prog_delivery_but_has_x_bit_set._(#4.7.0)/
Feb 27 20:45:51 XXX qmail: 1551296751.134309 status: local 0/10 remote 0/20
Feb 27 20:46:21 XXX /var/qmail/bin/relaylock[1950]: /var/qmail/bin/relaylock: mail from (not defined)
Feb 27 20:46:21 XXX smtp_auth[1951]: SMTP connect from unknown []
Feb 27 20:46:21 XXX smtp_auth[1951]: Invalid mail address 'scanuser'
Feb 27 20:46:21 XXX smtp_auth[1951]: FAILED: scanuser - password incorrect from (null) []

Dovecot hat keinen separaten Log oder habe ich das da irgendwo übersehen?

Hoffe man kann damit was anfangen.

Mail Probleme

KayNoise

Guest

Attachments

GwenDragon

Registered User

KayNoise

Guest

Attachments

mr_brain

Registered User

GwenDragon

Registered User

KayNoise

Guest

GwenDragon

Registered User

KayNoise

Guest

mr_brain

Registered User

KayNoise

Guest

GwenDragon

Registered User

mr_brain

Registered User

KayNoise

Guest