Re: Submission config being ignored
I see. Which config setting should be used to change the port and encryption
Dovecot proxy attempts to talk SMTP to? The default seems to be port 587 with
STARTTLS, but the docs don’t seem to mention how to change that.
Sent from mobile
> Op 12 dec. 2019 om 02:17 heeft Aki Tuomi het
> volgende geschreven:
>
>
>> On 12/12/2019 00:10 William Edwards wrote:
>>
>>
>> I'm having trouble setting up submission with Dovecot proxy. The submission
>> config seems to be getting ignored, but I'm probably doing something wrong.
>>
>> Expected behaviour: have messages sent to submission ports (25, 465) relayed
>> to `submission_relay_host`.
>>
>> --
>> root@imapproxy1:~# cat /etc/dovecot/conf.d/20-submission.conf
>> submission_logout_format = in=%i out=%o
>> submission_relay_host = smtp.prorelay.nl
>> submission_relay_port = 587
>> submission_relay_ssl = starttls
>> submission_relay_ssl_verify = no
>>
>> service submission {
>> }
>>
>> service submission-login {
>> inet_listener submission_25 {
>> port = 25
>>
>> }
>> inet_listener submission_465 {
>> port = 465
>> ssl = yes
>>
>> }
>> }
>> --
>>
>> What happens instead: Dovecot is attempting to send mail to the host
>> specified in the passdb file:
>>
>> root@imapproxy1:~# cat /etc/virtual/xalys.nl/passwd
>> test:$password.:8:8::/home/test.nl/test:/bin/false:userdb_quota_rule=*:bytes=0
>> proxy_maybe=y host=$ipaddr
>>
>> How do I get Dovecot to relay mail sent to submission ports to
>> 'submission_relay_host'?
>>
>> Met vriendelijke groeten,
>>
>> William Edwards
>> T. 040 - 711 44 96
>> E. wedwa...@cyberfusion.nl
>
> Due to design reasons, submission relaying to MTA occurs at backend, so move
> the relay configuration there.
> ---
> Aki Tuomi
Re: Ticket Received - [#22073] Re: Duplicate e-mail with Dovecot and Sieve
Bernd Petrovitsch skrev den 2019-12-12 00:44: Reply-to munging is considered harmful - please fix that. And thunderbird shows in the "From", "Recipient", "Correspondents" and "Sender[@]" column only "dovecot@dovecot.org" which neither helpful nor correct. it is solved imho ARC-Authentication-Results i=1; talvi.dovecot.org; dkim=none; spf=pass (talvi.dovecot.org: domain of be...@petrovitsch.priv.at designates 78.47.184.11 as permitted sender) smtp.mailfrom=be...@petrovitsch.priv.at not dkim signed is not a problem and Reply-to is not default dkim signed we are btw OT, i am happy its now solved, if more maillists based on mailman follow what dovecot did now we would be out of bussiness
Re: Submission config being ignored
On 12/12/2019 00:10 William Edwards wrote:
I'm having trouble setting up submission with Dovecot proxy. The submission config seems to be getting ignored, but I'm probably doing something wrong.
Expected behaviour: have messages sent to submission ports (25, 465) relayed to `submission_relay_host`.
--
root@imapproxy1:~# cat /etc/dovecot/conf.d/20-submission.conf
submission_logout_format = in=%i out=%o
submission_relay_host = smtp.prorelay.nl
submission_relay_port = 587
submission_relay_ssl = starttls
submission_relay_ssl_verify = no
service submission {
}
service submission-login {
inet_listener submission_25 {
port = 25
}
inet_listener submission_465 {
port = 465
ssl = yes
}
}
--
What happens instead: Dovecot is attempting to send mail to the host specified in the passdb file:
root@imapproxy1:~# cat /etc/virtual/xalys.nl/passwd
test:$password.:8:8::/home/test.nl/test:/bin/false:userdb_quota_rule=*:bytes=0 proxy_maybe=y host=$ipaddr
How do I get Dovecot to relay mail sent to submission ports to 'submission_relay_host'?
Met vriendelijke groeten,
William Edwards
T. 040 - 711 44 96
E. wedwa...@cyberfusion.nl
Due to design reasons, submission relaying to MTA occurs at backend, so move the relay configuration there.
---
Aki Tuomi
Submission config being ignored
I'm having trouble setting up submission with Dovecot proxy. The submission
config seems to be getting ignored, but I'm probably doing something wrong.
Expected behaviour: have messages sent to submission ports (25, 465) relayed to
`submission_relay_host`.
--
root@imapproxy1:~# cat /etc/dovecot/conf.d/20-submission.conf
submission_logout_format = in=%i out=%o
submission_relay_host = smtp.prorelay.nl
submission_relay_port = 587
submission_relay_ssl = starttls
submission_relay_ssl_verify = no
service submission {
}
service submission-login {
inet_listener submission_25 {
port = 25
}
inet_listener submission_465 {
port = 465
ssl = yes
}
}
--
What happens instead: Dovecot is attempting to send mail to the host specified
in the passdb file:
root@imapproxy1:~# cat /etc/virtual/xalys.nl/passwd
test:$password.:8:8::/home/test.nl/test:/bin/false:userdb_quota_rule=*:bytes=0
proxy_maybe=y host=$ipaddr
How do I get Dovecot to relay mail sent to submission ports to
'submission_relay_host'?
Met vriendelijke groeten,
William Edwards
T. 040 - 711 44 96
E. wedwa...@cyberfusion.nl
submission_relay_host
Re: Ticket Received - [#22073] Re: Duplicate e-mail with Dovecot and Sieve
Hi all! On 11/12/2019 19:16, Benny Pedersen via dovecot wrote: > Atomia via dovecot skrev den 2019-12-11 17:37: [...] > wonderfull example on why mailman sooks on change sender from :// Reply-to munging is considered harmful - please fix that. And thunderbird shows in the "From", "Recipient", "Correspondents" and "Sender[@]" column only "dovecot@dovecot.org" which neither helpful nor correct. [...] Mfg, Bernd -- Bernd Petrovitsch Email : be...@petrovitsch.priv.at LUGA : http://www.luga.at
RE: Lmtp redirection to other backend server
Maybe this host= availability can be configured through the pam service? -Original Message- To: dovecot Subject: Lmtp redirection to other backend server I have currently a working local delivery working ok on 2 backend servers. The backend servers use slapd/nslcd/nscd for local accounts. If I enable proxy=yes in the lmtp config section, I am getting this error 'auth: Debug: passdb out: FAIL#0111#011reason=Configured passdbs don't support credentials lookups' which is obvious because I do not have a passdb. I am not sure if it is possible to get this value from the system environment eg. nslcd/nscd, without the need to configure some separate ldap lookup in dovecot? Or do I really need to configure a ldap lmtp lookup just for this host attribute? What would be an efficient solution?
Lmtp redirection to other backend server
I have currently a working local delivery working ok on 2 backend servers. The backend servers use slapd/nslcd/nscd for local accounts. If I enable proxy=yes in the lmtp config section, I am getting this error 'auth: Debug: passdb out: FAIL#0111#011reason=Configured passdbs don't support credentials lookups' which is obvious because I do not have a passdb. I am not sure if it is possible to get this value from the system environment eg. nslcd/nscd, without the need to configure some separate ldap lookup in dovecot? Or do I really need to configure a ldap lmtp lookup just for this host attribute? What would be an efficient solution?
Re: dkim + arc
Aki Tuomi via dovecot skrev den 2019-12-11 21:00: And last attempt, since mailman didn't actually bother to update the settings in time. Sorry for the spam. ARC-Authentication-Results: i=1; talvi.dovecot.org; dkim=pass header.d=open-xchange.com header.s=201705 header.b=SwA7TIE8; spf=pass (talvi.dovecot.org: domain of aki.tu...@open-xchange.com designates 87.191.39.187 as permitted sender) smtp.mailfrom=aki.tu...@open-xchange.com progressing
RE: lmtp delivery auth error, but successful delivery
It is a test environment, so I do not have much data. I am testing with 'mail wegjd' seems to deliver ok every time. -Original Message- Subject: RE: lmtp delivery auth error, but successful delivery Can you let me know if you get lots of delivery failures? Aki Original message From: Marc Roos Date: 11/12/2019 22.16 (GMT+02:00) To: dovecot Subject: lmtp delivery auth error, but successful delivery How to fix the auth passwd-file unknown user error? I guess I maybe have something active that I do not need? With this configuration in sendmail FEATURE(`local_lmtp',`[IPC]',`TCP [192.168.10.44] 24')dnl MAILER(local)dnl Dec 11 21:04:18 mailsvr dovecot: lmtp(15361): Connect from 192.168.10.44 Dec 11 21:04:18 mailsvr dovecot: auth: passwd-file(wegjd,192.168.10.44): unknown user Dec 11 21:04:18 mailsvr dovecot: lmtp(wegjd): msgid=<201912112004.xbbk4hoz015...@mailsvr.xx.xxx>: saved mail to INBOX Dec 11 21:04:18 mailsvr dovecot: lmtp(15361): Disconnect from 192.168.10.44: Successful quit With this configuration in sendmail: FEATURE(`local_lmtp',`[IPC]',`FILE /var/run/dovecot/lmtp')dnl MAILER(local)dnl Dec 11 21:11:50 mailsvr dovecot: lmtp(15754): Connect from local Dec 11 21:11:51 mailsvr dovecot: auth: passwd-file(wegjd): unknown user Dec 11 21:11:51 mailsvr dovecot: lmtp(wegjd): msgid=<201912112011.xbbkborb015...@mailsvr.xx.xxx>: saved mail to INBOX Dec 11 21:11:51 mailsvr dovecot: lmtp(15754): Disconnect from local: Successful quit
lmtp delivery auth error, but successful delivery
How to fix the auth passwd-file unknown user error? I guess I maybe have something active that I do not need? With this configuration in sendmail FEATURE(`local_lmtp',`[IPC]',`TCP [192.168.10.44] 24')dnl MAILER(local)dnl Dec 11 21:04:18 mailsvr dovecot: lmtp(15361): Connect from 192.168.10.44 Dec 11 21:04:18 mailsvr dovecot: auth: passwd-file(wegjd,192.168.10.44): unknown user Dec 11 21:04:18 mailsvr dovecot: lmtp(wegjd): msgid=<201912112004.xbbk4hoz015...@mailsvr.xx.xxx>: saved mail to INBOX Dec 11 21:04:18 mailsvr dovecot: lmtp(15361): Disconnect from 192.168.10.44: Successful quit With this configuration in sendmail: FEATURE(`local_lmtp',`[IPC]',`FILE /var/run/dovecot/lmtp')dnl MAILER(local)dnl Dec 11 21:11:50 mailsvr dovecot: lmtp(15754): Connect from local Dec 11 21:11:51 mailsvr dovecot: auth: passwd-file(wegjd): unknown user Dec 11 21:11:51 mailsvr dovecot: lmtp(wegjd): msgid=<201912112011.xbbkborb015...@mailsvr.xx.xxx>: saved mail to INBOX Dec 11 21:11:51 mailsvr dovecot: lmtp(15754): Disconnect from local: Successful quit
Re: dkim + arc
> On 11/12/2019 21:58 Aki Tuomi via dovecot wrote: > > > If I don't get swamp of errors with this email, I'll stop the From munging > starting tomorrow. There is now ARC signing done for mails. Lets see how this > works, if we can stop rewriting from I'll be happy. > > Aki And last attempt, since mailman didn't actually bother to update the settings in time. Sorry for the spam. Aki
dkim + arc
If I don't get swamp of errors with this email, I'll stop the From munging starting tomorrow. There is now ARC signing done for mails. Lets see how this works, if we can stop rewriting from I'll be happy. Aki
Re: Ban Atomia.com?
On mer. 11 déc. 19:53:23 2019, Benny Pedersen via dovecot wrote: > he used dovecot@dovecot.org as sender address, very cleaver > > so if he try password recovery fun starts No, he used his address, but the mailling list rewrites the from -- Alarig
Re: Ban Atomia.com?
LuKreme via dovecot skrev den 2019-12-11 19:36: Can a mail admin ban atomia.com from posting? I mean, I like the idea that every post is clogging up their support queue, but really, not that much. he used dovecot@dovecot.org as sender address, very cleaver so if he try password recovery fun starts
Re[2]: Lightweight LMTP daemon to avoid overkill MTA
Hi,
I was unclear in my question. The spam filter is only able to deliver mail over
SMTP, not over LMTP.. So I would still need some kind of daemon that listens
for SMTP and then offers incoming email to Dovecot's LMTP socket.
Met vriendelijke groeten,
William Edwards
T. 040 - 711 44 96
E. wedwa...@cyberfusion.nl
- Original Message -
From: Marc Roos (m.r...@f1-outsourcing.eu)
Date: 12/11/19 18:59
To: dovecot (dovecot@dovecot.org), wedwards (wedwa...@cyberfusion.nl)
Subject: RE: Lightweight LMTP daemon to avoid overkill MTA
Yes dovecot, /etc/dovecot/conf.d/20-lmtp.conf ;)
service lmtp {
chroot =
client_limit = 1
drop_priv_before_exec = no
executable = lmtp
extra_groups = $default_internal_group
group =
idle_kill = 0
inet_listener lmtp {
address =
haproxy = no
port = 24
reuse_port = no
ssl = no
}
privileged_group =
process_limit = 0
process_min_avail = 0
protocol = lmtp
service_count = 0
type =
unix_listener lmtp {
group =
mode = 0666
user =
}
user =
vsz_limit = 18446744073709551615 B
}
-Original Message-
To: dovecot@dovecot.org
Subject: Lightweight LMTP daemon to avoid overkill MTA
Hi,
My situation is as follows.
-An internet-facing spam filter relays email to destination mail server
(Dovecot) with SMTP.
- Dovecot should take email and deliver it to user's mailboxes. I guess
I'd need LMTP for this.
- An external SMTP relay is already in place. I am thinking of using
Dovecot submission to relay to the external relaying cluster.
So, both relaying and routing are done externally - the Dovecot machine
should only store mail. Of course, there should also be a mechanism that
takes care of local delivery to Dovecot, like LMTP. Usually, I would use
an MTA like Exim to take care of local delivery. I feel like a
fully-featured MTA is overkill, though, as all other roles such an MTA
would fulfill - relaying and spam filtering - are fulfilled on external
servers.
Q: Does anyone know of a lightweight LMTP daemon that can take care of
local delivery to Dovecot without the need for a full MTA?
With kind regards,
William Edwards
T. 040 - 711 44 96
E. wedwa...@cyberfusion.nl
Re: Ban Atomia.com?
> On 11/12/2019 20:36 LuKreme via dovecot wrote: > > > Can a mail admin ban atomia.com from posting? I mean, I like the idea that > every post is clogging up their support queue, but really, not that much. > > Sent from my iPhone I have unsubscribed atomia. Aki
Ban Atomia.com?
Can a mail admin ban atomia.com from posting? I mean, I like the idea that every post is clogging up their support queue, but really, not that much. Sent from my iPhone
Re: Ticket Received - [#22073] Re: Duplicate e-mail with Dovecot and Sieve
Atomia via dovecot skrev den 2019-12-11 17:37: Hi Claudio Corvino via dovecot, wonderfull example on why mailman sooks on change sender from :// this mail here should imho be very private not posted to maillists stop breaking dkim please
Ticket Received - [#22079] RE: Re[2]: Lightweight LMTP daemon to avoid overkill MTA
Hi Claudio Corvino via dovecot, We have received your request and a ticket has been created with Ticket ID - 22079. A support representative will be reviewing your request and will contact you shortly. To view the status of the ticket or add comments, please visit https://support.atomia.com/helpdesk/tickets/22079 Speak to you soon, Atomia Support Team
RE: Re[2]: Lightweight LMTP daemon to avoid overkill MTA
Yes I am running sendmail next to dovecot on backend servers. That works
ok. I have some problems with re-routing mail in a proxy setup.
-Original Message-
To: Marc Roos; dovecot
Subject: Re[2]: Lightweight LMTP daemon to avoid overkill MTA
Hi,
I was unclear in my question. The spam filter is only able to deliver
mail over SMTP, not over LMTP.. So I would still need some kind of
daemon that listens for SMTP and then offers incoming email to Dovecot's
LMTP socket.
Met vriendelijke groeten,
William Edwards
T. 040 - 711 44 96
E. wedwa...@cyberfusion.nl
- Original Message -
From: Marc Roos (m.r...@f1-outsourcing.eu)
Date: 12/11/19 18:59
To: dovecot (dovecot@dovecot.org), wedwards (wedwa...@cyberfusion.nl)
Subject: RE: Lightweight LMTP daemon to avoid overkill MTA
Yes dovecot, /etc/dovecot/conf.d/20-lmtp.conf ;)
service lmtp {
chroot =
client_limit = 1
drop_priv_before_exec = no
executable = lmtp
extra_groups = $default_internal_group
group =
idle_kill = 0
inet_listener lmtp {
address =
haproxy = no
port = 24
reuse_port = no
ssl = no
}
privileged_group =
process_limit = 0
process_min_avail = 0
protocol = lmtp
service_count = 0
type =
unix_listener lmtp {
group =
mode = 0666
user =
}
user =
vsz_limit = 18446744073709551615 B
}
-Original Message-
To: dovecot@dovecot.org
Subject: Lightweight LMTP daemon to avoid overkill MTA
Hi,
My situation is as follows.
-An internet-facing spam filter relays email to destination mail server
(Dovecot) with SMTP.
- Dovecot should take email and deliver it to user's mailboxes. I guess
I'd need LMTP for this.
- An external SMTP relay is already in place. I am thinking of using
Dovecot submission to relay to the external relaying cluster.
So, both relaying and routing are done externally - the Dovecot machine
should only store mail. Of course, there should also be a mechanism that
takes care of local delivery to Dovecot, like LMTP. Usually, I would use
an MTA like Exim to take care of local delivery. I feel like a
fully-featured MTA is overkill, though, as all other roles such an MTA
would fulfill - relaying and spam filtering - are fulfilled on external
servers.
Q: Does anyone know of a lightweight LMTP daemon that can take care of
local delivery to Dovecot without the need for a full MTA?
With kind regards,
William Edwards
T. 040 - 711 44 96
E. wedwa...@cyberfusion.nl
RE: Lightweight LMTP daemon to avoid overkill MTA
Yes dovecot, /etc/dovecot/conf.d/20-lmtp.conf ;)
service lmtp {
chroot =
client_limit = 1
drop_priv_before_exec = no
executable = lmtp
extra_groups = $default_internal_group
group =
idle_kill = 0
inet_listener lmtp {
address =
haproxy = no
port = 24
reuse_port = no
ssl = no
}
privileged_group =
process_limit = 0
process_min_avail = 0
protocol = lmtp
service_count = 0
type =
unix_listener lmtp {
group =
mode = 0666
user =
}
user =
vsz_limit = 18446744073709551615 B
}
-Original Message-
To: dovecot@dovecot.org
Subject: Lightweight LMTP daemon to avoid overkill MTA
Hi,
My situation is as follows.
-An internet-facing spam filter relays email to destination mail server
(Dovecot) with SMTP.
- Dovecot should take email and deliver it to user's mailboxes. I guess
I'd need LMTP for this.
- An external SMTP relay is already in place. I am thinking of using
Dovecot submission to relay to the external relaying cluster.
So, both relaying and routing are done externally - the Dovecot machine
should only store mail. Of course, there should also be a mechanism that
takes care of local delivery to Dovecot, like LMTP. Usually, I would use
an MTA like Exim to take care of local delivery. I feel like a
fully-featured MTA is overkill, though, as all other roles such an MTA
would fulfill - relaying and spam filtering - are fulfilled on external
servers.
Q: Does anyone know of a lightweight LMTP daemon that can take care of
local delivery to Dovecot without the need for a full MTA?
With kind regards,
William Edwards
T. 040 - 711 44 96
E. wedwa...@cyberfusion.nl
Ticket Received - [#22078] Lightweight LMTP daemon to avoid overkill MTA
Hi Claudio Corvino via dovecot, We have received your request and a ticket has been created with Ticket ID - 22078. A support representative will be reviewing your request and will contact you shortly. To view the status of the ticket or add comments, please visit https://support.atomia.com/helpdesk/tickets/22078 Speak to you soon, Atomia Support Team
Lightweight LMTP daemon to avoid overkill MTA
Hi, My situation is as follows. -An internet-facing spam filter relays email to destination mail server (Dovecot) with SMTP. - Dovecot should take email and deliver it to user's mailboxes. I guess I'd need LMTP for this. - An external SMTP relay is already in place. I am thinking of using Dovecot submission to relay to the external relaying cluster. So, both relaying and routing are done externally - the Dovecot machine should only store mail. Of course, there should also be a mechanism that takes care of local delivery to Dovecot, like LMTP. Usually, I would use an MTA like Exim to take care of local delivery. I feel like a fully-featured MTA is overkill, though, as all other roles such an MTA would fulfill - relaying and spam filtering - are fulfilled on external servers. Q: Does anyone know of a lightweight LMTP daemon that can take care of local delivery to Dovecot without the need for a full MTA? With kind regards, William Edwards T. 040 - 711 44 96 E. wedwa...@cyberfusion.nl
Atomia user activation
Hi Claudio Corvino via dovecot, A new Atomia account has been created for you. Click the url below to activate your account and select a password! https://support.atomia.com/register/KfOvGCowO4TkXeAXlMH0 If the above URL does not work try copying and pasting it into your browser. If you continue to have problems, please feel free to contact us. Regards, Atomia
Ticket Received - [#22073] Re: Duplicate e-mail with Dovecot and Sieve
Hi Claudio Corvino via dovecot, We have received your request and a ticket has been created with Ticket ID - 22073. A support representative will be reviewing your request and will contact you shortly. To view the status of the ticket or add comments, please visit https://support.atomia.com/helpdesk/tickets/22073 Speak to you soon, Atomia Support Team
Re: Duplicate e-mail with Dovecot and Sieve
Trying to figure out how to implement an X-Loop header to my configuration, any ideas? On 29/11/19 10:00, Claudio Corvino via dovecot wrote: X-Loop header could be what I was looking for, thanks! On 28/11/19 22:03, @lbutlr via dovecot wrote: On 28 Nov 2019, at 09:44, Claudio Corvino wrote: Just one problem remaining: the e-mail that have l...@domain.tld in BCC could not be intercepted by the sieve filter as in the header is not present any reference to l...@domain.tld; am I missing something or this cannot be fixed? The normal way to do this is to add an X-Loop header. And no, there is no way to “fix” the design of Bcc. smime.p7s Description: S/MIME Cryptographic Signature
Re: Can't see a specific mail in thunderbird but with mobile mail client
Hi, sorry for the delay. I disabled compression on the server , decompressed the mails and re-created the index. All is working normally for now. I hope this was the problem. Thanks to all for helping! Am 04.12.19 um 15:40 schrieb @lbutlr via dovecot: > On 04 Dec 2019, at 02:36, Sami Ketola wrote: >> did not notice that you have imap_zlib enabled for protocol imap, can you >> disable that temporarily and re-record the rawlog. > Is it possible that is the source of the issue? It seems like when I tried to > test that it did not work with a lot of clients, but I might be thinking of > something else. > >
configured solr - question 2
How to free space when say folders are removed in mail account. Or whole account is removed?
configured solr - question 1
tested dovecot with solr. Works well. But it uses TCP connection between solr server and dovecot. Can it be password protected? I have other things than IMAP on the same server including remote users. i don't want them to be able to do mess.
