Re: Cached postscreen blacklist bypass
On 2020-07-14 09:29, Michael Orlitzky wrote: It appears that the blacklist entry is superseded by the cache? ... Is that intentional? Fixable? Work-aroundable? On 15.07.20 09:25, Michael Orlitzky wrote: For posterity: digging into the source led me to discover the You apparently missed my reply to your mail; It's in the archives: https://marc.info/?l=postfix-users=159473514401531=2 postscreen_blacklist_action (default: ignore) parameter that was new to me. Setting it to "enforce" or "drop" makes postscreen reject these connections. I recomment using enforce. Drop makes clients retry. -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. I wonder how much deeper the ocean would be without sponges.
Re: Cached postscreen blacklist bypass
Michael Orlitzky: > On 2020-07-14 09:29, Michael Orlitzky wrote: > > It appears that the blacklist entry is superseded by the cache? > > > > ... > > > > Is that intentional? Fixable? Work-aroundable? > > > > For posterity: digging into the source led me to discover the > > postscreen_blacklist_action (default: ignore) > > parameter that was new to me. Setting it to "enforce" or "drop" makes > postscreen reject these connections. This is documented, in http://www.postfix.org/POSTSCREEN_README.html "The postscreen_blacklist_action parameter specifies the action that is taken next." And that text links to http://www.postfix.org/postconf.5.html#postscreen_blacklist_action Wietse
Re: Cached postscreen blacklist bypass
On 2020-07-14 09:29, Michael Orlitzky wrote: > It appears that the blacklist entry is superseded by the cache? > > ... > > Is that intentional? Fixable? Work-aroundable? > For posterity: digging into the source led me to discover the postscreen_blacklist_action (default: ignore) parameter that was new to me. Setting it to "enforce" or "drop" makes postscreen reject these connections.
Re: User doesn't exist via lmtp
Hello! Matus UHLAR - fantomas schrieb am 15.07.20 um 13:28:02 Uhr: > >The local user exists as andr...@dualbit.de. What is the problem? > > andr...@dualbit1.dualbit.de it different than andr...@dualbit.de > > either the doveco must accept dualbit1.dualbit.de same as dualbit.de or you > need alias andr...@dualbit1.dualbit.de to andr...@dualbit.de > ... or maybe vice versa, stop aliasing andr...@dualbit.de to > andr...@dualbit1.dualbit.de > > >Is it possible to use only the domainpart in users address to deliver mail? > > you apparently mean only the localpart, and I think it's not posible. Thank you! Setting myorigin = $mydomain solved it. No need to alias something. Andreas
Re: User doesn't exist via lmtp
On 15.07.20 13:22, ratatouille wrote: mail_version = 3.3.1 I am blind at the moment. I configured postfix and dovecot to deliver via lmtp to a users local mailbox and get Jul 15 13:14:40 dualbit1 postfix/lmtp[8901]: 173C931068B4: to=, orig_to=, relay=dualbit1.dualbit.de[private/dovecot-lmtp], delay=0.23, delays=0.12/0.01/0.02/0.08, dsn=4.1.1, status=SOFTBOUNCE (host dualbit1.dualbit.de[private/dovecot-lmtp] said: 550 5.1.1 User doesn't exist: andr...@dualbit1.dualbit.de (in reply to RCPT TO command)) The local user exists as andr...@dualbit.de. What is the problem? andr...@dualbit1.dualbit.de it different than andr...@dualbit.de either the doveco must accept dualbit1.dualbit.de same as dualbit.de or you need alias andr...@dualbit1.dualbit.de to andr...@dualbit.de ... or maybe vice versa, stop aliasing andr...@dualbit.de to andr...@dualbit1.dualbit.de Is it possible to use only the domainpart in users address to deliver mail? you apparently mean only the localpart, and I think it's not posible. -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. I drive way too fast to worry about cholesterol.
User doesn't exist via lmtp
Hello! mail_version = 3.3.1 I am blind at the moment. I configured postfix and dovecot to deliver via lmtp to a users local mailbox and get Jul 15 13:14:40 dualbit1 postfix/lmtp[8901]: 173C931068B4: to=, orig_to=, relay=dualbit1.dualbit.de[private/dovecot-lmtp], delay=0.23, delays=0.12/0.01/0.02/0.08, dsn=4.1.1, status=SOFTBOUNCE (host dualbit1.dualbit.de[private/dovecot-lmtp] said: 550 5.1.1 User doesn't exist: andr...@dualbit1.dualbit.de (in reply to RCPT TO command)) The local user exists as andr...@dualbit.de. What is the problem? Is it possible to use only the domainpart in users address to deliver mail? This is postconf -n alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases command_directory = /usr/sbin compatibility_level = 2 daemon_directory = /usr/libexec/postfix data_directory = /var/lib/postfix debug_peer_level = 2 debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin ddd $daemon_directory/$process_name $process_id & sleep 5 home_mailbox = Maildir/ html_directory = no inet_interfaces = all inet_protocols = all mail_owner = postfix mailbox_transport = lmtp:unix:private/dovecot-lmtp mailq_path = /usr/bin/mailq.postfix manpage_directory = /usr/share/man meta_directory = /etc/postfix mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain, newaliases_path = /usr/bin/newaliases.postfix queue_directory = /var/spool/postfix readme_directory = /usr/share/doc/postfix/README_FILES sample_directory = /usr/share/doc/postfix/samples sendmail_path = /usr/sbin/sendmail.postfix setgid_group = postdrop shlib_directory = /usr/lib64/postfix smtp_tls_CAfile = /etc/pki/tls/certs/ca-bundle.crt smtp_tls_CApath = /etc/pki/tls/certs smtp_tls_security_level = may smtpd_tls_cert_file = /etc/pki/tls/certs/postfix.pem smtpd_tls_key_file = /etc/pki/tls/private/postfix.key smtpd_tls_security_level = may soft_bounce = yes unknown_local_recipient_reject_code = 550 Thank you for any hint! Andreas
