From: Mail Delivery System <Mailer-Daemon@lists.sourceforge.net>
To: alsa-devel@lists.sourceforge.net
Subject: Warning: message 1H9E2m-0001Qz-AR delayed 48 hours
Date: Wed, 24 Jan 2007 21:53:25 -0800 [thread overview]
Message-ID: <E1H9xY5-0004q2-2T@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 48 hours on the queue on externalmx-1.sourceforge.net.
The message identifier is: 1H9E2m-0001Qz-AR
The subject of the message is: To whom ceased from the skin is therefore was before
The date of the message is: Tue, 23 Jan 2007 10:47:52 +0530
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.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
reply other threads:[~2007-01-25 5:53 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=E1H9xY5-0004q2-2T@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).