Re: Fwd: Mail delivery failed: returning message to sender

[Russ Allbery]

Russ Allbery  writes:

> I will file a bug against reportbug on your behalf.

I think this bug may have been introduced in the Python 2 to Python 3
conversion, if I am understanding it correctly.  Bug report is here:

https://bugs.debian.org/849586

-- 
Russ Allbery (r...@debian.org)   

Re: Fwd: Mail delivery failed: returning message to sender

[Russ Allbery]

TOMAS MARTIŠIUS  writes:

> Thanks for solving this problem, bus I am not expert of all these
> encodings too, so I simply need working reportbug package and I really
> don't know in which point the problem is: in packege or in mailing
> system, which must accept bug report. But if both encodings can be used
> (as says some different RCS's) I prefer to fix mailing system, if it is
> possible, to accept both types of encodings. Especially because bug
> report can be send using some common mail system.

If reportbug generated:

From: =?utf-8?b?VG9tYXMgTWFydGnFoWl1cyA8dG9tYXNAcHVnYS52ZHUubHQ+?=

then this is definitely a bug in reportbug itself.  Looking at the
reportbug source, it is not giving email.message sufficient hints about
how to encode the From header correctly when the name includes non-ASCII
characters, which causes exactly this problem:

| lothlorien:~$ python3
| Python 3.5.2+ (default, Nov 22 2016, 01:00:20) 
| [GCC 6.2.1 20161119] on linux
| Type "help", "copyright", "credits" or "license" for more information.
| >>> from email.mime.text import MIMEText
| >>> message = MIMEText('Some test')
| >>> message['From'] = 'TOMAS MARTIŠIUS '
| >>> message['To'] = 'Russ Allbery '
| >>> print(message)
| Content-Type: text/plain; charset="us-ascii"
| MIME-Version: 1.0
| Content-Transfer-Encoding: 7bit
| From: =?utf-8?b?VE9NQVMgTUFSVEnFoElVUyA8dG9tYXNAcHVnYS52ZHUubHQ+?=
| To: Russ Allbery 
| 
| Some test

There are various ways to fix this.  The easiest is probably to use
email.utils.formataddr:

| >>> message = MIMEText('Some test')
| >>> message['From'] = formataddr(('TOMAS MARTIŠIUS', 'to...@puga.vdu.lt'))
| >>> message['To'] = formataddr(('Russ Allbery', 'ea...@eyrie.org'))
| >>> print(message)
| Content-Type: text/plain; charset="us-ascii"
| MIME-Version: 1.0
| Content-Transfer-Encoding: 7bit
| From: =?utf-8?q?TOMAS_MARTI=C5=A0IUS?= 
| To: Russ Allbery 
| 
| Some test

I will file a bug against reportbug on your behalf.

-- 
Russ Allbery (r...@debian.org)   

Re: Fwd: Mail delivery failed: returning message to sender

[Andrew Shadura]

Tomas,

On 28 December 2016 at 18:52, TOMAS MARTIŠIUS  wrote:
> Thanks for solving this problem, bus I am not  expert of all these encodings
> too,
> so I simply need working reportbug package and I really don't know in which
> point the problem is: in packege or in mailing system, which must accept bug
> report. But if both encodings can be used (as says some different RCS's) I
> prefer to fix mailing system, if it is possible, to accept both types of
> encodings. Especially because bug report can be send using some common mail
> system.

This isn't a common issue to deal with; I understand your reportbug is
misconfigured, hence there's no reason BTS should accept what it
produces.

However, reportbug could detect an incorrect configuration and produce
a warning.

It would be helpful if you posted some more information about your
system and in particular reportbug-related configuration here.

Thanks.

-- 
Cheers,
  Andrew

Re: Fwd: Mail delivery failed: returning message to sender

[TOMAS MARTIŠIUS]

Thanks for solving this problem, bus I am not  expert of all these 
encodings too,
so I simply need working reportbug package and I really don't know in 
which point the problem is: in packege or in mailing system, which must 
accept bug report. But if both encodings can be used (as says some 
different RCS's) I prefer to fix mailing system, if it is possible, to 
accept both types of encodings. Especially because bug report can be 
send using some common mail system.


Best regards,

Pagarbiai,

Tomas Martišius
Vytauto Didžiojo universitetas
vyr. tinklo administratorius

2016.12.28 18:53, Andreas Metzler rašė:

Niels Thykier  wrote:

Andreas Metzler:

[...]

No, the encoding was not correct. Compare how you (your MUA) just did it in
this message with the rejected one.
   From: =?UTF-8?Q?TOMAS_MARTI=c5=a0IUS?= 
   From: =?utf-8?b?VG9tYXMgTWFydGnFoWl1cyA8dG9tYXNAcHVnYS52ZHUubHQ+?=

[...]


Hi,
The latter is "simply" a base64 encoding:
$ echo 'VG9tYXMgTWFydGnFoWl1cyA8dG9tYXNAcHVnYS52ZHUubHQ+' | base64 -d
Tomas Martišius 

[...]

I am not an expert on permitted ways of quoting UTF-8 in mail
headers, but the base64 method does not seem entirely inconceivable
for some RFC to support that (especially not considering you can
encode the body with base64).

Whether VG9tYXMgTWFydGnFoWl1cyA8dG9tYXNAcHVnYS52ZHUubHQ+ can be
/decoded/ to something that contains a mail-address is not relevant. The
header

   From: =?utf-8?b?VG9tYXMgTWFydGnFoWl1cyA8dG9tYXNAcHVnYS52ZHUubHQ+?=

does not fullfill the syntax required by RFC 2822. These syntax
requiremts apply to the (possibly rfc2047-) *encoded* field contents,
not to the decoded values.

cu Andreas

Re: Fwd: Mail delivery failed: returning message to sender

[Andreas Metzler]

Niels Thykier  wrote:
> Andreas Metzler:
[...]
>> No, the encoding was not correct. Compare how you (your MUA) just did it in
>> this message with the rejected one.

>>   From: =?UTF-8?Q?TOMAS_MARTI=c5=a0IUS?= 

>>   From: =?utf-8?b?VG9tYXMgTWFydGnFoWl1cyA8dG9tYXNAcHVnYS52ZHUubHQ+?=
[...]

> Hi,

> The latter is "simply" a base64 encoding:

> $ echo 'VG9tYXMgTWFydGnFoWl1cyA8dG9tYXNAcHVnYS52ZHUubHQ+' | base64 -d
> Tomas Martišius 
[...]
> I am not an expert on permitted ways of quoting UTF-8 in mail
> headers, but the base64 method does not seem entirely inconceivable
> for some RFC to support that (especially not considering you can
> encode the body with base64).

Whether VG9tYXMgTWFydGnFoWl1cyA8dG9tYXNAcHVnYS52ZHUubHQ+ can be
/decoded/ to something that contains a mail-address is not relevant. The
header 

  From: =?utf-8?b?VG9tYXMgTWFydGnFoWl1cyA8dG9tYXNAcHVnYS52ZHUubHQ+?=

does not fullfill the syntax required by RFC 2822. These syntax
requiremts apply to the (possibly rfc2047-) *encoded* field contents,
not to the decoded values.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Re: Fwd: Mail delivery failed: returning message to sender

[Andrew Shadura]

On 28 December 2016 at 17:14, Niels Thykier  wrote:
> Niels Thykier:
>> Andreas Metzler:
>>> [...]
>>>
>>> Hello,
>>>
>>> No, the encoding was not correct. Compare how you (your MUA) just did it in
>>> this message with the rejected one.
>>>
>>>   From: =?UTF-8?Q?TOMAS_MARTI=c5=a0IUS?= 
>>>
>>>   From: =?utf-8?b?VG9tYXMgTWFydGnFoWl1cyA8dG9tYXNAcHVnYS52ZHUubHQ+?=
>>>
>>
>>
>>[...]
>
> >From a quick glance, it looks to be specified in RFC1342, which also
> specified the ?Q? variant that was used in the accepted mail.
>
>
> RFC1342:
> """
> [...]
>
>An "encoded-word" is more precisely defined by the following EBNF
>grammar, using the notation of RFC 822:
>
>encoded-word = "=" "?" charset "?" encoding "?" encoded-text "?" "="
>
>charset = token; legal charsets defined by RFC 1341
>
>encoding = token   ; Either "B" or "Q"
>
>token = 1*
>
>tspecials = "(" / ")" / "<" / ">" / "@" / "," / ";" / ":" / "\" /
><"> / "/" / "[" / "]" / "?" / "." / "="
>
>encoded-text = 1*   ; SPACE> (but see "Use of encoded-words in message
>   ; headers", below)
> [...]
>
>
> The "B" encoding
>
>The "B" encoding is identical to the "BASE64" encoding defined by RFC
>1341.
> """
>
> This is not a comment on whether RFC1342 encoded "From:" headers is
> something we is supporting/should support.

Clint is being slightly unhelpful. BTS does accept base64, see #849535 with:

From: =?utf-8?b?w4HFiMSPxZnDqMW1IMWgxKfDpMSPxa3FlcOl?= 
Subject: =?utf-8?b?dG5hdDY0OiDFpWXFocWlIGLDvMSdIMWZw6nhuZXDs8WVxaU=?=

What Clint is saying, and what Andreas has pointed out before, is that
display name and address have to be separately encoded, i.e. they
can't be a single encoded string, otherwise they decode into "Name
" not "Name" 

-- 
Cheers,
  Andrew

Re: Fwd: Mail delivery failed: returning message to sender

[Alec Leamas]

On 28/12/16 17:02, Niels Thykier wrote:


Note the difference between "=?UTF-8?Q?" vs. "=?UTF-8?b?" (Q vs. b).  I
presume the "b" is for "binary" or/and "Base64 encoded" vs. Q which
would be "quoted printed" or something like that.

I am not an expert on permitted ways of quoting UTF-8 in mail headers,
but the base64 method does not seem entirely inconceivable for some RFC
to support that (especially not considering you can encode the body with
base64).


Nor am I, the experts wrote the MIME RFC [1]. Which basically says that 
both encodings are allowed, but the Q (Quoted printable) is actually 
recommended in a case like this.


Cheers!

--alec


[1] https://www.ietf.org/rfc/rfc2047.txt, section 4,

Re: Fwd: Mail delivery failed: returning message to sender

[Niels Thykier]

Niels Thykier:
> Andreas Metzler:
>> [...]
>>
>> Hello,
>>
>> No, the encoding was not correct. Compare how you (your MUA) just did it in
>> this message with the rejected one.
>>
>>   From: =?UTF-8?Q?TOMAS_MARTI=c5=a0IUS?= 
>>
>>   From: =?utf-8?b?VG9tYXMgTWFydGnFoWl1cyA8dG9tYXNAcHVnYS52ZHUubHQ+?=
>>
> 
> 
>[...]

>From a quick glance, it looks to be specified in RFC1342, which also
specified the ?Q? variant that was used in the accepted mail.


RFC1342:
"""
[...]

   An "encoded-word" is more precisely defined by the following EBNF
   grammar, using the notation of RFC 822:

   encoded-word = "=" "?" charset "?" encoding "?" encoded-text "?" "="

   charset = token; legal charsets defined by RFC 1341

   encoding = token   ; Either "B" or "Q"

   token = 1*

   tspecials = "(" / ")" / "<" / ">" / "@" / "," / ";" / ":" / "\" /
   <"> / "/" / "[" / "]" / "?" / "." / "="

   encoded-text = 1* (but see "Use of encoded-words in message
  ; headers", below)
[...]


The "B" encoding

   The "B" encoding is identical to the "BASE64" encoding defined by RFC
   1341.
"""

This is not a comment on whether RFC1342 encoded "From:" headers is
something we is supporting/should support.

Thanks,
~Niels

Re: Fwd: Mail delivery failed: returning message to sender

[Clint Adams]

On Wed, Dec 28, 2016 at 04:02:00PM +, Niels Thykier wrote:
> I am not an expert on permitted ways of quoting UTF-8 in mail headers,
> but the base64 method does not seem entirely inconceivable for some RFC
> to support that (especially not considering you can encode the body with
> base64).

You might want to look at RFC 2047.

Re: Fwd: Mail delivery failed: returning message to sender

[Niels Thykier]

Andreas Metzler:
> [...]
> 
> Hello,
> 
> No, the encoding was not correct. Compare how you (your MUA) just did it in
> this message with the rejected one.
> 
>   From: =?UTF-8?Q?TOMAS_MARTI=c5=a0IUS?= 
> 
>   From: =?utf-8?b?VG9tYXMgTWFydGnFoWl1cyA8dG9tYXNAcHVnYS52ZHUubHQ+?=
> 


Hi,

The latter is "simply" a base64 encoding:

$ echo 'VG9tYXMgTWFydGnFoWl1cyA8dG9tYXNAcHVnYS52ZHUubHQ+' | base64 -d
Tomas Martišius 

Note the difference between "=?UTF-8?Q?" vs. "=?UTF-8?b?" (Q vs. b).  I
presume the "b" is for "binary" or/and "Base64 encoded" vs. Q which
would be "quoted printed" or something like that.

I am not an expert on permitted ways of quoting UTF-8 in mail headers,
but the base64 method does not seem entirely inconceivable for some RFC
to support that (especially not considering you can encode the body with
base64).

Thanks,
~Niels

Re: Fwd: Mail delivery failed: returning message to sender

[Andreas Metzler]

On 2016-12-28 TOMAS MARTIŠIUS  wrote:
> 2016.12.28 09:09, Andreas Metzler rašė:
>> On 2016-12-27 TOMAS MARTIŠIUS  wrote:
>>> Why I can't report bug using reportbug command? After reporting I get back
>>> e-mail with this message:
[...]
>> The From header does not look too good:

>>> From: =?utf-8?b?VG9tYXMgTWFydGnFoWl1cyA8dG9tYXNAcHVnYS52ZHUubHQ+?=

> But I am not only english speaking man, so there are UTF-8 chars in my
> last name. Thats why subject is encoded. And it is encoded in standard
> way, using reportbug command.

> It seams that if someone using UTF-8 in his name and wants report bug - it
> has a problems.

> I think this is totally bad for debian community - we are losing important
> bug reports.
[...]

Hello,

No, the encoding was not correct. Compare how you (your MUA) just did it in
this message with the rejected one.

  From: =?UTF-8?Q?TOMAS_MARTI=c5=a0IUS?= 

This matches

from=   "From:" mailbox-list CRLF
mailbox-list=   (mailbox *("," mailbox)) / obs-mbox-list
mailbox =   name-addr / addr-spec
name-addr   =   [display-name] angle-addr
angle-addr  =   [CFWS] "<" addr-spec ">" [CFWS] / obs-angle-addr
display-name=   phrase
obs-angle-addr  =   [CFWS] "<" [obs-route] addr-spec ">" [CFWS]
addr-spec   =   local-part "@" domain

in RFC 2822. There is an addr-spec (to...@puga.vdu.lt) and a
display-name ("=?UTF-8?Q?TOMAS_MARTI=c5=a0IUS?=). The rejected message
OTOH has no valid e-mail adress.
 From: =?utf-8?b?VG9tYXMgTWFydGnFoWl1cyA8dG9tYXNAcHVnYS52ZHUubHQ+?=

FWIW I just used reportbug to generate a test-bugreport (with 8-bit
characters in the submitter name), and reportbug generated a correctly
encoded.

Please submit a bug-report against reportbug if there is an easy way to
reproduce the issue.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Re: Fwd: Mail delivery failed: returning message to sender

[Andrew Shadura]

On 28 December 2016 at 10:08, TOMAS MARTIŠIUS  wrote:
> Hello,
>
> But I am not only english speaking man, so there are UTF-8 chars in my last
> name. Thats why subject
> is encoded. And it is encoded in standard way, using reportbug command.
>
> It seams that if someone using UTF-8 in his name and wants report bug - it
> has a problems.
>
> I think this is totally bad for debian community - we are losing important
> bug reports.

I think that's not the reason, I succeeded in creating
http://bugs.debian.org/849535

-- 
Cheers,
  Andrew

Re: Fwd: Mail delivery failed: returning message to sender

[TOMAS MARTIŠIUS]

Hello,

But I am not only english speaking man, so there are UTF-8 chars in my 
last name. Thats why subject

is encoded. And it is encoded in standard way, using reportbug command.

It seams that if someone using UTF-8 in his name and wants report bug - 
it has a problems.


I think this is totally bad for debian community - we are losing 
important bug reports.


Best regards,

Pagarbiai

Tomas Martišius
Vytauto Didžiojo universitetas
vyr. tinklo administratorius

2016.12.28 09:09, Andreas Metzler rašė:

On 2016-12-27 TOMAS MARTIŠIUS  wrote:

Hello,
Why I can't report bug using reportbug command? After reporting I get back
e-mail with this message:

[...]

Remote-MTA: dns; buxtehude.debian.org
Diagnostic-Code: smtp; 550 Invalid header syntax:

The From header does not look too good:


From: =?utf-8?b?VG9tYXMgTWFydGnFoWl1cyA8dG9tYXNAcHVnYS52ZHUubHQ+?=

cu Andreas

Re: Fwd: Mail delivery failed: returning message to sender

[Andreas Metzler]

On 2016-12-27 TOMAS MARTIŠIUS  wrote:
> Hello,

> Why I can't report bug using reportbug command? After reporting I get back
> e-mail with this message:

[...]
> Remote-MTA: dns; buxtehude.debian.org
> Diagnostic-Code: smtp; 550 Invalid header syntax:

The From header does not look too good:

> From: =?utf-8?b?VG9tYXMgTWFydGnFoWl1cyA8dG9tYXNAcHVnYS52ZHUubHQ+?=

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Fwd: Mail delivery failed: returning message to sender

[TOMAS MARTIŠIUS]

Hello,

Why I can't report bug using reportbug command? After reporting I get 
back e-mail with this message:


Best regards,

Tomas

 Persiųstas laiškas 
Tema:   Mail delivery failed: returning message to sender
Data:   Tue, 27 Dec 2016 19:41:49 +0200
Kas:Mail Delivery System 
Kam:to...@puga.vdu.lt



This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  sub...@bugs.debian.org
host buxtehude.debian.org [209.87.16.39]
SMTP error from remote mail server after end of data:
550 Invalid header syntax:

Reporting-MTA: dns; tarnas.vdu.lt

Action: failed
Final-Recipient: rfc822;submit@bugs.debian.org
Status: 5.0.0
Remote-MTA: dns; buxtehude.debian.org
Diagnostic-Code: smtp; 550 Invalid header syntax:

--- Begin Message ---
Package: reportbug
Version: 7.1.1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

reportbug GTK interface in fresh debian install with MATE is unusable. First it 
crashes with error:

Gtk-Message: Failed to load module "canberra-gtk-module"
Traceback (most recent call last):
  File "/usr/bin/reportbug", line 2233, in 
main()
  File "/usr/bin/reportbug", line 1107, in main
return iface.user_interface()
  File "/usr/bin/reportbug", line 2149, in user_interface
package, severity, mode, charset=charset, tags=tags)
  File "/usr/bin/reportbug", line 182, in handle_editing
editor, charset)
  File "/usr/lib/python3/dist-packages/reportbug/ui/gtk2_ui.py", line 1561, in 
func
op = klass(parent)
  File "/usr/lib/python3/dist-packages/reportbug/ui/gtk2_ui.py", line 539, in 
__init__
self.widget = self.create_widget()
  File "/usr/lib/python3/dist-packages/reportbug/ui/gtk2_ui.py", line 1173, in 
create_widget
expander = Gtk.Expander("Other system information")
TypeError: GObject.__init__() takes exactly 0 arguments (1 given)

Instaling libcanberra-gtk-module looks like solves this error, so I think 
reportbug must have libcanberra-gtk-module
as runtime depenedency. But other error rises trying report bug:

TypeError: Couldn't find foreign struct converter for 'cairo.Context'

Some other dependencies are missing?

Please fix reportbug runtime dependencies.

Best regards,

Tomas

-- Package-specific info:
** /home/tomas/.reportbugrc:
reportbug_version "7.1.1"
mode standard
realname "Tomas Martišius"
email "to...@puga.vdu.lt"
smtphost "tarnas.vdu.lt"

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.8.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages reportbug depends on:
ii  apt1.4~beta2
ii  python3-reportbug  7.1.1
pn  python3:any

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail 
pn  debconf-utils  
pn  debsums
pn  dlocate
pn  emacs23-bin-common | emacs24-bin-common
ii  exim4  4.88~RC6-2
ii  exim4-daemon-light [mail-transport-agent]  4.88~RC6-2
ii  file   1:5.29-2
ii  gir1.2-gtk-3.0 3.22.5-1
ii  gir1.2-vte-2.910.46.1-1
ii  gnupg  2.1.17-2
ii  python3-gi 3.22.0-2
pn  python3-gtkspellcheck  
pn  python3-urwid  
ii  xdg-utils  1.1.1-1

-- no debconf information
--- End Message ---

Re: Looking for Martin Quinson (Fwd: Mail delivery failed: returning message to sender (Tue, Sep 25, 2001 at 01:13:12AM +0200))

[Jérôme Marant]

Eric Van Buggenhaut [EMAIL PROTECTED] writes:

 From: Mail Delivery System [EMAIL PROTECTED]
 Subject: Mail delivery failed: returning message to sender
 To: [EMAIL PROTECTED]
 
 This message was created automatically by mail delivery software (Exim).
 
 A message that you sent could not be delivered to one or more of its
 recipients. This is a permanent error. The following address(es) failed:
 
   [EMAIL PROTECTED]
 retry time not reached for any host after a long failure period


  The email address is correct and worked yesterday with me, at least.

-- 
Jérôme Marant [EMAIL PROTECTED]
  [EMAIL PROTECTED]

Re: Looking for Martin Quinson (Fwd: Mail delivery failed: returning message to sender (Tue, Sep 25, 2001 at 01:13:12AM +0200))

[Martin Quinson]

I'm still alive ! ;)

The mail server of my school had some hard problems yesterday. I reply
privately now..

Mt

On Tue, Sep 25, 2001 at 01:35:07AM +0200, Eric Van Buggenhaut wrote:
 - Forwarded message from Mail Delivery System [EMAIL PROTECTED] -
 
 Envelope-to: [EMAIL PROTECTED]
 X-Failed-Recipients: [EMAIL PROTECTED]
 From: Mail Delivery System [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Subject: Mail delivery failed: returning message to sender
 
 This message was created automatically by mail delivery software (Exim).
 
 A message that you sent could not be delivered to one or more of its
 recipients. This is a permanent error. The following address(es) failed:
 
   [EMAIL PROTECTED]
 retry time not reached for any host after a long failure period

Re: Looking for Martin Quinson (Fwd: Mail delivery failed: returning message to sender (Tue, Sep 25, 2001 at 01:13:12AM +0200))

[Eric Van Buggenhaut]

On Tue, Sep 25, 2001 at 09:33:43AM +0200, Martin Quinson wrote:
 I'm still alive ! ;)
 
 The mail server of my school had some hard problems yesterday. I reply
 privately now..

This doesn't help me. Provide an alternate email address please.

 
 Mt
 
 On Tue, Sep 25, 2001 at 01:35:07AM +0200, Eric Van Buggenhaut wrote:
  - Forwarded message from Mail Delivery System [EMAIL PROTECTED] -
  
  Envelope-to: [EMAIL PROTECTED]
  X-Failed-Recipients: [EMAIL PROTECTED]
  From: Mail Delivery System [EMAIL PROTECTED]
  To: [EMAIL PROTECTED]
  Subject: Mail delivery failed: returning message to sender
  
  This message was created automatically by mail delivery software (Exim).
  
  A message that you sent could not be delivered to one or more of its
  recipients. This is a permanent error. The following address(es) failed:
  
[EMAIL PROTECTED]
  retry time not reached for any host after a long failure period
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 
 
 

-- 
Eric VAN BUGGENHAUT Oh My God! They killed init! You Bastards!
--from a /. post
\_|_/   Andago
   \/   \/  Av. Santa Engracia, 54
a n d a g o  |--E-28010 Madrid - tfno:+34(91)2041100
   /\___/\  http://www.andago.com
/ | \   Innovando en Internet
[EMAIL PROTECTED]

Re: Looking for Martin Quinson (Fwd: Mail delivery failed: returning message to sender (Tue, Sep 25, 2001 at 01:13:12AM +0200))

[Martin Quinson]

On Tue, Sep 25, 2001 at 11:33:56AM +0200, Eric Van Buggenhaut wrote:
 On Tue, Sep 25, 2001 at 09:33:43AM +0200, Martin Quinson wrote:
  I'm still alive ! ;)
  
  The mail server of my school had some hard problems yesterday. I reply
  privately now..
 
 This doesn't help me. Provide an alternate email address please.

May be a problem with ECN. The firewall of my scholl is broken. Remove ECN
from your kernel, or write to [EMAIL PROTECTED] ...

Sorry, Mt.

-- 
Un clavier azerty en vaut deux.

Looking for Martin Quinson (Fwd: Mail delivery failed: returning message to sender (Tue, Sep 25, 2001 at 01:13:12AM +0200))

[Eric Van Buggenhaut]

- Forwarded message from Mail Delivery System [EMAIL PROTECTED] -

Envelope-to: [EMAIL PROTECTED]
X-Failed-Recipients: [EMAIL PROTECTED]
From: Mail Delivery System [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Mail delivery failed: returning message to sender

This message was created automatically by mail delivery software (Exim).

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  [EMAIL PROTECTED]
retry time not reached for any host after a long failure period

-- This is a copy of the message, including all the headers. --

Return-path: [EMAIL PROTECTED]
Received: from eric by femto with local (Exim 3.32 #1 (Debian))
id 15leuV-KU-00
for [EMAIL PROTECTED]; Tue, 25 Sep 2001 01:13:11 +0200
Date: Tue, 25 Sep 2001 01:13:11 +0200
From: Eric Van Buggenhaut [EMAIL PROTECTED]
To: Martin Quinson [EMAIL PROTECTED]
Subject: Re: Who does the french translation of bf and di ? (me?)
Message-ID: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
References: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: [EMAIL PROTECTED]
User-Agent: Mutt/1.3.20i
X-Echelon: FBI CIA NSA Handgun Assault Atomic Bomb Heroin Drug Terrorism
Sender: Eric Van Buggenhaut [EMAIL PROTECTED]

On Sat, Sep 22, 2001 at 11:39:56AM +0200, Martin Quinson wrote:
 On Thu, Sep 20, 2001 at 07:29:41PM +0200, Eric Van Buggenhaut wrote:
  On Thu, Sep 20, 2001 at 12:03:12PM +0200, Martin Quinson wrote:
   Hello,
   
   I would like to contact the french translator(s) of bf and di to see if 
   they
   need my help. 
   
  
  I used to maitain the French translation of the documentation of the
  boot-floppies for the last year. We currently have 2 branches, one for 
  potato
  and one for woody.
 
 Ah, zut, et quel est la branche principale ? I.e., quelle est la branche que
 j'ai récupéré quand je n'ai rien précisé ?

Woddy est à ce jour la branche MAIN

 
  Obviously any help is always welcome ;) 
 
 Certes. Mais c'etait pour eviter le travail en double, aussi. (:
 
  I guess you have write access to cvs/boot-floppies right ?
 
 Ben non. Je suis pas dévelopeur. En fait, j'en sais rien, j'ai le droit
 d'ecriture sur le site web, et aussi dans les docs, il me semble. Donc,
 j'essayerais quand j'en aurais besoin, et si ca marche pas, on verra.
 
 Qu'est ce que tu (ou quiconque) traduis en ce moment ? Qu'est ce que je peux
 traduire sans marcher sur les pieds de quiconque ? J'ai une nette préférence
 pour les fichiers po par rapport à la documentation en blabla-ML, mais s'il
 faut vraiment, ...

Moi je m'occupe des .sgml

Comme je n'ai jamais vraiment prêté attention aux fichiers .po ça tombe bien.
Bon, ben vas-y attaque ! Fais les commit toi-même si tu peux. Sinon, envoie-moi
les .diff et je ferai le commit pour toi.

 
 
 Voila, voila, Mt.
 
 -- 
 Un clavier azerty en vaut deux.

hahahaha ;)

-- 
Eric VAN BUGGENHAUT

[EMAIL PROTECTED]

- End forwarded message -

-- 
Eric VAN BUGGENHAUT

[EMAIL PROTECTED]