On 09.03.21 15:26, Curtis Maurand wrote:
your a record and fqdn, your helo/ehlo hostname and the ptr record all need to
match.
that's incorrect.
IP address has to point to DNS name that maps back to the IP address.
HELO (EHLO) hostname does not necessarily need to point to that DNS name.
HE
Thank you Victor.
The LAN is created by the Host physical server as a software construct --
there is no physical network connection outside of the Host. The Host and
Virtual Machines (VMs) communicate on this LAN.
The mail server is using an API that is available to the Host and all VMs
for send
your a record and fqdn, your helo/ehlo hostname and the ptr record all need to
match.
Sent from my iPhone
> On Mar 9, 2021, at 12:36 PM, Greg Sims wrote:
>
>
> We are receiving the following in our email logs:
>
> Mar 09 08:12:15 mail01.raystedman.org postfix/smtpd[13431]: warning: hostnam
On Tue, Mar 09, 2021 at 09:35:35AM -0800, Greg Sims wrote:
> Mar 09 08:12:15 mail01.raystedman.org postfix/smtpd[13431]:
> warning: hostname mail01.raystedman.org
> does not resolve to address 192.168.122.12
An SMTP client at IP address 192.168.122.12 connected to your SMTP
server. That IP a
We are receiving the following in our email logs:
Mar 09 08:12:15 mail01.raystedman.org postfix/smtpd[13431]: warning:
hostname mail01.raystedman.org does not resolve to address 192.168.122.12
This warning is in fact true. I believe something is not configured
correctly.
The postfix mail server
> On Oct 2, 2019, at 6:34 PM, Christian Göttsche wrote:
>
> Hi,
> I am getting several warning a day of the form
>
>postfix/smtpd[6969]: warning: hostname domain does not resolve to address
> ip
>postfix/smtpd[10614]: warning: hostname domain does not resolve to
> address ip: Name or
Hi,
I am getting several warning a day of the form
postfix/smtpd[6969]: warning: hostname domain does not resolve to address ip
postfix/smtpd[10614]: warning: hostname domain does not resolve to
address ip: Name or service not known
My question is, why are these logged with syslog priorit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 18/04/2015 21:19, Noel Jones wrote:
> On 4/18/2015 1:31 PM, Krzs wrote:
>
> But relay is still denied. Probably because you forgot to add
> "permit_sasl_authenticated" to your postfix restrictions, or added
> it in the wrong place. Posting a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 4/18/2015 1:31 PM, Krzs wrote:
>
>
> On 18/04/2015 18:36, Alex JOST wrote:
>> Am 18.04.2015 um 16:35 schrieb Krzs:
>
>> To me it looks as if everything is working as it should.
>> This might simply be a Thunderbird misconfiguration.
>
>
> By
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 18/04/2015 18:36, Alex JOST wrote:
> Am 18.04.2015 um 16:35 schrieb Krzs:
> To me it looks as if everything is working as it should. This
> might simply be a Thunderbird misconfiguration.
>
By thunderbird and connection security SSL/TLS i get
Am 18.04.2015 um 16:35 schrieb Krzs:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
That's while i use openssl:
:~$ openssl s_client -starttls smtp -crlf -connect
88.198.107.18:25 CONNECTED(0003) depth=0 C = DE, ST = Berlin, L
= Berlin, O = Frozenstar Communications, OU = SMTP, CN =
smtp.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 18/04/2015 16:43, Christian Kivalo wrote:
> you seem to have a local problem with your auth daemon that
> postfix tries to connect to. is dovecot running and an auth socket
> exists at $queue_directory/private/auth?
Dovecot is up and running:
On 2015-04-18 15:08, Krzs wrote:
postfix/smtpd[23438]: xsasl_dovecot_server_connect: Connecting Apr
18 15:05:25 www postfix/smtpd[23438]: warning: SASL: Connect to
private/auth failed: Connection refused Apr 18 15:05:25 www
postfix/smtpd[23438]: fatal: no SASL authentication mechanisms Apr
18 15
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
That's while i use openssl:
> :~$ openssl s_client -starttls smtp -crlf -connect
> 88.198.107.18:25 CONNECTED(0003) depth=0 C = DE, ST = Berlin, L
> = Berlin, O = Frozenstar Communications, OU = SMTP, CN =
> smtp.frozenstar.info, emailAddress =
On 18/04/2015 2:08 pm, Krzs wrote:
> SMTPD does starttls
>
>> 220 2.0.0 Ready to start TLS
'Ready to start TLS' isn't the same as a running TLS connection, you've
shown no evidence of the key negotiation (if that's what it's called)
required to create the encrypted connection, and I don't belie
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I did set an A record for my MX domain name
> smtp.frozenstar.info. 3600IN A 88.198.107.18
SMTPD does starttls
> 220 2.0.0 Ready to start TLS
but i noticed this SSL error in logs:
> warning: TLS library problem: 1958:error:140760F
On 17/04/2015 1:02 pm, Krzs wrote:
> :~$ telnet smtp.myFQDN 25
> Trying 1.2.3.4 ...
> Connected to myFQDN.
> Escape character is '^]'.
> 220 smtp.myFQDN ESMTP Postfix
> ehlo smtp.myFQDN
> 250-smtp.myFQDN
> 250-PIPELINING
> 250-SIZE 1024
> 250-ETRN
> 250-STARTTLS
> 250-ENHANCEDSTATUSCODES
> 25
On 17/04/2015 17:26, Bill Cole wrote:
> On 17 Apr 2015, at 8:02, Krzs wrote:
>
>> HTML tags from postfixusers nabble dot come web site don't show up in
>> emails
They don't show up because i don't use html in emails
> Almost entirely useless. What you added is full of lies, where you've
> use
On Fri, Apr 17, 2015 at 11:26:44AM -0400, Bill Cole wrote:
> On 17 Apr 2015, at 8:02, Krzs wrote:
>
> >HTML tags from postfixusers nabble dot come web site don't show up in
> >emails ,i'll add their content in this replay:
>
> Almost entirely useless. What you added is full of lies, where you've
On 17 Apr 2015, at 8:02, Krzs wrote:
HTML tags from postfixusers nabble dot come web site don't show up in
emails ,i'll add their content in this replay:
Almost entirely useless. What you added is full of lies, where you've
used bogus names and addresses to replace nearly all information that
Regards
> Gab
>
>
>
> --
> View this message in context:
> http://postfix.1071664.n5.nabble.com/smtpd-warning-hostname-does-not-resolve-to-address-Name-or-service-not-known-tp76263.html
> Sent from the Postfix Users mailing list archive at Nabble.com.
>
--
Key fingerprint = EB67 3CA1 6C61 EACE B705 4EC3 A28D E2DD 4C47 A4D9
nabble.com/smtpd-warning-hostname-does-not-resolve-to-address-Name-or-service-not-known-tp76263.html
Sent from the Postfix Users mailing list archive at Nabble.com.
22 matches
Mail list logo
