Displaying 20 results from an estimated 2000 matches similar to: "Dovecot lmtp doesn't log"
2017 Nov 25
2
Dovecot lmtp doesn't log
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:
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
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 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 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
2020 Mar 01
0
dovecot-lmtp dont see otherMailbox record?
Hello Postfix + LDAP , Samba as LDAP server, Dovecot virtual_transport set in postfix to dovecot-lmtp ( for autoresponder support ) Users have their email aliases in the otherMailbox record For example, account_test at example-domain user has an alias: test at exmaple-domain Query from command line works fine: postmap -q test at example-domain ldap://etc/postfix/ad_virtual_
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 Mar 31
0
sieve trace directory: error
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 have Thunderbird configured to archive emails by year
>
> When archiving
2018 May 14
0
sieve trace directory: error
Op 31/03/2018 om 10:50 schreef Andr? Rodier:
> 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
2019 Dec 24
0
Sieve vacation not getting enough headers "no known (envelope) recipient address found in message headers"
I am getting these errors[1]. With fairly default setup where sendmail
is delivering mail via lmtp. Adding these, do not seem to make a
difference. Should I add something to the sendmail configuration?
sieve_vacation_dont_check_recipient = no
sieve_vacation_use_original_recipient = no
[1]
discarding vacation response for implicitly delivered message; no known
(envelope) recipient address
2020 Oct 14
0
AW: How do I enable sieve trace debugging?
Hey,
? nice, thats my question :D
If I remember correctly a log was created, but not under var/log but in the home directory of the mail user. For example /var/mail/user1/sieve.
And not everything was logged, only serious errors. But I can not remember exactly what happened...
we have solved this with sieve extprogramms and the - ubuntu - logger
2014 May 12
0
Released Pigeonhole v0.4.3 for Dovecot v2.2.13.
Hello Dovecot users,
Now that Dovecot v2.2.13 is released, I can release a new Pigeonhole.
Due to changes in Dovecot, this Pigeonhole release will not compile
cleanly against older Dovecot releases.
This release is mainly about bugfixes. One notable addition is that I
have updated the "vnd.dovecot.duplicate" extension to the new IETF draft
"duplicate" extension.
Changelog
2014 May 12
0
Released Pigeonhole v0.4.3 for Dovecot v2.2.13.
Hello Dovecot users,
Now that Dovecot v2.2.13 is released, I can release a new Pigeonhole.
Due to changes in Dovecot, this Pigeonhole release will not compile
cleanly against older Dovecot releases.
This release is mainly about bugfixes. One notable addition is that I
have updated the "vnd.dovecot.duplicate" extension to the new IETF draft
"duplicate" extension.
Changelog
2020 Apr 22
2
Seive + Spamprobe terminates with signal 6
Ubuntu 20.04, Dovecot 2.3.7.2, SpamProbe v1.4d. For the past weeks my
sieve filters that call spamprobe have been crashing out for some users.
I have a dozen similar server setups and this is not happening on any
of the other servers and it was working just fine for a year up until
recently. This particular server is quite busy. There is plenty of disk
space and inode usage is about 2.5%.
2019 Mar 11
0
Sieve scripts not triggered on IMAP inbound messages using IMAPC
Op 08/03/2019 om 15:12 schreef Fred via dovecot:
>
> 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
2019 Jun 19
0
Shared mailbox: share whole inbox
Hi,
I'd like to share the whole INBOX of one user with another. That should
go through:
doveadm acl add -u user1 at example.cz SharedDirectory
user=user2 at example.cz lookup read insert
It's works fine, when I connect through imap I see:
. list "" "*"* LIST (\Noselect \HasChildren) "/" shared* LIST (\Noselect
\HasChildren) "/"
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
2019 May 21
2
How to get original recipient from Postfix when using LMTP?
Many people prefer to use LMTP for delivery from postfix for better
efficiency but X-Original-to header support still missing after many
years. One affect of this is need to set
sieve_vacation_dont_check_recipient = yes which violate Sieve standard
and cause auto-replyies sent to messages that should not happen. Or
abandon LMTP. or abandon postfix??
So while feature request is stalled are