On 2023-09-04, Willy Manga wrote:
> It works now ! Thank you very much.
>
> I changed my settings as per your recommandation (
> http://paste.debian.net/1290945/ )
>
> Was it because I disabled 'plaintext' while at the same time allowing it
> through Dovecot?
dovecot with PAM needs plaintext meth
Hi Willy,
On Mon, 04 Sep 2023 at 09:32:02PM +, Willy Manga wrote:
It works now !
thanks for the feedback - I'm glad to hear that it works. :)
Was it because I disabled 'plaintext' while at the same time allowing it
through Dovecot?
Not only allowing, you force it ;-):
doveconf -n
Hi,
no one has received the same error?
In the meantime I upgraded to dovecot 2.3.20. But the error is still here.
ii dovecot-core 2:2.3.20-3+debian10
amd64secure POP3/IMAP server - core files
ii dovecot-dbg 2:2.3.20-3
04.09.2023 23:23, gene heskett wrote:
..
Ah contraire, Eduardo. My location since 1984 is in the middle northern area of WV, USA, And I am a minimum of 150 kilometers from the nearest ipv6
enabled network connection. I'm not even sure my cable modem, furnished by Shentel about 7 to 10 years ago,
.
On 05/09/2023 02:39, Shawn Heisey wrote:
On 9/4/23 15:40, Arjen de Korte wrote:
[...]
So you're saying that I can change my entire home network to IPv6,
eliminate IPv4 entirely, and I will have no problem connecting to sites
like bbc.com or cnn.com, which have no record? My ISP is Com
Damn. Forgot to hit "reply all" -- my bad
Forwarded Message
Subject: Re: DOvecot requires both IPv4 and IPV6 to start
Date: Mon, 4 Sep 2023 15:35:51 -0700
From: Stephen Satchell
Reply-To: l...@satchell.net
To: Arjen de Korte
On 9/4/23 2:40 PM, Arjen de Korte wrote:
This do
On 9/4/23 15:40, Arjen de Korte wrote:
Citeren Shawn Heisey :
An interesting read:
https://cr.yp.to/djbdns/ipv6mess.html
FUD.
This document was written something like two decades ago and pretty much
all arguments against IPv6 are no longer relevant anymore. In most cases
nowadays, the use
On 9/4/23 1:41 PM, TWHG Technical via dovecot wrote:
Sep 04 10:45:29 ourdomain dovecot[63336]: ^[[0;1;31m^[[0;1;39m^[[0;1;31mmaster:
Error: service(imap-login): listen(::, 143) failed: A>
Sep 04 10:45:29 ourdomain dovecot[63336]: Error: socket() failed: Address
family not supported by protocol
Citeren Shawn Heisey :
An interesting read:
https://cr.yp.to/djbdns/ipv6mess.html
FUD.
This document was written something like two decades ago and pretty
much all arguments against IPv6 are no longer relevant anymore. In
most cases nowadays, the user experience for IPv6 will be far supe
Hi Markus,
On 04/09/2023 23:11, Markus Winkler wrote:
Hi Willy,
On 04.09.23 19:54, Willy Manga wrote:
I updated a little bit my configuration . Here is the current one with
at the top the error I get if I try to send over submissions (port 465)
http://paste.debian.net/1290927/
could you pl
On 9/4/23 13:42, TWHG Technical via dovecot wrote:
I believe it really would be good practice to fallback to IPV4 only listeners
if IPV6 listener fails. Rather than crash out.
On my previous reply, I had not yet read the other messages. They were
part of another thread in Thunderbird that I
Shawn,
That config is not the standard as from the repos. As the standard one has that
line commented out signifying it is the default and the default is now:
listen = *, ::
The :: is the issue here as if there is no IPV6 stack and dovecot crashes as,
as a default it expects IPV6 to be there
On 9/4/23 12:20, Eduardo M KALINOWSKI via dovecot wrote:
On 04/09/2023 11:12, TWHG Technical via dovecot wrote:
But that is not this issue. The issue is that dovecot is assuming that
IPV6 is there and crashes out if it's not. Hacking the config to only
listen on IP4 solves the problem but not w
* TWHG Technical via dovecot:
> I hope this is the right place to start.
Not really. What you are asking for (changing the default configuration
provided by Ubuntu) is something better asked of the Ubuntu package
maintainers, should they even agree with your assessment. They might
tell you that a
On 9/4/23 12:36, Michael Peddemors wrote:
However, I 'get' this persons' opinion, from a developers perspective.
The system should either run, or provide a clear reason why it didn't
startup (that reason could be .. You have selected * but IPv6 is not
available). Doesn't really matter what the
I will reply to the email rather than press reply on the web mailing list page.
Probably got this wrong too!
I don't consider our setup non-standard. It is a standard IPV4 setup. We will
support IPV6 once our network security is reworked and everyone has a full
understanding of IPV6 and it's ch
Hi Willy,
On 04.09.23 19:54, Willy Manga wrote:
I updated a little bit my configuration . Here is the current one with at
the top the error I get if I try to send over submissions (port 465)
http://paste.debian.net/1290927/
could you please try the following changes:
1) remove
smtpd_sas
On 2023-09-04 08:58, Eduardo M KALINOWSKI via dovecot wrote:
On 04/09/2023 11:12, TWHG Technical via dovecot wrote:
But that is not this issue. The issue is that dovecot is assuming that
IPV6 is there and crashes out if it's not. Hacking the config to only
listen on IP4 solves the problem but n
.
On 04/09/2023 09:02, mangawi...@gmail.com wrote:
Hi. Can someone help me please check what is wrong with my config? postfix is saying
"no SASL authentication mechanisms" and I'm using dovecot. From what I read so
far, it is related to my dovecot settings. Here are the details of my config
h
* mangawi...@gmail.com :
> Hi. Can someone help me please check what is wrong with my config? postfix
> is saying "no SASL authentication mechanisms" and I'm using dovecot. From
> what I read so far, it is related to my dovecot settings. Here are the
> details of my config http://paste.debian.net/1
On 04/09/2023 11:12, TWHG Technical via dovecot wrote:
But that is not this issue. The issue is that dovecot is assuming that IPV6 is
there and crashes out if it's not. Hacking the config to only listen on IP4
solves the problem but not while installing from standard repos to install the
curre
On 9/4/23 8:11 AM, Jochen Bern wrote:
Define "disabled", please. I don't have many Ubuntu systems around, but
on the RHEL/CentOS/Fedora ones, even if they have IPv6 set to "Ignore",
the interfaces get link-local IPv6 addresses assigned - at which point
IPv6 LISTENs will work, too.
Of course,
IPV6 is disabled in the grub command line. So before the OS boots. So there is
no IPV6 support in the system. Unless one enables it in the Grub bootloader.
Cheers
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-
On 04.09.23 13:24, TWHG Technical wrote:
on systems that have IP6 disabled dovecot will not start.
Define "disabled", please. I don't have many Ubuntu systems around, but
on the RHEL/CentOS/Fedora ones, even if they have IPv6 set to "Ignore",
the interfaces get link-local IPv6 addresses assig
I think we are off topic.
We have a network policy that until such time as we have fully implemented the
same security we have on our IPV4 network we simply do not allow IPV6 as it is
another attack vector we are not fully upto speed on. So we block all IPV6 at
the perimeter and on all switche
> On 04/09/2023 16:30 EEST TWHG Technical via dovecot
> wrote:
>
>
> I have tried replying twice.
>
> We have IPV6 disabled for security reasons on all server builds. An installer
> script failed which is how we caught this issue. We can see it is due to the
> config line.
>
> A gracef
TWHG Technical via dovecot schreef op 2023-09-04 15:30:
I have tried replying twice.
We have IPV6 disabled for security reasons on all server builds.
IPv6 is secure, so that is not needed.
An installer script failed which is how we caught this issue. We can
see it is due to the config line.
Hi,
We have IPV6 disabled for security reasons on all server builds.
Why did you disable it for security reasons?
Regards
Bjoern
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
I have tried replying twice.
We have IPV6 disabled for security reasons on all server builds. An installer
script failed which is how we caught this issue. We can see it is due to the
config line.
A graceful fallback to IPV4 if the IPV6 stack is not available would seem to be
an elegant solu
TWHG Technical via dovecot schreef op 2023-09-04 13:24:
Hello,
I hope this is the right place to start. Ubuntu server the default
listener configuration in dovecot.conf uses both IP4 and IP6 on systems
that have IP6 disabled dovecot will not start.
Is it possible to set the default to:
list
> On 04/09/2023 15:23 EEST lejeczek via dovecot wrote:
>
>
> On 04/09/2023 09:32, Aki Tuomi via dovecot wrote:
> >> On 04/09/2023 10:19 EEST lejeczek via dovecot wrote:
> >>
> >>
> >> On 04/09/2023 08:54, Aki Tuomi via dovecot wrote:
> On 04/09/2023 09:47 EEST lejeczek via dovecot
>
On 04/09/2023 09:32, Aki Tuomi via dovecot wrote:
On 04/09/2023 10:19 EEST lejeczek via dovecot wrote:
On 04/09/2023 08:54, Aki Tuomi via dovecot wrote:
On 04/09/2023 09:47 EEST lejeczek via dovecot wrote:
Hi guys.
I'm having quite bizarre situation where Dovecot logs:
...
pam_uni
Am 04.09.23 um 13:24 schrieb TWHG Technical via dovecot:
Hello,
I hope this is the right place to start. Ubuntu server the default listener configuration in dovecot.conf uses both IP4 and IP6
I think that is a good default value.
on systems that have IP6 disabled dovecot will not start.
Hello,
I hope this is the right place to start. Ubuntu server the default listener
configuration in dovecot.conf uses both IP4 and IP6 on systems that have IP6
disabled dovecot will not start.
Is it possible to set the default to:
listen = * to only bind to IP4 for installation and initial
.
On 04/09/2023 13:00, Jim Popovitch via dovecot wrote:
On September 4, 2023 8:39:33 AM UTC, Willy Manga wrote:
[...]
Since it's possible that you are using Debian or Ubuntu, you should make
certain that you have libsasl2-modules installed.
I'm using debian12
It was already installed
roo
On September 4, 2023 8:39:33 AM UTC, Willy Manga wrote:
>
>.
>On 04/09/2023 11:03, Michel Verdier wrote:
>> On 2023-09-04, Willy Manga wrote:
>>
>>> When I switch that setting to 'yes', I still got
>>>
>>> "fatal: no SASL authentication mechanisms"
>>
>> give us
>> ls -l /var/spool/postfix/priv
.
On 04/09/2023 11:03, Michel Verdier wrote:
On 2023-09-04, Willy Manga wrote:
When I switch that setting to 'yes', I still got
"fatal: no SASL authentication mechanisms"
give us
ls -l /var/spool/postfix/private/
http://paste.debian.net/1290879/
Sep 04 07:01:01 smtp2 postfix/relay/smtp[
cyril.lecl...@mantiq.com skrev den 2023-09-04 07:38:
you have this smtpd_sasl_auth_enable = no
in postfix main.cf this is default, dont make it yes :)
in your config
it should be smtpd_sasl_auth_enable=yes
in postfix master.cf make this yes, not in global scopes
unsure show postconf -nf, p
> On 04/09/2023 10:19 EEST lejeczek via dovecot wrote:
>
>
> On 04/09/2023 08:54, Aki Tuomi via dovecot wrote:
> >> On 04/09/2023 09:47 EEST lejeczek via dovecot wrote:
> >>
> >>
> >> Hi guys.
> >>
> >> I'm having quite bizarre situation where Dovecot logs:
> >> ...
> >> pam_unix(dovecot:a
On 04/09/2023 08:54, Aki Tuomi via dovecot wrote:
On 04/09/2023 09:47 EEST lejeczek via dovecot wrote:
Hi guys.
I'm having quite bizarre situation where Dovecot logs:
...
pam_unix(dovecot:auth): check pass; user unknown
pam_unix(dovecot:auth): authentication failure; logname=
uid=0 euid=
On 4/9/23 14:03, Willy Manga wrote:
"fatal: no SASL authentication mechanisms"
--
try setting in dovecot
auth_debug = yes
auth_verbose = yes
and then restart both services and check logs when the problem occurs.
Also, be aware that dovecot usually 'subcontracts' the auth process to
pam,
On 2023-09-04, Willy Manga wrote:
> When I switch that setting to 'yes', I still got
>
> "fatal: no SASL authentication mechanisms"
give us
ls -l /var/spool/postfix/private/
> Sep 04 07:01:01 smtp2 postfix/relay/smtp[186183]: B61CB5FCFF:
> to=, relay=smtp.example.com[1.2.3.4]:587, delay=1.3,
> d
> On 04/09/2023 09:47 EEST lejeczek via dovecot wrote:
>
>
> Hi guys.
>
> I'm having quite bizarre situation where Dovecot logs:
> ...
> pam_unix(dovecot:auth): check pass; user unknown
> pam_unix(dovecot:auth): authentication failure; logname=
> uid=0 euid=0 tty=dovecot ruser=dupa rhost=AA.B
43 matches
Mail list logo
