On 30/09/24 18:54, Danjel Jungersen via Postfix-users wrote:
>This looks like a port 25 block to me. Check with your host to make
sure they are not blocking outbound port 25, many of them require a
request to open the port.
I had to ask my ISP 4 or 5 times.
They kept insisting that they did
Dnia 30.09.2024 o godz. 18:53:29 Antonin VERRIER via Postfix-users pisze:
> For context, I'm using Dovecot submission service, which handles
> connections from SMTP client and, if authentication is successful,
> proxies them to a dedicated Postfix port and provides client data
> using XCLIENT.
>
>
W dniu pon, 30.09.2024 o godzinie 09∶52 -0400, użytkownik Steve Matzura
via Postfix-users napisał:
>
> I enabled port 25.
>
> $ sudo ufw allow 25
>
> /var/log/mail.log still shows connection timeout. Maybe ports 465 and
> 587 as well?
It's not the problem with *incoming* port 25 on *your* serve
Most hosting providers block outbound traffic to port 25 by default. A
simple telnet to outside port 25 can verify it quickly.
Regards
On 2024-09-30 23:20, Jarosław Rafa via Postfix-users wrote:
W dniu pon, 30.09.2024 o godzinie 09∶52 -0400, użytkownik Steve Matzura
via Postfix-users napisa
Scott K:
On 9/30/2024 12:17 AM, Scott Kitterman via Postfix-users wrote:
On September 30, 2024 4:00:32 AM UTC, Peter via
Postfix-users wrote:
On 30/09/24 10:38, Steve Matzura via Postfix-users wrote:
2024-09-29T21:31:27.402601+00:00 tgv24 postfix/error[1775]: B9E5510584F:
to=, orig_to=, re
On 9/30/2024 1:54 AM, Danjel Jungersen via Postfix-users wrote:
On 30 September 2024 06:00:32 CEST, Peter via Postfix-users
wrote:
>On 30/09/24 10:38, Steve Matzura via Postfix-users wrote:
>> 2024-09-29T21:31:27.402601+00:00 tgv24 postfix/error[1775]:
B9E5510584F: to=, orig_to=,
relay=no
Hello,
I'm a bit confused about whether Postfix considers a client
authenticated using XCLIENT to be SASL-authenticated or not.
Apparently "permit_sasl_authenticated" says no but
"reject_sender_login_mismatch" says yes.
For context, I'm using Dovecot submission service, which handles
conne
On 9/29/2024 8:11 PM, Viktor Dukhovni via Postfix-users wrote:
On Sun, Sep 29, 2024 at 05:38:16PM -0400, Steve Matzura via Postfix-users wrote:
2024-09-29T21:31:27.402601+00:00 tgv24 postfix/error[1775]: B9E5510584F:
to=, orig_to=, relay=none,
delay=48744, delays=48594/150/0/0.01, dsn=4.4.1, s
Le 30/09/2024 à 19:10, Jaroslaw Rafa via Postfix-users a écrit :
"smtpd_relay_restrictions=permit_mynetworks,reject" should do what you want.
While I don't know the exact value of your "mynetworks" parameter, it almost
always includes localhost 🙂.
But that doesn't work since the IP address that
Antonin VERRIER via Postfix-users:
> Hello,
>
> I'm a bit confused about whether Postfix considers a client
> authenticated using XCLIENT to be SASL-authenticated or not.
If XCLIENT receives a SASL login name, Postfix assumes that client
is authenticated.
> Apparently "permit_sasl_authenticated
Steve Matzura via Postfix-users:
>
> On 9/29/2024 8:11 PM, Viktor Dukhovni via Postfix-users wrote:
> > On Sun, Sep 29, 2024 at 05:38:16PM -0400, Steve Matzura via Postfix-users
> > wrote:
> >
> >> 2024-09-29T21:31:27.402601+00:00 tgv24 postfix/error[1775]: B9E5510584F:
> >> to=, orig_to=, relay=
On 9/30/2024 11:20 AM, Jarosław Rafa via Postfix-users wrote:
W dniu pon, 30.09.2024 o godzinie 09∶52 -0400, użytkownik Steve Matzura
via Postfix-users napisał:
I enabled port 25.
$ sudo ufw allow 25
/var/log/mail.log still shows connection timeout. Maybe ports 465 and
587 as well?
It's not
Hello
Long time ago I used Postfix to send automated emails to customers
(Slackware, 10+ years ago), then moved to another job and I stopped using
it. Now I'm working on a local network and just configured a local DNS
server for the LAN and as a first approach I want to setup a local mail
system a
On 9/29/2024 7:56 PM, Phil Stracchino via Postfix-users wrote:
On 9/29/24 17:38, Steve Matzura via Postfix-users wrote:
sudo hostname theglobalvoice.info
The bash prompt changes, but after the reboot, it reverted back to
TGV24. I'll take this up elsewhere, but I thought I'd explain why it
On October 1, 2024 3:19:42 AM UTC, Crazy Developer via Postfix-users
wrote:
>Hello
>
>Long time ago I used Postfix to send automated emails to customers
>(Slackware, 10+ years ago), then moved to another job and I stopped using
>it. Now I'm working on a local network and just configured a loca
Wietse Venema via Postfix-users:
> > $ telnet wzv smtp
> > Trying 168.100.3.7...
> > Connected to wzv.
> > Escape character is '^]'.
> > 220 wzv.porcupine.org ESMTP Postfix
> > XCLIENT LOGIN=whatever
> > 220 wzv.porcupine.org ESMTP Postfix
> > MAIL FROM:<>
> > 25
Wietse Venema via Postfix-users:
> Antonin VERRIER via Postfix-users:
> > Hello,
> >
> > I'm a bit confused about whether Postfix considers a client
> > authenticated using XCLIENT to be SASL-authenticated or not.
>
> If XCLIENT receives a SASL login name, Postfix assumes that client
> is authen
On Mon, Sep 30, 2024 at 09:38:46AM -0400, Steve Matzura via Postfix-users wrote:
> When I do it, I get:
>
> posttls-finger: warning: DNSSEC validation may be unavailable
> posttls-finger: warning: reason: dnssec_probe 'ns:.' received a response
> that is not DNSSEC validated
Your DNS resolver (a
Le 30/09/2024 à 20:34, Wietse Venema via Postfix-users a écrit :
Workaround: specify "smtpd_sasl_auth_enable = yes". That means
Postfix needs some of the Dovecot machinery even if most of it will
remain unused.
That was fast! That works perfectly, many thanks.
_
19 matches
Mail list logo
