>>From [EMAIL PROTECTED] Mon Feb 28 07:23:40 2005
>Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
>Precedence: bulk
>list-help: <mailto:[EMAIL PROTECTED]>
>list-unsubscribe: <mailto:[EMAIL PROTECTED]>
>List-Post: <mailto:[email protected]>
>List-Id: <users.spamassassin.apache.org>
>Delivered-To: mailing list [email protected]
>...
>
>On Sun, Feb 27, 2005 at 09:52:05PM -0800, Loren Wilton wrote:
>> Sure sounds like a problem with the ClamAV setup rather than SA to me.
>> Nothing in what you show indicates that SA even ever saw the messages.
>
>Also, FYI, amazon is in the SA default whitelist.
>
>...
The problem I alway see with Amazon, is they bring new servers online
before they update their DNS records - so I/Postfix issues quite a few 450
errors about the HELO host not resolving, but they always keep trying and fix
it within a day. Also, they sometimes "leak" internal only names to the HELO
causing the same problem - but their administrators seem fairly competent and
always fix the problem (usually within a few hours), then I see the same
message (recognizable by the msgid) come through properly.
We buy a *lot* from Amazon, no messages ever seem lost, though I do
seem to issue a large number of 450's for a legitimate outfit (I just guess
that business is so good, that they are growing fast and make mistakes - as
long as they fix them I really don't care, it is just clutter in the log files
though). I've never seen any problem once the message makes it to SA at all.
Paul Shupak
[EMAIL PROTECTED]
