Hi Lars/etc,

* Lars Hecking <lheckingnmrc.ie> [010410 02:32], about

: Hard to guess what's going on. You don't even provide a minimum of
: information about your configuration, versions of software etc.

        Sorry, guess I was too frustrated, and thought it would be
implied/nonimportant. I'm running postfix20010228-pl01 (patched with
PER_USER), on OpenBSD, amavisd-snapshot-0407 (since I'm replying to this
thread I also presumed that implied. ;)

: Disk space? Some cron job that changes permissions? Have you tried
: to enable logging?

        It is supposed to log to syslog by default, right? ($DO_SYSLOG =
"yes"), I guess I'll try disabling that and trying its own. Maybe I haven't
setup syslog properly? What do I add to syslog.conf?

/dev/wd0e 3872744 11826 3667281 0% /var

-rw-r--r-- 1 vscan nobody 0 Mar 16 19:12 /var/log/amavis

# ls -lat /var/amavis/
total 2
drwxr-xr-x 2 vscan nobody 512 Apr 10 06:39 ./
srwx------ 1 vscan nobody 0 Apr 9 19:38 amavisd.sock=
drwxr-xr-x 26 root wheel 512 Apr 8 10:23 ../

And here's its top entry:
# ls -lat /var/amavis/
total 2
drwxr-xr-x 2 vscan nobody 512 Apr 10 06:39 ./
srwx------ 1 vscan nobody 0 Apr 9 19:38 amavisd.sock=
drwxr-xr-x 26 root wheel 512 Apr 8 10:23 ../

Hopefully that should answer some/all questions. No scripts changing
permissions or anything, and even if there was anything funny like that, me
killing amavisd and restarting it would've corrected them, even after
starting fresh it wouldn't deliver the messages. As I mentioned, debugging
is one of the things I'm hoping somebody will help me with, it's not my
strong suit. ;^)

: Your problem is that vscan doesn't work. If these messages are deferred
: by vscan, postfix will try to deliver them to vscan again.

There's NO way to have it try an alternate delivery method?? ;(
Maybe I should enable soft-bounce so the users w/ msgs in the queue will
know their mail's gone unreceived. (But then they'll start to think the new
mail setup is flakey, possibly. (but just 9 msgs, so maybe... who knows.))

        Hmm.. so the other possibility would be using another thing in place
of the 'vscan' entry in master.cf? Maybe the .sh amavisd or something?
(temporary solution.. long-term if I don't figure out what's wrong.)

: Nothing you can do about that.

I can accept the fact that there's no way to keep mails from continually
getting scanned currently, but what about in the future of postfix, Wietse?
Anyone?

Or even amavis, maybe it would not scan msgs with its header on it? (Isn't
that a good reason to be adding the header in the first place? ;)

>-- End of excerpt from Lars Hecking

TIA!

        -Ajay

(Okay, using amavis 0.2.1 right (because it's a shell script (so I assume
lower load), and because that's the last version I've used (or played with)
since I was scared of CPAN originally. ;))

-- 
Milpitas, ca	atallamtelocity.com	HempVille, Planet Talarian
			http://os2man.cjb.net/
<barkode> don't trust anything that bleeds for 5 days and doesn't die.
-
To unsubscribe, send mail to majordomopostfix.org with content
(not subject): unsubscribe postfix-users

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]