pkernstock Bei dir in der Firewall, moeglich ja. Aber um Spam zu reduzieren blockt Hetzner das typischerweise (wie andere Hoster auch), was via Support Ticket freigegeben werden muss,
Das kann durchaus sein. Stimmt, davon habe ich gelesen, dass sie einige Ports zum Schutz des Nutzers eine Zeit lang sperren.
[unknown] Okay, dann werde ich das zeitnah anstoßen, dafür schon mal danke.
[unknown]
Okay, dann werde ich das zeitnah anstoßen, dafür schon mal danke.
Komisch, die Webseite gibt mir immer eine Fehlermeldung aus, wenn ich einen Post abschicke, und die Seite muss neu geladen werden.
Ups! Da ist was schief gelaufen. Bitte lade die Seite neu oder versuche es erneut.
Verspätet die Logs, ich habe allerdings keine Ahnung was das für Benutzerkonten sein sollen, die habe ich definitiv nicht
angelegt:
postfix-mailcow-1 | 2025-05-02 14:24:44,706 INFO Set uid to user 0 succeeded
postfix-mailcow-1 | 2025-05-02 14:24:44,711 INFO supervisord started with pid 1
postfix-mailcow-1 | 2025-05-02 14:24:45,717 INFO spawned: 'processes' with pid 8
postfix-mailcow-1 | 2025-05-02 14:24:45,731 INFO spawned: 'postfix' with pid 9
postfix-mailcow-1 | 2025-05-02 14:24:45,750 INFO spawned: 'syslog-ng' with pid 10
postfix-mailcow-1 | Uptime: 29 Threads: 6 Questions: 331 Slow queries: 0 Opens: 48 Open tables: 41 Queries per second avg: 11.413
postfix-mailcow-1 | May 2 14:24:46 bef8fe4212f2 syslog-ng[10]: syslog-ng starting up; version='3.38.1'
postfix-mailcow-1 | Checking if ASN for your IP is listed for Spamhaus Bad ASN List...
postfix-mailcow-1 | The AS of your IP is NOT listed as a banned AS from Spamhaus!
postfix-mailcow-1 | Using the open Spamhaus blocklists.
postfix-mailcow-1 | 2025-05-02 14:24:47,540 INFO success: processes entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
postfix-mailcow-1 | 2025-05-02 14:24:47,544 INFO success: syslog-ng entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
postfix-mailcow-1 | chown: cannot access '/usr/share/man/man1/mailq.1.gz': No such file or directory
postfix-mailcow-1 | May 2 14:24:48 bef8fe4212f2 postfix/postfix-script[342]: starting the Postfix mail system
postfix-mailcow-1 | May 2 14:24:49 bef8fe4212f2 postfix/master[344]: daemon started -- version 3.7.11, configuration /opt/postfix/conf
postfix-mailcow-1 | 2025-05-02 14:24:56,041 INFO success: postfix entered RUNNING state, process has stayed up for > than 10 seconds (startsecs)
postfix-mailcow-1 | 2025-05-02 14:25:10,059 WARN received SIGTERM indicating exit request
postfix-mailcow-1 | 2025-05-02 14:25:10,060 INFO waiting for processes, postfix, syslog-ng to die
postfix-mailcow-1 | May 2 14:25:10 bef8fe4212f2 syslog-ng[10]: syslog-ng shutting down; version='3.38.1'
postfix-mailcow-1 | 2025-05-02 14:25:10,176 INFO stopped: syslog-ng (exit status 0)
postfix-mailcow-1 | 2025-05-02 14:25:11,181 WARN stopped: postfix (terminated by SIGTERM)
postfix-mailcow-1 | 2025-05-02 14:25:11,182 INFO reaped unknown pid 344 (terminated by SIGTERM)
postfix-mailcow-1 | 2025-05-02 14:25:11,182 INFO reaped unknown pid 345 (terminated by SIGTERM)
postfix-mailcow-1 | 2025-05-02 14:25:11,182 INFO reaped unknown pid 346 (terminated by SIGTERM)
postfix-mailcow-1 | 2025-05-02 14:25:11,182 INFO reaped unknown pid 348 (terminated by SIGTERM)
postfix-mailcow-1 | 2025-05-02 14:25:11,182 INFO reaped unknown pid 349 (terminated by SIGTERM)
postfix-mailcow-1 | 2025-05-02 14:25:11,187 WARN stopped: processes (terminated by SIGTERM)
postfix-mailcow-1 | 2025-05-02 14:25:11,188 INFO reaped unknown pid 360 (exit status 0)
postfix-mailcow-1 | 2025-05-02 14:25:12,991 INFO Set uid to user 0 succeeded
postfix-mailcow-1 | 2025-05-02 14:25:13,000 INFO supervisord started with pid 1
postfix-mailcow-1 | 2025-05-02 14:25:14,006 INFO spawned: 'processes' with pid 10
postfix-mailcow-1 | 2025-05-02 14:25:14,010 INFO spawned: 'postfix' with pid 11
postfix-mailcow-1 | 2025-05-02 14:25:14,018 INFO spawned: 'syslog-ng' with pid 12
postfix-mailcow-1 | Uptime: 58 Threads: 6 Questions: 356 Slow queries: 0 Opens: 51 Open tables: 44 Queries per second avg: 6.137
postfix-mailcow-1 | May 2 14:25:14 bef8fe4212f2 syslog-ng[12]: syslog-ng starting up; version='3.38.1'
postfix-mailcow-1 | Checking if ASN for your IP is listed for Spamhaus Bad ASN List...
postfix-mailcow-1 | The AS of your IP is NOT listed as a banned AS from Spamhaus!
postfix-mailcow-1 | Using the open Spamhaus blocklists.
postfix-mailcow-1 | chown: cannot access '/usr/share/man/man1/mailq.1.gz': No such file or directory
postfix-mailcow-1 | 2025-05-02 14:25:15,941 INFO success: processes entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
postfix-mailcow-1 | 2025-05-02 14:25:15,941 INFO success: syslog-ng entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
postfix-mailcow-1 | May 2 14:25:16 bef8fe4212f2 postfix/postfix-script[344]: starting the Postfix mail system
postfix-mailcow-1 | May 2 14:25:17 bef8fe4212f2 postfix/master[346]: daemon started -- version 3.7.11, configuration /opt/postfix/conf
postfix-mailcow-1 | May 2 14:25:22 bef8fe4212f2 postfix/postscreen[359]: cache proxy:btree:/var/lib/postfix/postscreen_cache full cleanup: retained=0 dropped=0 entries
postfix-mailcow-1 | May 2 14:25:22 bef8fe4212f2 postfix/postscreen[359]: CONNECT from [172.22.1.11]:46255 to [172.22.1.253]:25
postfix-mailcow-1 | May 2 14:25:22 bef8fe4212f2 postfix/postscreen[359]: ALLOWLISTED [172.22.1.11]:46255
postfix-mailcow-1 | May 2 14:25:22 bef8fe4212f2 postfix/smtpd[361]: connect from mailcowdockerized-acme-mailcow-1.mailcowdockerized_mailcow-network[172.22.1.11]
postfix-mailcow-1 | May 2 14:25:22 bef8fe4212f2 postfix/smtpd[361]: lost connection after CONNECT from mailcowdockerized-acme-mailcow-1.mailcowdockerized_mailcow-network[172.22.1.11]
postfix-mailcow-1 | May 2 14:25:22 bef8fe4212f2 postfix/smtpd[361]: disconnect from mailcowdockerized-acme-mailcow-1.mailcowdockerized_mailcow-network[172.22.1.11] commands=0/0
postfix-mailcow-1 | May 2 14:25:22 bef8fe4212f2 postfix/postscreen[359]: CONNECT from [172.22.1.11]:56842 to [172.22.1.253]:25
postfix-mailcow-1 | May 2 14:25:22 bef8fe4212f2 postfix/postscreen[359]: ALLOWLISTED [172.22.1.11]:56842
postfix-mailcow-1 | May 2 14:25:22 bef8fe4212f2 postfix/smtpd[361]: connect from mailcowdockerized-acme-mailcow-1.mailcowdockerized_mailcow-network[172.22.1.11]
postfix-mailcow-1 | May 2 14:25:22 bef8fe4212f2 postfix/smtpd[361]: Anonymous TLS connection established from mailcowdockerized-acme-mailcow-1.mailcowdockerized_mailcow-network[172.22.1.11]: TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256
postfix-mailcow-1 | May 2 14:25:22 bef8fe4212f2 postfix/smtpd[361]: lost connection after STARTTLS from mailcowdockerized-acme-mailcow-1.mailcowdockerized_mailcow-network[172.22.1.11]
postfix-mailcow-1 | May 2 14:25:22 bef8fe4212f2 postfix/smtpd[361]: disconnect from mailcowdockerized-acme-mailcow-1.mailcowdockerized_mailcow-network[172.22.1.11] ehlo=1 starttls=1 commands=2
postfix-mailcow-1 | 2025-05-02 14:25:24,632 INFO success: postfix entered RUNNING state, process has stayed up for > than 10 seconds (startsecs)
postfix-mailcow-1 | May 2 14:25:38 bef8fe4212f2 postfix/smtps/smtpd[363]: warning: hostname hostingmailto189.statics.servermail.org does not resolve to address 193.46.255.40: Name or service not known
postfix-mailcow-1 | May 2 14:25:38 bef8fe4212f2 postfix/smtps/smtpd[363]: connect from unknown[193.46.255.40]
postfix-mailcow-1 | May 2 14:25:38 bef8fe4212f2 postfix/smtps/smtpd[363]: Anonymous TLS connection established from unknown[193.46.255.40]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)
postfix-mailcow-1 | May 2 14:25:41 bef8fe4212f2 postfix/smtps/smtpd[363]: warning: unknown[193.46.255.40]: SASL LOGIN authentication failed: (reason unavailable), sasl_username=kimberley@nicolaiwiehe.de
postfix-mailcow-1 | May 2 14:25:41 bef8fe4212f2 postfix/smtps/smtpd[363]: lost connection after AUTH from unknown[193.46.255.40]
postfix-mailcow-1 | May 2 14:25:41 bef8fe4212f2 postfix/smtps/smtpd[363]: disconnect from unknown[193.46.255.40] ehlo=1 auth=0/1 rset=1 commands=2/3
postfix-mailcow-1 | May 2 14:27:48 bef8fe4212f2 postfix/smtps/smtpd[369]: warning: hostname hostingmailto189.statics.servermail.org does not resolve to address 193.46.255.40: No address associated with hostname
postfix-mailcow-1 | May 2 14:27:48 bef8fe4212f2 postfix/smtps/smtpd[369]: connect from unknown[193.46.255.40]
postfix-mailcow-1 | May 2 14:27:49 bef8fe4212f2 postfix/smtps/smtpd[369]: Anonymous TLS connection established from unknown[193.46.255.40]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)
postfix-mailcow-1 | May 2 14:27:49 bef8fe4212f2 postfix/smtps/smtpd[369]: lost connection after EHLO from unknown[193.46.255.40]
postfix-mailcow-1 | May 2 14:27:49 bef8fe4212f2 postfix/smtps/smtpd[369]: disconnect from unknown[193.46.255.40] ehlo=1 commands=1
postfix-mailcow-1 | May 2 14:28:51 bef8fe4212f2 postfix/postscreen[373]: warning: getpeername: Transport endpoint is not connected -- dropping this connection
postfix-mailcow-1 | May 2 14:29:14 bef8fe4212f2 postfix/submission/smtpd[376]: connect from unknown[103.108.174.169]
postfix-mailcow-1 | May 2 14:29:15 bef8fe4212f2 postfix/submission/smtpd[376]: Anonymous TLS connection established from unknown[103.108.174.169] to mail.nicolaiwiehe.de: TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256
postfix-mailcow-1 | May 2 14:29:16 bef8fe4212f2 postfix/submission/smtpd[376]: lost connection after EHLO from unknown[103.108.174.169]
postfix-mailcow-1 | May 2 14:29:16 bef8fe4212f2 postfix/submission/smtpd[376]: disconnect from unknown[103.108.174.169] ehlo=2 starttls=1 commands=3
Okay, sind Bots:
02.05.2025, 14:32:21 warn 2 more attempts in the next 3600 seconds until 193.46.255.40/32 is banned
02.05.2025, 14:32:21 warn 193.46.255.40 matched rule id 3 (warning: unknown[193.46.255.40]: SASL LOGIN authentication failed: (reason unavailable), sasl_username=carolina@nicolaiwiehe.de)
02.05.2025, 14:30:04 warn 3 more attempts in the next 3600 seconds until 193.46.255.40/32 is banned
02.05.2025, 14:30:04 warn 193.46.255.40 matched rule id 3 (warning: unknown[193.46.255.40]: SASL LOGIN authentication failed: (reason unavailable), sasl_username=helena@nicolaiwiehe.de)
02.05.2025, 14:25:41 warn 4 more attempts in the next 3600 seconds until 193.46.255.40/32 is banned
02.05.2025, 14:25:41 warn 193.46.255.40 matched rule id 3 (warning: unknown[193.46.255.40]: SASL LOGIN authentication failed: (reason unavailable), sasl_username=kimberley@nicolaiwiehe.de)
