Radim Roska | 1 Jan 2009 18:05
Picon

Re: delivers mail to bad directory(prefix) using sieve filters

well..thanks :)..but thats not so simple as it could seem..at least i didnt
figure out how to do it :).

Squirrelmail does not allow to create folders without prefix. Anyway
according to following mail it seems it could still be problem in dovecot

http://www.dovecot.org/list/dovecot/2007-September/025415.html

but its already more than a year..and it looks its still not working in
1.0.15 (stable on debian from backports)

Is it possible to patch stable version??

Thanks

Radim

On Tue, Dec 23, 2008 at 3:09 PM, Neil <kngspook <at> gmail.com> wrote:

> On Tue, Dec 23, 2008 at 4:53 AM, Radim Roska <radim.roska <at> gmail.com>
> wrote:
> > really nobody has similar issue?
> >
> > On Mon, Dec 15, 2008 at 7:29 PM, Radim Roska <radim.roska <at> gmail.com>
> wrote:
> >
> >> Hi,
> >>
> >> I've installed dovecot debian stable(from backports) version (1.0.15).
> Its
(Continue reading)

Radim Roska | 1 Jan 2009 18:31
Picon

Re: delivers mail to bad directory(prefix) using sieve filters

ok..i somehow missed one sentence on dovecot wiki. Its written that
namespaces are not working..so no sieve client can work correctly, right?

Any guess when will 1.1 be stable in backports for debian stable?

Thanks
Radim

On Thu, Jan 1, 2009 at 6:05 PM, Radim Roska <radim.roska <at> gmail.com> wrote:

> well..thanks :)..but thats not so simple as it could seem..at least i didnt
> figure out how to do it :).
>
> Squirrelmail does not allow to create folders without prefix. Anyway
> according to following mail it seems it could still be problem in dovecot
>
> http://www.dovecot.org/list/dovecot/2007-September/025415.html
>
> but its already more than a year..and it looks its still not working in
> 1.0.15 (stable on debian from backports)
>
> Is it possible to patch stable version??
>
> Thanks
>
> Radim
>
>
> On Tue, Dec 23, 2008 at 3:09 PM, Neil <kngspook <at> gmail.com> wrote:
>
(Continue reading)

Guillaume Hilt | 2 Jan 2009 15:38
Favicon
Gravatar

deliver looking into root directory for sieve configuration ?

    Hi,

I'm using dovecot (+sieve), dspam, clamav and postfix with wirtual users 
and domains.
When the server receive an email, I get this error :
Jan  2 14:48:52 mail postfix/qmgr[13573]: 89DE1276C42B: 
from=<postmaster <at> shadowprojects.org>, size=926, nrcpt=1 (queue active)
Jan  2 14:48:52 mail deliver(postmaster <at> adomain.fr): chdir(/root) 
failed: Permission denied
Jan  2 14:48:52 mail deliver(postmaster <at> adomain.fr): 
stat(/root/.dovecot.sieve) failed: Permission denied
Jan  2 14:48:52 mail deliver(postmaster <at> adomain.fr): 
msgid=<495E1B33.5020009 <at> shadowprojects.org>: saved mail to INBOX
Jan  2 14:48:52 mail postfix/lmtp[13584]: 89DE1276C42B: 
to=<postmaster <at> adomain.fr>, 
relay=mail.mydomain.com[/var/run/dspam/dspam.sock], delay=0.07, 
delays=0.05/0/0/0.01, dsn=2.6.0, status=sent (250 2.6.0 
<postmaster <at> adomain> Message accepted for delivery)

Why does it look inside the /root folder for sieve configuration ?
All virtual mailboxes are in /home/vmail/DOMAIN/USER/.maildir (owned by 
postfix:postfix; dspam has been put in the postfix group)

I uploaded the following config files in http://hiltg.pastebin.com/ :
- main.cf
- master.cf
- dovecot.conf
- dspam.conf

