Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

mails delivery failure

35 views
Skip to first unread message

Lu Wei

unread,
May 4, 2011, 4:17:20 AM5/4/11
to
I have got a message from mailer...@google.com saying
"Delivery to the following recipient failed permanently...
...has exceeded its quota for sending messages to googlegroups.com", but
I did not see any failure in hamster pg. Does this mean that the mail
sending process (SMTP) is successful, but later google's internal
process blocked the delivery? If SMTP process failed, where would the
mails go? Would there be a "mails.err" folder like "news.err"?

--
Regards,
Lu Wei
PGP key ID: 0x92CCE1EA

Wolfgang Jäth

unread,
May 4, 2011, 1:56:59 PM5/4/11
to
Am 04.05.2011 10:17, schrieb Lu Wei:
> I have got a message from mailer...@google.com saying
> "Delivery to the following recipient failed permanently...
> ...has exceeded its quota for sending messages to googlegroups.com", but
> I did not see any failure in hamster pg. Does this mean that the mail
> sending process (SMTP) is successful, but later google's internal
> process blocked the delivery?

Exactly.

>If SMTP process failed, where would the
> mails go?

Depends on the kind of failure and on the hosting program.

If the SMTP process itself fails, the sending user agent (e. g. hamster)
will receive an ERR answer. If the failure happens later, within the
target host, you'll either (mostly) receive a failure note like you did,
or (sometimes) the email drops in the andmin box like hamster does, or
(rarely) it simply will be thrown away without any further note to anybody.

>Would there be a "mails.err" folder like "news.err"?

No; the files stay in the mail.out folder, but will be renamed; at first
into something like 'xyz-a.msg' (while 'a' represents the number of
missed tries; see 'Configuration => Mail:Settings => SMTP-Settings =>
Maximum atttempts for sending a mail'), and finally into 'xyz.err'.

Wolfgang
--

Lu Wei

unread,
May 5, 2011, 9:23:37 AM5/5/11
to
Wolfgang Jäth wrote on 2011-5-5 1:56:
>> Would there be a "mails.err" folder like "news.err"?
>
> No; the files stay in the mail.out folder, but will be renamed; at first
> into something like 'xyz-a.msg' (while 'a' represents the number of
> missed tries; see 'Configuration => Mail:Settings => SMTP-Settings =>
> Maximum atttempts for sending a mail'), and finally into 'xyz.err'.
>
So I can re-send it by rename the "xyz.err" to "xyz.msg"?

P.S. I found today that most of these "permanently" failed messages were
actually successfully posted to the group. Odd.

Wolfgang Jäth

unread,
May 6, 2011, 2:59:23 AM5/6/11
to
Am 05.05.2011 15:23, schrieb Lu Wei:
>
>> No; the files stay in the mail.out folder, but will be renamed; at first
>> into something like 'xyz-a.msg' (while 'a' represents the number of
>> missed tries; see 'Configuration => Mail:Settings => SMTP-Settings =>
>> Maximum atttempts for sending a mail'), and finally into 'xyz.err'.
>>
> So I can re-send it by rename the "xyz.err" to "xyz.msg"?

Yes.

> P.S. I found today that most of these "permanently" failed messages were
> actually successfully posted to the group. Odd.

A message within the mail.out folder are emails; they can't be sent as
news.

Nevertheless, any sender has to rely on the answer it gets while
sending. The RFCs regulate, that, as long as this answer is not
received, and is not a positive confirmation, the message has to be
considered as being not sent. I'm sure, in your cases, there was
something going wrong (most probably the server didn't answer within time).

Wolfgang
--

Lu Wei

unread,
May 6, 2011, 10:24:01 PM5/6/11
to
Wolfgang Jäth wrote on 2011-5-6 14:59:
>> P.S. I found today that most of these "permanently" failed messages were
>> actually successfully posted to the group. Odd.
>
> A message within the mail.out folder are emails; they can't be sent as
> news.
>
> Nevertheless, any sender has to rely on the answer it gets while
> sending. The RFCs regulate, that, as long as this answer is not
> received, and is not a positive confirmation, the message has to be
> considered as being not sent. I'm sure, in your cases, there was
> something going wrong (most probably the server didn't answer within time).
>

Yes you are right! I was wondering that why there's so many e-mails
created and I found that it's because of my mistake in the script which
resulted in re-create same e-mails again and again. Seems google
filtered these duplicate messages (only give me "quota exceeded" error)
so I did not recognize the problem at first.

0 new messages