thank you, everyone, much appreciate advice and testing!
I'll try to summarize how it went:
user is India complained he couldn't access geko.sbt.net.au mail server
as there was an issue with some 'links' at data centre reported few hours
earlier, I assumed it was related and didn't try to test
n
Hello world,
in a containerized setup I noticed a bad command startup if the AUTH
socket is not available (i.e. the container is down):
$ postconf smtpd_sasl_path
smtpd_sasl_path = inet:dovecot:12345
#v+
postfix/submission/smtpd[156]: connect from
client.example.com[:xxx:xx:::3]
post
On 18.09.22 14:00, Stefan Foerster wrote:
in a containerized setup I noticed a bad command startup if the AUTH
socket is not available (i.e. the container is down):
$ postconf smtpd_sasl_path
smtpd_sasl_path = inet:dovecot:12345
#v+
postfix/submission/smtpd[156]: connect from
client.example.c
raf skrev den 2022-09-18 01:47:
The logfile message showed that the envelope sender
domain was sbt.net.au, not geko.sbt.net.au.
fair, but spamassassin should say spf_helo_pass on this subdomain
i have lost ip now, but myhostname in postfix should be spf helo pass
dig mx.junc.eu txt
dig junc.
On Sun, Sep 18, 2022 at 06:34:11PM +1000, li...@sbt.net.au wrote:
> I'll try to summarize how it went:
The summary largely misses the point. Your DNS provider had a major
outage (plausibly a DDoS, though they haven't said so outright). DNS
queries from many sources were consequently dropped. D
Hi, i've a problem, i need to limit outgoing mail sendend by Industry
device.
If a device is in alarm it send one mail every 5 minutes using my
postfix smtp (customer can define is own mail address and receive this
email),
The risk is to reach limit and to be consider an abuse from customer
On Sun, Sep 18, 2022 at 06:03:47PM +0200, Matteo Cazzador wrote:
> If a device is in alarm it send one mail every 5 minutes using my
> postfix smtp (customer can define is own mail address and receive this
> email),
>
> The risk is to reach limit and to be consider an abuse from customer
> mai
Stefan Foerster:
> Hello world,
>
> in a containerized setup I noticed a bad command startup if the AUTH
> socket is not available (i.e. the container is down):
>
> $ postconf smtpd_sasl_path
> smtpd_sasl_path = inet:dovecot:12345
>
> #v+
> postfix/submission/smtpd[156]: connect from
> client.
Sorry, my initial diagnosis was incorrect.
Stefan Foerster:
> postfix/submission/smtpd[156]: warning: host or service dovecot:12345 not
> found: Name does not resolve
> postfix/submission/smtpd[156]: warning: SASL: Connect to Dovecot auth socket
> 'inet:dovecot:12345' failed: Address not availab
Wietse Venema:
> Sorry, my initial diagnosis was incorrect.
>
> Stefan Foerster:
> > postfix/submission/smtpd[156]: warning: host or service dovecot:12345 not
> > found: Name does not resolve
> > postfix/submission/smtpd[156]: warning: SASL: Connect to Dovecot auth
> > socket 'inet:dovecot:12345
- Message from Viktor Dukhovni -
Date: Sat, 17 Sep 2022 23:26:34 -0400
From: Viktor Dukhovni
Reply-To: postfix-users@postfix.org
Subject: Re: ot: SPF/DKIM woes
To: postfix-users@postfix.org
On Sat, Sep 17, 2022 at 10:39:46AM -0400, Viktor Dukhovni wrote:
If this d
11 matches
Mail list logo
