connect to transport spamassassin

M

ms-gdh

New Member
Hallo allerseits, zwei Problemchen hab ich
a) Spamassassin umschreibt den Header nicht, siehe Bild unten
b) siehe mail.warn
das ganze unter Debian mit Postfix & Spamassassin

mail.warn:
Code: 
Jan  4 01:29:24 vs3 postfix/qmgr[656]: warning: connect to transport spamassassin: No such file or directory
Jan  4 01:30:24 vs3 postfix/qmgr[656]: warning: connect to transport spamassassin: No such file or directory
Jan  4 01:31:24 vs3 postfix/qmgr[656]: warning: connect to transport spamassassin: No such file or directory
Jan  4 01:32:24 vs3 postfix/qmgr[656]: warning: connect to transport spamassassin: No such file or directory
Jan  4 01:33:24 vs3 postfix/qmgr[656]: warning: connect to transport spamassassin: No such file or directory
Jan  4 01:34:24 vs3 postfix/qmgr[656]: warning: connect to transport spamassassin: No such file or directory
Jan  4 01:35:24 vs3 postfix/qmgr[656]: warning: connect to transport spamassassin: No such file or directory
Jan  4 01:36:24 vs3 postfix/qmgr[656]: warning: connect to transport spamassassin: No such file or directory
Jan  4 01:37:24 vs3 postfix/qmgr[656]: warning: connect to transport spamassassin: No such file or directory
Jan  4 01:38:24 vs3 postfix/qmgr[656]: warning: connect to transport spamassassin: No such file or directory
Jan  4 01:39:24 vs3 postfix/qmgr[656]: warning: connect to transport spamassassin: No such file or directory
Jan  4 01:40:24 vs3 postfix/qmgr[656]: warning: connect to transport spamassassin: No such file or directory
Jan  4 01:41:24 vs3 postfix/qmgr[656]: warning: connect to transport spamassassin: No such file or directory
Jan  4 01:42:24 vs3 postfix/qmgr[656]: warning: connect to transport spamassassin: No such file or directory
Jan  4 01:43:24 vs3 postfix/qmgr[656]: warning: connect to transport spamassassin: No such file or directory
Jan  4 01:44:24 vs3 postfix/qmgr[656]: warning: connect to transport spamassassin: No such file or directory
Jan  4 01:44:45 vs3 postfix/smtpd[10740]: warning: 58.187.59.247: hostname adsl-dynamic-pool-xxx.fpt.vn verification failed: Name or service not known
Jan  4 01:45:24 vs3 postfix/qmgr[656]: warning: connect to transport spamassassin: No such file or directory
Jan  4 01:45:36 vs3 postfix/qmgr[11162]: warning: connect to transport spamassassin: No such file or directory
Jan  4 01:46:36 vs3 postfix/qmgr[11162]: warning: connect to transport spamassassin: No such file or directory
Jan  4 01:47:36 vs3 postfix/qmgr[11162]: warning: connect to transport spamassassin: No such file or directory
Jan  4 01:48:36 vs3 postfix/qmgr[11162]: warning: connect to transport spamassassin: No such file or directory
Jan  4 01:49:36 vs3 postfix/qmgr[11162]: warning: connect to transport spamassassin: No such file or directory
Jan  4 01:50:36 vs3 postfix/qmgr[11162]: warning: connect to transport spamassassin: No such file or directory
Jan  4 01:51:36 vs3 postfix/qmgr[11162]: warning: connect to transport spamassassin: No such file or directory
Jan  4 01:52:36 vs3 postfix/qmgr[11162]: warning: connect to transport spamassassin: No such file or directory
Jan  4 01:53:36 vs3 postfix/qmgr[11162]: warning: connect to transport spamassassin: No such file or directory
Jan  4 01:54:36 vs3 postfix/qmgr[11162]: warning: connect to transport spamassassin: No such file or directory
Jan  4 01:55:36 vs3 postfix/qmgr[11162]: warning: connect to transport spamassassin: No such file or directory
Jan  4 01:56:36 vs3 postfix/qmgr[11162]: warning: connect to transport spamassassin: No such file or directory
Jan  4 01:57:36 vs3 postfix/qmgr[11162]: warning: connect to transport spamassassin: No such file or directory
Jan  4 01:58:36 vs3 postfix/qmgr[11162]: warning: connect to transport spamassassin: No such file or directory
Jan  4 01:59:36 vs3 postfix/qmgr[11162]: warning: connect to transport spamassassin: No such file or directory

Zur Kontrolle hie meine

/postfix/main.cf
Code: 
# See /usr/share/postfix/main.cf.dist for a commented, more complete version


# Debian specific:  Specifying a file name will cause the first
# line of that file to be used as the name.  The Debian default
# is /etc/mailname.
#myorigin = /etc/mailname

smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
biff = no

# appending .domain is the MUA's job.
append_dot_mydomain = no

# Uncomment the next line to generate "delayed mail" warnings
#delay_warning_time = 4h

# TLS parameters
smtpd_tls_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem
smtpd_tls_key_file=/etc/ssl/private/ssl-cert-snakeoil.key
smtpd_use_tls=yes
smtpd_tls_session_cache_database = btree:${queue_directory}/smtpd_scache
smtp_tls_session_cache_database = btree:${queue_directory}/smtp_scache

