<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div>hallo,</div><div><br class="webkit-block-placeholder"></div><div><blockquote type="cite"><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Ich nutze Clamsmtp mit Clamav - läuft ohne Probleme.</div></blockquote></div><div><br class="webkit-block-placeholder"></div>danke für den tipp, aber der mailserver sollte möglichst ohne zusätzliche unterbrechungen laufen, da werde ich nicht irgendwelche experimente mit einer methode machen, die ich noch nicht kenne - amavisd-new wird ja dabei umgangen, wenn ich das richtig sehe?<div><br class="webkit-block-placeholder"></div><div>mittlerweile habe ich ClamAV deinstalliert und neu installiert, es bleibt bei derselben fehlermeldung. </div><div><div><br></div><div>meine notizen sagen mir, dass der clam schon öfters nicht lief, zuletzt im august 2007. damals hatte ich mir für mich selber notiert:</div><div><br></div><div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Verdana" size="4" color="#000603" style="font: 13.0px Verdana; color: #000603">"Lösung: erst clamscan und freshclam und amavis stoppen, dann amavis und beide clams starten (in dieser reihenfolge!):</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 13px/normal Verdana; color: rgb(0, 6, 3); min-height: 16px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Verdana" size="4" color="#000603" style="font: 13.0px Verdana; color: #000603"><i> 674 /etc/init.d/amavis start</i></font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Verdana" size="4" color="#000603" style="font: 13.0px Verdana; color: #000603"><i> 675 /etc/init.d/clamav-daemon start</i></font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Verdana" size="4" color="#000603" style="font: 13.0px Verdana; color: #000603"><i> 676 /etc/init.d/clamav-freshclam start"</i></font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font class="Apple-style-span" color="#000603" size="3"><span class="Apple-style-span" style="font-size: 13px;"><i><br class="webkit-block-placeholder"></i></span></font></div></div><div>das hilft jetzt ebenfals nicht mehr. ich kann den clam per apt-get reomve --purge clamav deinstallieren, dann per</div><div><br class="webkit-block-placeholder"></div><div>apt-get clamav clamav-daemon clamav-freshclam</div><div><br class="webkit-block-placeholder"></div><div>erneut installieren (die konfigfiles und das verzeichnis /var/run/clamav/ bleiben übrigens erhalten ... ?!), dann postfix reloaden, dann geht es wieder.</div><div><br class="webkit-block-placeholder"></div><div>sobald ich aber irgend etwas an den diensten neu starte, kommt wieder dieselbe fehlermeldung und ich habe jetzt immer clamscan-prozesse, die ich nur mit killall clamscan beenden kann; anschliessend funktioniert der gesamte Mailtransport aber nicht mehr wegen der "cant connect to"-fehlermeldung.</div><div><br class="webkit-block-placeholder"></div><div>Klasse, und das mal wieder aus heiterem himmel :-( </div><div><br class="webkit-block-placeholder"></div><div>falls jemand etwas wüsste? einen alternativen scanner (zuverlässiger als die clamav-prozedur!)?</div><div><br class="webkit-block-placeholder"></div><div><br class="webkit-block-placeholder"></div><div>mein system:</div><div><br class="webkit-block-placeholder"></div><div><div>mail:/etc/postfix# dpkg -s postfix amavisd-new clamav | grep Version</div><div><br class="webkit-block-placeholder"></div><div>Version: 2.3.8-2+b1</div><div>Version: 1:2.4.2-6.1</div><div>Version: 0.90.1-3etch7</div></div><div><br class="webkit-block-placeholder"></div><div>meine postconf -n:</div><div><br class="webkit-block-placeholder"></div><div><div>alias_maps = hash:/etc/aliases</div><div>append_dot_mydomain = no</div><div>biff = no</div><div>body_checks = regexp:/etc/postfix/body_checks</div><div>bounce_template_file = /etc/postfix/bounce-templates/bounce.de-DE.cf</div><div>broken_sasl_auth_clients = yes</div><div>config_directory = /etc/postfix</div><div>header_checks = regexp:/etc/postfix/header_checks</div><div>home_mailbox = Maildir/</div><div>inet_interfaces = all</div><div>local_recipient_maps = proxy:unix:passwd.byname $alias_maps</div><div>local_transport = local</div><div>luser_relay = </div><div>mailbox_size_limit = 750000000</div><div>message_size_limit = 25240000</div><div>mydestination = $mydomain,(...)</div><div>mydomain = server.lokal</div><div>myhostname = mail.server.lokal</div><div>mynetworks = 127.0.0.0/8, 172.16.0.0/16, 1.2.3.0/23</div><div>myorigin = $mydomain</div><div>proxy_interfaces = 1.2.3.7</div><div>recipient_delimiter = +</div><div>sender_canonical_maps = hash:/etc/postfix/sender_canonical</div><div>smtp_tls_note_starttls_offer = yes</div><div>smtp_use_tls = yes</div><div>smtpd_banner = $myhostname ESMTP Microsoft ESMTP MAIL Service, Version: 5.0.2195.6713 ready</div><div>smtpd_recipient_restrictions = permit_sasl_authenticated, check_client_access hash:/etc/postfix/check_client_access check_sender_access hash:/etc/postfix/sender_access check_recipient_access hash:/etc/postfix/recipient_access reject_non_fqdn_sender, permit_mynetworks, reject_unauth_destination, check_policy_service inet:127.0.0.1:12525 check_policy_service inet:127.0.0.1:60000 permit</div><div>smtpd_sasl_auth_enable = yes</div><div>smtpd_sasl_local_domain = $myhostname</div><div>smtpd_sasl_security_options = noanonymous</div><div>smtpd_sender_restrictions = hash:/etc/postfix/ip_block, permit</div><div>smtpd_tls_CAfile = /etc/postfix/ssl/cacert.pem</div><div>smtpd_tls_auth_only = no</div><div>smtpd_tls_cert_file = /etc/postfix/ssl/smtpd.crt</div><div>smtpd_tls_key_file = /etc/postfix/ssl/smtpd.key</div><div>smtpd_tls_loglevel = 1</div><div>smtpd_tls_received_header = yes</div><div>smtpd_tls_session_cache_timeout = 3600s</div><div>smtpd_use_tls = yes</div><div>tls_random_source = dev:/dev/urandom</div><div>transport_maps = hash:/etc/postfix/transport</div><div><br class="webkit-block-placeholder"></div><div>user clamav ist bei amavis eingetragen und vice versa, /var/run/clamav/ gehört clamav:clamav, es lief und läuft ja auch mit dieser konfig. das problem sind offensichtlich die nicht zu beendenden clamscan-prozesse :(</div><div><br class="webkit-block-placeholder"></div><div><br class="webkit-block-placeholder"></div><div>gruss</div><div><br class="webkit-block-placeholder"></div><div><br class="webkit-block-placeholder"></div><div><br class="webkit-block-placeholder"></div><div>lars</div><div><br class="webkit-block-placeholder"></div><div><br class="webkit-block-placeholder"></div><div><br class="webkit-block-placeholder"></div></div></div></body></html>