"iL_weReo" wrote in message
news:7ddee00f-bb7b-4511-8073-...
>
> "VanguardLH" wrote:
>>
>> "iL_weReo" wrote ...
>>>
>>> If I get a fatal email return FROM AOL and it says "mailbox full"
>>> can that mean the party refuses to accept my email as well?
>>> Or does it just mean their mailbox is full?
>>
>> Not sure since you summarized the NDR (non-delivery report) e-mail
>> that you got back rather than provided an exact copy of it.
>> Probably
>> means the recipient's mailbox quota has been consumed and their
>> receiving mail server will not accept any more inbound e-mails that
>> target that mailbox.
>
> Thank you to everyone for your concern. Here is the header of the
> bounced email in question:
>
> *** ATTENTION ***
>
> Your e-mail is being returned to you because there was a problem
> with
> its delivery. The address which was undeliverable is listed in the
> section labeled: "----- The following addresses had permanent fatal
> errors -----".
>
> The reason your mail is being returned to you is listed in the
> section
> labeled: "----- Transcript of Session Follows -----".
>
> The line beginning with "<<<" describes the specific reason your e-
> mail could not be delivered. The next line contains a second error
> message which is a general translation for other e-mail servers.
>
> Please direct further questions regarding this message to your
> e-mail
> administrator.
>
> --AOL Postmaster
>
> ----- The following addresses had permanent fatal errors -----
> <>
> (reason: 552 niteshift MAILBOX FULL)
>
> ----- Transcript of session follows -----
> ... while talking to air-me06.mail.aol.com.:
> >>> RCPT To:<>
> <<< 552 niteshift MAILBOX FULL
> 554 5.0.0 Service unavailable
--- REPLY SEPARATOR ---
Only required because above poster used QUOTED-PRINTABLE format.
When posting to newsgroups, do NOT use quoted-printable format.
* Not all NNTP clients handle quoted-printable format.
- Some users still use console-mode (non-GUI) NNTP clients.
- The long lines may not wrap properly.
- Scrolling is needed if the long line does not get wrapped.
- The long line may get truncated at the window's width.
- Quoted-printable format uses special character sequences for
logical formatting. View the raw source of your post. Text-
only clients may show that encoding when viewing your post.
* Quoting levels get mangled, especially for multiple replies.
* In replies, there is no clear delineation of content.
- Cannot tell what content is from the original poster and
what is from the respondent.
- Makes impossible to determine who said what when a reply
inserts comments inline with the quoted content.
---[end of comments]---
That's the problem when posting from Google Groups which arbitrarily
decides at times to use the non-recommended quoted-printable format
for its posts. Google Groups should be used as an archive to lookup
old posts, not to submit new ones. Because of Google Groups' ****up
in quoting, I had to manually add the proper indentation to the quoted
content, and which was not appreciated. STOP USING GOOGLE GROUPS to
post to Usenet, then go read .
As to your, er, THEIR problem:
The error status, according to RFC 2821
(
ftp://ftp.rfc-editor.org/in-notes/rfc2821.txt), "Simple Mail Transfer
Protocol", says:
552 Requested mail action aborted: exceeded storage allocation
Pretty much speaks for itself. The recipient's mailbox quota has been
consumed. *No one* can send that person any new e-mails until that
person cleans out their mailbox to regain some disk quota in their
account. It is THEIR problem and you can't do anything about it
(other than use some other means to inform them that their e-mail
account has been disable due to 100% disk quota consumption).
Similar Threads