# See /usr/share/doc/postfix/TLS_README.gz in the postfix-doc package for
# information on enabling SSL in the smtp client.

myhostname = vs3.******.de
alias_maps = hash:/etc/aliases
alias_database = hash:/etc/aliases
mydestination = vs3, localhost, localhost.localdomain, vs3.****.de
relayhost = 
mynetworks = 127.0.0.0/8
mailbox_size_limit = 0
recipient_delimiter = +
inet_interfaces = all
mailbox_command=/usr/bin/procmail
local_destination_concurrency_limit = 1

smtpd_sasl_auth_enable = yes
smtpd_sasl_security_options = noanonymous
smtpd_sasl_local_domain =
broken_sasl_auth_clients = yes
smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination


### CONFIXX POSTFIX ENTRY ###

virtual_maps = hash:/etc/postfix/confixx_virtualUsers, hash:/etc/postfix/confixx_localDomains

### /CONFIXX POSTFIX ENTRY ###

/postfix/master.cf
Code: 
#
# Postfix master process configuration file.  For details on the format
# of the file, see the master(5) manual page (command: "man 5 master").
#
# ==========================================================================
# service type  private unpriv  chroot  wakeup  maxproc command + args
#               (yes)   (yes)   (yes)   (never) (100)
# ==========================================================================
smtp      inet  n       -       -       -       -       smtpd
#submission inet n       -       -       -       -       smtpd
#  -o smtpd_enforce_tls=yes
#  -o smtpd_sasl_auth_enable=yes
#  -o smtpd_client_restrictions=permit_sasl_authenticated,reject
#smtps     inet  n       -       -       -       -       smtpd
#  -o smtpd_tls_wrappermode=yes
#  -o smtpd_sasl_auth_enable=yes
#  -o smtpd_client_restrictions=permit_sasl_authenticated,reject
#628      inet  n       -       -       -       -       qmqpd
pickup    fifo  n       -       -       60      1       pickup
cleanup   unix  n       -       -       -       0       cleanup
qmgr      fifo  n       -       n       300     1       qmgr
#qmgr     fifo  n       -       -       300     1       oqmgr
tlsmgr    unix  -       -       -       1000?   1       tlsmgr
rewrite   unix  -       -       -       -       -       trivial-rewrite
bounce    unix  -       -       -       -       0       bounce
defer     unix  -       -       -       -       0       bounce
trace     unix  -       -       -       -       0       bounce
verify    unix  -       -       -       -       1       verify
flush     unix  n       -       -       1000?   0       flush
proxymap  unix  -       -       n       -       -       proxymap
smtp      unix  -       -       -       -       -       smtp
# When relaying mail as backup MX, disable fallback_relay to avoid MX loops
relay     unix  -       -       -       -       -       smtp
	-o fallback_relay=
#       -o smtp_helo_timeout=5 -o smtp_connect_timeout=5
showq     unix  n       -       -       -       -       showq
error     unix  -       -       -       -       -       error
discard   unix  -       -       -       -       -       discard
local     unix  -       n       n       -       -       local
virtual   unix  -       n       n       -       -       virtual
lmtp      unix  -       -       -       -       -       lmtp
anvil     unix  -       -       -       -       1       anvil
scache	  unix	-	-	-	-	1	scache
#
# ====================================================================
# Interfaces to non-Postfix software. Be sure to examine the manual
# pages of the non-Postfix software to find out what options it wants.
#
# Many of the following services use the Postfix pipe(8) delivery
# agent.  See the pipe(8) man page for information about ${recipient}
# and other message envelope options.
# ====================================================================
#
# maildrop. See the Postfix MAILDROP_README file for details.
# Also specify in main.cf: maildrop_destination_recipient_limit=1
#
maildrop  unix  -       n       n       -       -       pipe
  flags=DRhu user=vmail argv=/usr/bin/maildrop -d ${recipient}
#
# See the Postfix UUCP_README file for configuration details.
#
uucp      unix  -       n       n       -       -       pipe
  flags=Fqhu user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient)
#
# Other external delivery methods.
#
ifmail    unix  -       n       n       -       -       pipe
  flags=F user=ftn argv=/usr/lib/ifmail/ifmail -r $nexthop ($recipient)
bsmtp     unix  -       n       n       -       -       pipe
  flags=Fq. user=bsmtp argv=/usr/lib/bsmtp/bsmtp -t$nexthop -f$sender $recipient
scalemail-backend unix	-	n	n	-	2	pipe
  flags=R user=scalemail argv=/usr/lib/scalemail/bin/scalemail-store ${nexthop} ${user} ${extension}
mailman   unix  -       n       n       -       -       pipe
  flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py
  ${nexthop} ${user}

procmailrc
Code: 
DROPPRIVS=yes

:0fw: spamassassin.lock
* < 256000
| /usr/bin/spamassassin

:0:
* ^X-Spam-Level: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
almost-certainly-spam

:0:
* ^X-Spam-Status: Yes
 .spam/

