-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 11 Apr 2008, [EMAIL PROTECTED] wrote:
"lda" is no protocol, but an acrynom in the chain of MTA and MSA, hence,
remove it here and read the Wiki to enable the Dovecot LDA in exim.
My setup does not look like the Wiki, but it has worked fine
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Mon, 7 Apr 2008, [EMAIL PROTECTED] wrote:
>
>> I have Exim, which does its usual thing, and the LDA is Dovecot (IMAPS).
>
> Dovecot does not support LMTP, hence, Dovecot IMAPS cannot be your LDA.
>
> An LDA is a program the MTA is calling to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 7 Apr 2008, [EMAIL PROTECTED] wrote:
I have Exim, which does its usual thing, and the LDA is Dovecot (IMAPS).
Dovecot does not support LMTP, hence, Dovecot IMAPS cannot be your LDA.
An LDA is a program the MTA is calling to locally delive
> I'm reentering this conversation a little late - but how are you
> delivering mail? Via the Dovecot LDA (in which case Sieve should be
> used)? Or directly via e.g. procmail (in which case Sieve never gets a
> chance to be run)?
I have Exim, which does its usual thing, and the LDA is Dovecot
On Mon, 7 Apr 2008, [EMAIL PROTECTED] wrote:
Unfortunately, this does not seem to be over, yet. I have a script in the
right place now, it is set as Active, but it does not seem to be doing
anything. That is, everything is still going to the INBOX instead of to
the designated directories, and
Unfortunately, this does not seem to be over, yet. I have a script in the
right place now, it is set as Active, but it does not seem to be doing
anything. That is, everything is still going to the INBOX instead of to
the designated directories, and there are no entries in the log files. I
am usi
> sieve_storage = ~/sieve
>
> That means that your script files are inside your home directory in a
> subdirectory called 'sieve'. All scripts must have an extension '.sieve'.
> Meaning that if you put a script called 'ingo' on your server through
> ManageSieve, it is stored in that directory as
[EMAIL PROTECTED] schreef:
OK. I understand all this. Thank you for the reference to the
specification. Apart from the wrong name, I was using PUTSCRIPT instead
of GETSCRIPT. Now, where do I have to put the scripts to GET them? My
home directory does not work, nor do the /var/mail/user/ and
> From what I see here I am not quite sure whether you have understood
> the ManageSieve protocol. The putscript command as specified above
> expects you to provide 2049 bytes of script directly after entering the
> command. It will not accept other commands until it has fully read the
> 2049 byte
(Forgot to CC to the mailinglist)
[EMAIL PROTECTED] schreef:
Here's the latest managesieve session:
OK "Logged in."
CAPABILITY
"IMPLEMENTATION" "dovecot"
"SIEVE" "fileinto reject envelope vacation imapflags notify subaddress
relational comparator-i;ascii-numeric regex"
OK "Capability completed."
There are no entries in any of the logs related to lda or managesieve.
I did run managesieve again (after creating the relevant logfiles), and
got this:
OK "Logged in."
LISTSCRIPTS
imap(root): Warning: Active sieve script symlink /home/cam/.dovecot.sieve
is no symlink.
OK "Listscripts completed."
> First of all, could you provide us with the output of 'dovecot -n' and,
> since you are talking ManageSieve manually to the server already, a
> listing of a protocol session (i.e. commands and responses)? And, if you
> enable mail_debug for the managesieve protocol, you will get messages in
>
[EMAIL PROTECTED] wrote:
With all the mess that my email has become, it makes sense for me to try
to make use of Sieve, but I'm having quite the time finding out how to
make it work. I'm running 1.0.13 on a Debian machine. Sieve appears to
be compiled with it. I can access managesieve, and I h
With all the mess that my email has become, it makes sense for me to try
to make use of Sieve, but I'm having quite the time finding out how to
make it work. I'm running 1.0.13 on a Debian machine. Sieve appears to
be compiled with it. I can access managesieve, and I have set up
dovecot.conf wi
With all the mess that my email has become, it makes sense for me to try
to make use of Sieve, but I'm having quite the time finding out how to
make it work. I'm running 1.0.13 on a Debian machine. Sieve appears to
be compiled with it. I can access managesieve, and I have set up
dovecot.conf wi
15 matches
Mail list logo
