Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index

On 11/24/2012 01:19 AM, Thomas Blasejewicz wrote:
Good afternoon
I am trying to post a message, or rather repons to another one, but my
messages are rejected.
Although I DID sent a message from this computer / mail address a few
days ago.
(I did not change anything here on my computer ...)

What is it, that I am making wrong this time?

Below the first part of a rather lengthy error message.


Your mail could not be delivered due to the following error.

<>: host[]
     said: 550 5.7.1 <>: Recipient address rejected:
     Mail appears to be spam or forged and is rejected due to policy. Using
     cached results - retrying too fast. penalty: 30 seconds x 0 retries. (in
     reply to RCPT TO command)

Thank you.


Your message this time made it through to the list.

It appears it did not like something in the header such as possibly your time stamp or a time stamp or address of one of the relays. I have no idea how one could reply to fast when manually sending an email. The fact you did send one successfully would indicate that the problem has been corrected or there was a specific problem with the email you were responding to.

5.7.1 is the error code for spam.

Jay Lozier

For unsubscribe instructions e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.