:0
* ^^rom[ ]
{
  LOG="*** Dropped F off From_ header! Fixing up. "
  
  :0 fhw
  | sed -e '1s/^/F/'
}

#bogofilter
:0fw
| bogofilter -u -e -p

:0 H:
* ^X-Bogosity: Spam, tests=bogofilter
$HOME/Maildir/.Junk/new

DEFAULT=$HOME/Maildir/

Für Hinweise zur Fehlerbeseitigung wäre ich euch sehr dankbar...
PS: der Mailverkehr funktioniert aber....
 

Attachments

  • sa-fehler.gif
    sa-fehler.gif
    18 KB · Views: 246
Last edited by a moderator:
ms-gdh said:
Spamassassin umschreibt den Header nicht, siehe Bild unten
Click to expand...
Das Bild sagt gar nichts aus. Ein vollständiger Mail-Header wäre sinnvoller.
Zum debuggen kann man procmail auch beibringen ein Logfile zu schreiben.

Jan 4 01:29:24 vs3 postfix/qmgr[656]: warning: connect to transport spamassassin: No such file or directory
Click to expand...
Wenn dieser "transport" nicht in der main oder master definiert ist, steht er evtl. in der /etc/postfix/transport.
Da Du SA ja per procmail aufrufst, brauchst Du diesen Teil wohl auch nicht...

huschi.
 
...hier schon mal eines der Header

Code: 
Received: from localhost by vs3
	with SpamAssassin (version 3.0.3);
	Fri, 04 Jan 2008 13:16:18 +0100
From: "Roland Metz" <piledxu054@cerfinc.com>
To: <info@*****.de>
Subject: Mittel gegen Impotenz
Date: Fri, 3 Jan 2008 15:22:10 +0300
Message-Id: <01c84e1c$688a3d00$3d31713e@piledxu054>
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on vs3
X-Spam-Level: *********
X-Spam-Status: Yes, score=9.3 required=5.0 tests=FROM_ENDS_IN_NUMS,HTML_40_50,
	HTML_MESSAGE,HTML_TAG_BALANCE_BODY,RCVD_IN_BL_SPAMCOP_NET,
	URIBL_OB_SURBL,URIBL_SC_SURBL,URIBL_WS_SURBL autolearn=no 
	version=3.0.3
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----------=_477E2392.F4459D8C"
X-Bogosity: Unsure, tests=bogofilter, spamicity=0.520000, version=1.1.3

procmail.log:
Code: 
procmail: Lock failure on "spamassassin.lock"
cannot open "/etc/spamassassin/local.cf": Permission denied
procmail: Lock failure on "almost-certainly-spam.lock"
procmail: Error while writing to "almost-certainly-spam"
procmail: Lock failure on "spamassassin.lock"
cannot open "/etc/spamassassin/local.cf": Permission denied
procmail: Lock failure on "almost-certainly-spam.lock"
procmail: Error while writing to "almost-certainly-spam"
procmail: Lock failure on ".spam/.lock"
procmail: Unable to treat as directory ".spam"
procmail: Error while writing to ".spam"
From [email]RuthiefollowDarby@engadget.com[/email]  Fri Jan  4 14:11:03 2008
 Subject: Your health
  Folder: /home/email/web3p1/Maildir/new/1199452315.1444_2.vs3		   5900
procmail: Lock failure on ".spam/.lock"
procmail: Unable to treat as directory ".spam"
procmail: Error while writing to ".spam"
From [email]RuthiefollowDarby@engadget.com[/email]  Fri Jan  4 14:11:19 2008
 Subject: Your health
  Folder: /home/email/web3p1/Maildir/new/1199452331.1553_2.vs3		   5909

so wie es aussieht, fehlen nur einige Rechte, wie kann ich die setzen?
 
Last edited by a moderator:
ms-gdh said:
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on vs3
X-Spam-Level: *********
X-Spam-Status: Yes, score=9.3 required=5.0
Click to expand...
Sieht doch gut aus. Also laufen die Mails durch SA.

cannot open "/etc/spamassassin/local.cf": Permission denied
Click to expand...
Procmail wird entweder als User "mail" oder als der auszuliefernde User gestartet.

procmail: Lock failure on ".spam/.lock"
procmail: Unable to treat as directory ".spam"
procmail: Error while writing to ".spam"
Click to expand...
Evtl. kann Dein procmail noch kein Maildir, oder Du hast es nicht richtig Eingestellt.
Hab die richtige Konfig gerade nicht im Kopf, aber der DEFAULT sollte meist oben gesetzt werden und nicht als letztes und Dir fehlt wohl die Zeile:
MAILDIR=$HOME/Maildir/

huschi.
 
Huschi said:
.....Hab die richtige Konfig gerade nicht im Kopf, aber der DEFAULT sollte meist oben gesetzt werden und nicht als letztes und Dir fehlt wohl die Zeile:
MAILDIR=$HOME/Maildir/

huschi.
Click to expand...

dann ändere ich das mal noch....Spams werden aber erfolgreich in den Spamorder verschoben. Also werd ich mal weiter beobachten

DANKE
 
You must log in or register to reply here.
Back
Top