Hello,
I want to install Dovecot Pigeonhole and use the Extdata and Extprograms
plugins on CentOS 7. I prefer to install software via yum, and a reasonably
new version of Dovecot is available in the CentOS repo. But according to the
dovecot documentation, these plugins need to be compiled, so
Hi,
On a new install-from-source with Dovecot 2.2.16rc1, Piegeonhole 0.4.6 and a
grab of the newest Extdata code, I confirmed basic Sieve functionality is
working (made a simple sieve script with a test on message subject resulting in
a fileinto action).
But I cannot get Sieve to see Extdata o
Also, of course I have entered this in 90-plugins.conf
plugin {
seive_plugins = sieve_extdata sieve_extprograms
sieve_extensions = +vnd.dovecot.filter +vnd.dovecot.extdata
}
And enabled sieve for lmtp (as I noted, I have tested that simple
sieve scripting is working OK)
protocol lmtp {
mai
> > Also, of course I have entered this in 90-plugins.conf
> >
> >
> > plugin {
> > seive_plugins = sieve_extdata sieve_extprograms
>
> maybe you have a typo...
> seive != sieve
Oh yes that was problem!! Thank you!! Tricky because it's the plugins
section, dovecot cannot lint it so typos won't b
Hi,
I thought I read that anything from dovecot.conf can be overridden in a
userdb lookup. Or a passdb lookup with "userdb_" prefix.
But I tried for fun change log_path but it never worked. Is that because
logging is special, already started logging before it comes to the
passdb/userdb lookups?
> I thought I read that anything from dovecot.conf can be
> overridden in a
> userdb lookup. Or a passdb lookup with "userdb_" prefix.
>
> But I tried for fun change log_path but it never worked. Is
> that because
> logging is special, already started logging before it comes
> to the
> passdb/user
> Last time I had a few stupid problems in the releases, so
> I'll follow
> Timo's example and I release an RC first.
>
> The highlights include the implementation of the index and
> metadata
> extensions. Quite a few bugs are fixed as well.
When I compiled and installed this, Sieve scripts were
I have some global scripts that were running nicely.
Then I opened one in an editor and (probably, but not 100% sure)
mindlessly saved the file, even though I hadn't made any changes.
Shortly after, Sieve errors started showing in the log:
Error: 4k5JA74R/1TlIwABG/SpMA: sieve: binary save: faile
> > I have some global scripts that were running nicely.
> >
> > Then I opened one in an editor and (probably, but not 100% sure)
> > mindlessly saved the file, even though I hadn't made any changes.
> >
> > Shortly after, Sieve errors started showing in the log:
> >
> > Error: 4k5JA74R/1TlIwABG/Sp
> > > I have some global scripts that were running nicely.
> > >
> > > Then I opened one in an editor and (probably, but not 100% sure)
> > > mindlessly saved the file, even though I hadn't made any changes.
> > >
> > > Shortly after, Sieve errors started showing in the log:
> > >
> > > Error: 4k5J
> >> Last time I had a few stupid problems in the releases, so
> >> I'll follow
> >> Timo's example and I release an RC first.
> >>
> >> The highlights include the implementation of the index and
> >> metadata
> >> extensions. Quite a few bugs are fixed as well.
> > When I compiled and installed th
> > > > I have some global scripts that were running nicely.
> > > >
> > > > Then I opened one in an editor and (probably, but not 100% sure)
> > > > mindlessly saved the file, even though I hadn't made any changes.
> > > >
> > > > Shortly after, Sieve errors started showing in the log:
> > > >
> >
Hi,
How difficult would it be to try to hack some extension to the Dovecot
dict mechanism for someone unfamiliar with the code?
I'm using SQL as a backend and am looking for, at a minimum, the
ability to specify a WHERE clause in addition to the built-in one
that feeds the current username. The
> > > > > I have some global scripts that were running nicely.
> > > > >
> > > > > Then I opened one in an editor and (probably, but not 100% sure)
> > > > > mindlessly saved the file, even though I hadn't made any changes.
> > > > >
> > > > > Shortly after, Sieve errors started showing in the log:
Hi, I'm hoping to get some clarification of the differences between calling
a script using the Sieve extprograms plugin execute method via direct
execution or using the socket feature.
Being naive, I see the socket option and think that way you tell Dovecot
to spawn a daemon and I think that's goi
Hi,
The bounce message generated by the reject extension
has what looks like a hard coded message prefix that
comes before the configurable reason text:
"Your message to was automatically rejected:"
In some cases, the is NOT the original-to
address, which can cause confusion to the sender or
e
I need to connect to a database in a script called using Sieve
extprograms plugin. When delivering mail, Sieve is running
as the mail recipient user, which means any files, either the
sieve script or the extprograms it invokes, are run under that
user's permissions.
What would be a way to hide th
> Not sure how I got it to go away last time.
Might have gotten it to go away by deleting the scripts, causing an
email delivery, THEN creating the scripts again.
Although I think my ideas are all flawed:
I can delete the scripts and recreate and recompile all in the same
minute and I don't ge
> >>> When I compiled and installed this, Sieve scripts were being ignored. Not
> >>> sure if it's my own stupid mistake, but when I put v0.4.6 back in place,
> >>> it
> >>> worked fine. No configuration changes, only make install on the different
> >>> sources and restart dovecot.
> >> Could you
> Since E.B. still got an obscure debug message about metadata not being
> up to date, I added debug lines to the remaining places where this could
> emerge (currently only available from hg).
Using hg from just now - first line looks like what you want:
dovecot: lmtp(testu...@ex
> Using hg from just now - first line looks like what you want:
>
> dovecot: lmtp(testu...@example.com): Debug: U5ZtLH8IAVXydgNAM/SpMA: sieve:
> file script: Binary reports different script location (`script2.sieve' rather
> than `/usr/local/var/dovecot/sieve/script2.sieve')
> dovecot: lmtp(testu
> > > However, I do see that Sieve was accessing the user home directory
> > > because for some reason now it just created a ".pki" directory
> > > therein, which inside of it has an empty "nssdb" directory. That
> > > never happened before...? Not a big problem, but I'd prefer not
> > > to have th
> > I thought I read that anything from dovecot.conf can be overridden in a
> > userdb lookup. Or a passdb lookup with "userdb_" prefix.
> >
> > But I tried for fun change log_path but it never worked. Is that because
> > logging is special, already started logging before it comes to the
> > pass
I can't find any posts on this list for peoples using quota_over_flag
http://wiki2.dovecot.org/Quota/Configuration#Overquota-flag_.28v2.2.16.2B-.29
If my userdb is sql what would be best script to use in terms of performance?
(I mean if over-quota-flag triggers script every time it changes and th
For reverse quota warning, it looks like webmail works nice.
quota_warning3 = -storage=100%% quota-warning below %u # user is no longer over
quota
But using thunderbird I deleted enough messages to go below
quota and I deleted them from trash folder too. But mail log
does not show thunderbird co
> Try to right-click a folder and click "compact". That
> should trigger an expunge.
> There are additional configuration items under account
> settings. You
> can make TB expunge on exit, you can turn off local
> cache to make it
> more "live" a la webmail...
>
> See more:
> http://kb.mozillazi
Thanks you so much for your reply--
> > Anyone knows how to use this flag with postfix *making postfix send
> > special reject* "user over quota" note instead of plain SMTP reject??
> > Is an additional database lookup (restriction class?) unavoidable? :(
>
> I don't actually use this, but try per
> > I can't find any posts on this list for peoples using quota_over_flag
> >
> > http://wiki2.dovecot.org/Quota/Configuration#Overquota-flag_.28v2.2.16.2B-.29
> >
> > If my userdb is sql what would be best script to use in terms of
> > performance?
> > (I mean if over-quota-flag triggers script e
Hello, I was testing the extprograms plugin. I think I had it working
in the past, but many things have changed since then, so no use
trying to figure out where it broke - starting over again...
Debug-enabled log give me:
Apr 27 04:11:36 mail dovecot: lmtp(t...@example.com): Debug:
qOGyA0DePHVaOyH
> > Debug-enabled log give me:
> > Apr 27 04:11:36 mail dovecot: lmtp(t...@example.com): Debug:
> > qOGyA0DePHVaOyHEM/SpMA: sieve: action execute: running
> > program: test.sh
> > Apr 27 04:11:36 mail dovecot: lmtp(t...@example.com): Debug:
> > waiting for program `/usr/local/etc/dovecot/sieve_glob
I switched from running my extprograms execute script directly
to running with dovecot socket. Log shows only this
dovecot: lmtp(t...@example.com): Debug: wdi0Tb5VPlGfPnEAM/SpMA: sieve: action
execute: running program: test
dovecot: lmtp(t...@example.com): Debug: Namespace : Using permissions fro
> In another thread you said you are running CentOS. So I strongly guess
> it is SELinux interfering. Check your auditd log
>
> grep -i AVC /var/log/audit/audit.log
>
> You can test whether your setup works after "setenforce 0". That sets
> SELinux into permissive mode, loggging AVCs but not block
> > > Anyone knows how to use this flag with postfix *making postfix send
> > > special reject* "user over quota" note instead of plain SMTP reject??
> > > Is an additional database lookup (restriction class?) unavoidable? :(
> >
> > I don't actually use this, but try perhaps:
> > https://sys4.de/e
> I switched from running my extprograms execute script directly
> to running with dovecot socket. Log shows only this
>
> dovecot: lmtp(t...@example.com): Debug: wdi0Tb5VPlGfPnEAM/SpMA: sieve: action
> execute: running program: test
> dovecot: lmtp(t...@example.com): Debug: Namespace : Using perm
>>> Debug-enabled log give me:
>>> Apr 27 04:11:36 mail dovecot: lmtp(t...@example.com): Debug:
>>> qOGyA0DePHVaOyHEM/SpMA: sieve: action execute: running
>>> program: test.sh
>>> Apr 27 04:11:36 mail dovecot: lmtp(t...@example.com): Debug:
>>> waiting for program `/usr/local/etc/dovecot/sieve_glob
> Will look at this later this week.
Thank you.
> >> I switched from running my extprograms execute script directly
> >> to running with dovecot socket. Log shows only this
> >>
> >> dovecot: lmtp(t...@example.com): Debug: wdi0Tb5VPlGfPnEAM/SpMA: sieve:
> >> action execute: running program: test
> >> dovecot: lmtp(t...@example.com): Debug: Name
> > Last two changes should fix this:
>
>
> Not yet -- this may be unrelated(?) but here is what I have
> after installing the newest source package:
>
> Error: Couldn't load required plugin
> /usr/local/lib/dovecot/lib90_sieve_plugin.so:
> dlopen() failed: /usr/local/lib/dovecot/lib90_sieve_plug
> > > Last two changes should fix this:
> >
> >
> > Not yet -- this may be unrelated(?) but here is what I have
> > after installing the newest source package:
> >
> > Error: Couldn't load required plugin
> > /usr/local/lib/dovecot/lib90_sieve_plugin.so:
> > dlopen() failed: /usr/local/lib/dovecot
> Last two changes should fix this:
> >>>
> >>> Not yet -- this may be unrelated(?) but here is what I have
> >>> after installing the newest source package:
> >>>
> >>> Error: Couldn't load required plugin
> >>> /usr/local/lib/dovecot/lib90_sieve_plugin.so:
> >>> dlopen() failed: /usr/local/
> > I went to go verifying in dovecot-pigeonhole that the two new patches are
> > there
> > by manual inspect the source files you patched. I found only the first one,
> > not
> > http://hg.rename-it.nl/dovecot-2.2-pigeonhole/rev/1eb0362461f0 maybe this
> > because I downloaded a snap shot link a
> Hello, I was testing the extprograms plugin. I think I had it working
> in the past, but many things have changed since then, so no use
> trying to figure out where it broke - starting over again...
>
> Debug-enabled log give me:
> Apr 27 04:11:36 mail dovecot: lmtp(t...@example.com): Debug:
> q
> Only thing still unsolved is my other thread don't know why the exectued
> script has no filesystem access? (like "touch /tmp/test" ignored no error)
See my other post. Problem is systemd PrivateTmp=true hides anything
you do with /tmp from view by anyone else. Wondering if its in memory
or stas
Hello,
I'm having some problems getting LDA to work without
userdb lookups and have a few related questions. This system has all
users in MySQL, each user with unique UID/GID, no local users at all.
Installation is from apt-get.
1) If LDA is invoked without
lookups, is it correct to assume
> 1) If LDA is invoked without
> lookups, is it correct to assume that the "service auth" and
> "service
> auth-worker" can be completely removed from dovecot master
> configuration? (I have tried commenting them out and logging into IMAP,
> which seems to work, not sure if anyone else needs
>> 3) The interesting part -- I am invoking LDA from Maildrop. See:
>> http://thread.gmane.org/gmane.mail.imap.dovecot/65473
>> So
>> when invoked, Maildrop has already dropped to the destination UID/GID
>> and the needed paths are available in the environment. However, using
>> as many p
Timo,
Sorry I didn't see your response until now
>> 3) The interesting part -- I am invoking LDA from Maildrop. See:
>> http://thread.gmane.org/gmane.mail.imap.dovecot/65473 > So
>> when invoked, Maildrop has already dropped to the destination UID/GID
>> and the needed paths are available i
47 matches
Mail list logo
