Wonderful words to reflect on.. on a Sunday.
You too will get old. And when you do you'll fantasize that when you
were young prices where reasonable, politicians were noble, and children
respected their elders. Respect your elders.
Rgds/DP
9849111010
Sent from my iPhone. Pls excuse brevity and
On 2018-05-12 (23:01 MDT), Viktor Dukhovni wrote:
>
>> On May 13, 2018, at 12:42 AM, @lbutlr wrote:
>>
>> In these log lines, what is "UGFzc3dvcmQ6"?
>>
>> May 12 07:52:07 mail submit-tls/smtpd[32670]: warning:
>> vps1590651.vs.webtropia-customer.com[62.141.41.104]: SASL LOGIN
>> authenticat
> On May 13, 2018, at 12:42 AM, @lbutlr wrote:
>
> In these log lines, what is "UGFzc3dvcmQ6"?
>
> May 12 07:52:07 mail submit-tls/smtpd[32670]: warning:
> vps1590651.vs.webtropia-customer.com[62.141.41.104]: SASL LOGIN
> authentication failed: UGFzc3dvcmQ6
$ printf "%s\n" $(printf "%s\n" U
In these log lines, what is "UGFzc3dvcmQ6"?
May 12 07:52:07 mail submit-tls/smtpd[32670]: warning:
vps1590651.vs.webtropia-customer.com[62.141.41.104]: SASL LOGIN authentication
failed: UGFzc3dvcmQ6
May 12 17:05:14 mail submit-tls/smtpd[87898]: warning:
ma350.mars.fastwebserver.de[193.111.198.8
I use it. I like it. But... real world can/will bite you in the ass:
Yes, it can. Note this Received header from *your* message:
Received: from trackivity.com (unknown [IPv6:2607:f0b0:0:205::2])
(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
(No client certificate requested)
On 12 May 2018, at 17:55 (-0400), Thomas Smith wrote:
The documentation[1] and several e-mails here mention that
reject_unknown_client_hostname can reject legitimate e-mails.
What exactly are these scenarios? When do they occur in real life? Are
there really legitimate mail servers that don't
On 12 May 2018, at 18:45 (-0400), James wrote:
The documentation[1] and several e-mails here mention that
reject_unknown_client_hostname can reject legitimate e-mails.
What exactly are these scenarios? When do they occur in real life?
Are there really legitimate mail servers that don't have a
> On May 12, 2018, at 6:45 PM, James wrote:
>
> 1) DNS lookup failures: stuff *does* break occasionally and there *will* be
> minutes/hours when you reject stuff unintentionally,
For the record, when the problem is lost packets, lame delegations,
expired DNSSEC signatures, ... mail will be de
The documentation[1] and several e-mails here mention that
reject_unknown_client_hostname can reject legitimate e-mails.
What exactly are these scenarios? When do they occur in real life? Are
there really legitimate mail servers that don't have a reverse DNS
record that resolves to their IP?
On 2018-05-12 (15:55 MDT), Thomas Smith
wrote:
>
> The documentation[1] and several e-mails here mention that
> reject_unknown_client_hostname can reject legitimate e-mails.
>
> What exactly are these scenarios?
A mail sender doesn't have an A record.
> When do they occur in real life?
Yes.
The documentation[1] and several e-mails here mention that
reject_unknown_client_hostname can reject legitimate e-mails.
What exactly are these scenarios? When do they occur in real life? Are
there really legitimate mail servers that don't have a reverse DNS
record that resolves to their IP?
11 matches
Mail list logo
