Displaying 20 results from an estimated 5000 matches similar to: "Dovecot lmtp doesn't log"
2017 Dec 01
3
Dovecot lmtp doesn't log
Hi,
Thanks for replying.
initially logging was done via syslog, and the custom log file for mail.*
facility was /var/log/maillog. Everything was logged normally (dovecot
login logouts, sieve scripts, extra debugging lines) but nothing regarding
LMTP. I would receive the email in my inbox but I wouldnt be able to see
anything in the logs regarding this. After that i turned off syslog and
used the
2017 Dec 04
1
Dovecot lmtp doesn't log
Im sure because dovecot from server A takes the email from the MTA and
proxies it to the dovecot on server B that doesnt have an MTA.
On 4 Dec 2017 10:54, "Stephan Bosch" <s.bosch at ox.io> wrote:
>
>
> Op 1-12-2017 om 15:30 schreef Tomislav Perisic:
>
>> Hi,
>>
>> Thanks for replying.
>>
>> initially logging was done via syslog, and the
2017 Dec 04
0
Dovecot lmtp doesn't log
Op 1-12-2017 om 15:30 schreef Tomislav Perisic:
> Hi,
>
> Thanks for replying.
>
> initially logging was done via syslog, and the custom log file for
> mail.* facility was /var/log/maillog. Everything was logged normally
> (dovecot login logouts, sieve scripts, extra debugging lines) but
> nothing regarding LMTP. I would receive the email in my inbox but I
> wouldnt
2017 Nov 30
0
Dovecot lmtp doesn't log
Op 25-11-2017 om 13:00 schreef Tomislav Perisic:
> Does anyone have any idea regarding this?
>
> On 17 Nov 2017 11:36, "Tomislav Perisic" <tomiperisic at gmail.com> wrote:
>
> Hi,
>
> We have 2 servers, server A and server B.
>
> Server A has:
>
> Postfix
> dovecot-2.2.33.2-1.el6.x86_64
>
> Server B has:
>
>
2017 Nov 17
0
Dovecot lmtp doesn't log
Hi,
We have 2 servers, server A and server B.
Server A has:
Postfix
dovecot-2.2.33.2-1.el6.x86_64
Server B has:
dovecot-2.2.33.2-1.el6.x86_64
dovecot-pigeonhole-2.2.33.2-1.el6.x86_64
Server A receives email on postfix, dovecot then takes that email from
postfix and proxies it to Server B Dovecot. Dovecot on Server B takes the
proxied email and delivers it with lmtp to the user inboxes.
The
2018 Nov 25
3
rspamd / imapsieve script is not executed/called
Hi to all of you,
as I am struggling around with this a week or so I'm afraid I have to ask
for help here.
The problem is sitting right in front of the computer, as most of the time.
;-)
So let me explain:
Dovecot is working properly for IMAP with LE certificates, so I thought
it's time to continue with Christoph Haas tutorial primarily and other
blogs and tutorials for setting up the
2018 Mar 31
3
sieve trace directory: error
Hello,
I am using a custom directory for sieve logs and trace and it apparently
generate an error, in some corner case.
- I have an IMAP global sieve script, that is run when appending emails
into the "Archives" folder.
- I have Thunderbird configured to archive emails by year
When archiving an email, for instance in "Archives/2018", I often have
an error message like this:
2018 Mar 31
2
sieve trace directory: error
On 31/03/18 09:29, Stephan Bosch wrote:
> Op 3/31/2018 om 9:27 AM schreef Andr? Rodier:
>> Hello,
>>
>> I am using a custom directory for sieve logs and trace and it apparently
>> generate an error, in some corner case.
>>
>> - I have an IMAP global sieve script, that is run when appending emails
>> into the "Archives" folder.
>> - I
2020 Oct 14
3
How do I enable sieve trace debugging?
Hi all,
I want to enable trace debugging for sieve. Most specifically, I want to know what sieve scripts are running, and whether they?re doing anything.
I cannot get anything other than dead silence from dovecot with respect to sieve.
I have tried the same as asked in this question: https://unix.stackexchange.com/questions/550618/dovecot-sieve-trace-does-not-create-a-log
In my case, the
2018 Dec 10
2
Replication fatal error
Dear suscribers.
I just dont understand this error. Don't know where to look first. If
someone have already meet this problem...
Dec 10 16:06:17 prudence dovecot: dsync-server(address at domain.fr):
Panic: file dsync-brain-mailbox.c: line 370
(dsync_brain_sync_mailbox_deinit): assertion failed: (brain->failed)
Dec 10 16:06:17 prudence dovecot: dsync-server(address at domain.fr):
2018 Mar 02
2
sieve vacation alias handling problem
Hi,
I am using Dovecot LDA as LMTP renders envelope extension unusable.
The problem I have noticed is that when user has multiple aliases sieve
responds to all of them, not only to :addresses specified.
>From testing it seems that :addresses only adds addresses to the list of
"known" emails to check against. It is not limiting it.
As I understand, sieve should check if To: header
2019 Mar 08
2
Sieve scripts not triggered on IMAP inbound messages using IMAPC
Good morning.
I am using Dovecot as an IMAP proxy -- using IMAPC -- and the system is
working great. Thank you for contributing such great software to the
community!
I'm using Dovcot 2.3.5 and Pigeonhole 0.5.5.
My server is located behind a content-filtering firewall that will mark
incoming messages by adding "[SPAM]" to the subject line. I'm trying to use
Sieve to
2023 Mar 15
1
Bug with lmtp_save_to_detail_mailbox
> On 15/03/2023 13:12 EET Dejan <me at dejanstrbac.com> wrote:
>
>
> > lmtp_save_to_detail_mailbox = yes
>
> Plus-delivery conflicts with existing, reserved files such as
> "subscriptions":
>
> Message for kim+subscriptions@ results in:
>
> lmtp(kim@***.com)<14493><SK7sEvaHEWSdOAAAvAYmHA>: Error:
>
2019 Dec 03
2
Dovecot 2.3.8 - How to force index creation for user/mailbox?
Neither of dovecot.index files are created (.cache, .log, .thread) - these
files are created when I open the folder with IMAP client. When mailbox is
not used for long time, the indexing takes very long time. So I'm looking
for any solution (preferably with doveadm) to manually reindex folders in
background.
wt., 3 gru 2019 o 20:23 Aki Tuomi <aki.tuomi at open-xchange.com> napisa?(a):
2018 Mar 03
2
sieve vacation alias handling problem
On 2018-03-03 21:28, Stephan Bosch wrote:
> Op 3/2/2018 om 3:35 PM schreef Karol Augustin:
>> Hi,
>>
>> I am using Dovecot LDA as LMTP renders envelope extension unusable.
>>
>> The problem I have noticed is that when user has multiple aliases sieve
>> responds to all of them, not only to :addresses specified.
>>
>> From testing it seems that
2018 Feb 17
4
2.2.33.2 - Virtual Mailbox Issue bug maybe ?
Been experimenting with virtual mailbox and have a question :-
I have defined 2 virtual mailboxes 'all' and 'combined' as follows ...
virtual/all/dovecot-virtual
virtual/combined
inthread refs x-mailbox INBOX
virtual/combined/dovecot-virtual
!INBOX
INBOX/Sent
INBOX/Drafts
all
When new mail comes I would assume that both virtual mailboxes should
actually see the message
2017 Oct 13
2
Question regarding replication - duplicate emails
Dear Dovecot and community,
We run a small email service for our customers, based on two machines that are made ?redundant or clustered? by using the replication feature of Dovecot.
This works well, for most emails.
Sometimes the following happends:
Email to our support database arrives at the inbox.
Every period a cronjob looks into that mailbox and parses the information and makes a support
2018 Dec 19
2
Fatal: master: service(indexer-worker): child 493 killed with signal 11 (core dumped)
Dear list,
We been having some issues where the indexer-worker is crashing. This
happens on production servers which are handling a slight amount of
mail, but is also reproducible by moving messages. Also, users on my
server are complaining about "Trashed" items coming back etc.
Some details:
- Dovecot 2.3.2.1 in alpine:3.8 based Docker container. As part of the
Mailu distribution.
2016 Jul 27
2
Sieve vacation address problem
Hi,
it seams I have a problem with the vacation script.
The problem is that the vacation answers to a address that is not listed
in the sieve script. I checked the postfix master.conf which delivers to
lda correct parameter.
In the logfile you can see that that office at example.com received a
message that get delivered to user at example.com (with the sievescipt) and
to office at
2018 Aug 06
2
limit sharing ability to certain users
Thanks for the advice Aki
> On 6 Aug 2018, at 07:26, Aki Tuomi <aki.tuomi at dovecot.fi> wrote:
>
> userdb {
> driver = username_format=%Lu passwd-file
> args = /etc/dovecot/share.passwd
> }
Something is wrong with the suggested driver configuration ? Leads to a fatal ? I think there is missing a driver name.
Any chance of doing this via LDAP attribute?
Here is