To date here are the IPs used by
briteverify.com that I have marked to drop in my firewall...
## briteverify.com (Amazon AWS)
34.195.68.199
50.19.103.141
50.19.103.149
50.19.105.217
50.19.253.57
52.1.117.226
52.3.174.189
52.203.39.60
54.83.44.163
54.83.54.115
54.197.230.106
54.197.250.255
54.225.
On 05-22-2021 3:41 pm, David D. Scribner wrote:
Personally, I consider email-verification services parasites -- and
manage my server accordingly.
I fully agree, and have even complained to Amazon AWS about them to no
avail.
Amazon policies allow for abuse, and seems like Amazon is turning a
"...complained to Amazon AWS about them to no avail...”
I’m not privy to your specific scenario but if you are using AWS to
provide unmanaged cloud VM services, such as EC2, then why would you
complain to AWS re: any EM issue such as spam, verification, etc.?
That’s not their job - that’s the
Question about one of those services that validates email addresses on
the fly when you fill in a form...
There is one (Briteverify) which seems to fail email addresses at our
postfix server for an unknown reason.
I put my email in the form (it's used by a local food delivery
service), an
J Doe:
J Doe:
> A section that is shared in all of the service daemon man pages is
> "CONFIGURATION PARAMETERS". In bounce(8) there are parameters under
> this section that relate to delivery status notifications. For
> instance: delay_notice_recipient. This made me think that bounce(8) is
> sol
Simon Wilson:
> May 22 17:17:54 emp87 postfix/smtpd[805371]: NOQUEUE: reject: RCPT
> from smtpout10.briteverify.com[107.20.235.139]: 550 5.1.1
> :
> Recipient address rejected: User unknown in virtual alias table;
> from=
> to=
> proto=SMTP
> helo=
Is that your email adrress?
Wi
> May 22 17:17:54 emp87 postfix/smtpd[805371]: NOQUEUE: reject: RCPT
> from smtpout10.briteverify.com[107.20.235.139]: 550 5.1.1
> :
> Recipient address rejected: User unknown in virtual alias table;
> from=
> to=
> proto=SMTP
> helo=
Is that your email adrress?
Wietse
No. My ema
On 5/22/21 8:25 AM, Simon Wilson wrote:
What am I missing,as a commercial email verification service what are they
trying to validate?
Likely someone/somewhere submitted that^ email to a list, on your ... ahem ... "behalf".
Now, some client is using that list -- whether they originated it or
On 5/22/21 9:16 AM, Simon Wilson wrote:
You've misunderstood.
yep, sorry.
this
No. My email used is the same one I use on this list.
threw me off.
in this instance it's a valid check they are running on an email address I have
provided for a transaction.
... not that there aren't ot
On 22.05.21 22:25, Simon Wilson wrote:
May 22 17:17:54 emp87 postfix/smtpd[805371]: NOQUEUE: reject: RCPT
from smtpout10.briteverify.com[107.20.235.139]: 550 5.1.1
:
Recipient address rejected: User unknown in virtual alias table;
from=
to=
proto=SMTP
helo=
No. My email used is the same
On 2021-05-22 at 03:33:37 UTC-0400 (Sat, 22 May 2021 17:33:37 +1000)
Simon Wilson
is rumored to have said:
Question about one of those services that validates email addresses on
the fly when you fill in a form...
There is one (Briteverify) which seems to fail email addresses at our
postfix s
On 5/22/21 7:41 AM, PGNet Dev wrote:
> On 5/22/21 8:25 AM, Simon Wilson wrote:
>> What am I missing,as a commercial email verification service what are
>> they trying to validate?
> ...
>
> Personally, I consider email-verification services parasites -- and
> manage my server accordingly.
I fully
Simon Wilson
is rumored to have said:
Question about one of those services that validates email addresses
on the fly when you fill in a form...
There is one (Briteverify) which seems to fail email addresses at
our postfix server for an unknown reason.
Let's start with 2 stipulations:
1.
My guess is that the 5.2-second null connections are significant. I
suspect that you can fix this without significantly damaging the
effect of the postscreen PREGREET test by reducing the wait time to
never exceed that 5.2 seconds, e.g.:
postconf -e 'postscreen_greet_wait = ${stress?{2}:{4
14 matches
Mail list logo
