[Dovecot] doveadm move syntax
Hello I want to forward an email to us...@domain.com box to the box us...@domain.com For this I try to use 'doveadm move', but I'm having problems with the syntax. Could you give me an example please? thanks
Re: [Dovecot] pop3 and imap don't run
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 20 Jun 2013, Mohsen Pahlevanzadeh wrote: I run dovecot and when i use 'ps ax |egrep dovecot' command , i get the following result: what about ps ax|grep imap ? what about lsof -i :143 or netstat -an | grep 143 ? - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBUcK0bF3r2wJMiz2NAQL1cQf/T08fwL+kmijkXpq3zwyG3T0ngcSCMg4h Se3ZsI60r5hxKnbkZ7hxDW0JbUSw1Saw4Ivn57g+2OLGgBSC9m/+Sz4f3gv/Jn9t IR3Z/xqkSldFm4hIKq8xhV9M6QlnB1FzXdZjHXm47l1pzttUzSLf/DL/b21WBVeB SaTa2xUDj0nlhLK5zmPGKeBwm6zLEsiiBcT2k5DOFCY5mlpIjnZEmpracEBhIKou rMYO/1bb9HN/DUhgotcqa/P52X7fQFy+rWUnbGIgztYdykxPSOc/2C6USAEhjJeD d7g8e4uhvbPgoknIkHecAoe6XNL73amFAObangeTxt2mUUKf+OBeoA== =KCNL -END PGP SIGNATURE-
Re: [Dovecot] pop3 and imap don't run
Or even a better command: netstat | grep pop3 netstat | grep imap Will tell you if the ports are in listening status. On Thu, Jun 20, 2013 at 3:51 AM, Steffen Kaiser skdove...@smail.inf.fh-brs.de wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 20 Jun 2013, Mohsen Pahlevanzadeh wrote: I run dovecot and when i use 'ps ax |egrep dovecot' command , i get the following result: what about ps ax|grep imap ? what about lsof -i :143 or netstat -an | grep 143 ? - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBUcK0bF3r2wJMiz2NAQL1cQ**f/T08fwL+**kmijkXpq3zwyG3T0ngcSCMg4h Se3ZsI60r5hxKnbkZ7hxDW0JbUSw1S**aw4Ivn57g+2OLGgBSC9m/+Sz4f3gv/**Jn9t IR3Z/**xqkSldFm4hIKq8xhV9M6QlnB1FzXdZ**jHXm47l1pzttUzSLf/DL/b21WBVeB SaTa2xUDj0nlhLK5zmPGKeBwm6zLEs**iiBcT2k5DOFCY5mlpIjnZEmpracEBh**IKou rMYO/1bb9HN/DUhgotcqa/**P52X7fQFy+rWUnbGIgztYdykxPSOc/**2C6USAEhjJeD d7g8e4uhvbPgoknIkHecAoe6XNL73a**mFAObangeTxt2mUUKf+OBeoA== =KCNL -END PGP SIGNATURE- -- Daniel Reinhardt crypto...@cryptodan.net http://www.cryptodan.net 301-875-7018(c) 410-455-0488(h)
Re: [Dovecot] Sieve file permission problem
Thanks for the answer, I'm not sure what you mean by the additional permission details. Here is a quick example: /var/mail/domainname.hu/zolcsi chmod: 700, owner: vmail:mail After I set the initial sieve filters, the following file and directory gets created: /var/mail/domainname.hu/zolcsi/sieve (directory) chmod: 700, owner: vmail:mail /var/mail/domainname.hu/zolcsi/.dovecot.sieve (symlink to the sieve/sieve.sieve file) chmod: 600, owner: vmail:mail After these two are created then the webmail can't modify them unless I delete the files manually. I looked in the mail.log and mail.err files, but couldn't find anything related to this. Perhaps if I set the log level to a higher value? Or is it possible to connect via telnet to port 2000 and issue some commands to see the actual answers of the ManageSieve server? Best regards, Zoltan On 2013. June 19., Wednesday at 18:40, Daniel Parthey wrote: Please provide permission details of the affected directories and files and possibly error messages from dovecot logfile. Regards Daniel Zoltan Lippai z...@lippai.net (mailto:z...@lippai.net) schrieb: Hi folks, I am using dovecot 2.1.7 with the ManageSieve plugin which works great. Recently I set up Afterlogic webmail on my server (the community version) and it has a nice UI to manage the sieve settings. It uses port 2000 to communicate with dovecot via the ManageSieve plugin. Also, dovecot uses Maildirs to store the messages. The problem is that the permissions on the files that store the sieve rules are to strict. I am talking about the sieve directory and the .dovecot.sieve file. The sieve folder has a chmod 700 and the .dovecot.sieve is chmod 600. Both are owned by vmail:mail If I delete these two items, then the rules can be saved via the web interface. Then these files are created but for some reason the ManageSieve plugin can't modify them. Here is the output of dovecot -n: http://pastebin.com/4eqyBKCA Can you help me out on this? Thanks a lot! Zoltan
Re: [Dovecot] Mbox corruption - Inbox beginning with 'FFrom' or 'FrFrom'
Dimos Alevizos skrev den 2013-06-19 15:00:
protocol imap {
imap_client_workarounds = delay-newmail tb-extra-mailbox-sep
mail_max_userip_connections = 100
mail_plugins = quota imap_quota quota notify mail_log
}
quota listed 2 times
--
senders that put my email into body content will deliver it to my own
trashcan, so if you like to get reply, dont do it
Re: [Dovecot] dovecot enterprise release
mourik jan SOGo skrev den 2013-06-18 11:32: On the dovecot enterprise release pages, only debian 6 compatibility is shown. Are there any plans to support wheezy? (as 7 is stable now, and we are running it...) apt-get source dovecot -b will not work ?, if not then your enterprise is building on precompiled problems -- senders that put my email into body content will deliver it to my own trashcan, so if you like to get reply, dont do it
Re: [Dovecot] dovecot enterprise release
On 6/20/2013 10:54, Benny Pedersen wrote: On the dovecot enterprise release pages, only debian 6 compatibility is shown. Are there any plans to support wheezy? (as 7 is stable now, and we are running it...) apt-get source dovecot -b will not work ?, if not then your enterprise is building on precompiled problems I'm not sure I understand..?
Re: [Dovecot] dovecot enterprise release
mourik jan heupink skrev den 2013-06-20 11:53: I'm not sure I understand..? dovecot is opensource, so why depend on someone that will not package it for enterprise ? get the tarballs. create a deb package. install, be happy -- senders that put my email into body content will deliver it to my own trashcan, so if you like to get reply, dont do it
Re: [Dovecot] dovecot enterprise release
dovecot is opensource, so why depend on someone that will not package it for enterprise ? get the tarballs. create a deb package. install, be happy Ah right. :-) But the advantage of using the http://www.dovecot.fi/ 'enterprise dovecot' would be that they provide up-to-date versions of dovecot. And currently we're running debian wheezy with it's default dovecot, version 2.1.7. MJ
Re: [Dovecot] dovecot enterprise release
mourik jan heupink skrev den 2013-06-20 12:17: Ah right. :-) +1 But the advantage of using the http://www.dovecot.fi/ 'enterprise dovecot' would be that they provide up-to-date versions of dovecot. is there code changes in dovecot for enterprise ?, does it need a patch ? do you really belive Timo take his dev time to test on enterprise ? its waste of time And currently we're running debian wheezy with it's default dovecot, version 2.1.7. all that counts is glibc/gcc, and the source tarballs, the rest is up to YOU -- senders that put my email into body content will deliver it to my own trashcan, so if you like to get reply, dont do it
[Dovecot] HowTo / VirtualUserFlatFilesPostfix
The following is an excerpt from the HOWTO mentioned Per-domain authentication and configuration structure /var/vmail dr-x-- 3 doveauth dovecot 4096 2010-03-17 19:09 auth.d |-- domain.tld Can anybody decypher the |-- domain.tld part please. Regards, treanorv -- View this message in context: http://dovecot.2317879.n4.nabble.com/HowTo-VirtualUserFlatFilesPostfix-tp42887.html Sent from the Dovecot mailing list archive at Nabble.com.
Re: [Dovecot] dovecot enterprise release (benny stop trolling)
Am 20.06.2013 12:25, schrieb Benny Pedersen: is there code changes in dovecot for enterprise ?, does it need a patch ? do you really belive Timo take his dev time to test on enterprise ? its waste of time Am 20.06.2013 10:54, schrieb Benny Pedersen: mourik jan SOGo skrev den 2013-06-18 11:32: apt-get source dovecot -b will not work ?, if not then your enterprise is building on precompiled problems benny stop your foolish trolling and no idea what enterprise means you have little to zero technical knowledge but your mouth wide open examples why benny is only a clueless troll? try to explain the postfix-developer how postfix works is ridiculous wie...@porcupine.org skrev den 2013-06-15 16:13: The server does not announce or accept AUTH, therefore AUTH it is disabled Benny: auth does not need starttls, if auth is not anounced then auth is disabled ___ http://news.gmane.org/gmane.mail.postfix.user/cutoff=237641 postfix have both auth and starttls, starttls is just for clients to use ssl/tls on port 25 STARTTLS has *nothing* to with the port email clients will not use starttls in 2013, since submission is the right thing anyway *foolish idiot* - clients will use STARTTLS *on* submission in 2013 which is *nothing else* than smptd on Port 587 and usually requires auth and if you have zero to nothing of a clue *shut up* wie...@porcupine.org skrev den 2013-06-15 16:13: The server does not announce or accept AUTH, therefore AUTH it is disabled auth does not need starttls, if auth is not anounced then auth is disabled *foolish idiot* with smtpd_tls_auth_only it *is not* announced *until* the TLS handshake between server and client is done signature.asc Description: OpenPGP digital signature
[Dovecot] MySQL tables and official documenttation
Dear all, Unfortunately, i created my tables according to the older tutorial, i search in dovecot.org and postfix.org but i didn't find any official documentation for tables. I want to use PF 2.10 and dovecot 2. Its tutorial was wrote on debian etch. eatch is very old. ---mohsen
Re: [Dovecot] dovecot enterprise release (benny stop trolling)
Reindl Harald skrev den 2013-06-20 14:41: Am 20.06.2013 12:25, schrieb Benny Pedersen: is there code changes in dovecot for enterprise ?, does it need a patch ? do you really belive Timo take his dev time to test on enterprise ? its waste of time Am 20.06.2013 10:54, schrieb Benny Pedersen: mourik jan SOGo skrev den 2013-06-18 11:32: apt-get source dovecot -b will not work ?, if not then your enterprise is building on precompiled problems benny stop your foolish trolling and no idea what enterprise means you have little to zero technical knowledge but your mouth wide open examples why benny is only a clueless troll? try to explain the postfix-developer how postfix works is ridiculous wie...@porcupine.org skrev den 2013-06-15 16:13: The server does not announce or accept AUTH, therefore AUTH it is disabled Benny: auth does not need starttls, if auth is not anounced then auth is disabled ___ http://news.gmane.org/gmane.mail.postfix.user/cutoff=237641 postfix have both auth and starttls, starttls is just for clients to use ssl/tls on port 25 STARTTLS has *nothing* to with the port email clients will not use starttls in 2013, since submission is the right thing anyway *foolish idiot* - clients will use STARTTLS *on* submission in 2013 which is *nothing else* than smptd on Port 587 and usually requires auth and if you have zero to nothing of a clue *shut up* wie...@porcupine.org skrev den 2013-06-15 16:13: The server does not announce or accept AUTH, therefore AUTH it is disabled auth does not need starttls, if auth is not anounced then auth is disabled *foolish idiot* with smtpd_tls_auth_only it *is not* announced *until* the TLS handshake between server and client is done -- senders that put my email into body content will deliver it to my own trashcan, so if you like to get reply, dont do it
Re: [Dovecot] Sieve file permission problem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 20 Jun 2013, Zoltan Lippai wrote:
Thanks for the answer, I'm not sure what you mean by the additional permission
details.
Here is a quick example:
/var/mail/domainname.hu/zolcsi chmod: 700, owner: vmail:mail
After I set the initial sieve filters, the following file and directory gets
created:
/var/mail/domainname.hu/zolcsi/sieve (directory) chmod: 700, owner: vmail:mail
/var/mail/domainname.hu/zolcsi/.dovecot.sieve (symlink to the sieve/sieve.sieve
file) chmod: 600, owner: vmail:mail
After these two are created then the webmail can't modify them unless I delete
the files manually.
Or is it possible to connect via telnet to port 2000 and issue some commands to
see the actual answers of the ManageSieve server?
Er, below you've wrote that It uses port 2000 to communicate with dovecot
via the ManageSieve plugin. Now you write webmail can't modify them ...
. So it seems that the webmail is not using port 2000??
If the UI is using the ManageSieve port, all should work fine, once the
files are delete and only Pigeonhole (Dovecot Sieve ManageSieve)
accesses the files directly.
To test via telnet:
perl -e 'use MIME::Base64; print encode_base64(join(\0, @ARGV)), \n '
account account 'pwd'
$ gnutls-cli -p 2000 --starttls localhost
STARTTLS
^D
Authenticate PLAIN output from perl
CAPABILITY
HAVESPACE myscript 99
Putscript foo {31+}
#comment
InvalidSieveCommand
Putscript mysievescript {110+}
require [fileinto, envelope];
if envelope :contains to tmartin+sent {
fileinto INBOX.sent;
}
Getscript mysievescript
Deletescript mysievescript
setactive mysievescript
gnutls allows you to use STARTTLS; the number in PutScript's {#+}
specifies the number of bytes following the putscript line, that makes up
the script, which must be encoded as UTF8.
If you know Perl, check out
http://search.cpan.org/~ska/Net-ManageSieve-0.12/lib/Net/ManageSieve.pm;
or maybe http://search.cpan.org/~mdom/App-Siesh-0.21/bin/siesh interactive
sieve shell
On 2013. June 19., Wednesday at 18:40, Daniel Parthey wrote:
Please provide permission details of the affected directories and files and
possibly error messages from dovecot logfile.
Regards
Daniel
Zoltan Lippai z...@lippai.net (mailto:z...@lippai.net) schrieb:
Hi folks,
I am using dovecot 2.1.7 with the ManageSieve plugin which works great.
Recently I set up Afterlogic webmail on my server (the community version) and
it has a nice UI to manage the sieve settings. It uses port 2000 to communicate
with dovecot via the ManageSieve plugin. Also, dovecot uses Maildirs to store
the messages.
The problem is that the permissions on the files that store the sieve rules are
to strict.
I am talking about the sieve directory and the .dovecot.sieve file.
The sieve folder has a chmod 700 and the .dovecot.sieve is chmod 600. Both are
owned by vmail:mail
If I delete these two items, then the rules can be saved via the web interface.
Then these files are created but for some reason the ManageSieve plugin can't
modify them.
Here is the output of dovecot -n:
http://pastebin.com/4eqyBKCA
Can you help me out on this?
Thanks a lot!
Zoltan
- --
Steffen Kaiser
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
iQEVAwUBUcMEpl3r2wJMiz2NAQKOpgf+I5WOAWs8+ruXJYen/HhUQK4d6biY9psq
PjKmLdKXD/MBvOpXqKpB9E3dbWQXoYuZeU6nqLFOgJVGbgmbvq4Dpj4/CQod3dMy
wLFECXRDkW8rTVetaC2gLlJN/U/wVlV7nQ3CjtseZZQ+MTBAP+iYcyv0AKYNXafH
BWpUYG1eVPIsCV+GFXjKP0+MkCgHyYpnvySNAIYafV/3+9ETFrC3w7Oa7VsEXJtg
Pm+JEMtkgCxJDHSLamiirrLdL93IZwfeT+AHJ2eQSu0GskPStjjUv/RAu+F7suCM
1PQ7t790L7BY5SDe7LXWzGP+Gz6TC3ZU/FLxB6kcBCy9aCIWMuozXg==
=SLh7
-END PGP SIGNATURE-
Re: [Dovecot] dovecot enterprise release (benny stop trolling)
and why do you troll see the need to mail Wietse what he already knows? people like *you* are the reason why others get moderated or blocked because they can no longer hear bullshit-answers http://news.gmane.org/gmane.mail.postfix.user/cutoff=237641 Benny Pedersen: auth does not need starttls, if auth is not anounced then auth is disabled AUTH requires STARTTLS with smtpd_tls_auth_only=yes. In view of your contributions in recent threads, you are one step away from removal from this mailing list Am 20.06.2013 15:27, schrieb Benny Pedersen: Reindl Harald skrev den 2013-06-20 14:41: Am 20.06.2013 12:25, schrieb Benny Pedersen: is there code changes in dovecot for enterprise ?, does it need a patch ? do you really belive Timo take his dev time to test on enterprise ? its waste of time Am 20.06.2013 10:54, schrieb Benny Pedersen: mourik jan SOGo skrev den 2013-06-18 11:32: apt-get source dovecot -b will not work ?, if not then your enterprise is building on precompiled problems benny stop your foolish trolling and no idea what enterprise means you have little to zero technical knowledge but your mouth wide open examples why benny is only a clueless troll? try to explain the postfix-developer how postfix works is ridiculous wie...@porcupine.org skrev den 2013-06-15 16:13: The server does not announce or accept AUTH, therefore AUTH it is disabled Benny: auth does not need starttls, if auth is not anounced then auth is disabled ___ http://news.gmane.org/gmane.mail.postfix.user/cutoff=237641 postfix have both auth and starttls, starttls is just for clients to use ssl/tls on port 25 STARTTLS has *nothing* to with the port email clients will not use starttls in 2013, since submission is the right thing anyway *foolish idiot* - clients will use STARTTLS *on* submission in 2013 which is *nothing else* than smptd on Port 587 and usually requires auth and if you have zero to nothing of a clue *shut up* wie...@porcupine.org skrev den 2013-06-15 16:13: The server does not announce or accept AUTH, therefore AUTH it is disabled auth does not need starttls, if auth is not anounced then auth is disabled *foolish idiot* with smtpd_tls_auth_only it *is not* announced *until* the TLS handshake between server and client is done signature.asc Description: OpenPGP digital signature
Re: [Dovecot] Calling dovecot-lda from within Antispam pipe script (bash) seems to have no effect
On 6/20/2013 12:14 AM, Bob Miller wrote:
Hi Ben,
I checked over your script, and I don't see the problem either. You
already checked everything that comes to my mind.
Maybe using something like set -e to try and get some output from the
script?
Adding the -e switch doesn't seem to produce any output, either.
But I did think to try echo-ing $? after calling dovecot-lda, which
dumps the program's exit status code. The code is 75, which, according
to the manual at http://wiki.dovecot.org/LDA , means the following:
75 (EX_TEMPFAIL): A temporary failure. This is returned for almost all
failures. See the log file for details.
Well, I checked the log files and there's absolutely nothing written
when my script is executed and yields exit code 75. (But other failures
are indeed written to the same log file, such as when the message can't
be delivered due to over-quota.)
As noted earlier in my doveconf -n output, I added explicit log paths
for LDA:
protocol lda {
mail_plugins = sieve quota
log_path = /var/log/dovecot-lda-errors.log
info_log_path = /var/log/dovecot-lda.log
}
These are the logs that I am checking, which are devoid of messages
relating to this script.
Also, nothing is written to /var/log/mail.log.
The only logging that I am able to discern is to /var/log/syslog:
Jun 20 09:59:33 host imap: antispam: mailbox_is_unsure(Junk): 0
Jun 20 09:59:33 host imap: antispam: mailbox_is_trash(INBOX): 0
Jun 20 09:59:33 host imap: antispam: mailbox_is_trash(Junk): 0
Jun 20 09:59:33 host imap: antispam: mail copy: from trash: 0, to trash: 0
Jun 20 09:59:33 host imap: antispam: mailbox_is_spam(INBOX): 0
Jun 20 09:59:33 host imap: antispam: mailbox_is_spam(Junk): 1
Jun 20 09:59:33 host imap: antispam: mailbox_is_unsure(INBOX): 0
Jun 20 09:59:33 host imap: antispam: mail copy: src spam: 0, dst spam:
1, src unsure: 0
Jun 20 09:59:33 host imap: antispam: running mailtrain backend program
/usr/bin/sa-learn-pipe.sh
Jun 20 09:59:33 host imap: antispam: running mailtrain backend program
/usr/bin/sa-learn-pipe.sh
Jun 20 09:59:33 host imap: antispam: running mailtrain backend program
parameter 1 --debug
Jun 20 09:59:33 host imap: antispam: running mailtrain backend program
parameter 2 --username=amavis
Jun 20 09:59:33 host imap: antispam: running mailtrain backend program
parameter 3 --spam
I'm not sure what to try next...
Thanks for the help,
-Ben
Re: [Dovecot] HowTo / VirtualUserFlatFilesPostfix
* treanorv trean...@gmail.com 2013.06.20 12:31: The following is an excerpt from the HOWTO mentioned Per-domain authentication and configuration structure /var/vmail dr-x-- 3 doveauth dovecot 4096 2010-03-17 19:09 auth.d |-- domain.tld It is meant as a hint/illustration rather than actual output of 'ls'. In this configuration example the domain specific part will reside under the 'auth.d' dir - the actual passwd-file will be in the 'domain.tld' directory below 'auth.d'. Regards Thomas signature.asc Description: Digital signature
Re: [Dovecot] dovecot enterprise release (benny stop trolling)
On Thu, 20 Jun 2013 15:54:15 +0200 Reindl Harald articulated: and why do you troll see the need to mail Wietse what he already knows? people like *you* are the reason why others get moderated or blocked because they can no longer hear bullshit-answers Wrong! Most people get bounced because they either feed the trolls, continually propagate misinformation under the guise of fact or continue to argue a point after they have been proven wrong. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __
Re: [Dovecot] dovecot enterprise release (benny stop trolling)
Am 20.06.2013 16:34, schrieb Jerry: On Thu, 20 Jun 2013 15:54:15 +0200 Reindl Harald articulated: and why do you troll see the need to mail Wietse what he already knows? people like *you* are the reason why others get moderated or blocked because they can no longer hear bullshit-answers Wrong! Most people get bounced because they either feed the trolls, continually propagate misinformation under the guise of fact or continue to argue a point after they have been proven wrong *not* wrong i got not only one time bounced because i did no longer find any nice word for idiots which argue a point after they have been proven wrong instead the foolish trolls like the one i answered here signature.asc Description: OpenPGP digital signature
Re: [Dovecot] HowTo / VirtualUserFlatFilesPostfix
Thomas, I understand, thank you. When is a comment not a comment and visa versa ? Regards, treanorv On Thu, Jun 20, 2013 at 3:13 PM, Thomas Leuxner [via Dovecot] ml-node+s2317879n42894...@n4.nabble.com wrote: * treanorv [hidden email]http://user/SendEmail.jtp?type=nodenode=42894i=0 2013.06.20 12:31: The following is an excerpt from the HOWTO mentioned Per-domain authentication and configuration structure /var/vmail dr-x-- 3 doveauth dovecot 4096 2010-03-17 19:09 auth.d |-- domain.tld It is meant as a hint/illustration rather than actual output of 'ls'. In this configuration example the domain specific part will reside under the 'auth.d' dir - the actual passwd-file will be in the 'domain.tld' directory below 'auth.d'. Regards Thomas *signature.asc* (205 bytes) Download Attachmenthttp://dovecot.2317879.n4.nabble.com/attachment/42894/0/signature.asc -- If you reply to this email, your message will be added to the discussion below: http://dovecot.2317879.n4.nabble.com/HowTo-VirtualUserFlatFilesPostfix-tp42887p42894.html To unsubscribe from HowTo / VirtualUserFlatFilesPostfix, click herehttp://dovecot.2317879.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_codenode=42887code=dHJlYW5vcnZAZ21haWwuY29tfDQyODg3fDg1NjYwOTQ1Mg== . NAMLhttp://dovecot.2317879.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml -- View this message in context: http://dovecot.2317879.n4.nabble.com/HowTo-VirtualUserFlatFilesPostfix-tp42887p42897.html Sent from the Dovecot mailing list archive at Nabble.com.
Re: [Dovecot] Calling dovecot-lda from within Antispam pipe script (bash) seems to have no effect
It really boils-down to the fact that I can call the following on the command-line and it functions as expected: su vmail -c '/usr/lib/dovecot/deliver -a sa-train...@example.com -d sa-train...@example.com -m Training.SPAM -p /tmp/sendmail-msg-25794.txt' Yet, when I attempt to do the exact same thing from within the pipe script that Dovecot Antispam calls, I receive exit code 75 from deliver/dovecot-lda and absolutely nothing is logged, with exception of the information of which I'm already aware (logged to syslog). I am echo-ing $(whoami) just before calling deliver within the pipe script and the output is vmail. So, it's not as though the vmail user somehow lacks the permissions required to send via dovecot-lda. What is the explanation for this behavior? It has to be something to do with how the plug-in calls the script. Does the plug-in call the script in some other context, like chroot? As a final point of note, is it just me, or is the 90-plugin.conf snippet incorrect at the bottom of http://wiki2.dovecot.org/Plugins/Antispam ? Those values appear to be for the analogous Dovecot 1 plug-in, e.g., antispam_mail_sendmail is used, when the equivalent directive is called antispam_pipe_program in versions = 2.0. -Ben
Re: [Dovecot] MySQL tables and official documenttation
On 20-06-2013 15:04, Mohsen Pahlevanzadeh wrote: Dear all, Unfortunately, i created my tables according to the older tutorial, i search in dovecot.org and postfix.org but i didn't find any official documentation for tables. Because Dovecot wiki says: Dovecot supports user authentication against a MySQL-database. (http://wiki2.dovecot.org/FeatAuthMysql) my guest would be that you are trying to find the definitions which are given here: http://wiki2.dovecot.org/AuthDatabase/SQL I want to use PF 2.10 and dovecot 2. i'm sorry, but i dont know what 'PF 2.10' is (but that could be my problem ;) Its tutorial was wrote on debian etch. eatch is very old. ---mohsen
Re: [Dovecot] MySQL tables and official documenttation
On 6/20/2013 9:04 AM, Mohsen Pahlevanzadeh wrote: Dear all, Unfortunately, i created my tables according to the older tutorial, i search in dovecot.org and postfix.org but i didn't find any official documentation for tables. I want to use PF 2.10 and dovecot 2. Its tutorial was wrote on debian etch. eatch is very old. You'll want to look at the following website for postfixadmin stuff: http://sourceforge.net/projects/postfixadmin/ http://postfixadmin.sourceforge.net/ Roughly, the install process is: 1. Create a database user in mysql and create the database 2. Install the postfixadmin tgz contents somewhere under /var/www 3. Fire up your webbrowser and point it at the postfixadmin setup.php URL If you follow the install directions, the postfixadmin page will create your database for you. After which you can start populating the database with domains, mailboxes and aliases. (Installing RoundCube is a similar process.)
Re: [Dovecot] doveadm move syntax
On 6/19/2013 10:25 PM, vincent truc wrote: Hello I want to forward an email to us...@domain.com box to the box us...@domain.com For this I try to use 'doveadm move', but I'm having problems with the syntax. Could you give me an example please? Assuming that you looked at man doveadm-move (I had to dig for a few minutes to uncover that)... EXAMPLE Move jane's messages - received in September 2011 - from her INBOX into her archive. doveadm move -u jane Archive/2011/09 mailbox INBOX BEFORE \ 2011-10-01 SINCE 01-Sep-2011 At a guess... Archive/2011/09 can be either a path relative to the origin user, or an absolute destination such as: maildir:/backup/20101126/jane.doe/Maildir I don't know if it automatically handles putting the proper permissions on the destination files though. I'm basing that guess on the examples at the bottom of man doveadm-import.
Re: [Dovecot] Calling dovecot-lda from within Antispam pipe script (bash) seems to have no effect
Ben Johnson writes: It really boils-down to the fact that I can call the following on the command-line and it functions as expected: su vmail -c '/usr/lib/dovecot/deliver -a sa-train...@example.com -d sa-train...@example.com -m Training.SPAM -p /tmp/sendmail-msg-25794.txt' Yet, when I attempt to do the exact same thing from within the pipe script that Dovecot Antispam calls, I receive exit code 75 from deliver/dovecot-lda and absolutely nothing is logged, with exception of the information of which I'm already aware (logged to syslog). Have you also checked the environment variables? I think dovecot-lda gets some information from them. Also, it's possible the PATH or some other critical environment variables is different, causing the difference in outcome. Joseph Tam jtam.h...@gmail.com
[Dovecot] Would attempting plaintext auth repeatably cause a DOS and server to crash?
Hey All, I'm just wondering whether this is what caused my server to crash. Started last night in NZ land. Jun 20 19:22:11 elm dovecot: imap-login: Disconnected (tried to use disallowed plaintext auth): user=, rip=attackerip, lip=10.0.0.3, session=0C8LzpDfZQDINsQC occasionally get Jun 20 19:22:52 elm dovecot: imap-login: Disconnected (no auth attempts in 1 secs): user=, rip=attackerip, lip=10.0.0.3, session=bHdz0JDfpwDINsQC or in 0 secs last at Jun 20 19:26:24 elm dovecot: imap-login: Disconnected (tried to use disallowed plaintext auth): user=, rip=attackerip, lip=10.0.0.3, session=1MUR3ZDfcwDINsQC and a minute later the server lost contact to the world. When I checked a bit later, the underlying host machine (dovecot runs on a VM (KVM)) had been powered off. Now, here in NZ land, there was also a crazy storm last night, and lots of brown outs. There could potentially of been a surge that killed it, but the UPS was still running fine when I started it again. The attack lasted around 4 minutes, in which there was 1161 lines in the log for a single attacker ip, and no other similar logs previously. Would this be enough to kill not only the VM running dovecot, but the underlying host machine? All up to date with patches, running debian stable (wheezy). dovecot-core debian package version 1:2.1.7-7 dovecot version 2.1.7 I notice there is a version 2.2.3 out, but not in debian yet. Could this fix this issue? I don't particularly want to have it happen again :D. Any thoughts? Cheers, Hugh
Re: [Dovecot] Calling dovecot-lda from within Antispam pipe script (bash) seems to have no effect
Hi Ben, Maybe using something like set -e to try and get some output from the script? Adding the -e switch doesn't seem to produce any output, either. To be clear, I meant putting the line: set -e near the top of your script. I forget exactly how it functions, but it makes it so when a script fails it spits out a why on stdout (or maybe stderr). I believe the -x argument does something useful for troubleshooting too, but it's been too long. `man bash` knows all... It really boils-down to the fact that I can call the following on the command-line and it functions as expected: su vmail -c '/usr/lib/dovecot/deliver -a sa-train...@example.com -d sa-train...@example.com -m Training.SPAM -p /tmp/sendmail-msg-25794.txt' Yet, when I attempt to do the exact same thing from within the pipe script that Dovecot Antispam calls, I receive exit code 75 from deliver/dovecot-lda and absolutely nothing is logged, with exception of the information of which I'm already aware (logged to syslog). I am echo-ing $(whoami) just before calling deliver within the pipe script and the output is vmail. So, it's not as though the vmail user somehow lacks the permissions required to send via dovecot-lda. There are two things that came to mind when I read your mail yesterday. They are the first things I check for when my commands work and my scripts don't. The first is $PATH, I have found innumerable times when a script wouldn't run it was because it wasn't running with a fully loaded $PATH variable, and this is especially true if you are launching your script from cron. To work around this I either put a PATH= at the top of the script, or I run the script as an argument to bash instead of using the executable bit (ie `bash /path/to/script.sh` instead of `./script.sh`) so the path is retained from the shell. I decided against mentioning this yesterday because I noted you only used full paths in your script, which should also work to avoid this problem. The other thing I didn't mention was the permissions on the path to /usr/lib/dovecot/deliver (or any other path, really). Directories with no world read/execute can prevent scripts from using files beneath them if they don't have permissions on each directory level in the path. I didn't mention this yesterday because you said you ran the script as vmail. However, looking at your su vmail -c command, I remember some times when su postrgres -c didn't work when su - postrgres then running the command did. Probably neither of these will be useful to you, but I mention them in hope that they trigger and idea or set you on an investigative path that proves helpful... What is the explanation for this behavior? It has to be something to do with how the plug-in calls the script. Does the plug-in call the script in some other context, like chroot? As a final point of note, is it just me, or is the 90-plugin.conf snippet incorrect at the bottom of http://wiki2.dovecot.org/Plugins/Antispam ? Those values appear to be for the analogous Dovecot 1 plug-in, e.g., antispam_mail_sendmail is used, when the equivalent directive is called antispam_pipe_program in versions = 2.0. -Ben
Re: [Dovecot] Calling dovecot-lda from within Antispam pipe script (bash) seems to have no effect
I got another quick idea, too; try running dovecot in the foreground. Maybe something that isn't being written to the log will show up on the terminal... -- Computerisms Bob Miller 867-334-7117 / 867-633-3760 http://computerisms.ca On Thu, 2013-06-20 at 19:00 -0700, Bob Miller wrote: Hi Ben, Maybe using something like set -e to try and get some output from the script? Adding the -e switch doesn't seem to produce any output, either. To be clear, I meant putting the line: set -e near the top of your script. I forget exactly how it functions, but it makes it so when a script fails it spits out a why on stdout (or maybe stderr). I believe the -x argument does something useful for troubleshooting too, but it's been too long. `man bash` knows all... It really boils-down to the fact that I can call the following on the command-line and it functions as expected: su vmail -c '/usr/lib/dovecot/deliver -a sa-train...@example.com -d sa-train...@example.com -m Training.SPAM -p /tmp/sendmail-msg-25794.txt' Yet, when I attempt to do the exact same thing from within the pipe script that Dovecot Antispam calls, I receive exit code 75 from deliver/dovecot-lda and absolutely nothing is logged, with exception of the information of which I'm already aware (logged to syslog). I am echo-ing $(whoami) just before calling deliver within the pipe script and the output is vmail. So, it's not as though the vmail user somehow lacks the permissions required to send via dovecot-lda. There are two things that came to mind when I read your mail yesterday. They are the first things I check for when my commands work and my scripts don't. The first is $PATH, I have found innumerable times when a script wouldn't run it was because it wasn't running with a fully loaded $PATH variable, and this is especially true if you are launching your script from cron. To work around this I either put a PATH= at the top of the script, or I run the script as an argument to bash instead of using the executable bit (ie `bash /path/to/script.sh` instead of `./script.sh`) so the path is retained from the shell. I decided against mentioning this yesterday because I noted you only used full paths in your script, which should also work to avoid this problem. The other thing I didn't mention was the permissions on the path to /usr/lib/dovecot/deliver (or any other path, really). Directories with no world read/execute can prevent scripts from using files beneath them if they don't have permissions on each directory level in the path. I didn't mention this yesterday because you said you ran the script as vmail. However, looking at your su vmail -c command, I remember some times when su postrgres -c didn't work when su - postrgres then running the command did. Probably neither of these will be useful to you, but I mention them in hope that they trigger and idea or set you on an investigative path that proves helpful... What is the explanation for this behavior? It has to be something to do with how the plug-in calls the script. Does the plug-in call the script in some other context, like chroot? As a final point of note, is it just me, or is the 90-plugin.conf snippet incorrect at the bottom of http://wiki2.dovecot.org/Plugins/Antispam ? Those values appear to be for the analogous Dovecot 1 plug-in, e.g., antispam_mail_sendmail is used, when the equivalent directive is called antispam_pipe_program in versions = 2.0. -Ben
