Re: Spawn milter access to Verified Sender database

Hi Wietse, The DB dump shows : londonstransport+bncbdzntlposqirbr426sgamgqeh7mv...@googlegroups.com??? 0:0:1637682515:250 2.1.5 OK s8si901258edx.4 - gsmtp There are 0xc2 0xa0 bytes at the end of the storage key, but not in your query. Apologies,  I pasted the output generated by 'postmap

RCPT info in logging

I am guessing when this happens: postfix/smtpd[879005]: connect from smtpout79.briteverify.com[54.175.215.209] postfix/smtpd[879005]: 4J0QTC1PzHz4l3gS: client=smtpout79.briteverify.com[54.175.215.209] postfix/smtpd[879005]: disconnect from smtpout79.briteverify.com[54.175.215.209]

Re: Spawn milter access to Verified Sender database

Hi Wietse, OK, the storage key is null-terminated. you may have to use a postmap option to add a null byte to the query. All the storage keys are null-terminated, but I tried adding the N option anyway though to no avail.  However the issue seems to be resolved.  I totally missed the fact

Re: RCPT info in logging

Not a direct answer but the domain in question has an Email verification API. They are definitely probing for valid users. I wonder if there's ever a valid use case for this. However, if you wanted to allow you would just enable the VERIFY feature. On Thu, Nov 25, 2021, 12:19 PM wrote: > I am

Re: RCPT info in logging

For 3.6.2 (from source) may influence this, but I am seeing enough to identify without any change in mail.log: > Nov 25 18:57:01 mail postfix/smtpd[2814]: NOQUEUE: reject: RCPT from localhost[127.0.0.1]: 450 4.7.1 : Helo command rejected: Host not found; from= to= proto=ESMTP helo= However,

Re: Spawn milter access to Verified Sender database

M Champion: > Hi Wietse, > > >> The DB dump shows : > >> > >> londonstransport+bncbdzntlposqirbr426sgamgqeh7mv...@googlegroups.com??? > >> 0:0:1637682515:250 2.1.5 OK s8si901258edx.4 - gsmtp > > There are 0xc2 0xa0 bytes at the end of the storage key, but not > > in your query. > > Apologies,?