(mails are supposed to be delivered to the mailbox by dovecot, which is 
(Continue reading)

Charles Marcus | 2 Jan 2009 16:07

Re: deliver looking into root directory for sieve configuration ?

On 1/2/2009, Guillaume Hilt (postmaster <at> shadowprojects.org) wrote:
> I uploaded the following config files in http://hiltg.pastebin.com/ :
> - main.cf
> - master.cf
> - dovecot.conf
> - dspam.conf 

Posting to a service like this is really a bother - just paste into the
email body...

Also, you should only post output of 'postconf -n' and 'dovecot -n'...
this shows the actual working config, which, believe it or not,
sometimes can be different from what you think it is - it also skips the
comments, which really makes reading a config file a lot harder.

Please try again...

--

-- 

Best regards,

Charles

Guillaume Hilt | 2 Jan 2009 16:10
Favicon
Gravatar

Re: deliver looking into root directory for sieve configuration ?

 # postconf -n
broken_sasl_auth_clients = yes
command_directory = /usr/sbin
config_directory = /etc/postfix
content_filter = lmtp:unix:/var/run/dspam/dspam.sock
daemon_directory = /usr/lib64/postfix
data_directory = /var/lib/postfix
debug_peer_level = 2
home_mailbox = .maildir/
html_directory = /usr/share/doc/postfix-2.5.5/html
mail_owner = postfix
mailbox_command = /usr/bin/dspam --deliver=innocent -- -d %u
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
mydestination = $myhostname, localhost.$mydomain, localhost,    
mail.$mydomain, www.$mydomain, ftp.$mydomain
mydomain = apteo.com
myhostname = mail.apteo.com
mynetworks = 127.0.0.0/8, hash:/etc/postfix/pop-before-smtp
myorigin = $mydomain
newaliases_path = /usr/bin/newaliases
queue_directory = /var/spool/postfix
readme_directory = /usr/share/doc/postfix-2.5.5/readme
recipient_canonical_maps = hash:/etc/postfix/recipient_canonical
recipient_delimiter = +
sample_directory = /etc/postfix
sender_canonical_maps = hash:/etc/postfix/sender_canonical
sendmail_path = /usr/sbin/sendmail
setgid_group = postdrop
smtp_sender_dependent_authentication = yes
(Continue reading)

Charles Marcus | 2 Jan 2009 17:49

Re: deliver looking into root directory for sieve configuration ?

On 1/2/2009 10:10 AM, Guillaume Hilt wrote:
> # OS: Linux 2.6.24.5-grsec-xxxx-grs-ipv4-64

Hmmm... maybe it is a grsec problem? I can't help you there...

> ssl_key_password: Y0ullN3v3rF1ndTh1sPassphras3 

If thats really your passphrase, you'd best change it asap...

> smtpd_client_restrictions = permit_mynetworks

Redundant... remove this...

> smtpd_recipient_restrictions = 
>  reject_unauth_pipelining,

useless here... either put this in smtpd_data_restrictions, or remove it

>  reject_non_fqdn_recipient,
>  reject_unknown_recipient_domain,
>  permit_mynetworks,
>  permit_sasl_authenticated,
>  reject_unauth_destination,
>  warn_if_reject,  reject_non_fqdn_hostname,

Is that comma a cut-n-paste typo? if you want to warn only on
reject_non_fqdn_hostname, then remove this comma, otherwise remove
'warn_if_reject' completely...

master.cf contents (ie, is it running chrooted?)?
(Continue reading)

Guillaume Hilt | 2 Jan 2009 17:54
Favicon
Gravatar

Re: deliver looking into root directory for sieve configuration ?

It's okay, you're trying to help me, so I won't complain :)

So, postfix isn't running in a chroot.
I've done the modifications you suggested.

My problem is that sieve is looking into the root folder for a sieve 
configuration file when the server receive a new email (mail for a 
virtual user).
I'll change the ssl key later, the server is not in production and i 
haven't finished the ssl part yet.

  Guillaume Hilt

Charles Marcus a écrit :
> On 1/2/2009 10:10 AM, Guillaume Hilt wrote:
>   
>> # OS: Linux 2.6.24.5-grsec-xxxx-grs-ipv4-64
>>     
>
> Hmmm... maybe it is a grsec problem? I can't help you there...
>
>   
>> ssl_key_password: Y0ullN3v3rF1ndTh1sPassphras3 
>>     
>
> If thats really your passphrase, you'd best change it asap...
>
>   
>> smtpd_client_restrictions = permit_mynetworks
>>     
(Continue reading)

Charles Marcus | 2 Jan 2009 18:13

Re: deliver looking into root directory for sieve configuration ?

On 1/2/2009 11:54 AM, Guillaume Hilt wrote:
> It's okay, you're trying to help me, so I won't complain :)
> 
> So, postfix isn't running in a chroot.

Are you sure? master .cf?

> My problem is that sieve is looking into the root folder for a sieve
> configuration file when the server receive a new email (mail for a
> virtual user).

I didn't see anything in your dovecot config about sieve...

Did you read and install/configure according to this page?

http://wiki.dovecot.org/LDA/Sieve

> I'll change the ssl key later, the server is not in production and i
> haven't finished the ssl part yet.

no worries then... ;)

--

-- 

Best regards,

Charles

Guillaume Hilt | 2 Jan 2009 18:18
Favicon
Gravatar

Re: deliver looking into root directory for sieve configuration ?

Charles Marcus a écrit :
> On 1/2/2009 11:54 AM, Guillaume Hilt wrote:
>   
>> It's okay, you're trying to help me, so I won't complain :)
>>
>> So, postfix isn't running in a chroot.
>>     
>
> Are you sure? master .cf?
>   
smtp      inet  n       -       n       -       -       smtpd
pickup    fifo  n       -       n       60      1       pickup
cleanup   unix  n       -       n       -       0       cleanup
qmgr      fifo  n       -       n       300     1       qmgr
tlsmgr    unix  -       -       n       1000?   1       tlsmgr
rewrite   unix  -       -       n       -       -       trivial-rewrite
bounce    unix  -       -       n       -       0       bounce
defer     unix  -       -       n       -       0       bounce
trace     unix  -       -       n       -       0       bounce
verify    unix  -       -       n       -       1       verify
flush     unix  n       -       n       1000?   0       flush
proxymap  unix  -       -       n       -       -       proxymap
proxywrite unix -       -       n       -       1       proxymap
smtp      unix  -       -       n       -       -       smtp
relay     unix  -       -       n       -       -       smtp
    -o smtp_fallback_relay=
showq     unix  n       -       n       -       -       showq
error     unix  -       -       n       -       -       error
retry     unix  -       -       n       -       -       error
discard   unix  -       -       n       -       -       discard
(Continue reading)

Charles Marcus | 2 Jan 2009 18:34

Re: deliver looking into root directory for sieve configuration ?

On 1/2/2009 12:18 PM, Guillaume Hilt wrote:
>> Did you read and install/configure according to this page?
>>
>> http://wiki.dovecot.org/LDA/Sieve

> sieve is declared and called in the lda section :)
> (i followed the tutorial yeah)

Well... I don't use dspam, but the sieve tutorial explicitly says you
need to be using the dovecot LDA, and you are using dspam in your
postfix config...

First thing I'd try is removing dspam from the mix, get postfix+dovecot
working right, then introduce dspam into the mix, and if you have
problems ask again (on the dspam list first, then maybe here)...

--

-- 

Best regards,

Charles


Gmane