April 19, 2022 Roberto Puzzanghera 56 comments
The Pigeonhole project provides Sieve support as a plugin for Dovecot's Local Delivery Agent (LDA) and also for its LMTP service. The plugin implements a Sieve interpreter, which filters incoming messages using a script specified in the Sieve language. The Sieve script is provided by the user and, using that Sieve script, the user can customize how incoming messages are handled. Messages can be delivered to specific folders, forwarded, rejected, discarded, etc.
Dovecot Managesieve Server is a service used to manage a user's Sieve script collection.
If you want to support filters in your email you have to manage the Sieve rules by means of the dovecot-pigeonhole
server. When you create a filter with your webmail or email client, you write a Sieve script to customize how messages are delivered, e.g. whether they are forwarded, rejected or stored in special folders. But, in order to do so, Dovecot
must also act as a Local Delivery Agent in place of vpopmail/vdelivermail
, e.g. it must be Dovecot to store the email messages in the users' Maildirs. This guide will try to show how to accomplish this.
Install as follows:
PIGEONHOLE_VER=0.5.20 cd /usr/local/src wget https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-${PIGEONHOLE_VER}.tar.gz tar xzf dovecot-2.3-pigeonhole-${PIGEONHOLE_VER}.tar.gz chown -R root.root dovecot-2.3-pigeonhole-${PIGEONHOLE_VER} cd dovecot-2.3-pigeonhole-${PIGEONHOLE_VER} # the program has to find the dovecot-config file in /usr/local/dovecot/lib/dovecot/ ./configure \ --prefix=/usr/local/dovecot-pigeonhole \ --with-dovecot=/usr/local/dovecot/lib/dovecot/ make
If an old version of pigeonhole
is already installed, delete the symbolic link before installing:
rm /usr/local/dovecot-pigeonhole
Then proceed with the installation
make install cd /usr/local mv /usr/local/dovecot-pigeonhole /usr/local/dovecot-2.3-pigeonhole-${PIGEONHOLE_VER} ln -s /usr/local/dovecot-2.3-pigeonhole-${PIGEONHOLE_VER} /usr/local/dovecot-pigeonhole
Copy the default config files in the actual config directory:
cd /usr/local/dovecot/etc/dovecot/conf.d cp -p ../../../share/doc/dovecot/example-config/conf.d/20-managesieve.conf . cp -p ../../../share/doc/dovecot/example-config/conf.d/90-sieve.conf .
In this way the next time you will run dovecot the two config files will be loaded.
Now enable (if not done yet) the plugin inside 15-lda.conf
protocol lda { mail_plugins = $mail_plugins sieve }
and adjust the file conf.d/20-managesieve.conf
to your needs. This is the file which works for me; you can find it in my tarball:
## ## ManageSieve specific settings ## # Uncomment to enable managesieve protocol: protocols = $protocols sieve # Service definitions service managesieve-login { inet_listener sieve { port = 4190 } } service managesieve { } # Service configuration protocol sieve { }
Now adjust the file conf.d/90-sieve.conf
. This works for me (you have this file in your config directory if you have downloaded my tarball):
## ## Settings for the Sieve interpreter ## # Do not forget to enable the Sieve plugin in 15-lda.conf and 20-lmtp.conf # by adding it to the respective mail_plugins= settings. plugin { sieve = file:~/.sieve;active=~/.sieve/dovecot.sieve sieve_before = /usr/local/dovecot/etc/dovecot/sieve/ sieve_extensions = +notify +imapflags +spamtest }
Now restart dovecot
dovecotctl restart
Read this for more information on how the dot-qmail
files work.
The point is that if you want to use Sieve rules, vdelivermail will no longer deliver your mail but this will be a task to be accomplished by Dovecot LDA. In other words in each domain where you want to enable sieve you must modify the .qmail-default
as follows:
|/var/qmail/bin/preline -f /usr/local/dovecot/libexec/dovecot/deliver -d $EXT@$USER
Of course you can decide to limit the sieve rules to certain users, in that case it is sufficient to adjust the .qmail-user
file in the domain folder or the .qmail
file in the user home dir.
If you decide to enable sieve by default you can always adjust /var/qmail/control/defaultdelivery
provided that you clean .qmail-default
of newly created domain (just remove the first line, never erase that file if you don't want vpopmail
to stop working), even though this is not a good idea. Infact, adjusting defaultdelivery
and cleaning .qmail-default has the risk to throw qmailadmin
into confusion when listing the mailing-lists, because a non existent "default" mailing-list seems to appear in some case. Comments about this would be appreciated.
If you applied my vpopmail
combined patch and compiled with --enable-defauldelivery
your default delivery agent line will be copied from /var/qmail/control/defaultdelivery
. So it would be the case to save there the above line:
echo '|/var/qmail/bin/preline -f /usr/local/dovecot/libexec/dovecot/deliver -d $EXT@$USER' > /var/qmail/control/defaultdelivery
NB: do not use double quotes in the command above, otherwise the $EXT@$USER
variable will be replaced with your current account (@root).
Info: http://tools.ietf.org/html/rfc5235 - http://wiki2.dovecot.org/Pigeonhole/Sieve/Examples
If you decided to let simscan pass through the spam with a score below spam_hits (qmail/control/simcontrol
file), you may want to store them in the Junk folder. In this case Managesieve server will execute a script before processing the user's script so that all spam messages will be discarded or moved into junk and all the other rules ignored.
First of all create a folder where to store your global scripts and assign the write priviledges to the vpopmail user:
cd /usr/local/dovecot/etc mkdir sieve chown -R vpopmail.vchkpw sieve
Modify conf.d/90-sieve.conf to enable the required sieve extensions and load the script that you want to execute before:
sieve_extensions = +spamtest +spamtestplus +relational +comparator-i;ascii-numeric sieve_before = /usr/local/dovecot/etc/sieve/
Now create the script /usr/local/dovecot/etc/sieve/move-spam.sieve
(.sieve
extension otherwise it will be ignored):
require ["fileinto"]; if anyof (header :contains "X-Spam-Flag" "YES") { fileinto "Junk"; } /* Other messages get filed into INBOX */
Every time you modify the global files you have to pre-compile them using the sievec
program (more info here):
su vpopmail cd /usr/local/dovecot/etc/sieve /usr/local/dovecot-pigeonhole/bin/sievec .
First of all try to connect to the 4190 port via telnet. This is what you are going to see if the server is working:
> telnet 0 4190 Trying 0.0.0.0... Connected to 0. Escape character is '^]'. "IMPLEMENTATION" "Dovecot Pigeonhole" "SIEVE" "fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date spamtest spamtestplus" "NOTIFY" "mailto" "SASL" "PLAIN LOGIN CRAM-MD5" "STARTTLS" "VERSION" "1.0" OK "Dovecot ready."
If you create a sieve rule by your mail client (Mozilla Thunderbird provides a special add-on here https://addons.mozilla.org/en-US/thunderbird/addon/2548/) or via webmail (read the next note concerning Roundcube webmail), this is what you should see in the log simply setting a redirect filter:
Oct 22 00:03:13 lda(test@yourdomain.net): Info: sieve: msgid=<c3445037f979a8cb793df1f858b7a4f9@somedomain.com>: forwarded to <someone@somewhere.net>
qq_temporary_problem_(#4.3.0)
June 2, 2023 06:32
qq_temporary_problem_(#4.3.0)
June 1, 2023 21:18
qq_temporary_problem_(#4.3.0)
May 31, 2023 18:22
qq_temporary_problem_(#4.3.0)
May 31, 2023 14:42
qq_temporary_problem_(#4.3.0)
May 31, 2023 14:33
Thank you! for all the documentation, patches and support
May 26, 2023 08:42
free(): double free detected in tcache 2: /var/www/qmail/cgi-bin/qmailadmin
May 17, 2023 15:25
free(): double free detected in tcache 2: /var/www/qmail/cgi-bin/qmailadmin
May 17, 2023 07:46
Tags
apache clamav dkim dovecot ezmlm fail2ban hacks lamp letsencrypt linux linux-vserver lxc mariadb mediawiki mozilla mysql openboard owncloud patches php proftpd qmail qmail to postfix qmail-spp qmailadmin rbl roundcube rsync sieve simscan slackware solr spamassassin spf ssh ssl surbl tcprules tex ucspi-tcp vpopmail vqadmin
Comments
Error net connect
Bob August 5, 2022 21:55
I'm using this in my .qmail files:
However, when I try to deliver mail I get this error in qmail-send:
Any ideas what is causing this?
Reply | Permalink
Error net connect
Roberto Puzzanghera Bob August 5, 2022 22:14
You have to setup the stats-writer service's privileges as explained here
Reply | Permalink
not delivered to the mailbox under domain's subfolder 0 or 1
kengheng April 17, 2022 12:45
Hi,
I'm implementing the Dovecot LDA and Sieve as below:
I noticed that the mail was accepeted and send to local folder, however, if the mailbox in the domain's 0 and 1, was never show the mails.
If I changed to:
The mails show in the mailbox in the domain's 0 and 1,
Reply | Permalink
not delivered to the mailbox under domain's subfolder 0 or 1
Roberto Puzzanghera kengheng April 17, 2022 14:12
Assuming that you are using the sql driver with my sql queries, I think that the userdb lookup for LDA in auth-sql.conf.ext is not correct in your case
You can see that the home dir is not retrieved correctly.
Try to replace it with an explicit sql lookup as follows
Now it should read the correct home dir in the database.
Let me know if this solves, so that I can correct this page
Reply | Permalink
not delivered to the mailbox under domain's subfolder 0 or 1
kengheng Roberto Puzzanghera August 8, 2022 18:35
Hi, I solved it as below:
change: dovecot-sql.conf.ext
A new stored procedure as below:
Reply | Permalink
not delivered to the mailbox under domain's subfolder 0 or 1
Roberto Puzzanghera kengheng August 8, 2022 19:03
Thank's for the contribution, appreciated. I didn't get that you were using the "disable many domains" configuration.
Anyway, I don't understand what's wrong in my procedure, as I select the userdb_home field in the password_query:
so, why not using the prefetch driver for the userdb and avoid to write an additional procedure?
Reply | Permalink
not delivered to the mailbox under domain's subfolder 0 or 1
kengheng Roberto Puzzanghera August 9, 2022 08:24
Hi,
In the dovecot-sql.conf.ex:
The dovecot debug log show:
The dovecot_password_query_disable_many_domains is for password_query, however for user_query, it is still refer to vpopmail table (one table for all domains setup)
Reply | Permalink
not delivered to the mailbox under domain's subfolder 0 or 1
Roberto Puzzanghera kengheng August 9, 2022 11:36
Sorry, you are right. LDA won't work with prefetch and needs its own userdb_query.
I'm going to add your procedure and update my patch
Thanks for the contribution
Reply | Permalink
not delivered to the mailbox under domain's subfolder 0 or 1
Roberto Puzzanghera kengheng August 9, 2022 08:39
>> The dovecot_password_query_disable_many_domains is for password_query, however for user_query, it is still refer to vpopmail table (one table for all domains setup)
No. The password_query can do the stuff for user_query provided that you declare the prefetch driver for user_query in your auth-sql.conf.ext
you can see that in my password query I'm including all the queries needed for user_query:
those field with a "userdb_" prefix are for the user_query.
Please test the prefetch driver and let me know
PS: of course in the @SQL above "vpopmail" stands for the domain table
Reply | Permalink
not delivered to the mailbox under domain's subfolder 0 or 1
kengheng Roberto Puzzanghera August 9, 2022 12:49
In my auth-sql.conf.ext, it is declared driver = prefetch, and still calling for user_query
Reply | Permalink
not delivered to the mailbox under domain's subfolder 0 or 1
Roberto Puzzanghera kengheng August 9, 2022 12:55
Yes, I know. The user_query with prefetch is for the imap connection, while LDA needs a dedicate user_query (I don't know why it is not satisfied by the other one)
Reply | Permalink
not delivered to the mailbox under domain's subfolder 0 or 1
kengheng Roberto Puzzanghera August 9, 2022 14:42
Both procedures return different column name, and I believe password_query & user_query are expecting different column name
dovecot_password_query_disable_many_domains return:
dovecot_user_query_disable_many_domains return:
Reply | Permalink
not delivered to the mailbox under domain's subfolder 0 or 1
Roberto Puzzanghera kengheng August 9, 2022 15:05
Yes. You have to prepend userdb_ if you want those column to be recognized by the user_query with the prefetch driver. I don't know why LDA complains that the password_query doesn't provide enough informations.
Reply | Permalink
dovecot mail delivery
ed vrijmoet July 29, 2020 15:31
Hello Roberto
I am having a problem delivering mail to the mailboxes, incoming mail is accepted and delivered to the queue after that the mail is not delivered to the mailbox.
This is in my log file:
In my defaultdelivery i have | /var/qmail/bin/preline -f /usr/local/dovecot/libexec/dovecot/deliver -d $EXT@$USER
It looks like lda is looking for user ' ' @ domain 'ed' while it should look at user 'ed' @ domain 'xxxx'
where could be the problem
Reply | Permalink
dovecot mail delivery
Roberto Puzzanghera ed vrijmoet July 29, 2020 16:53
Hi Ed, can you share the content of doveconf?
Reply | Permalink
dovecot mail delivery
ed vrijmoet Roberto Puzzanghera August 3, 2020 13:29
Hi Roberto,
Sorry bit late on the awnser had to work.
Wich of the dovecot conf files would you like to see.
Is it possible to past as zip file?
Reply | Permalink
dovecot mail delivery
Roberto Puzzanghera ed vrijmoet August 3, 2020 13:44
the best would be that you post the output of the "doveconf" command on https://pastebin.com/ (don't forget to masquerade your sql pwd :) so that everybody can see your configuration.
Reply | Permalink
dovecot mail delivery
ed vrijmoet Roberto Puzzanghera August 3, 2020 15:52
Hi Roberto, here is my config dovecotconf
Reply | Permalink
dovecot mail delivery
Roberto Puzzanghera ed vrijmoet August 3, 2020 16:18
Can you please post just the output of "dovecot -n" so that only non default options will be shown? Sorry if I didn't tell it before
Reply | Permalink
dovecot mail delivery
ed vrijmoet Roberto Puzzanghera August 3, 2020 16:54
Hi Roberto,
doveconf -n doveconf -n
dovecot-sql.conf.ext dovecot-sql.conf.ext
Reply | Permalink
dovecot mail delivery
Roberto Puzzanghera ed vrijmoet August 3, 2020 17:26
the doveconf seems to be ok. Something seems to alter the envelope before it gets through dovecot/lda. Did you already tested if the the delivery is restored when restoring vdelivermail, i.e. putting "| /home/vpopmail/bin/vdelivermail '' delete" in your .qmail-default?
are you using my patches/installation/configuration? did you added anything to the process that could alter the mail header? wrappers?
Reply | Permalink
dovecot mail delivery
ed vrijmoet Roberto Puzzanghera August 3, 2020 18:17
Hi Roberto,
I tried " | /home/vpopmail/bin/vdelivermail '' delete " my qmail send log tells me the messages are delivered but they are not in the mailbox.
Yes i am using your patches/configuration nothing else.
no SPF or DKIM because i cannot put a TXT record in DNS will check anyway for sender and no EZMLM because i don't need that
Reply | Permalink
dovecot mail delivery
Roberto Puzzanghera ed vrijmoet August 3, 2020 18:54
And the recipient address is correct according to the logs?
Reply | Permalink
Pigeonhole installation - upgrade
miz October 30, 2019 12:02
Hello Roberto,
just a small point: before installing / upgrading dovecot-pigeonhole, I think it's better to perform the same move / relink operation that you describe for dovecot,
in order to keep the old version:
Reply | Permalink
Pigeonhole installation - upgrade
Roberto Puzzanghera miz October 30, 2019 14:26
ok, approved ;-)
Reply | Permalink
POP3 user
nic October 23, 2017 13:57
Hi,
Just wondering, what happen to the spams if the user is on POP3 and Junk folder is not available?
Thanks
nic
Reply | Permalink
Anonymous nic October 29, 2017 10:30
Hi Roberto,
My pop3 user do not have a Junk folder. So spams scoring 6.0 - 9.4 will be discard?
Reply | Permalink
Re: POP3 user
Roberto Puzzanghera Anonymous October 29, 2017 10:47
Do you mean a junk folder in their server's maildir? I haven't verified what happens in that case
Reply | Permalink
Anonymous Roberto Puzzanghera October 29, 2017 15:21
Hi,
Yes. Correct,
POP3 has only
cur
new
tmp
Thanks
Reply | Permalink
Autocreate
Roberto Puzzanghera Anonymous October 29, 2017 19:06
The folders should be autocreated, look at lda and plug-in config
Reply | Permalink
Autocreate
nic Roberto Puzzanghera October 30, 2017 15:58
Hello,
I am using your config files and i had downloaded again to compare. They are exactly the same.
I noticed that if i setup the account as pop3, .Junk will not be created. If i setup with IMAP or login via roundcube, .Junk will be created.
Is it correct? If so, those users who only create their account on pop3 and did not login to roundcube, .Junk will not be created, what will happen to the spam email scoring 6.0 - 9.4 goes to?
Many thanks
nic
Reply | Permalink
Autocreate and dovecot-lda
Roberto Puzzanghera nic October 30, 2017 20:31
Nic, according to the documentation inside 15-lda.conf file, a nonexistent mailbox is automatically created before saving an e-mail into it.
Reply | Permalink
Autocreate and dovecot-lda
Roberto Puzzanghera Roberto Puzzanghera October 31, 2017 09:05
I did a test and it works well. Steps to reproduce
-create a new account
-login via webmail and set a minimum spamscore =1 using your spam/userprefs settings
-manually delete the .Junk folder from shell
-send from the outnet a message to that account. To get a spamscore > 1 you can simply start the body with "Dear friend". It is important to send the test messages from the outnet, otherwise spamassassin won't be called
Reply | Permalink
Autocreate
Roberto Puzzanghera nic October 30, 2017 18:11
Yes, I think this is correct.. that folder is created as soon as user enters the mailbox via imap. What happens to the spam? Unfortunately I don't know, tests would be needed... and I would like to investigate if it's possible to force the autocreation with pop3 as well, when I find some time..
Edit: dovecot-lda is going to autocreate the missing folder before saving the message. Look at 15-lda.conf
Reply | Permalink
Autocreate
nic Roberto Puzzanghera October 30, 2017 21:07
Hello,
Google leads me to these sites.
https://sys4.de/de/blog/2013/02/11/dovecot-virtual-setup-mit-globaler-sieve-spamfilter-regel-fur-pop3-nutzer/
https://wiki.dovecot.org/Plugins/Virtual
I will try them out on a test server. Hopefully i can get it.
Thanks
nic
Reply | Permalink
POP3 and junk folder
Roberto Puzzanghera nic October 23, 2017 21:44
In my configuration, if the score is beyond the allowed threeshold (9.5 or so) the messages will be deleted and not shown to the user, if the score is in the "grey zone" (say 6.0 to 9.5) it is saved in the junk folder inside the Maildir, but the user will never retrieve these messages via POP3. This is because the junk folder is in the server, but the POP3 user just downloads the new messages stored in the Inbox
Reply | Permalink
New versions of dovecot
mz December 24, 2013 14:41
Hello Roberto,
just to let you and all of the users that the procedure works also for version 2.2.9 of dovecot.
I'm testing version 2.2.10 which has been just released.
thank you again !
Reply | Permalink
Good to know, mz! Have you
roberto puzzanghera mz December 24, 2013 14:54
Good to know, mz! Have you already tested pigeonhole-0.4.2? I think it will work as well.
btw, I think I will stick with the 2.2.2 version unless I have to install a new server before the next major release. It is very time consuming to update the dovecot.conf.tar.gz file with all the configuration files.
In case you are doing your configuration files from scratch, having copied them from the share/doc/dovecot/example-config/ dir, I hope you will be so kind to send me a targz. Send me it in private if you like at "roberto dot puzzanghera at sagredo dot eu" so that I can make it available for all users.
Reply | Permalink
yes, I'm using
mz roberto puzzanghera December 24, 2013 16:14
I made my config files starting from the examples and then customizing them step by step following your guide.
I'm using plain vpopmail authentication (not mysql) so configs are a bit different.
Didn't find differences between version 2.2.2 and 2.2.9; I just compiled and installed version 2.2.10 because there are a few interesting updates and bugfix on various quota stuff which I need:
Will definitely send you my files when I'm confident that everything is working correcty, but now I have to go buy the last presents, so Merry Christmas to all of you out there ! :-)
Reply | Permalink
Error in the config file
mz December 16, 2013 15:08
Hello Roberto,
thank you for your GREAT tutorial!
Just to point out a little mistake in the conf file you are pasting here:
should be
as your zipped tar reports correctly.
Thank you !
mz
Reply | Permalink
corrected. thank you
roberto puzzanghera mz December 16, 2013 15:46
corrected. thank you
Reply | Permalink
Dovecot-lda and vpopmail quotas
Anonymous June 24, 2013 14:21
Hi roberto Congrats for your great job I have to admit your blog is the reason why i decided to use this implementation for mail server
I have tried to follow your instructions as closer as as i could. Everything works fine but ... What i noticed is when i use dovecot-lda for delicery the sieve rule works fine but the per user quotas i have set through vpopmail are ignored Any ideas ??
this is my .qmail-default on the domain level
| /usr/bin/spamc | /var/qmail/bin/preline -f /usr/local/libexec/dovecot/deliver -d $EXT@$USER
Reply | Permalink
no idea at the moment..
roberto puzzanghera Anonymous June 24, 2013 16:19
no idea at the moment.. at least I can confirm that my config works fine here
Reply | Permalink
defaultdelivery
nik October 18, 2012 05:29
Thank you for your site.
Everything works fine, but there was a problem with the /var/qmail/control/defaultdelivery
If line |/ var/qmail/bin/preline -f /usr/local/dovecot/libexec/dovecot/deliver -d $EXT@$USER in place .qmail, sieve-script works, if it is placed in .qmail-default, too fine.
According to the description has changed .qmail-default, ie delete the first line, second line #. Added to defaultdelivery command preline, mail delivery stops working. But in the process, I see that defaultdelivery works:
I would be grateful for any idea.
Thank you.
Reply | Permalink
Hi Nik
roberto puzzanghera nik October 18, 2012 06:55
Hi Nik, I would try to clean up the .qmail-default file so that it is completely blank
Reply | Permalink
defauldelivery
nik roberto puzzanghera November 20, 2012 06:43
Hello Roberto!
Thank you very much for your reply.
Sorry for the delay in response.
So. I cleaned .qmail-default.
But mail delivery stopped working.
In qmail logs the message:
The blog reported: "If you decide to enable sieve by default you can always adjust / var / qmail / control / defaultdelivery provided that you clean. Qmail-default of newly created domain (just remove the first line, never erase that file if you don't want vpopmail to stop working), even though this is not a good idea. "
Of course, I can use. Qmail-default, but:
1. Want to understand why this is not working (either you control the situation, or the situation control you)
2. I also need to use bounced messages:
If I use in .qmail-default, these two lines, the messages duplicated, i.e. email goes through 'vdelivermail' and through 'deliver'.
Perhaps there is a solution based on the deliver a bounce message?
Thank you again.
I hope for your help.
P.S. Very uncomfortable system of confirmation messages.The picture is very promiscuous.
Reply | Permalink
Re: defaultdelivery
roberto puzzanghera nik November 20, 2012 08:12
I can confirm that cleaning .qmail-default works fine here. I wrote that it could not be a good idea just because at the time I wrote this note, as I said, qmailadmin showed a maling-list named "default" in that case. I'm doing some test right now but the issue is not shown anymore.
I don't think that this guide would be available to the public if I am not experienced on this topic. That said, vpopmail, qmailadmin and so on are not programmed to make dovecot-lda or whatelse to manage the delivery, but patches and tests are needed. So feel free to contribute posting yours
I suppose that you can do it by means of a global sieve rules.
I know, but I have tens of bots trying to break the captcha filter at the same time. If I relax the filter I would have to connect at least once an hour to check/moderate spam messages..
Reply | Permalink
this is not true
roberto puzzanghera roberto puzzanghera November 20, 2012 13:37
sorry, this is not true, because at the time of dovecot-lda delivery chkuser has already bounced the message..
Reply | Permalink
.qmail-default
nik roberto puzzanghera November 22, 2012 06:11
Hello, Roberto.
Apparently I was wrong to describe the situation.
The file contains two lines:
In this case, the message is delivered to a mailbox twice:
Now, about chkuser.
chkuser closes the session when a message is received for a nonexistent mailbox (ie step rcpt to). I believe that it is wrong, because spammers can understand that this mailbox does not exist. Therefore, I accept all the messages and then vdelivermail deletes messages to nonexistent mailboxes.
Please correct me if I'm wrong.
Therefore, the question is by what means to remove messages to non-existent mailboxes?
Again, that using dovecot vpopmail in the file, it works. But the messages are duplicated.
Thank you for your help!
Reply | Permalink
Hi Nik, of course you get a
roberto puzzanghera nik November 22, 2012 20:46
Hi Nik, of course you get a double relay in the situation described.
I've never tried to make chkuser delete messages for non existent users, but I suppose that it can do it. I would try to play with the CHKUSER_SPECIFIC_BOUNCING variable in the chkuser_settings.h and recompile. The documentation on the purpose is not so clear to me, but it seems like chkuser is going to look for a specific file in the domain dir to decide if the bouncing has to be done.
Let me know if you manage to avoid the reply.
Reply | Permalink
Sieve interpreter AND catch all in .qmail-default
Jan November 26, 2011 22:14
hi roberto,
i wonder how i can make a catch all account available per domain but maintain the the functionality of thie in the .qmail-default per domain:
the above works great untill i activate a catch all account, the i have this instead:
can i combine the two somehow or even better, can i alter the catchall function of qmailadmin to use a different line in .qmail-default including to have both enabled ?
thanks
Jan
Reply | Permalink
in case you are patching
roberto puzzanghera Jan November 26, 2011 23:12
in case you are patching qmail with chkuser, I would try to turn on this chkuser's option
and see if it does the trick. But you have to recompile qmail. See details here http://www.interazioni.it/opensource/chkuser/documentation/chkuser_settings.html
Let me know if it works!
Reply | Permalink
i will have another go on
Jan roberto puzzanghera November 26, 2011 23:18
i will have another go on monday, was at it all day today for over 12hrs now. i am getting 'blind' and start making mistakes. i let you know beginning next week how i get on.
thanks and have a nice sunday
Jan
Reply | Permalink
permission problems with 'sievec'
Jan November 26, 2011 16:23
I am getting errors about directory permission and i am unsure how i can resolve this and stay secure. here the error i get after i have followed this
This is what i get:
Any help would be very much appreciated
Thanks
Jan
Reply | Permalink
Re: permission problems
roberto puzzanghera Jan November 26, 2011 17:13
Hi Jan, it seems like if the sievec file is not executable. In this case, simply try to:
and recompile
Reply | Permalink
I see what i have
Jan roberto puzzanghera November 26, 2011 19:40
I see what i have missed:
Thanks for the help
Reply | Permalink