-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2006-04-03 at 12:23 +0100, David Bolt wrote:
So the bounce message was generated by a different MTA than the SuSE mailinglist server was talking to, which means that this is a case of accept-then-bounce-later, which is bad for the reasons you already mentioned. Unfortunately, this is done by the OP's ISP, so short of complaining about this, there is probably little he can do about it.
Well, the only way to reject an email because it is considered spam is after complete reception; the scanning is surely done later. It is simply a «bad thing» to bounce back spam. I'd complain to the ISP, or change ISP.
Unfortunately that's true. The bad news for the OP is that, because their ISP is operating in that fashion, there are some people, myself included[0], who would add the IP addresses of the servers that bounce mail to local block lists.
[0] after being on the receiving end of several thousand bounces due to accept-then-bounce policies in place at some ISPs, I've been using this as method of self-defence.
Mmmm... I don't like blocking lists. I wonder if it would be possible to block the bounces, and not the rest, ie, the users' mail. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFEMRSFtTMYHG2NR9URAnJhAJ9PfM2rE9YCnL1hbObiHr4mZz6v0gCglT49 B37AQ2Ff9ltQUGaR1GLGDUA= =X040 -----END PGP SIGNATURE-----