[Postfixbuch-users] Problem mit dem Plugin avelsievevon squirrelmail
Info Beilfuss
info at beilfuss.de
Mi Jun 18 13:29:23 CEST 2008
Hallo,
jetzt stehe ich voll auf dem Schlauch, wie meinst Du das mit überprüfen?
Unter /Var/Spool/sieve/ habe ich kein Verzeichnis, sondern nur unter
/var/lib/sieve/ die scripte.
Welchen Befehl zum überprüfen der Berechtigung meinst Du???
Danke
Christian
-----Ursprüngliche Nachricht-----
Von: postfixbuch-users-bounces at listi.jpberlin.de
[mailto:postfixbuch-users-bounces at listi.jpberlin.de] Im Auftrag von Frank
Siebert
Gesendet: Mittwoch, 18. Juni 2008 11:55
An: Eine Diskussionsliste rund um das Postfix-Buch von Peer Heinlein.
Betreff: Re: [Postfixbuch-users] Problem mit dem Plugin avelsievevon
squirrelmail
Hallo,
hatte auch das Problem, habe dann die Berechtigungen
in /var/spool/sieve/ überprüft und auf cyrus:mail gesetzt.
Am Mittwoch, den 18.06.2008, 11:27 +0200 schrieb Info Beilfuss:
> Hallo,
>
> Ich habe Problem mit dem Plugin avelsieve von Squirrelmail.
> Sieve ist aktiv und läuft.
>
> Apache:~ # telnet localhost 2000
> Trying 127.0.0.1...
> Connected to localhost.
> Escape character is '^]'.
> "IMPLEMENTATION" "Cyrus timsieved v2.3.8"
> "SASL" "DIGEST-MD5 LOGIN CRAM-MD5 PLAIN"
> "SIEVE" "comparator-i;ascii-numeric fileinto reject vacation imapflags
> notify envelope relational regex subaddress copy"
> OK
>
> Über Smartsieve kann ich einloggen und das Sievescript verändern.
>
>
> Wenn ich über Squirrelmail die Filterfunktion aufrufe become ich folgende
> Fehlermeldung:
>
> Fehler aufgetreten
> Konnte den timsieved-Prozess auf Ihrem IMAP-Server nicht erreichen
> localhost.
> Bitte kontaktieren Sie Ihren Administrator.
>
> Meine imap.conf
>
> configdirectory: /var/lib/imap
> ##partition-default: /var/spool/imap
> partition-default: /Chris2/Mailuser
> sievedir: /var/lib/sieve
> admins: cyrus root postfix
> srvtab: /var/lib/imap/srvtab
> allowanonymouslogin: no
> autocreatequota: 50000
> reject8bit: no
> quotawarn: 90
> timeout: 480
> ##poptimeout: 10
> ##dracinterval: 0
> ##drachost: localhost
> sasl_pwcheck_method: auxprop ##sasldb ##auxprop ###
> sasl_mech_list: PLAIN LOGIN CRAM-MD5 DIGEST-MD5
> lmtpsocket: /var/lib/cyrus/socket/lmtp
> ##lmtp_overquota_perm_failure: no
> ##lmtp_downcase_rcpt: yes
> #
> # if you want TLS, you have to generate certificates and keys
> #
> #tls_cert_file: /usr/ssl/certs/cert.pem
> #tls_key_file: /usr/ssl/certs/skey.pem
> #tls_ca_file: /usr/ssl/CA/CAcert.pem
> #tls_ca_path: /usr/ssl/CA
>
> Meine cyrus conf.
> # standard standalone server implementation
>
> START {
> # do not delete this entry!
> recover cmd="ctl_cyrusdb -r"
>
> # this is only necessary if using idled for IMAP IDLE
> idled cmd="idled"
> }
>
> # UNIX sockets start with a slash and are put into /var/lib/imap/socket
> SERVICES {
> # add or remove based on preferences
> imap cmd="imapd" listen="imap" prefork=0
> # imaps cmd="imapd -s" listen="imaps" prefork=0
> pop3 cmd="pop3d" listen="pop3" prefork=0
> # pop3s cmd="pop3d -s" listen="pop3s" prefork=0
> # sieve cmd="timsieved" listen="sieve" prefork=0
> sieve cmd="timsieved" listen="localhost:sieve" prefork=0
> maxchild=100
>
> # at least one LMTP is required for delivery
> # lmtp cmd="lmtpd" listen="lmtp" prefork=0
> ##lmtpunix cmd="lmtpd" listen="/var/lib/imap/socket/lmtp" prefork=0
> lmtpunix cmd="lmtpd" listen="/var/spool/postfix/public/lmtp" \
> prefork=1
>
> # this is only necessary if using notifications
> # notify cmd="notifyd" listen="/var/lib/imap/socket/notify"
> proto="udp" prefork=1
> }
>
> EVENTS {
> # this is required
> checkpoint cmd="ctl_cyrusdb -c" period=30
>
> # this is only necessary if using duplicate delivery suppression
> delprune cmd="cyr_expire -E 3" at=0400
>
> # this is only necessary if caching TLS sessions
> tlsprune cmd="tls_prune" at=0400
>
> # Uncomment the next entry, if you want to automatically remove
> # old messages of EVERY user.
> # This example calls ipurge every 60 minutes and ipurge will delete
> # ALL messages older then 30 days.
> # enter 'man 8 ipurge' for more details
>
> # cleanup cmd="ipurge -d 30 -f" period=60
> }
>
> Auszug aus meiner config.php vom plugin avelsieve:
>
> /* Port where timsieved listens on the Cyrus IMAP server. Default is 2000.
> */
>
> $sieveport = 2000;
>
>
> /* **** NEW OPTION (as of 0.9.4) ****
> * Space separated list of preferred SASL mechanisms for the
authentication
> to
> * timsieved */
>
>
> $ieve_preferred_sasl_mech = "LOGIN";
> /*$sieve_preferred_sasl_mech = "LOGIN";
> /*$preferred_mech = "LOGIN";
> //$preferred_mech = "PLAIN DIGEST-MD5";
>
>
> /* **** NEW OPTION (as of 0.9.6) ***** Enable ImapProxy mode.
> * If you use imapproxy, because imapproxy cannot understand and proxy the
> * SIEVE protocol, you must connect to the SIEVE daemon (usually on the
IMAP
> * server) itself. So you need to set $imapproxymode to true, and define a
> * mapping, from the imapproxy host (usually localhost) to your real IMAP
> * server (usually the same that is defined on Imapproxy's configuration).
> *
> * This will not work if you use a perdition-style proxy, where different
> users
> * go to different IMAP servers; it applies mostly to people running
> imapproxy
> * for speed and want a quick hack.
> */
>
> $imapproxymode = false;
> $imapproxyserv = array(
> 'localhost' => '172.29.170.12'
> );
>
> /* *** Option Reenabled since 0.9.9 ***
> * Save changes to SIEVE server immediately or be conservative and save
only
> * when "Save Changes" is selected? */
>
> $conservative = true;
>
> /* Ldapuserdata mode: Gets user's email addresses (including mailAlternate
&
> * mailAuthorized) from LDAP Prefs Backend plugin's cache */
>
> $ldapuserdatamode = false;
>
> /* Map of cyrus administrator users, for proxy authentication */
>
> $cyrusadmins_map = array(
> 'cyrusimap' => 'cyrussieve'
> );
>
> Danke für die Hilfe.
> Christian
>
>
>
> Christian Beilfuß
> Mannspergerstr. 168
> 70619 Stuttgart
>
> Tel. 0711 6451560
> Fax 0711 6451561
> Mobil 0172 8906106
>
>
--
_______________________________________________
Postfixbuch-users -- http://www.postfixbuch.de
Heinlein Professional Linux Support GmbH
Postfixbuch-users at listi.jpberlin.de
https://listi.jpberlin.de/mailman/listinfo/postfixbuch-users
Mehr Informationen über die Mailingliste Postfixbuch-users