Hello!
Thanks for the reply.
I've now looked at the log files and I think this problem has been
from beginning of this server because I started it a few days ago.
Everything work fine when I send to addresses that exists. The problem
is that when I send to addresses that don't exists the bounce doesn't
work properly. The user gets "Undeliverable" message for the
non-existing mail but it continues to come because it has been
delivered to the deferred queue probable because of the "bounce and
trace service failure" that is logged. I then put on debugging on the
bounce process to see if I could got more info but when I did it it
started to work so I couldn't get info on what was wrong. When I
stopped debugging the error reappeared.
I'm no wondering if it can have something to do with locking of files?
When I put on debugging maybe the processes get slower and some how
can read the files that have been locked when the processes is not on
debugging mode.
Another thing to note is when I'm using relayhost=[mail.irf.se]:60180
everything works with bouncing of non-existing messages. But I don't
want to use that because I don't want all domains to go to that host.
Therefore I use the transport map to deliver one domain to the
mail.irf.se:60180 and the other domains to the Internet. However with
that configuration it doesn't work properly with bouncing of messages
unless I put on debugging as I wrote before.
Maybe someone out there experienced the same problem?
/Regards Mats
Quoting Wietse Venema <wie...@porcupine.org>:
Mats Luspa:
Hello again!
This is very strange. When I automatically trace the bounce process
according to the documentation here:
http://www.postfix.org/DEBUG_README.html#logging it works with the
bouncing.
The log file says:
I wrote most of Postfix, and I will speak in simple sentences.
Turn OFF verbose logging. Turn OFF tracing.
Then, do "postfix reload".
Then, follow instructions at http://www.postfix.org/DEBUG_README.html#logging
which provides a filter to look for signs of trouble.
In particular, pay attention to this sentence:
Note: the most important message is near the BEGINNING of the
output. Error messages that come later are less useful.
With :the beginning output", I mean: the point in time that corresponds
with the start of your troubles.
Now, it is possible that your logfile has been rotated due to massive
amounts of verbose logging. In that case you have to hunt down the
older logfile and apply the above trouble filter on that file.
Wietse
