[pfx] Re: smtp code 450 and delivery to secondary MX

On 2023-04-18 12:49, Viktor Dukhovni via Postfix-users wrote: On Tue, Apr 18, 2023 at 10:35:22AM +0800, tom--- via Postfix-users wrote: So my question is, smtp code 450 will cause the sender to retry delivery to secondary MX? Yes, if the client is a legitimate MTA, less common with a junk-s

[pfx] Re: smtp code 450 and delivery to secondary MX

Note that reject_unknown_client_hostname is a very strict test that is likely to reject legit mail. Consider using reject_unknown_reverse_client_hostname instead. Do you know where I can set the action code 550 for this directive? Thanks. ___

[pfx] Re: smtp code 450 and delivery to secondary MX

On Tue, Apr 18, 2023 at 10:35:22AM +0800, tom--- via Postfix-users wrote: > So my question is, smtp code 450 will cause the sender to retry delivery > to secondary MX? Yes, if the client is a legitimate MTA, less common with a junk-sending botnet. Once you're confident your restriction settings

[pfx] Re: is localhost.localdomain a FQDN?

On 4/17/2023 9:19 PM, tom--- via Postfix-users wrote: I saw many peer MTA connecting me with this default HELO hostname: localhost.localdomain. is this a FQDN? is it valid? Yes, it's FQDN and valid from a syntax standpoint. That said, it's a strong spam indicator and should never be seen fro

[pfx] Re: is localhost.localdomain a FQDN?

On Tue, Apr 18, 2023 at 10:19:58AM +0800, tom--- via Postfix-users wrote: > I saw many peer MTA connecting me with this default HELO hostname: > localhost.localdomain. > > Is this a FQDN? Yes, it is a fully-qualified domain name. > Is it valid? Depends on your perspective. This FQDN does not

[pfx] Re: smtp code 450 and delivery to secondary MX

