Was recently configuring lmtp to listen in the postfix spool for mail.
I set the socket as suggested in the documentation, however, when I
look at what sockets were created there was an additional one for
dovecot.
Since I made the change, my expectation would have been just the one
that I set up.
I doubt it impacts it negatively, but I wanted to understand if I
configured things correctly or not.
Thanks.
Mike
On 17/01/2022 20:56 Mike alaskabarsalou@gmail.com wrote:
Was recently configuring lmtp to listen in the postfix spool for mail.
I set the socket as suggested in the documentation, however, when I
look at what sockets were created there was an additional one for
dovecot.Since I made the change, my expectation would have been just the one
that I set up.I doubt it impacts it negatively, but I wanted to understand if I
configured things correctly or not.Thanks.
Mike
Can you provide any details on what you did, what you expected, and what you actually observed?
Aki
Quoting Aki Tuomi aki.tuomi@open-xchange.com:
On 17/01/2022 20:56 Mike alaskabarsalou@gmail.com wrote:
Was recently configuring lmtp to listen in the postfix spool for mail.
I set the socket as suggested in the documentation, however, when I look at what sockets were created there was an additional one for dovecot.
Since I made the change, my expectation would have been just the one that I set up.
I doubt it impacts it negatively, but I wanted to understand if I configured things correctly or not.
Thanks.
Mike
Can you provide any details on what you did, what you expected, and
what you actually observed?Aki
Sure. I used the documentation to setup lmtp from here:
https://doc.dovecot.org/configuration_manual/howto/postfix_dovecot_lmtp/
When issuing this command:
ss -lxn | grep lmtp
And I get:
u_str LISTEN 0 100
private/lmtp 64917 * 0
u_str LISTEN 0 100
/var/spool/postfix/private/dovecot-lmtp 63578 * 0
u_str LISTEN 0 100
/var/run/dovecot/lmtp 63575 * 0
When I expect:
u_str LISTEN 0 100
private/lmtp 64917 * 0
u_str LISTEN 0 100
/var/spool/postfix/private/dovecot-lmtp 63578 * 0
The first entry I believe belongs to postfix. The second one is the one I set as above. The third seems to be an extra.
I have an Ubuntu setup if that matters.
Again, I don't think it is an issue. Everything seems to work, just
thought it makes sense to understand what is going on.
Mike
On 19/01/2022 01:07 Mike alaskabarsalou@gmail.com wrote:
Quoting Aki Tuomi aki.tuomi@open-xchange.com:
On 17/01/2022 20:56 Mike alaskabarsalou@gmail.com wrote:
Was recently configuring lmtp to listen in the postfix spool for mail.
I set the socket as suggested in the documentation, however, when I look at what sockets were created there was an additional one for dovecot.
Since I made the change, my expectation would have been just the one that I set up.
I doubt it impacts it negatively, but I wanted to understand if I configured things correctly or not.
Thanks.
Mike
Can you provide any details on what you did, what you expected, and
what you actually observed?Aki
Sure. I used the documentation to setup lmtp from here:
https://doc.dovecot.org/configuration_manual/howto/postfix_dovecot_lmtp/
When issuing this command:
ss -lxn | grep lmtp
And I get:
u_str LISTEN 0 100
private/lmtp 64917 * 0 u_str LISTEN 0 100
/var/spool/postfix/private/dovecot-lmtp 63578 * 0 u_str LISTEN 0 100
/var/run/dovecot/lmtp 63575 * 0When I expect:
u_str LISTEN 0 100
private/lmtp 64917 * 0 u_str LISTEN 0 100
/var/spool/postfix/private/dovecot-lmtp 63578 * 0The first entry I believe belongs to postfix. The second one is the one I set as above. The third seems to be an extra.
I have an Ubuntu setup if that matters.
Again, I don't think it is an issue. Everything seems to work, just
thought it makes sense to understand what is going on.Mike
Check doveconf service/lmtp
Aki
Quoting Aki Tuomi aki.tuomi@open-xchange.com:
On 19/01/2022 01:07 Mike alaskabarsalou@gmail.com wrote:
Quoting Aki Tuomi aki.tuomi@open-xchange.com:
On 17/01/2022 20:56 Mike alaskabarsalou@gmail.com wrote:
Was recently configuring lmtp to listen in the postfix spool for mail.
I set the socket as suggested in the documentation, however, when I look at what sockets were created there was an additional one for dovecot.
Since I made the change, my expectation would have been just the one that I set up.
I doubt it impacts it negatively, but I wanted to understand if I configured things correctly or not.
Thanks.
Mike
Can you provide any details on what you did, what you expected, and what you actually observed?
Aki
Sure. I used the documentation to setup lmtp from here:
https://doc.dovecot.org/configuration_manual/howto/postfix_dovecot_lmtp/
When issuing this command:
ss -lxn | grep lmtp
And I get:
u_str LISTEN 0 100 private/lmtp 64917 * 0 u_str LISTEN 0 100 /var/spool/postfix/private/dovecot-lmtp 63578 * 0 u_str LISTEN 0 100 /var/run/dovecot/lmtp 63575 * 0
When I expect:
u_str LISTEN 0 100 private/lmtp 64917 * 0 u_str LISTEN 0 100 /var/spool/postfix/private/dovecot-lmtp 63578 * 0
The first entry I believe belongs to postfix. The second one is the one I set as above. The third seems to be an extra.
I have an Ubuntu setup if that matters.
Again, I don't think it is an issue. Everything seems to work, just thought it makes sense to understand what is going on.
Mike
Check
doveconf service/lmtp
Aki
service { chroot = client_limit = 1 drop_priv_before_exec = no executable = lmtp -L extra_groups = $default_internal_group group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = lmtp service_count = 0 type = unix_listener { group = postfix mode = 0600 user = postfix path = /var/spool/postfix/private/dovecot-lmtp } unix_listener { group = mode = 0666 user = path = lmtp } user = vsz_limit = 18446744073709551615 B name = lmtp }
I assume the second unix_listener stanza is where the other entry
comes from, but I haven't a clue where it is getting defined.
I'll keep looking.
Thanks.
Mike
Am 20.01.2022 um 06:32 schrieb Mike:
unix_listener { group = mode = 0666 user = path = lmtp } user = vsz_limit = 18446744073709551615 B name = lmtp }
I assume the second unix_listener stanza is where the other entry comes from, but I haven't a clue where it is getting defined.
See https://doc.dovecot.org/settings/core/#core_setting-base_dir and then check your "doveconf -n base_dir".
Alexander
Quoting Alexander Dalloz ad+lists@uni-x.org:
Am 20.01.2022 um 06:32 schrieb Mike:
unix_listener { group = mode = 0666 user = path = lmtp } user = vsz_limit = 18446744073709551615 B name = lmtp }
I assume the second unix_listener stanza is where the other entry
comes from, but I haven't a clue where it is getting defined.See https://doc.dovecot.org/settings/core/#core_setting-base_dir and
then check your "doveconf -n base_dir".Alexander
Sorry, that wasn't very clear... I know where stuff gets set... for
Ubuntu it is in the /etc/dovecot/conf.d directory.
When I look through those files, there isn't any place setting a
protocol for lmtp other than for the director.
However, even when I remove that entry for the director, it is still there.
So when I said I don't have a clue where it is set, I mean, it isn't
obvious how it is getting picked up from those config files.
I guess I could just start renaming files until I identify it.
Maybe something related to global versus service specific?
If I WANTED to set it in a global way, how would I go about that?
I figure if I do that and I can impact my config, then it will narrow
down where the issue is.
Mike
participants (4)
-
Aki Tuomi
-
Alexander Dalloz
-
mbarsalou@lcgalaska.com
-
Mike