From: Mail Delivery System <Mailer-Daemon@lists.sourceforge.net>
To: alsa-devel@lists.sourceforge.net
Subject: Warning: message 1HG0WP-0006de-BJ delayed 24 hours
Date: Sun, 11 Feb 2007 19:49:41 -0800 [thread overview]
Message-ID: <E1HGSCD-0008W8-J4@externalmx-1.sourceforge.net> (raw)
This message was created automatically by mail delivery software.
A message that you sent has not yet been delivered to one or more of its
recipients after more than 24 hours on the queue on externalmx-1.sourceforge.net.
The message identifier is: 1HG0WP-0006de-BJ
The subject of the message is: of stone, but Let them and power but that
The date of the message is: Sun, 11 Feb 2007 00:16:45 +0200
The address to which the message has not yet been delivered is:
alsa-devel@lists.sourceforge.net
Delay reason: SMTP error from remote mailer after RCPT TO:<alsa-devel@lists.sourceforge.net>:
host mail.sourceforge.net [66.35.250.206]: 451-Could not complete sender verify callout
451-Could not complete sender verify callout for
451-<alsa-devel@lists.sourceforge.net>.
451-The mail server(s) for the domain may be temporarily unreachable, or
451-they may be permanently unreachable from this server. In the latter case,
451-you need to change the address or create an MX record for its domain
451-if it is supposed to
No action is required on your part. Delivery attempts will continue for
some time, and this warning may be repeated at intervals if the message
remains undelivered. Eventually the mail delivery software will give up,
and when that happens, the message will be returned to you.
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
reply other threads:[~2007-02-12 3:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1HGSCD-0008W8-J4@externalmx-1.sourceforge.net \
--to=mailer-daemon@lists.sourceforge.net \
--cc=alsa-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.