| View previous topic :: View next topic |
| Author |
Message |
mariourk
l33t
Joined: 11 Jul 2003
Posts: 807
Location: Urk, Netherlands
|
 Posted: Tue Feb 10, 2004 9:10 am Post subject: amavis, works fine but still 1 error in my logs [solved] |
 |
|
I have Postfix running as MTA on my Gentoo-box. To check all incoming emails for virusses, I use amavisd-new in combination with f-prot.
This works fine but I still get one error in my logs:
| Code: |
Feb 10 10:07:21 [postfix/qmgr] warning: connect to transport amavis: No such file or directory
|
Does anyone know how I can fix this?
Thanks
Last edited by mariourk on Sat Mar 11, 2006 7:13 pm; edited 1 time in total |
|
| Back to top |
|
 |
Paulten
Apprentice
Joined: 28 Mar 2003
Posts: 257
Location: Sykkylven, Norway
|
| Posted: Tue Feb 10, 2004 10:31 am Post subject: |
|
|
Are you sure it works?
Please paste your master.cf.
And the "forward**" lines is amavisd.conf
_________________
Homepage : http://paul.kde.no Jabber ID : tenfjord@jabber.org
"Dei levde som dyr. Dei verken røykte eller drakk" -Ukjent |
|
| Back to top |
|
|
mariourk
l33t
Joined: 11 Jul 2003
Posts: 807
Location: Urk, Netherlands
|
| Posted: Tue Feb 10, 2004 12:40 pm Post subject: |
|
|
Yes Iam very suse everything runs fine. All mails are accepted and infected mails are intercepted.
Here is my master.cf
| Code: |
# SPECIFY ONLY PROGRAMS THAT ARE WRITTEN TO RUN AS POSTFIX DAEMONS.
# ALL DAEMONS SPECIFIED HERE MUST SPEAK A POSTFIX-INTERNAL PROTOCOL.
#
# DO NOT SHARE THE POSTFIX QUEUE BETWEEN MULTIPLE POSTFIX INSTANCES.
#
# ==========================================================================
# service type private unpriv chroot wakeup maxproc command + args
# (yes) (yes) (yes) (never) (100)
# ==========================================================================
smtp inet n - n - - smtpd
#smtps inet n - n - - smtpd
# -o smtpd_tls_wrappermode=yes -o smtpd_sasl_auth_enable=yes
#submission inet n - n - - smtpd
# -o smtpd_enforce_tls=yes -o smtpd_sasl_auth_enable=yes
#628 inet n - n - - qmqpd
pickup fifo n - n 60 1 pickup
cleanup unix n - n - 0 cleanup
qmgr fifo n - n 300 1 qmgr
#qmgr fifo n - n 300 1 nqmgr
#tlsmgr fifo - - n 300 1 tlsmgr
rewrite unix - - n - - trivial-rewrite
bounce unix - - n - 0 bounce
defer unix - - n - 0 bounce
flush unix n - n 1000? 0 flush
proxymap unix - - n - - proxymap
smtp unix - - n - - smtp
relay unix - - n - - smtp
# -o smtp_helo_timeout=5 -o smtp_connect_timeout=5
showq unix n - n - - showq
error unix - - n - - error
local unix - n n - - local
virtual unix - n n - - virtual
lmtp unix - - n - - lmtp
#
# Interfaces to non-Postfix software. Be sure to examine the manual
# pages of the non-Postfix software to find out what options it wants.
#
# maildrop. See the Postfix MAILDROP_README file for details.
#
maildrop unix - n n - - pipe
flags=DRhu user=vmail argv=/usr/local/bin/maildrop -d ${recipient}
#
# The Cyrus deliver program has changed incompatibly, multiple times.
#
old-cyrus unix - n n - - pipe
flags=R user=cyrus argv=/cyrus/bin/deliver -e -m ${extension} ${user}
# Cyrus 2.1.5 (Amos Gouaux)
cyrus unix - n n - - pipe
user=cyrus argv=/cyrus/bin/deliver -e -r ${sender} -m ${extension} ${user}
uucp unix - n n - - pipe
flags=Fqhu user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient)
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=foo argv=/usr/local/sbin/bsmtp -f $sender $nexthop $recipient
smtp-amavis unix - - n - 2 smtp
-o smtp_data_done_timeout=1200
127.0.0.1:10025 inet n - n - - smtpd
-o content_filter=
-o local_recipient_maps=
-o relay_recipient_maps=
-o smtpd_restriction_classes=
-o smtpd_client_restrictions=
-o smtpd_helo_restrictions=
-o smtpd_sender_restrictions=
-o smtpd_recipient_restrictions=permit_mynetworks,reject
-o mynetworks=127.0.0.0/8
-o strict_rfc821_envelopes=yes
-o smtpd_error_sleep_time=0
-o smtpd_soft_error_limit=1001
-o smtpd_hard_error_limit=1000
|
and here are the forward lines fron amavisd.conf
| Code: |
# MTA SETTINGS, UNCOMMENT AS APPROPRIATE,
# both $forward_method and $notify_method default to 'smtp:127.0.0.1:10025'
# POSTFIX, or SENDMAIL in dual-MTA setup, or EXIM V4
# (set host and port number as required; host can be specified
# as IP address or DNS name (A or CNAME, but MX is ignored)
#$forward_method = 'smtp:127.0.0.1:10025'; # where to forward checked mail
#$notify_method = $forward_method; # where to submit notifications
# NOTE: The defaults (above) are good for Postfix or dual-sendmail. You MUST
# uncomment the appropriate settings below if using other setups!
# SENDMAIL MILTER, using amavis-milter.c helper program:
#$forward_method = undef; # no explicit forwarding, sendmail does it by itself
# milter; option -odd is needed to avoid deadlocks
#$notify_method = 'pipe:flags=q argv=/usr/sbin/sendmail -Ac -i -odd -f ${sender} -- ${recipient}';
# just a thought: can we use use -Am instead of -odd ?
# SENDMAIL (old non-milter setup, as relay):
#$forward_method = 'pipe:flags=q argv=/usr/sbin/sendmail -C/etc/sendmail.orig.cf -i -f ${sender} -- ${recipient}';
#$notify_method = $forward_method;
# SENDMAIL (old non-milter setup, amavis.c calls local delivery agent):
#$forward_method = undef; # no explicit forwarding, amavis.c will call LDA
#$notify_method = 'pipe:flags=q argv=/usr/sbin/sendmail -Ac -i -f ${sender} -- ${recipient}';
# EXIM v3 (not recommended with v4 or later, which can use SMTP setup instead):
#$forward_method = 'pipe:flags=q argv=/usr/sbin/exim -oMr scanned-ok -i -f ${sender} -- ${recipient}';
#$notify_method = $forward_method;
# prefer to collect mail for forwarding as BSMTP files?
#$forward_method = "bsmtp:$MYHOME/out-%i-%n.bsmtp";
#$notify_method = $forward_method;
|
All commented out, I use the default values.
Om my own server it runs fine. |
|
| Back to top |
|
|
Paulten
Apprentice
Joined: 28 Mar 2003
Posts: 257
Location: Sykkylven, Norway
|
| Posted: Wed Feb 11, 2004 1:12 pm Post subject: |
|
|
Ok.
Your not sending all smtp connctions to smtp-amavis.
Since you have only :
smtp inet n - n - - smtpd
but
smtp inet n - n - - smtpd
-o content_filter=smtp-amavis:[127.0.0.1]:10024
Content filter sends the mails to external programs.
And in amavis.conf
$forward_method = 'smtp:127.0.0.1:10025'; # where to forward checked mail
$notify_method = $forward_method; # where to submit notification
But, I need to do some more reading because as far as I understand postfix + amavid-new this should not work.
Sorry can't help you.
Good luck
_________________
Homepage : http://paul.kde.no Jabber ID : tenfjord@jabber.org
"Dei levde som dyr. Dei verken røykte eller drakk" -Ukjent |
|
| Back to top |
|
|
mariourk
l33t
Joined: 11 Jul 2003
Posts: 807
Location: Urk, Netherlands
|
| Posted: Fri Mar 12, 2004 10:06 am Post subject: |
|
|
I still have this error in my logs. However, I don't think that mails are lost or dropped. I was thinking, is it possible that my mailserver sometimes wants to put an email to amavisd while amavisd is busy with another one? This way the mail is not accepted and produces the error in my logs.
Ofcource the mail is stored in the mailqueue for a while and delivered anyway.
Just a theory, somebody else has an idae about this? |
|
| Back to top |
|
|
mariourk
l33t
Joined: 11 Jul 2003
Posts: 807
Location: Urk, Netherlands
|
| Posted: Mon Apr 19, 2004 9:44 am Post subject: |
|
|
The problem is solved. I increased the number of "child-daemons" from 2 to 5
I think that in some situations amavis got more emails than it could handle and rejected some mails, this way the errors where produced.
The rejected mails got to the queue and where delivered anyway, so in fact no problem at all. But if you want to keep your logs clean, you know what to do 
However, don't make the number of child-deamons too high. If you do so, amavis will become unstable and crash. This will result in a very full mail-queue  |
|
| Back to top |
|
|
concord
Apprentice
Joined: 02 Oct 2005
Posts: 193
|
| Posted: Fri Jan 20, 2006 6:07 am Post subject: |
|
|
| mariourk wrote: | The problem is solved. I increased the number of "child-daemons" from 2 to 5
I think that in some situations amavis got more emails than it could handle and rejected some mails, this way the errors where produced.
The rejected mails got to the queue and where delivered anyway, so in fact no problem at all. But if you want to keep your logs clean, you know what to do
However, don't make the number of child-deamons too high. If you do so, amavis will become unstable and crash. This will result in a very full mail-queue |
Dear mariourk:
what is child-daemonds? In which file?
Thanks
_________________
AMD64 Desktop
Pentium4 Laptop
Pentium3 Server |
|
| Back to top |
|
|
mariourk
l33t
Joined: 11 Jul 2003
Posts: 807
Location: Urk, Netherlands
|
| Posted: Fri Jan 20, 2006 9:01 am Post subject: |
|
|
You'll find the setting in /etc/amavisd.conf
The default is 2. Be carefull with increasing the number.
It can get Amavisd-new to its knees
_________________
If there is one thing to learn from history, it's that we usualy don't learn anything from it, at all. |
|
| Back to top |
|
|
|
Networking & Security
