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.
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
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:
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
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
> postfix/smtpd[24986]: warning: hostname server17-ams1.internet-census.org
> does not resolve to address 107.6.163.34: Name or service not known
This is a type 4 error (the name->address mapping does not exist).
> postfix/smtpd[24986]: connect from unknown[107.6.163.34]
> postfix/smtpd[24986]:
Thanks for the reply.
The warning says that "hostname does not resolve to address" (case #4) but
then the log says that connection is rejected because it cannot find a
hostname (case #2).
So which one is the actual rejection reason? Doesn't it feel a bit
confusing?
Regar
Eugene Podshivalov:
> Hi all,
> I have the following config
>
> > smtpd_client_restrictions =
> > reject_unknown_client_hostname
> > smtpd_helo_required = yes
> > smtpd_helo_restrictions =
> > reject_invalid_helo_hostname,
> > reject_non_fqdn_helo_hostname,
> >
Hi all,
I have the following config
> smtpd_client_restrictions =
> reject_unknown_client_hostname
> smtpd_helo_required = yes
> smtpd_helo_restrictions =
> reject_invalid_helo_hostname,
> reject_non_fqdn_helo_hostname,
> reject_unknown_helo_hostname
> smtpd_sender_restrictions =
> 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 resol
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
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
-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:
-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:
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 believe
frozenstar.info
250-smtp.frozenstar.info 250-PIPELINING 250-SIZE 1024 250-ETRN
250-STARTTLS 250-ENHANCEDSTATUSCODES 250-8BITMIME 250 DSN
AUTH is NOT on the list and logs say:
postfix/smtpd[27162]: warning: hostname riseup.net does not resolve
to address 199.58.81.144: Name or service not known
:
www postfix/smtpd[11453]: warning: hostname anon.riseup.net does
not resolve to address 199.58.81.144: Name or service not known www
postfix/smtpd[11453]: connect from unknown[199.58.81.144] www
postfix/smtpd[11453]: lost connection after UNKNOWN from
unknown[199.58.81.144] www postfix/smtpd
and connection security SSL/TLS i get:
www postfix/smtpd[11453]: warning: hostname anon.riseup.net
does not resolve to address 199.58.81.144: Name or service
not known www postfix/smtpd[11453]: connect from
unknown[199.58.81.144] www postfix/smtpd[11453]: lost
connection after UNKNOWN from
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 =
-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
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
250-8BITMIME
/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
/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.
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
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 used
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
used bogus
On Jan 31, 2015, at 8:59 PM, Bill Cole
postfixlists-070...@billmail.scconsult.com wrote:
I do not use that rejection criteria but instead use
reject_unknown_reverse_client_hostname,
I do use that, and have for a long time.
which only requires that a PTR exists. On other systems I
On 31 Jan 2015, at 17:33, LuKreme wrote:
What should I do about these warnings? Is there any reason not to
reject the IPs in question? And if not, how do I do so? mail_version =
2.11.3
warning hostname 102-253-144-216.static.reverse.lstn.net does not
resolve to address 216.144.253.102
Am 01.02.2015 um 04:59 schrieb Bill Cole:
On 31 Jan 2015, at 17:33, LuKreme wrote:
What should I do about these warnings? Is there any reason not to
reject the IPs in question? And if not, how do I do so? mail_version =
2.11.3
warning hostname 102-253-144-216.static.reverse.lstn.net does not
What should I do about these warnings? Is there any reason not to reject the
IPs in question? And if not, how do I do so? mail_version = 2.11.3
warning hostname 102-253-144-216.static.reverse.lstn.net does not resolve to
address 216.144.253.102 hostname nor servname provided, or not known
Am 01.02.2015 um 05:45 schrieb Viktor Dukhovni:
On Sun, Feb 01, 2015 at 05:11:15AM +0100, li...@rhsoft.net wrote:
Nearly every SMTP client using an IP with a PTR whose name does not
resolve back to that IP sends nothing but spam
bullshit - in the real world that's not true
The message you
On Sun, Feb 01, 2015 at 05:50:44AM +0100, li...@rhsoft.net wrote:
Am 01.02.2015 um 05:45 schrieb Viktor Dukhovni:
On Sun, Feb 01, 2015 at 05:11:15AM +0100, li...@rhsoft.net wrote:
Nearly every SMTP client using an IP with a PTR whose name does not
resolve back to that IP sends nothing but
On Sun, Feb 01, 2015 at 05:11:15AM +0100, li...@rhsoft.net wrote:
Nearly every SMTP client using an IP with a PTR whose name does not
resolve back to that IP sends nothing but spam
bullshit - in the real world that's not true
The message you were responding too was generally helpful with
33 matches
Mail list logo
