This is a possibly naive question.
Currently I deliver local mail to myself on my linux (xubuntu 21.10)
system using a ~/.forward file as follows:-
| /home/chris/.mutt/bin/filter.py
I'm looking for a simple way to test new versions of filter.py and I'm
not coming up with easy answers.
If I add a second line to .forward, e.g. make it something like:-
| /home/chris/.mutt/bin/filter.py
| /home/chris/dev/bin/filter.py
Then, if (as is likely) there are errors in /home/chris/dev/bin/filter.py
the message sender will see an error returned even though the message
has been delivered successfully by the first line.
Is there a (simple) way to set up an extra message delivery whose
status won't get fed back to the sender?
I realise I could set up a complete other user and have a separate
environment but that seems overkill for a simple, single user
situation like this. I just want an easy way (that I can turn on and
off) to feed my incoming messages into a 'second place' that won't
return errors to the sender if it goes wrong.
It's not super critical that I never send errors back, this is only
handling my own personal mail. Up until now I have simply edited
filter.py very carefully and lived with the odd undelivered message,
in general SMTP copes very well and resends. It would just be nice to
come up with a slightly more robust approach which would allow me to
to more major changes to filter.py with less risk.
--
Chris Green