On 4/17/2023 9:35 PM, tom--- via Postfix-users wrote: When my main postfix rejected a message due to reject_unknown_client_hostname: Apr 18 10:27:12 mail postfix/smtpd[129429]: NOQUEUE: reject: RCPT from unknown[194.33.39.17]: 450 4.7.25 Client host rejected: cannot find your hostname, [194.3

[pfx] Re: is localhost.localdomain a FQDN?

On 4/17/23 22:19, tom--- via Postfix-users wrote: I saw many peer MTA connecting me with this default HELO hostname: localhost.localdomain. is this a FQDN? is it valid? No properly configured MTA should ever be advertising its identity as localhost.localdomain. Assuming it is that literal str

[pfx] smtp code 450 and delivery to secondary MX

When my main postfix rejected a message due to reject_unknown_client_hostname: Apr 18 10:27:12 mail postfix/smtpd[129429]: NOQUEUE: reject: RCPT from unknown[194.33.39.17]: 450 4.7.25 Client host rejected: cannot find your hostname, [194.33.39.17]; from= to= proto=ESMTP helo= I found this m

[pfx] is localhost.localdomain a FQDN?

I saw many peer MTA connecting me with this default HELO hostname: localhost.localdomain. is this a FQDN? is it valid? Thanks. Tom ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.o

[pfx] Re: Postfix stable release 3.8.0

On 2023-04-18 03:25, Wietse Venema via Postfix-users wrote: Postfix stable release 3.8.0 is available. Postfix 3.4..3.7 will be updated soon; after that, Postfix 3.4 will no longer be updated. The main changes are below. See the RELEASE_NOTES file for further details. * Support to look up DNS

[pfx] Re: Open relay clarification

> One important information is missing here: on what port? Good catch. Port 25. > There should be no authentication on port 25 and all mail destined for local > domains should be accepted. > > There should be mandatory authentication on ports 465/587. > > As both acme.com and corley.com

[pfx] Re: temporary lookup error with utf8mb4 characters

And here is a more conservative patch for MySQL client retries. It closes the server connection after every error, and it delays making a new server connection only after specific errors. Closing the connection eliminates the possibility that the client becomes stuck. Wietse 20230417

[pfx] Re: temporary lookup error with utf8mb4 characters

>>> I've patched postfix 3.7.4 on a low volume server. >> >> Thank you! >> >>> "charset" has to be present and defined in all mysql configs, otherwise >>> startup fails: >>> (no backwards compatibility) >>> >>> postfix/proxymap[3996]: fatal: /etc/postfix/test.mysql.cf: bad string >>> length 0

[pfx] Re: temporary lookup error with utf8mb4 characters

gt; >> Is there such an API? > > > > > > Based on documentation, perhaps mysql_set_character_set() can do that. > > > https://dev.mysql.com/doc/c-api/8.0/en/mysql-set-character-set.html > > > > > > Attached is patch 20230417-mysql-charset-patch.tx

[pfx] Re: temporary lookup error with utf8mb4 characters

I don't see any option to change default charset on mysql_table > >>> connector, maybe should be interesting add this option on configuration > >>> file. > >> > >> Is there such an API? > > > > Based on documentation, perhaps mysql_set_cha

[pfx] Re: Open relay clarification

Dnia 17.04.2023 o godz. 14:49:11 Noel Jones via Postfix-users pisze: > Please keep replies on list. > > On 4/17/2023 2:16 PM, Tyler Montney wrote: > >I'll put it this way, since I'm struggling to word this: > > > >Provider A contains the following customers: > >Acme Corporation (acme.com

[pfx] Re: Open relay clarification

On 4/17/2023 3:59 PM, Tyler Montney via Postfix-users wrote: That is the purpose of this discussion, to determine what exactly this scenario presents. As stated above, Provider A is aware and believes it's acceptable. It is acceptable because their documentation has features which rely on it.

[pfx] Re: temporary lookup error with utf8mb4 characters

t;>> connector, maybe should be interesting add this option on configuration >>> file. >> >> Is there such an API? > > Based on documentation, perhaps mysql_set_character_set() can do that. > https://dev.mysql.com/doc/c-api/8.0/en/mysql-set-character-set.html > > A

[pfx] Re: Open relay clarification

> Please keep replies on list. >You've explained what's observable, but not why it's a problem. > Any random server on the internet can send to b...@corley.com without > authentication. The original sender may or may not authenticate to > *their* mail server, corley.com cannot control that. So corl

[pfx] Re: Open relay clarification

Please keep replies on list. On 4/17/2023 2:16 PM, Tyler Montney wrote: I'll put it this way, since I'm struggling to word this: Provider A contains the following customers: Acme Corporation (acme.com ) Corley Motors (corley.com ) Provider B contains the fol

[pfx] Postfix stable release 3.8.0

Postfix stable release 3.8.0 is available. Postfix 3.4..3.7 will be updated soon; after that, Postfix 3.4 will no longer be updated. The main changes are below. See the RELEASE_NOTES file for further details. * Support to look up DNS SRV records in the Postfix SMTP/LMTP client, Based on cod

[pfx] Re: Open relay clarification

On 4/17/2023 1:38 PM, Tyler Montney via Postfix-users wrote: I use a mail provider (Provider A) which has thousands of organizations. This provider allows unauthenticated SMTP to other organizations so long as they're using them as a provider (within their ecosystem). Of course, you cannot se

[pfx] Open relay clarification

Before getting started, this has been publicly disclosed by someone else a while ago. However, I still don't think it's necessary to name the organization to explain myself. My goal here is not only to give a proper argument to the provider, but also my own curiosity and research (on the workings o

[pfx] Re: temporary lookup error with utf8mb4 characters

eresting add this option on configuration > > file. > > Is there such an API? Based on documentation, perhaps mysql_set_character_set() can do that. https://dev.mysql.com/doc/c-api/8.0/en/mysql-set-character-set.html Attached is patch 20230417-mysql-charset-patch.txt that adds a "

[pfx] Re: Postfix refuses to accept email from video camera

On 16/04/2023 21:11, Viktor Dukhovni via Postfix-users wrote: > Not surprising, I suspect that the OP did not recognise the $ and # characters in your instructions as shell prompts (to be omitted from the commands being executed), and copy/pasted them into his shell as-is. HTH, Jan __

[pfx] Re: temporary lookup error with utf8mb4 characters

V?ctor Rubiella Monfort via Postfix-users: > Hi, I have more info and I try to explain it better: > > First of all I have smtputf8_enable = no (disabled). > > I have several databases related with several mysql_virtual maps: > > - Some with utf8 + utf8_general_ci collation > > - Another ones wi

[pfx] Re: header_checks not work with regexp

On 17.04.23 08:54, SysAdmin EM via Postfix-users wrote: Hello everyone the problem persists. Maybe I’m doing something wrong. Step 1, I add the rule in the /etc/postfix/header_checks file /^Subject:.*You may need to add/ DISCARD TMP_BLOCK Step 2, postmap /etc/postfix/header_checks and postfix

[pfx] Re: header_checks not work with regexp

Hello everyone the problem persists. Maybe I’m doing something wrong. Step 1, I add the rule in the /etc/postfix/header_checks file /^Subject:.*You may need to add/ DISCARD TMP_BLOCK Step 2, postmap /etc/postfix/header_checks and postfix surcharge. Are these steps correct? Could the problem oc

[pfx] Re: any web.de staff here?

Dnia 17.04.2023 o godz. 01:44:34 Gerald Galster via Postfix-users pisze: > > Common practice in Germany is: once your server accepts an email it is > responsible for delivery. You cannot silently discard it. But you can still reject a submission and not accept it in the first place. Why aren't th