Nikolaus Rath writes:
> Hello,
>
> I'm starting timsieved with
[...]
>
> However, I'm still able to log into sieve without using any encryption
> at all.
It turns out that I wasn't actually able to log in, the Horde sieve
client just caches sieve scripts. Ever
Hello,
I'm starting timsieved with
# grep sieve /etc/cyrus.conf
# useful if you need to give users remote access to sieve
sieve cmd="timsieved" listen="sieve" prefork=1 maxchild=15
# except for sieve (which deals automatically with Murder)
And imapd.conf con
Andrew Morgan writes:
> On Wed, 8 Jul 2009, Pascal Gienger wrote:
>
>> Nikolaus Rath schrieb:
>>> Hello,
>>>
>>> Apparently (http://wiki.exim.org/CyrusImap) I need to let lmtpd accept
>>> connections from localhost as pre-authenticated to make cyru
Hello,
Apparently (http://wiki.exim.org/CyrusImap) I need to let lmtpd accept
connections from localhost as pre-authenticated to make cyrus and exim
work nicely together.
Can someone explain what this actually means security wise? I.e. what
could a malicious user on localhost do with a pre-authed
Chris Stromsoe <[EMAIL PROTECTED]> writes:
> On Fri, 16 May 2008, Nikolaus Rath wrote:
>
>> Hello,
>>
>> I am delivering mail to cyrus from exim using lmtpd.
>>
>> Apparently lmtpd adds the Return-Path header only after the sieve
>> scripts have
Marc Grober <[EMAIL PROTECTED]> writes:
> I am getting pounded by backscatter as a result of one of my addresses
> being used by some major spammers. Are there any solutions available
> to address all the Delivery failure and bounce notices. I would at
> least like to be able to sort between such
Hello,
I am delivering mail to cyrus from exim using lmtpd.
Apparently lmtpd adds the Return-Path header only after the sieve
scripts have been processed, because in the scripts I cannot match
this header.
If I add the return-path using exim before the message is delivered to
lmtpd, the sieve sc
