==================================================================
Please DO NOT REPLY to this mail or send email to the developers
about this bug. Please follow-up to Bugzilla using this link:
http://bugs.contribs.org/show_bug.cgi?id=9074
Have you checked the Frequently Asked Questions (FAQ)?
http://wiki.contribs.org/SME_Server:Documentation:FAQ
Please also take the time to read the following useful guide:
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
==================================================================
Bug ID: 9074
Summary: Stop bounces on permanent delivery failure
Classification: Contribs
Product: SME Contribs
Version: 9.0
Hardware: ---
OS: ---
Status: CONFIRMED
Severity: normal
Priority: P3
Component: smeserver-fetchmail
Assignee: [email protected]
Reporter: [email protected]
QA Contact: [email protected]
I hadn't this issue on SME8, only saw it on SME9, so it might affect only
fetchmail version on SME9.
The problem is that the default behaviour of fetchmail is to use "softbounce":
if the SMTP reply with a permanent delivery failure, a bounce is sent to the
original sender, but the mail is *not* deleted from the upstream server. So, on
next fetch, the same error will start over and over. We should disable this by
setting 'set no softbounce'
Another, related problem is that, if RHSBL is enabled and a mail fetched by
fetchmail is refused because of that, qpsmtpd replies with a 550 code (which is
the right thing to do), but by default, fetchmail doesn't consider this as a
spam blocking, and generate a bounce to the sender. Once again, this should be
avoided by adding the antispam 550 configuration
--
You are receiving this mail because:
You are the QA Contact for the bug._______________________________________________
Mail for each SME Contribs bug report
To unsubscribe, e-mail [email protected]
Searchable archive at http://lists.contribs.org/mailman/public/contribteam/
