On 2025-05-21 21:41, Aki Tuomi via dovecot wrote:
Can you add
log_debug=category=mail or category=auth
and try again, maybe the logs reveal something useful? My guess is that the
parameters provided to lda are now somehow mixed and exim is using physical
user as target user for dovecot
> On 21/05/2025 22:34 EEST Cam Ellison via dovecot wrote:
>
>
> When running v2.3, Dovecot correctly identifies both recipient and
> domain when receiving mail from Debian exim4 via dovecot-lda, with no
> flags set.
>
> With v2.4, whether the flags are set or not,
On 2025-05-21 16:22, Cam Ellison via dovecot wrote:
On 2025-05-21 14:11, Odhiambo Washington wrote:
Hi Cam,
I suffered something similar during my migration and an old post
somewhere saved the day for me: https://skeletor.org.ua/?p=2497
I hope it helps you too.
It was worth a try, and at lea
On 2025-05-21 14:11, Odhiambo Washington wrote:
Hi Cam,
I suffered something similar during my migration and an old post
somewhere saved the day for me: https://skeletor.org.ua/?p=2497
I hope it helps you too.
It was worth a try, and at least has changed the focus to Exim from
Dovecot: the e
When running v2.3, Dovecot correctly identifies both recipient and domain when
receiving mail from Debian exim4 via dovecot-lda, with no flags set.
With v2.4, whether the flags are set or not, Dovecot throws error 75. If
lda_mailbox_autocreate is set to yes, it creates the mailuser vmail and
do
it this way, instead of the proper more secure way.
> I have managed to get it to work better now.
> I did setuid the dovecot-lda, and then added www-data to the dovecot group,
> so now dovecot-lda executes sucessfully. This also meant I could set back
> the authdb to 0666 and also
than 0666 and Dovecot lets the kernel enforce the
# permissions (e.g. 0777 allows everyone full permissions).
"
But I did remove authdb=0777 and put it back to 0666. Since the setuid
works.
I did setuid dovecot-lda to root, and then remove execute permissions from
everyone.
Accord
Sebastian Nielsen via dovecot skrev den 2024-10-31 19:55:
Now it FINALLY works!
read other mails on maillist, if you belive its good, then you dont know
security at all
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to
so it gets
access to dovecot resources.
Now it FINALLY works!
-Ursprungligt meddelande-
Från: Benny Pedersen via dovecot
Skickat: den 31 oktober 2024 19:45
Till: dovecot@dovecot.org
Ämne: Re: Sv: dovecot-lda from www-data - doesnt work
Sebastian Nielsen via dovecot skrev den 2024-10-31
Sebastian Nielsen via dovecot skrev den 2024-10-31 19:15:
No errors in logs either.
maybe your perl need to make the sasl auth to postfix ?
or simply just setup phpmailer with proper sasl auth
___
dovecot mailing list -- dovecot@dovecot.org
To unsub
m trying to deliver email from a webform, but its not working.
I then tried manually in the console:
WORKS:
sudo -u info /usr/lib/dovecot/dovecot-lda -d info
DOES NOT WORK:
sudo -u www-data /usr/lib/dovecot/dovecot-lda -d info
sudo -u postfix /usr/lib/dovecot/dovecot-lda -d info
e debugn
on send mail to see what is doing dovect but no luck Aug 8
02:13:27 servidorabm dovecot:
lda(luis.alvarez)<870407>: Debug:
program exec:/usr/sbin/exim: Created Aug 8 02:13:27 servidorabm
dovecot: lda(luis.alvarez)<870407>:
Debug: program exec:/usr/sbin/exi
the mail and sending "like this one"
/usr/local/bin/dovecot-sendmail-wrapper I enable the debugn on
send mail to see what is doing dovect but no luck Aug 8 02:13:27
servidorabm dovecot:
lda(luis.alvarez)<870407>: Debug: program
exec:/usr/sbin/exim: Creat
sr/local/bin/dovecot-sendmail-wrapper
I enable the debugn on send mail to see what is doing dovect but no luck
Aug 8 02:13:27 servidorabm dovecot:
lda(luis.alvarez)<870407>: Debug: program
exec:/usr/sbin/exim: Created
Aug 8 02:13:27 servidorabm dovecot:
lda(luis.alvarez)<870407>
this one"
/usr/local/bin/dovecot-sendmail-wrapper I enable the debugn on
send mail to see what is doing dovect but no luck Aug 8 02:13:27
servidorabm dovecot:
lda(luis.alvarez)<870407>: Debug: program
exec:/usr/sbin/exim: Created Aug 8 02:13:27 servidorabm dove
UTGOING and not use sendmail on
command line.. There any way to create a warper to capture the
mail and sending "like this one"
/usr/local/bin/dovecot-sendmail-wrapper I enable the debugn on
send mail to see what is doing dovect but no luck Aug 8 02:13:27
servidorabm dove
on command line..
>
>There any way to create a warper to capture the mail and sending "like this
>one" /usr/local/bin/dovecot-sendmail-wrapper
>
>I enable the debugn on send mail to see what is doing dovect but no luck
>
>Aug 8 02:13:27 servidorabm dovecot:
>lda
mail to see what is doing dovect but no luck
Aug 8 02:13:27 servidorabm dovecot:
lda(luis.alvarez)<870407>: Debug: program
exec:/usr/sbin/exim: Created
Aug 8 02:13:27 servidorabm dovecot:
lda(luis.alvarez)<870407>: Debug: program
exec:/usr/sbin/exim: Establishing connection
Aug
the script and STDIN and
STDOUT are connected to dovecot-lda. It would be easy to abort the
call of spamc after X seconds (man 'timeout(1)'). But then the input
provided by dovecot-lda and piped into spamc would be lost. You would
therefore have to cache all input in the script that come
ed to dovecot-lda. It would be easy to abort the call
of spamc after X seconds (man 'timeout(1)'). But then the input provided
by dovecot-lda and piped into spamc would be lost. You would therefore
have to cache all input in the script that comes via STDIN in a file. If
spamc is abor
Corrected a typo in the previous message, should have read
sieve_filter_exec_timeout and not sieve_pipe_exec_timeout
On 10/07/2024 10:41, John Fawcett wrote:
On 10/07/2024 09:40, John Fawcett via dovecot wrote:
On 09/07/2024 09:02, Meinhard Schneider via dovecot wrote:
Hello,
I have
On 10/07/2024 09:40, John Fawcett via dovecot wrote:
On 09/07/2024 09:02, Meinhard Schneider via dovecot wrote:
Hello,
I have set both the values for "sieve_execute_exec_timeout" and
"sieve_extension_exec_timeout" to 60 sec, but according to the log,
this does not seem to affect the 10
On 09/07/2024 09:02, Meinhard Schneider via dovecot wrote:
Hello,
I have a small problem with dovecot-lda. I am using Debian 12 Bookworm:
root@lnxmail01:~# dovecot --version
2.3.13 (89f716dc2)
Historically grown (probably still from sendmail times, long time ago)
I always used procmail for
Hello,
I have a small problem with dovecot-lda. I am using Debian 12 Bookworm:
root@lnxmail01:~# dovecot --version
2.3.13 (89f716dc2)
Historically grown (probably still from sendmail times, long time ago) I
always used procmail for local e-mail delivery. This also included the
call for
Hi,
we have encountered an interesting behavior with users that have their
mailboxes over quota while having sieve-vacation enabled. We do a temp fail, if
a mailbox is over quota.
Problem:
If a remote sender sends an email to such a user (over quota + vacation),
Dovecot directly crea
em on my system. All
mail is sent from postfix to dovecot with lmtp
it simply works better with lda ? :)
return-path is std postfix envelope sender pseudo header, bugs ?
it's not a pseudo header, it is defined starting in rfc-822, as to be
added at time of delievery.
The LDA sho
/... configured? Are they configured
in some kind of loopback config using a lda that it shouldn't be
using? I do know in older postfix versions (I haven't tested it in
3.x) if an email came into my postfix server with a return-path
header, postfix would strip it out before deliver
ix to dovecot with lmtp
it simply works better with lda ? :)
return-path is std postfix envelope sender pseudo header, bugs ?
it's not a pseudo header, it is defined starting in rfc-822, as to be
added at time of delievery.
The LDA should add it, postfix lda add it (virtual/local) and do
Quoting Benny Pedersen :
Christian Kivalo skrev den 2024-01-21 02:08:
Just wish LMTP would not end up with duplicate Return-Path headers..
Duplicate return path headers? I don't see them on my system. All
mail is sent from postfix to dovecot with lmtp
it simply works better wit
Christian Kivalo skrev den 2024-01-21 02:08:
Just wish LMTP would not end up with duplicate Return-Path headers..
Duplicate return path headers? I don't see them on my system. All mail
is sent from postfix to dovecot with lmtp
it simply works better with lda ? :)
return-path is std po
Michael Peddemors skrev den 2024-01-21 00:51:
Just wish LMTP would not end up with duplicate Return-Path headers..
why ?
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
>> I noticed that many places in the documentation and in examples
gleaned from the wilderness, refer to the LDA protocol when
discussing sieve.
>>>
>>> The documentation also mentions that lmtp is preferred over lda,
and seems to say in places that
On January 21, 2024 12:51:00 AM GMT+01:00, Michael Peddemors
wrote:
>On 2024-01-19 16:12, Peter wrote:
>> On 20/01/24 12:28, Joe Acquisto wrote:
>>> I noticed that many places in the documentation and in examples gleaned
>>> from the wilderness, refer to the LDA pro
On 2024-01-19 16:12, Peter wrote:
On 20/01/24 12:28, Joe Acquisto wrote:
I noticed that many places in the documentation and in examples
gleaned from the wilderness, refer to the LDA protocol when discussing
sieve.
The documentation also mentions that lmtp is preferred over lda, and
seems
Thanks for the reassurance. It was a reach, hoping for some straw to
grasp regarding the managesieve 4190 failure to bind.
On 1/19/24 18:28, Joe Acquisto wrote:
I noticed that many places in the documentation and in examples
gleaned from the wilderness, refer to the LDA protocol when
On 20/01/24 12:28, Joe Acquisto wrote:
I noticed that many places in the documentation and in examples gleaned
from the wilderness, refer to the LDA protocol when discussing sieve.
The documentation also mentions that lmtp is preferred over lda, and
seems to say in places that sieve will
Does it matter to sieve implementation if one uses only lmtp?
No. Works here with only lmtp.
--
Christian Kivalo
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
Nope. That's what I do.
With the new Tainting rules in the Exim MTA, LMTP became the easier of the two.
On Fri, Jan 19, 2024 at 5:28 PM Joe Acquisto
wrote:
I noticed that many places in the documentation and in examples
gleaned
from the wilderness, refer to the LDA pro
I noticed that many places in the documentation and in examples gleaned
from the wilderness, refer to the LDA protocol when discussing sieve.
The documentation also mentions that lmtp is preferred over lda, and
seems to say in places that sieve will operate without issue in either case.
Does
Hi,
I have read elsewhere that the Maildir shouldn’t be at the home. But that’s how
it worked for me since the start.
I wonder if I could either change the location of these .dovecot.lda-dupes, or
if I could change home without having to move the mailboxes of all the users.
Today I have this:
Never mind, I found it. I had to add
`replication_dsync_parameters`, with the default values, but with `-x shared`
to exclude the namespace.
Best,
Francis
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@
Hi,
Since I enabled shared mailboxes I'm having these errors:
Sep 27 21:22:41 doveadm(fran...@med-lo.eu): Error: Failed to access
mailbox dovecot/lda-dupes:
stat(/var/mail/vmail/med-lo.eu/francis/.dovecot.lda-dupes/tmp) failed:
Not a directory
And replication stopped.
How can I fix
Weird, but I think I solved it, I had in my postfix main.cf, a line like:
"header_checks = regexp:/etc/postfix/list_unsub_header"
to have a header like: List-Unsubscribe:
mailto:i...@mydomain.com?subject=unsubscribe, and when I removed that line, the
auto-reply seems worked.
BUT, why's so? Th
, from my Gmail account, my maillog
has a line, stating;
Jul 18 15:28:06 mailsrv dovecot:
lda(i...@mywebsite.com)<44812>: sieve:
msgid=:
vacation action: discarding vacation response to mailinglist recipient
Any idea would be much appreciated, thank you!
__
Ahhh... thanks Viktor and ptld. Adding an entry for @sub.example.com to
virtual_alias_maps fixed everything.
How, exactly, do postfix and dovecot communicate when postfix attempts to
determine whether to deliver a message to the dovecot LDA, or to bounce it? In
other words, how does postfix decide to bounce foo, and deliver bar, in these
log messages:
This would be better answered on the postfix
[apologies for postfix/dovecot cross-post]
How, exactly, do postfix and dovecot communicate when postfix attempts
to determine whether to deliver a message to the dovecot LDA, or to
bounce it? In other words, how does postfix decide to bounce foo, and
deliver bar, in these log messages
Sorry - should have gone to the sendmail list; ignore.
On 20/09/2022 10:40, EML wrote:
Is there some way to configure logging so that I can see the command
line that's passed to dovecot-lda? I'm on 2.3.16. Thanks.
Is there some way to configure logging so that I can see the command
line that's passed to dovecot-lda? I'm on 2.3.16. Thanks.
Hallo again.
Dovecot is not doing a look up for the MailDirLoc in the mysql database
after postfix hands over the mail to dovecot-lda.
Postfix knows the right location
# postmap -q u...@domain.net mysql:/etc/postfix/Mail-Mailbox.cf
domain.com/user/
But apparently this has not worked as
My main goal was to warn Dovecot people about potential issues when
upgrading.
Using LMTP is, of course, an option, and should be considered, but there
are still cases when using LDA is appropriate.
In my case I couldn't easily just switch to LMTP, as that would affect
the way spam scannin
You could also just switch to LMTP instead of LDA.
Aki
> On 25/04/2022 16:47 Kirill Miazine wrote:
>
>
> So my workaround was to create a simple wrapper and call it, instead of
> dovecot-lda:
>
> $ cat /local/bin/dovecot-lda-wrapper
> #!/bin/sh
> exec /usr/local/
So my workaround was to create a simple wrapper and call it, instead of
dovecot-lda:
$ cat /local/bin/dovecot-lda-wrapper
#!/bin/sh
exec /usr/local/libexec/dovecot/dovecot-lda \
-d "${LOCAL_PART}@${DOMAIN}" \
-a "${LOCAL_PART}${LOCAL_PART_SUFFIX}@${DOMAIN}"
Hi, all
The just released RC0 for Exim 4.96 will break Dovecot LDA delivery as
described on https://wiki.dovecot.org/LDA/Exim
Here is the relevant ChangeLog entry:
JH/25 Taint-check exec arguments for transport-initiated external processes.
Previously, tainted values could be used. This
restricted for a reason. For example, it'd be nice to have it chgrp
to users, - but postfix does not do initgroups() so this wont work.
And the more interesting question is why sgid dovecot-lda does not
work, why it tries to setUID (to wrong value!) when it gets sticky
bit?
Thanks,
/mjt
> On 21/02/2022 23:24 Michael Tokarev wrote:
>
>
> Hi!
>
> There are many questions on the 'net about the same theme:
> lda(mjt): Error: net_connect_unix(/run/dovecot/stats-writer) failed:
> Permission denied
>
> dovecot-lda is run from postfix
Hi!
There are many questions on the 'net about the same theme:
lda(mjt): Error: net_connect_unix(/run/dovecot/stats-writer) failed: Permission
denied
dovecot-lda is run from postfix as mailbox_command for local users.
There's even a suggestion on dovecot wiki to make dovecot-lda
y that it
would cause dovecot-lda to crash on some specifig messages (and fail
to deliver them). Most of the mails (>99.9%) are delivered ok though.
Here's the trace of the crash in the system logs :
Nov 3 08:48:13 nowhere dovecot: lda(matthieu)<33178>:
Panic: Buffer write out of
Hi,
I've not touched the sieve filters I'm using for a long time (last
modification 2 years ago), but I've upgraded the dovecot package and
the system of my mail server.
~/.dovecot.svbin has not been updated, but I found out today that it
would cause dovecot-lda to crash o
On 10/17/21 02:01, Scott Q. wrote:
> I'm stuck with using Qmail which has no LMTP support, and thus I'm using
> dovecot-lda which has certain drawbacks.
>
> Has anyone found a way to direct dovecot-lda to deliver the mail to the LMTP
> server or any other way for Qmail t
I'm stuck with using Qmail which has no LMTP support, and thus I'm
using dovecot-lda which has certain drawbacks.
Has anyone found a way to direct dovecot-lda to deliver the mail to
the LMTP server or any other way for Qmail to deliver the mail to the
LMTP server directly ?
Thanks!
Hi Benny,
On 11.06.21 14:14, Benny Pedersen wrote:
but remember lda, ltmp is both signle recipient
^^^
are you sure?
'postconf -d' says:
lmtp_destination_recipient_limit = $default_destination_recipient_limit
default_destination_recip
I'm a bit shocked by this
this is the dovecot mailing list ... I do hope that you guys know each
other IRL and are just having friendly jibes at each other (which actually
would make this funny).
otherwise
seriously
trying to start a flame war (or something) on each other I never
thoug
On 13 Jun 2021, at 05:17, Benny Pedersen wrote:
> i dont reply anymore to you,
Best plan.
--
'Never build a dungeon you wouldn't be happy to spend the night in
yourself,' said the Patrician (...). 'The world would be a
happier place if more people remembered that.' --Guards! Gua
On 2021-06-13 12:12, Noel Butler wrote:
BS. it was a simple question did she need to run this option or not,
posting her config is immaterial and a waste of bandwith and everyones
time.
sayed from one with big email signatures
I dont do drugs, but dealing with you I think its becoming a
requi
BS. it was a simple question did she need to run this option or not,
posting her config is immaterial and a waste of bandwith and everyones
time.
I dont do drugs, but dealing with you I think its becoming a requirement
so i'll settle for jack daniels black label instead
On 12/06/2021 23:02,
On 2021-06-12 13:42, Noel Butler wrote:
off your drugs again benny?
WTF should she provide all the config outputs, when she asked a simple
question about one option, and WTF clamav came from is beyond me
this is very important AFTER i replayed to help, not BEFORE,
keep your own drugs problems
On 11/06/2021 22:14, Benny Pedersen wrote:
On 2021-06-11 12:42, Laura Steynes wrote:
so nobody
i am nobody then :)
it would be nice to see postconf -n, and doveconf -n
without this info its hard to help
but remember lda, ltmp is both signle recipient
where come clamav into the mix
On 2021-06-11 12:42, Laura Steynes wrote:
so nobody
i am nobody then :)
it would be nice to see postconf -n, and doveconf -n
without this info its hard to help
but remember lda, ltmp is both signle recipient
where come clamav into the mix ?
i dont know much, but its important to provide
so nobody
On Sun, Jun 6, 2021 at 12:03 PM Laura Steynes
wrote:
> Hi,
> Although dovecot-lda serves us fine, we only average 8k messages an hour,
> peaking at 11k, over 4 machines (mostly for redundancy, we've run this fine
> on just 1 machine, but sometimes clamav makes things
Hi,
Although dovecot-lda serves us fine, we only average 8k messages an hour,
peaking at 11k, over 4 machines (mostly for redundancy, we've run this fine
on just 1 machine, but sometimes clamav makes things get upset, so we
added some more especially since we are growing rapidly, we decid
All,
I am looking for an easy way to setup LDA so that it creates files with group
read permission. Currently LDA/Sieve create the '.dovecot.lda-dupes’ file with
‘0600’. My backup process needs to be able to read the file because it runs as
a user that is in the same group as the LDA pr
Hi Piotr,
On Fri, Jan 01, 2021 at 05:59:42PM +0100, Piotr Auksztulewicz wrote:
> Please note that local.conf is included by include_try directive.
> Check local.conf permissions versus userid running deliver, configured
> in master.cf. If it can't read local.conf, it will simply ignore it.
I wa
/etc/dovecot/local.conf.
>
> In local.conf, I have different values for that, but only if I comment
> them out in 10-mail.conf, I get LDA to try to deliver to the directory
> where it should deliver. Therefore, I assume that later directives are
Please note that local.conf is included
Hi,
thanks to all the people who tried to help me. I have made one more
step into the right direction and wanted to share my findings.
To recap, LDA pulls the right data from userdb, then ignores it and
tries to deliver to the system default maibox location at /var/mail:
On Sun, Dec 27
our configuration more? Maybe you are running
> > dovecot in chroot or something? Can you consider using LMTP instead of
> > LDA?
>
> I want to have as much information about the users and their mailboxes
> as possible in an SQL database (I use Pg), so I can easily move things
>
P instead of
> LDA?
I want to have as much information about the users and their mailboxes
as possible in an SQL database (I use Pg), so I can easily move things
around, change permissions and what-not.
I thought about using LMTP, but so far shyed away from it because I
suspected that it would
Hi,
Toni Mueller, 27.12.20:
16:04:16 dovecot: lda(u...@example.com)<5291>: Error:
Mailbox INBOX: Failed to autocreate mailbox: Mailbox INBOX:
open(/var/mail/u...@example.com) failed: Permission denied (euid=12345(mailbox)
egid=12345(mailbox) missing +w perm: /var/mail, we're not
give it a try (there was another variable needed to be set to avoid
> > clashes with "new", but the name escapes me atm), although it doesn't
> > cover a number of special cases that I have, where the location of the
> > mailboxen does not follow this pattern.
> &g
er of special cases that I have, where the location of the
> mailboxen does not follow this pattern.
>
> In the end, I want the database to be the single source of truth.
well, I tried, but with no luck. LDA still wants to deliver to
/var/mail, as before.
I am pretty sure that it must wor
Hi Tamsy,
(your message was formatted a bit strangely)
On Mon, Dec 28, 2020 at 09:52:17AM +0700, Tamsy wrote:
> Try this:
>
> mail_home = /path-to-mailboxen/%d/%n
> mail_location = maildir:~/Maildir:LAYOUT=fs
>
> and
>
> namespace inbox {
> separator = /
> prefix
*From:* Toni Mueller [mailto:supp...@oeko.net]
*Sent:* Monday, December 28, 2020, 3:18 AM
*To:* Aki Tuomi
*Cc:* dovecot@dovecot.org
*Subject:* LDA ignores virtual mailbox settings
Hi Aki,
thanks for your quick response
Hi Aki,
thanks for your quick response!
On Sun, Dec 27, 2020 at 10:00:40PM +0200, Aki Tuomi wrote:
> > On Sun, Dec 27, 2020 at 09:18:25PM +0200, Aki Tuomi wrote:
> > > > 16:04:16 dovecot: auth: Debug: master in:
> > > > USER#0111#011u...@example.com#011servic
Hi,
On Sun, Dec 27, 2020 at 07:54:56PM +, Toni Mueller wrote:
> My question is why this thing wants to deliver to /var/mail, despite
> having a different location from the userdb, and how I can force it to
> use the location from the userdb.
I forgot to say that this thing has no trouble wr
ize=880, nrcpt=1 (queue active)
> > > 16:04:16 dovecot: auth: Debug: master in:
> > > USER#0111#011u...@example.com#011service=lda
> > > 16:04:16 dovecot: auth: Debug: prefetch(u...@example.com): passdb didn't
> > > return userdb entries, trying the
; > USER#0111#011u...@example.com#011service=lda
> > 16:04:16 dovecot: auth: Debug: prefetch(u...@example.com): passdb didn't
> > return userdb entries, trying the next userdb
> > 16:04:16 dovecot: auth: Debug: sql(u...@example.com): SELECT
> > '/path-to-mailboxen/
quota in an
> PostgreSQL database. The intent is to have postfix deliver the email via
> dovecot's LDA, so I can set quota on a per-user basis.
>
> But for some odd reason, Dovecot's LDA can't find the user data from the
> userdb, and then complains about not being able to
dovecot's LDA, so I can set quota on a per-user basis.
But for some odd reason, Dovecot's LDA can't find the user data from the
userdb, and then complains about not being able to write to /var/mail.
The following example shows how things fail when delivering a message
from Postfix's q
> On 1. Oct 2020, at 11.18, rud...@padaru.de wrote:
>
> Hey,
>
> i have an question about the deliver_log_format.
>
> My log looks sometimes like:
> Oct 1 09:38:01 dd44414 dovecot: lda(user)<20009><9MYzGVmHdV8pTgAA+v7NQw>:
> msgid=<202010010
Hey,
i have an question about the deliver_log_format.
My log looks sometimes like:
Oct 1 09:38:01 dd44414 dovecot: lda(user)<20009><9MYzGVmHdV8pTgAA+v7NQw>:
msgid=<20201001073801.628713ac0...@myserver.com>: saved mail to INBOX
The deliver_log_format settings ar
Dear dovecot users,
I have setup doveot with quota warning.
Once a quota wearning is reached a shell script is called which then
sends an email to the user via dovecot LDA
this is the command in the shell script:
/usr/lib/dovecot/dovecot-lda -d $USER -o "plugin/quota=dict:User
Dear dovecot users,
I have setup doveot with quota warning.
Once a quota wearning is reached a shell script is called which then
sends an email to the user via dovecot LDA
this is the command in the shell script:
/usr/lib/dovecot/dovecot-lda -d $USER -o "plugin/quota=dict:User
, a delivery attempt will be made directly
via LMTP/LDA.
It does not go out (since it’s known local).
In case the domain is not hosted locally, it will be forwarded to a relay, and
that has to decide
where to send it next. If your machine is the best known option for the target
domain, then it
So there is no way to skip Postfix for incoming messages and go directly to
LMTP/LDA but I need two instances of Postfix in that case?
Regarding your second question - it is required to be complaint with Direct
Trust.
Thanks,
Adam
On 4/2/20, 3:07 PM, "dovecot on behalf of Juri Habe
On 02/04/2020 15:18, Adam Raszkiewicz wrote:
> Desired flow looks like:
>
> Dovecot -> Postfix --> Relay Server -┐
> Dovecot <-- LMTP/LDA <-- Postfix <-┘
This mail flow cannot work with one Postfix instance. Either Postfix
know
On Thu, 2 Apr 2020 13:18:14 +, Adam Raszkiewicz stated:
>Desired flow looks like:
>
>Dovecot -> Postfix --> Relay Server -┐
>Dovecot <-- LMTP/LDA <-- Postfix <-┘
>
>Top part of that flow works fine - a message will get to
Desired flow looks like:
Dovecot -> Postfix --> Relay Server -┐
Dovecot <-- LMTP/LDA <-- Postfix <-┘
Top part of that flow works fine - a message will get to the relay server and
it will be send back to the postfix for a local delivery b
On Dienstag, 31. März 2020 21:14:26 CEST Adam Raszkiewicz wrote:
> But then it loops again when get back to the postfix as an incoming message
> (doesn't know that a...@localdomain.com is located on that Dovecot)
+
> Is there any way to disable Dovecot LDA? I want to always
Well as you need LDA to deliver emails from postfix to dovecot, you can't just
turn it off. What you need is a second smtp daemon within postfix, which is
only responsible for local originating emails and is configured to send any
email to your gateway. This way your second smtpd will
am Raszkiewicz wrote:
>
>
>
> Hi,
>
>
> Is there any way to disable Dovecot LDA? I want to always send email via
postfix and relay server even it will be a local delivery within the Dovecot
server
>
Dovecot
1 - 100 of 1766 matches
Mail list logo
