Re: [exim] Connection timed out errors
On 01/02/2023 22:53, MRob via Exim-users wrote: Sorry, maybe I wrote it wrong: question is more to inquire if Exim checking any internal flags or status that make it different from use "telnet [host] 25" on command line. I dont understand why I could telnet-by-hand with immediate successful connection/no slow connect as soon after I saw the error in the log tail. If there has been an error for a specific destination host in the past, it is remembered so as to avoid trying to use that host again. Most mail destinations run multiple MX's so an alternate will get used. That memory does expire eventually. Look up "hints database" in the Concept Index, if you want more details. Is any tip for how to take other debug steps or a way to "coax" exim to see what I see? Thank you for response, I do not mean to bother but this problem is very hard to understand. If you have a queued message which needs to be sent to the host in question, you can run a deliver attempt on it manually, with debug enabled. See the manual section on commandline options. Also, maybe simple problem is the "timer" length was inadvertantly change. Do you mind to say if that timeout comes from a certain exim configuration setting? Thank you! The value is an option for the transport, in the configuration. -- Cheers, Jeremy -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
Re: [exim] Connection timed out errors
On 2023-02-01 22:32, Jeremy Harris via Exim-users wrote: On 01/02/2023 22:02, MRob via Exim-users wrote: How to find why exim thinks it is timing out? Exim thinks the connection timed out because it sets an alarm before calling the syscall "connect" - and that timer went off. Also, maybe simple problem is the "timer" length was inadvertantly change. Do you mind to say if that timeout comes from a certain exim configuration setting? Thank you! -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
Re: [exim] Connection timed out errors
On 2023-02-01 22:32, Jeremy Harris via Exim-users wrote: On 01/02/2023 22:02, MRob via Exim-users wrote: How to find why exim thinks it is timing out? Exim thinks the connection timed out because it sets an alarm before calling the syscall "connect" - and that timer went off. Sorry, maybe I wrote it wrong: question is more to inquire if Exim checking any internal flags or status that make it different from use "telnet [host] 25" on command line. I dont understand why I could telnet-by-hand with immediate successful connection/no slow connect as soon after I saw the error in the log tail. Is any tip for how to take other debug steps or a way to "coax" exim to see what I see? Thank you for response, I do not mean to bother but this problem is very hard to understand. -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
Re: [exim] Connection timed out errors
On 01/02/2023 22:02, MRob via Exim-users wrote: How to find why exim thinks it is timing out? Exim thinks the connection timed out because it sets an alarm before calling the syscall "connect" - and that timer went off. -- Cheers, Jeremy -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
[exim] Connection timed out errors
Can anyone suggest a tips how to diagnose suddenly getting some percentage of connections to other servers "timed out" but the network is ok 1) tail exim main log for something like: H=mail.example.net [1.2.3.4]:25 Connection timed out 2) manual telnet to 1.2.3.4 port 25 and see connection is ok How to find why exim thinks it is timing out? Is there a internal set of flags exim keeping? If yes, how can I reset? Thank you for the help -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
Re: [exim] New install EXIM + Dovecot - auth permission error
On 2023-02-01 Gary Stainburn via Exim-users wrote:
> Hi folks.
> I'm setting up Dovecot and local user accounts on an existing Centos 7 +
> EXIM install.
[...]
> However, when I try authenticate as a user, the following errors get logged:
> 2023-02-01 12:50:11 dovecot_login authenticator failed for hub.
> ([10.1.1.103]) [**.**.**.**]: 435 Unable to authenticate at present: unable
> to connect to UNIX socket (/var/run/dovecot/auth-client): Permission denied
> The socket exists, but does not have suitable permissions.
> [root@vps2 exim]# ll /var/run/dovecot/auth-client
> srw---. 1 dovecot root 0 Feb 1 11:47 /var/run/dovecot/auth-client
> [root@vps2 exim]#
> Is it simply a case of changing ownership / permissions, and if so, what do
> I change them to?
> If not, can anyone tell me what I need to do please.
On Debian I have configured dovecot to open a socket for exim with
exim-tailored permissions:
/etc/dovecot/conf.d/10-master.conf
[...]
### SASL listener for exim start
# SASL exim
unix_listener /var/spool/exim4/dovecot.auth-client {
mode = 0660
group = Debian-exim
}
### SASL listener for exim end
cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
Re: [exim] New install EXIM + Dovecot - auth permission error
On Wed, Feb 1, 2023 at 7:12 PM Slavko via Exim-users wrote: > Dňa 1. februára 2023 13:39:26 UTC používateľ nb via Exim-users < > exim-users@exim.org> napísal: > > >I think it should be: > >srw-rw dovecot > > being the group that exim user runs under. > > Or simple 666 rights, if one need access (auth) from multiple > daemons. It depends, of course, on particular environment... > > regards > I solved this issue with running Exim with exim_user=mailnull, same to dovecot also running as mailnull. I said to myself, maulnull has no shell; Exim and Dovecot handle the same email. What else can go wrong? Exim gets compromised, Dovecot too suffers?? Let them suffer :-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
Re: [exim] New install EXIM + Dovecot - auth permission error
Dňa 1. februára 2023 13:39:26 UTC používateľ nb via Exim-users napísal: >I think it should be: >srw-rw dovecot > being the group that exim user runs under. Or simple 666 rights, if one need access (auth) from multiple daemons. It depends, of course, on particular environment... regards -- Slavko https://www.slavino.sk/ -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
Re: [exim] New install EXIM + Dovecot - auth permission error
Le 2023-02-01 13:02, Gary Stainburn via Exim-users a écrit : > > [root@vps2 exim]# ll /var/run/dovecot/auth-client > srw---. 1 dovecot root 0 Feb 1 11:47 /var/run/dovecot/auth-client I think it should be: srw-rw dovecot being the group that exim user runs under. -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
Re: [exim] New install EXIM + Dovecot - auth permission error
Hi, I may be totally wrong, but… Gary Stainburn via Exim-users (Mi 01 Feb 2023 14:02:06 CET): > driver = dovecot > public_name = LOGIN > server_socket = /var/run/dovecot/auth-client > server_set_id = $auth1 > > dovecot_plain: > driver = dovecot > public_name = PLAIN > server_socket = /var/run/dovecot/auth-client > server_set_id = $auth1 Sure about $auth1? Isn'tit $auth2 in case of the PLAIN driver? > 2023-02-01 12:50:11 dovecot_login authenticator failed for hub. > ([10.1.1.103]) [**.**.**.**]: 435 Unable to authenticate at present: unable > to connect to UNIX socket (/var/run/dovecot/auth-client): Permission denied Yes, Exim connects to the socket as the Exim runtime user, but the permissions on the socket are a way to tight. I think, either set the socket to 666, or make 660 and assign it to a group, Exim belongs to (though I'm not sure, if Exim "joins" its supplementary groups (aka initgroups(3)) for auth purpose.) I'm not sure about the security impact of widening the permissions on this socket. In theory it can be used to do mass-checking of auth credentials. The permissions and ownership of the socket can be set in the dovecot config file. -- Heiko signature.asc Description: PGP signature -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
Re: [exim] New install EXIM + Dovecot - auth permission error
On 01/02/2023 13:26, Heiko Schlittermann via Exim-users wrote: Sure about $auth1? Isn'tit $auth2 in case of the PLAIN driver? Not for the dovecot driver (only for the plaintext driver). $auth1 is correct, here, -- Cheers, Jeremy -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
[exim] New install EXIM + Dovecot - auth permission error
Hi folks. I'm setting up Dovecot and local user accounts on an existing Centos 7 + EXIM install. I've added authentication for the local users as: dovecot_login: driver = dovecot public_name = LOGIN server_socket = /var/run/dovecot/auth-client server_set_id = $auth1 dovecot_plain: driver = dovecot public_name = PLAIN server_socket = /var/run/dovecot/auth-client server_set_id = $auth1 However, when I try authenticate as a user, the following errors get logged: 2023-02-01 12:50:11 dovecot_login authenticator failed for hub. ([10.1.1.103]) [**.**.**.**]: 435 Unable to authenticate at present: unable to connect to UNIX socket (/var/run/dovecot/auth-client): Permission denied The socket exists, but does not have suitable permissions. [root@vps2 exim]# ll /var/run/dovecot/auth-client srw---. 1 dovecot root 0 Feb 1 11:47 /var/run/dovecot/auth-client [root@vps2 exim]# Is it simply a case of changing ownership / permissions, and if so, what do I change them to? If not, can anyone tell me what I need to do please. Cheers Gary -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
Re: [exim] FreeBSD: Moving from BDB5 to BDB18
On Tue, Jan 31, 2023 at 6:20 PM Jeremy Harris via Exim-users < exim-users@exim.org> wrote: > On 31/01/2023 14:38, Odhiambo Washington via Exim-users wrote: > > What changes do I need to make in Local/Makefile to achieve this? > > For TDB: > > USE_TDB = y > DBMLIB = -ltdb > > For gdbm: > > USE_GDBM = yes > DBMLIB = -lgdbm > > Might you be able to explain like to a layman? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
