Turn off Spam reject by postfix?

[phdoerfler]

I'd like postfix to not reject spam messages for if they are classified as spam wrongly I will be unable to see them. I believe it'd be better if they are accepted by postfix only to then be classified as spam by rspamd and put into the Junk folder for later review.

I ran into this behaviour while running fetchmail which every once in a while said this:

fetchmail: SMTP error: 554 5.7.1 Spam message rejected; If this is not spam contact abuse
fetchmail: mail from [email protected] bounced to [email protected]
fetchmail: SMTP listener refused delivery

Thoughts?

[r-raymond]

Sorry, I don't understand. Can you describe how to reproduce the issue? Are you using fetchmail to send email? Are you using port 25 or 587? Are you authenticated?

[phdoerfler]

I use fetchmail to fetch mail from some existing mail accounts that I got. It then hands the mail over to the local postfix which then eventually gives it to the milters and to dovecot via LMTP which then puts it through the sieve scripts and then it ends up in the correct mailboxes.

I have not told fetchmail anything about ports or authentication.

While running fetchmail manually its output looks like this:

reading message [email protected]:15476 of 18822 (66412 octets) not flushed
reading message [email protected]:15477 of 18822 (4123 octets) not flushed
fetchmail: SMTP error: 554 5.7.1 Spam message rejected; If this is not spam contact abuse
fetchmail: mail from [email protected] bounced to [email protected]
fetchmail: SMTP listener refused delivery
reading message [email protected]:15478 of 18822 (66412 octets) not flushed
reading message [email protected]:15479 of 18822 (4123 octets) not flushed

I am just worried I am losing some mails in the process.

[r-raymond]

Ah I see. It seems that the the error you are getting is not related to spam, but rather that there is a RCPT TO, MAIL FROM mismatch. I'll have to think about why this is happening. On the other hand, isn't that simply a job for procmail?

[phdoerfler]

Thanks for the clarification. I am assuming that "SMTP error: 554" means it is postfix who is rejecting accepting the mail. I also believe it should indeed be a job for procmail / sieve to decide what is to happen with such mails.

[The-M1k3y]

I have the same issue but in another setup. I'm subscribed to a lot of mailing-lists where some of them have a low volume of SPAM. The problem here is that I automatically get unsubscribed from the lists when my server bounces the mails.

Logs:
mail.list-example.com (5.6.7.8) = sending server
mail.example.com (1.2.3.4) = my server

relevant Log line of my server:

Apr 03 18:12:07 $hostname postfix/cleanup[23627]: 5802B7E29A: milter-reject: END-OF-MESSAGE from mail.list-example.com[5.6.7.8]: 5.7.1 Spam message rejected; If this is not spam contact abuse; from=[email protected] to=[email protected] proto=ESMTP helo=<mail.list-example.com>

Log line of the sending server:

Apr 3 18:12:08 mail1 postfix/smtp[12038]: 19B147FC58: to=[email protected], relay=mail.example.com[1.2.3.4]:25, delay=0.91, delays=0.05/0.02/0.18/0.67, dsn=5.7.1, status=bounced (host mail.example.com[1.2.3.4] said: 554 5.7.1 Spam message rejected; If this is not spam contact abuse (in reply to end of DATA command))

It would be helpful when I could just make postfix to not bounce anything and let the local spamfilter handle it.