search for: directk

...64. Some other Sieve implementation allowed this, making this change necessary for successful migration. + Implemented the sieve_implicit_extensions setting. The extensions listed in this setting do not need to be enabled explicitly using the Sieve "require" command. This behavior directkly violates the standard, but can be necessary for compatibility with some existing implementations of Sieve. Do not use this setting unless you really need to! - redirect action: Made mail loop detection more robust by forcibly adding a Message-ID header if it is missing. - Prevent logging...

...64. Some other Sieve implementation allowed this, making this change necessary for successful migration. + Implemented the sieve_implicit_extensions setting. The extensions listed in this setting do not need to be enabled explicitly using the Sieve "require" command. This behavior directkly violates the standard, but can be necessary for compatibility with some existing implementations of Sieve. Do not use this setting unless you really need to! - redirect action: Made mail loop detection more robust by forcibly adding a Message-ID header if it is missing. - Prevent logging...

...64. Some other Sieve implementation allowed this, making this change necessary for successful migration. + Implemented the sieve_implicit_extensions setting. The extensions listed in this setting do not need to be enabled explicitly using the Sieve "require" command. This behavior directkly violates the standard, but can be necessary for compatibility with some existing implementations of Sieve. Do not use this setting unless you really need to! - redirect action: Made mail loop detection more robust by forcibly adding a Message-ID header if it is missing. - Prevent logging...

...64. Some other Sieve implementation allowed this, making this change necessary for successful migration. + Implemented the sieve_implicit_extensions setting. The extensions listed in this setting do not need to be enabled explicitly using the Sieve "require" command. This behavior directkly violates the standard, but can be necessary for compatibility with some existing implementations of Sieve. Do not use this setting unless you really need to! - redirect action: Made mail loop detection more robust by forcibly adding a Message-ID header if it is missing. - Prevent logging...

I have a _very_ specific situation where I need queues to work in a very specific manner - I need the queue to only accept one call at a time, even though several phones are attached to it. My memory tells me that queues might have even worked this way in the distant past (pre 1.0)...but I am willing to be mistaken. Is this even remotely possible? PaulH