On Sat, 15 Mar 2025, graeme vetterlein via Exim-users wrote:
My cronjobs downloaded the mail (fetchmail) then passed it (to me) locally
via exim4 (SMTP) ... it fails, and we retry later.
With fetchmail feeding messages in, I don't see the point in a local exim
rejecting anything. By the time you can reject it for any body-related
issue, exim has the whole message. You might as well deliver it to the spam
folder or to /dev/null*.
* I'm not sure that delivering literally to /dev/null actually works.
So, I'm guessing here, right now the message FAILS to be delivered (by virtue
of going to rejectlog) causing retries. What I should make it do is, SUCCEED
in delivering to SPAM-BOX/BADMAIL-BOX
any hints on how/where to do that? (a rule-name and an example rule would be
a good start)
Without knowing how your config does it now, I cannot say what you need to
change.
I use spamassassin to score messages in the exim config,
then filter high scoring messages into the spam folder with a rule like:
if $h_X-Spam-Level: contains "*****"
then
seen save $home/Mail/spam
finish
endif
in my ~/.forward file.
I have a "userforward" router in my exim config to ensure that
my ~/.forward is processed.
--
Andrew C. Aitchison Kendal, UK
and...@aitchison.me.uk
--
## subscription configuration (requires account):
## https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/
## unsubscribe (doesn't require an account):
## exim-users-unsubscr...@lists.exim.org
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
