Geraldine Mann さんは書きました:
Oct 14 08:50:17 fw postfix/smtp[6689]: connect to
127.0.0.1[127.0.0.1]:10586: Connection refused
content_filter = filter:[127.0.0.1]:10586
I guess that your filter (clamav?) is not running...
Wietse Venema さんは書きました:
I have a suggestion. When the script fails, don't lose control and
spill the guts all over the place.
Instead, catch the error and report an appropriate response.
Yes, that's the ideal thing to do. In fact I'm doing it.
What I'm actually doing wrong is being lazy and de
Sahil Tandon さんは書きました:
AFAIK, hiding the error output is not configurable. Concealing important
portions of the DSN seems silly and might even be a violation of RFC 3464
(something you might or might not care about).
I've checked the RFC, and about RFC3462 (about the report format) and I
thin
Hello,
I have a transport that pipes to a perl script. Everything is fine and
dandy, but whenever the script fails the whole perl error message
gets appended right after the failure_template message.
I've checked bounce(5), bounce(8), and pipe(8), and although I admit
that I haven't read thoroughl
Scott Haneda さんは書きました:
man postconf(5)
-bash: syntax error near unexpected token `('
man postconf5
No manual entry for postconf5
Does this imply there are version 1, 2, 3, and 4 as well? How do I
find out?
The number specifies the section, not version.
$ man 5 postconf
$ whereis postconf
pos
