Demi Marie Obenour wrote in
<6baaf997-0462-f5de-402b-c77f01ff5...@gmail.com>:
|On 12/2/22 08:08, David Dolan wrote:
|> On Fri, 2 Dec 2022 at 10:33, David Dolan wrote:
|>> Subject:Re: helo command rejected
|>>> From: Viktor Dukhovni
|>>>
On 12/2/22 08:08, David Dolan wrote:
> On Fri, 2 Dec 2022 at 10:33, David Dolan wrote:
>> Subject: Re: helo command rejected
>>> From: Viktor Dukhovni
>>> Date: 2022-12-01 16:56:13
>>> Message-ID: Y4jcrRxsEJPsWZVZ () straasha ! imrryr ! o
On Fri, Dec 02, 2022 at 09:47:03AM -0500, Wietse Venema
wrote:
> raf:
> > On Fri, Dec 02, 2022 at 08:51:14AM -0500, Wietse Venema
> > wrote:
> >
> > > David Dolan:
> > > > I guess it's using the musl resolver in Alpine so we need to migrate OS
> > > > to
> > > > get past this issue?
> > >
>
Steffen Nurpmeso wrote in
<20221202180252.bmzqg%stef...@sdaoden.eu>:
|Viktor Dukhovni wrote in
| :
||On Fri, Dec 02, 2022 at 06:03:51PM +0100, Steffen Nurpmeso wrote:
||> Simply add a dnsmasq local cache. dnsmasq is a package on
...
||Deploying dnsmasq does not do anything to address the li
Viktor Dukhovni wrote in
:
|On Fri, Dec 02, 2022 at 06:03:51PM +0100, Steffen Nurpmeso wrote:
|
|> Simply add a dnsmasq local cache. dnsmasq is a package on
|> AlpineLinux, i use it. (Including dnssec, and it even serves its
|> cache back into a VPN, so that effectively only one instance do
On Fri, Dec 02, 2022 at 06:03:51PM +0100, Steffen Nurpmeso wrote:
> Simply add a dnsmasq local cache. dnsmasq is a package on
> AlpineLinux, i use it. (Including dnssec, and it even serves its
> cache back into a VPN, so that effectively only one instance does
> all the web queries.) (I use it
Felker has past history with this mailing list and postfix, as well as
some things related to annoyances like versioning.
Are you on a MUSL libc system? IIRC there's no support for TCP in
MUSL's stub resolver. See, for example:
https://news.ycombinator.com/item?id=28312935
https://news
Wietse Venema wrote in
<4nnwkv4frxzj...@spike.porcupine.org>:
|raf:
|> On Fri, Dec 02, 2022 at 08:51:14AM -0500, Wietse Venema e.org> wrote:
|>
|>> David Dolan:
|>>> I guess it's using the musl resolver in Alpine so we need to migrate \
|>>> OS to
|>>> get past this issue?
|>>
|>> Yes.
David Dolan:
> I guess it's using the musl resolver in Alpine so we need to migrate OS to
> get past this issue?
On Fri, Dec 02, 2022 at 08:51:14AM -0500, Wietse Venema
wrote:
Yes. Don't use toy software in production.
On 03.12.22 00:59, raf wrote:
I suspect that alpine is used in many ma
raf:
> On Fri, Dec 02, 2022 at 08:51:14AM -0500, Wietse Venema
> wrote:
>
> > David Dolan:
> > > I guess it's using the musl resolver in Alpine so we need to migrate OS to
> > > get past this issue?
> >
> > Yes. Don't use toy software in production.
> >
> > Wietse
>
> I suspect that alpin
On Fri, Dec 02, 2022 at 08:51:14AM -0500, Wietse Venema
wrote:
> David Dolan:
> > I guess it's using the musl resolver in Alpine so we need to migrate OS to
> > get past this issue?
>
> Yes. Don't use toy software in production.
>
> Wietse
I suspect that alpine is used in many many
dock
David Dolan:
> On Fri, 2 Dec 2022 at 10:33, David Dolan wrote:
>
> >
> >
> > Subject:Re: helo command rejected
> >> From: Viktor Dukhovni
> >> Date: 2022-12-01 16:56:13
> >> Message-ID: Y4jcrRxsEJPsWZVZ () straasha ! imrryr ! o
On Fri, 2 Dec 2022 at 10:33, David Dolan wrote:
>
>
> Subject: Re: helo command rejected
>> From: Viktor Dukhovni
>> Date: 2022-12-01 16:56:13
>> Message-ID: Y4jcrRxsEJPsWZVZ () straasha ! imrryr ! org
>> [Download RAW message or body]
>>
Subject:Re: helo command rejected
> From: Viktor Dukhovni
> Date: 2022-12-01 16:56:13
> Message-ID: Y4jcrRxsEJPsWZVZ () straasha ! imrryr ! org
> [Download RAW message or body]
>
> On Thu, Dec 01, 2022 at 04:06:30PM +, David Dolan wrote:
>
>
On Thu, 1 Dec 2022 at 16:59, Matus UHLAR - fantomas
wrote:
> >> On 01.12.22 15:23, David Dolan wrote:
> >> >We have two customers who we're unable to receive email from.
> >> >It's failing the helo lookup as it can't resolve the hostname in the
> helo
> >> >message.
> >> >Helo command rejected: H
On 01.12.22 15:23, David Dolan wrote:
>We have two customers who we're unable to receive email from.
>It's failing the helo lookup as it can't resolve the hostname in the helo
>message.
>Helo command rejected: Host not found;
On Thu, 1 Dec 2022 at 15:49, Matus UHLAR - fantomas
wrote:
The issu
On Thu, Dec 01, 2022 at 04:06:30PM +, David Dolan wrote:
> This is the full line:
>
> NOQUEUE: reject: RCPT from unknown[103.246.251.109]:
> 450 4.7.1 :
> Helo command rejected: Host not found;
> from=<#> to=<#>
> proto=ESMTP helo=
Indeed the hostname "wx-use2.pro
On Thu, 1 Dec 2022 at 15:49, Matus UHLAR - fantomas
wrote:
> On 01.12.22 15:23, David Dolan wrote:
> >We have two customers who we're unable to receive email from.
> >It's failing the helo lookup as it can't resolve the hostname in the helo
> >message.
> >Helo command rejected: Host not found;
>
On 01.12.22 15:23, David Dolan wrote:
We have two customers who we're unable to receive email from.
It's failing the helo lookup as it can't resolve the hostname in the helo
message.
Helo command rejected: Host not found;
The issued hostname is logged just prior to this text.
You skipped the mo
On Thu, Dec 01, 2022 at 03:23:52PM +, David Dolan wrote:
> We have two customers who we're unable to receive email from. It's
> failing the helo lookup as it can't resolve the hostname in the helo
> message. Helo command rejected: Host not found;
Not surprising, too many systems have fictio
David Dolan skrev den 2022-12-01 16:23:
Has anybody come across this before and any idea how to resolve it?
32 ips with one single helo name ?
solution is 32 ips with not a single helo name
On Mon, Oct 09, 2017 at 05:04:44PM +0200, Enrico Morelli wrote:
> I'm trying to configure my outlook account to send email through my
> mail server, but I receive the following error:
That would presumably be the STARTTLS submission service on port
587, or perhaps smtps (TLS first then SMTP) port
On 10/13/2015 1:01 AM, Christian Kivalo wrote:
> Hi,
>
> On 2015-10-13 05:22, Richard B. Pyne wrote:
>> I am running postfix 2.10.1, dovecot 2.2.10, with postfixadmin and
>> maia mailguard.
>>
>> I am trying to figure out how to disable the HELO/EHLO
>> reject_non_fqdn_hostname on the submission p
Hi,
On 2015-10-13 05:22, Richard B. Pyne wrote:
I am running postfix 2.10.1, dovecot 2.2.10, with postfixadmin and
maia mailguard.
I am trying to figure out how to disable the HELO/EHLO
reject_non_fqdn_hostname on the submission port since many (most)
desktop and laptop clients don't send it.
On Thu, Aug 16, 2012 at 12:48:21PM -0400, Simon Brereton wrote:
> I have a line like this in my logs:
> mail #554 5.7.1 : Helo command rejected: Host not
> found ##
>
> This is clearly because I have reject_invalid_helo_name in my
> main.cf
No. You are confusing "invalid" and "unknown". The hos
On Aug 16, 2012 1:24 PM, "Jim Wright" wrote:
>
> On Aug 16, 2012, at 11:48 AM, Simon Brereton wrote:
>
> > mail #554 5.7.1 : Helo command rejected: Host not
found ##
> >
>
> > If I added in a check_helo_access before reject_invalid_helo_name that
would work, yes? Or would it be better to turn tha
* Simon Brereton :
> Hi
>
> I have a line like this in my logs:
> mail #554 5.7.1 : Helo command rejected: Host not found ##
~$ host SPEXCH07.sp.com
Host SPEXCH07.sp.com not found: 3(NXDOMAIN)
> This is clearly because I have reject_invalid_helo_name in my main.cf
Yes.
> Unfortunately, the f
Jim Wright:
> On Aug 28, 2009, at 5:50 PM, Noel Jones wrote:
>
> > Mail from yahoo.com is now rejected with:
> >
> > Aug 28 16:24:05 mgate2 postfix/smtpd[53002]: NOQUEUE: reject: RCPT
> > from web34202.mail.mud.yahoo.com[66.163.178.117]: 554 5.7.1
> > : Helo command rejected: Malformed DNS
>
On Aug 28, 2009, at 5:50 PM, Noel Jones wrote:
Mail from yahoo.com is now rejected with:
Aug 28 16:24:05 mgate2 postfix/smtpd[53002]: NOQUEUE: reject: RCPT
from web34202.mail.mud.yahoo.com[66.163.178.117]: 554 5.7.1
: Helo command rejected: Malformed DNS
server reply; from= to= proto=SMTP
Wietse Venema:
> Ralf Hildebrandt:
> > * Ralf Hildebrandt :
> > > Which Postfix restriction generates: "Helo command rejected: Domain not
> > > found"?
> > >
> > > From the log on albatross.python.org:
> > >
> > > Aug 21 15:07:07 albatross postfix/smtpd[15378]: NOQUEUE: reject_warning:
> > > RC
Ralf Hildebrandt:
[ Charset UTF-8 unsupported, converting... ]
> * Ralf Hildebrandt :
> > Which Postfix restriction generates: "Helo command rejected: Domain not
> > found"?
> >
> > From the log on albatross.python.org:
> >
> > Aug 21 15:07:07 albatross postfix/smtpd[15378]: NOQUEUE: reject_warn
On 8/28/2009 5:29 PM, Ralf Hildebrandt wrote:
* Ralf Hildebrandt:
* Ralf Hildebrandt:
BTW, this log entry in itself proves that the DNS name must resolved
back and forth, because otherwise postfix would have logged
"unknown[76.96.30.96]" instead of
qmta09.emeryville.ca.mail.comcast.net[76.96.3
* Ralf Hildebrandt :
> * Ralf Hildebrandt :
>
> > BTW, this log entry in itself proves that the DNS name must resolved
> > back and forth, because otherwise postfix would have logged
> > "unknown[76.96.30.96]" instead of
> > qmta09.emeryville.ca.mail.comcast.net[76.96.30.96]
> > -- which was also
* Ralf Hildebrandt :
> BTW, this log entry in itself proves that the DNS name must resolved
> back and forth, because otherwise postfix would have logged
> "unknown[76.96.30.96]" instead of
> qmta09.emeryville.ca.mail.comcast.net[76.96.30.96]
> -- which was also the HELO hostname!
mail_version =
* Ralf Hildebrandt :
> Which Postfix restriction generates: "Helo command rejected: Domain not
> found"?
>
> From the log on albatross.python.org:
>
> Aug 21 15:07:07 albatross postfix/smtpd[15378]: NOQUEUE: reject_warning: RCPT
> from qmta09.emeryville.ca.mail.comcast.net[76.96.30.96]: 554 5.0
35 matches
Mail list logo
