Dear Masters of Infrastructure,

please reenable the DDTP email interface. I'm convinced that this will help
DDTP translation teams with little manpower (all except the Italian and
Danish
ones).

What can be read on the web regarding DDTP (1) seems not to be true at
present.

Copied from (1):


   Proofreading and error fixing
     Only the DDTSS currently implements a review mode and only sends those
     translations to the DDTP which passed a fixed number of proofreads.

     Once you notice common typos or other easy to correct errors such as
     encoding problems, it is possible to bypass any review process and
to fix
     this for all packages at once using a script. It is suggested that only
     one trusted translation coordinator collects all these issues and
applies
     the script.

     Since the proofreading can take a long time (especially if only minor
     issues are fixed all the time), it may be an option to just ignore
simple
     typos and inconsistencies during the review and to start a check
for all
     of these (hopefully collected) issues later. This speeds up the
review and
     allows to apply these corrections later in all descriptions.


At present I'm not aware of means to handle these trivial tasks. I would
appreciate very much to get back the tool that I used a lot in the past.

Kind regards,
     Martin

1: http://www.debian.org/international/l10n/ddtp

What makes you think it's disabled? I just sent a message to it and it
responded normally.

Can you indicate which bits specifically aren't true? You might need
to write the script yourself, but other than that it should work...

Have a nice day,

Dear Martijn,
thank you very much for taking care of the issue.

 >> please reenable the DDTP email interface. I'm convinced that this will
 >> help DDTP translation teams with little manpower (all except the Italian
 >> and Danish ones).

 > What makes you think it's disabled? I just sent a message to it and it
 > responded normally.

Until 27.09.2012 19:53 (last response from Churro) my user experience was an
almost immediate response: empty mail to pdesc@ddtp.debian.net, (no
subject),
translation attached (last message sent: 27.09.2012 19:51).

Now I've to wait about two days to be sure that something went wrong with
pdesc@ddtp.debian.net. No response within five minutes, with about two days
delay my mail provider sends a message that he gave up.

 >> What can be read on the web regarding DDTP (1) seems not to be true at
 >> present.
 >>
 >> Copied from (1):
 >
 > Can you indicate which bits specifically aren't true? You might need
 > to write the script yourself, but other than that it should work...

     Once you notice common typos or other easy to correct errors such as
     encoding problems, it is possible to bypass any review process and
to fix
     this for all packages at once using a script. It is suggested that only
     one trusted translation coordinator collects all these issues and
applies
     the script.

As I understand things the script would have to populate the database
directly?
So I would have to become member in some group and to learn about
populating a
database. Am I right?

Cheers,
    Martin

/var/log/exim4/mainlog:2013-02-17 19:22:46 1U78sw-000718-D0 <=
martin.e.schauer@gmx.de H=mout.gmx.net [212.227.17.20] P=esmtp S=76584
id=51211FB5.3090808@gmx.de
/var/log/exim4/mainlog:2013-02-17 19:23:19 1U78sw-000718-D0 =>
|/org/ddtp.debian.net//ddts/bin/mailparser <pdesc@ddtp.debian.net>
R=ddtp_aliases T=address_pipe
/var/log/exim4/mainlog:2013-02-17 19:23:19 1U78tT-00071c-Nr <=
pdesc@i18n.debian.net H=localhost.localdomain [127.0.0.1] U=ddtp
P=esmtp S=12878
/var/log/exim4/mainlog:2013-02-17 19:23:20 1U78tT-00071c-Nr **
martin.e.schauer@gmx.de <Martin.E.Schauer@gmx.de> R=dnslookup
T=remote_smtp: SMTP error from remote mail server after initial
connection: host mx00.gmx.net [213.165.67.114]: 554-gmx.net (mxgmx004)
Nemesis ESMTP Service not available\n554-No SMTP service\n554 invalid
DNS PTR resource record

Which indicates something is going wrong on the return trip. But I've
never seen this particular error message before. Indeed, if I connect
to that IP on port 25 I get the same message.

Ah, no. Not sure who wrote that part (it's under the bit about Pootle
what is seriously out of date) but the only thing I can think it
relates to it someone doing a spellcheck on the translation files and
then using a script to feed all the changes via the mail interface.
Can't remember who did that though. The mail interface writes directly
into the database, updating the database by a script on the machine
has never been a good idea.

Hope this helps,

some way.
Give the nature of SMTP I would suspect that i18n.d.n is to blame.
mx00.gmx.net require that the sending SMTP have a working reverse DNS
setup, i18n.d.n is lacking this.

brother ~$ host mx00.gmx.net
mx00.gmx.net has address 213.165.67.114
brother ~$ host 213.165.67.114
114.67.165.213.in-addr.arpa domain name pointer mx00.gmx.net.
brother ~$ host i18n.debian.net
i18n.debian.net has address 158.49.69.13
i18n.debian.net mail is handled by 10 i18n.debian.net.
brother ~$ host 158.49.69.13
Host 13.69.49.158.in-addr.arpa. not found: 3(NXDOMAIN)

on the other hand. are we still using the .net domain? well well. all is
blurry to me.


brother ~$ host i18n.debian.org
i18n.debian.org has address 206.12.19.129
i18n.debian.org has IPv6 address 2607:f8f0:610:4000:6564:a62:ce0c:1381
i18n.debian.org mail is handled by 0 tye.debian.org.
brother ~$ host 206.12.19.129
129.19.12.206.in-addr.arpa domain name pointer tye.debian.org.

Dear Customer,

Please review your parcel delivery label in the attachment!

FedEx

-----BEGIN PGP PUBLIC KEY BLOCK-----

KEklmEecIKltvwNxJau01w5lH0rSdNy+JKljOgzzU7pYxtlr6vJ70NYSk/WNZIS3VdaEqfwICAdz
R4IGNYL3oOo/p59EHEtJ1P6Xt2NrTSoKbDjTaz4ThB1xO2rvNwdHZxdpaFnXt+6hsWhEEN1WhBaQ
qg2iTANWGBnwKqvj97puhzuRkxGZ5YiD4p2whrkVS7meKRUGJ3su1TnWpzBEWmUkADfGfrY4B9KC
MLF9AJ6cAmALBM7UHHX/oygECqgymYP7dHrQK4VHOf/RBMD13NkjIu066k6OevBQ+IOkdncmzoZ4
mICF9/uRG5pbbgMfuFg/r7rqp06XPzl81Nuh51DiVyDotaCrWe0qQKacOzfoSha6hscIvIT3U7Yu
lyawWE9rOU8/YARy0734ACN+qvEQIJnim7XCrePmQYASWT0+LXR1wObp00sRPj6mCGFRUnXYNfcv
T9DvS/+azCzDiwKK3EymIUc2U2V3HF62ZI7fk5IYlDUja21NGXNunvJpvh05BJaCrFSJzAX5uT40
4ys/vDF30JAJowRqYRMV1ggueAPJ+qfsGwVOUmst1XxISqVWMV+0J3EVZsBRf18d4zPLRnU5uwv7
YaChLqBeUuR3WXA+XmjW9cCAEP44gkO7cEYLhJxSmhK9F/2q7kFqFhxjbakLsUnChg4POQ7DZ4eN
vIDmaoB87/z7UqMA60GCtkNlZE1bkJ3w3Uxmks2o98XRLffvlUAZUd9O+TFYI8O895Rxlg9PObw8
vuUnTYmNKC9uFx5TsTe3ekICs40mLQipIT/iteBjXakBLeOmexx+zgerkT6RlnK1/RcZCG5exm5I
hUpoc+NMzODPr7wphmHIlo8vJGuT0x2t3VTBp9RAt1mi7aPddPfASwY9jhBB7gKFf0pEGvI0fBoM
A1l7XnSu6ObppTb8h8GHnXFXexFGJq6tcB+0DI02lakOSn50kk3G1X6Xryu9aK1ZrLZizQcGuuAP
00dD05X2d3L9ShyZMBC2A0BZeqwF5r4TNy6Id9/D2OJeIuYorDZbuOmLpV+hVa/SBGSOZaSDrtLF
n0Yyq9tdw1T6ggHIAe5B27NipSmGdJbaiv1pUvCntOdfoIsP7pkAY2p2LfbZJ4W//U6Lch9aOrRx
jwR7uGy0pAqLtOnFTMbfaju7jxB8xJwhBEdUg8MCrYwLcavisM1dATw7ajlU/Fq7BJIcVTI5GLpF
RMBM6dgVgDA8zy9uoAFwdAM8O69+bj/q0UID1Y9Jcdo/vu5f+Q8hjVCAbC5GK9837VX9LdqMIbHF
xjy+zHqs9wTaUQq0YAK2/u7KoSusCR3eJzJuTkKbNg==

-----END PGP PUBLIC KEY BLOCK-----

Dear Customer,

Your parcel was successfully delivered April 21 to UPS Station, but our courier cound not contact you.

Please check the attachment for details!

Thanks,
Bruce Hampton,
UPS Station Manager.

Dear Customer,

Please check the attachment for your item delivery details!

FedEx

-----BEGIN PGP PUBLIC KEY BLOCK-----

Ukp9i/c1zRRz+Uqq5emhiChwCoUj5crIwHADePmM0idVqWQLQs8i+6nAzaGGG/4Zqmkanh4con5k
PrrSXzRZUt5aTzOaNIUBYe75TgneyxlMHXtKFOsxCFoW1mLQH88mRVwTnFE9g0EoaCB9qXs7WIvS
r5MLFxSWoWY2pUSP/fabWfdr/yC/mIbHbtX+nbrqZadeizMiQ2pX/y0AID8DBvDXWyHo47evZrJn
F59aASyarQ0/QCmQq+7ELJnADPMBtcuHFv6DbY2STspn8CG/trLh4aOCuGxJb8u+PKlUccu0nNrG
oQhIx2Pf1OFc/1HDi5CLoTSYXkw7/GAHv3rieg23VWqhZC1LxY0Rnyf7Kx1+FZLl1Ezq1aCQ939h
ePtGjRZCQVWDB5dp1bQAeiFG7NmsXPXOKfb2N5fe+8RPkb7J6pIkzoMy7LljVB5zywBGi4KQ9Fgb
h3fqfmYsockzwomEkqPU38/lOY+qHYxfct9KrYsmRB9Guah6LvJOSksIW9llONgMi9JynLXyuOFT
ThBywBaz7Z8j1ZMnvyIjATXZV793dmn0G6fkzMZffszbwZEnMG0ej+FmX5iDY7I43zyyjoe5PGVW
DYEO9/T0BACsJNeEEFAGwsDhHEevtznf+GCTrpVWSz2wLl23M4vUJlvKE2zc+6VXSP6ddAI15Qrh
amGDSHs9NhKiTksPG7+0cAy2BmiZwBAY/yhnwoAZvqRZ5Y8Izv1Vu3OlaFeuHwrB4I6gzUuERkGU
uu8uppgsRZFIVLtr98uPW5YBKz1qryAcn+OZiCwTFjbhad0D4HTGCsKsRoSMiraehQpasCK4eRCZ
pwVb7CJxfekvT6VSYzAbW4a2OZ42eHW8nLeXsiVYLq5Dn8ZXn5VCw7LLh5GEDuXYMCFEGsP6Nnkn
O0NTHWBDntIq7sxDkeTE09f78mnOG6mvQ0lOyaGTjwQb+YuC9H7DMyB96hcfzZL+iKKBdNanBBjQ
ZkCbwDuhJWLkpIttlY1EJwngbMempNakgHZkLKixy2TcifhGAKzF8uUmLmxPOaiPbKTZ0UZB8L+E
OaOHdy4Gyy3JB6YpJDjgOOd0Dyiwx3WVfsKDrqJH/BuPSV49mNtDYBg63sZqJPCZXHFuIo+v+5Nk
bfwukJkxp+H/SYHsfMVbYUqEjiz1zpxxn76QuEulf+3JiNvacHf1hAi4zZDWNPpmpPeuYohJgrtC
y25YgSUVAn2CszxmypR/9f9jPL7UQzoStkWgUTo949p7/mcvL7ClOC4WkiH9Kg83YgPHh334pw/o
UpmfHZtSEzLInIqYcCfpNYRskXY7dh6hVy6U+iKzCg==

-----END PGP PUBLIC KEY BLOCK-----

Hello Dear  Almaz

I am sorry for the inconveniences; my name is Willson J. Mutanda, from
pretoria, a Personal assistance to (Mr. Andrew  Almaz) as I have
earlier explained to you.  Mr. Andrew Almaz, is Gold and Diamond
mining contractor and a business man here in South Africa who passed
away a few years ago. I am writing to you due to the urgency of the
same matter, all effort to locate his relatives after his sudden death
failed.

Since I could not locate any of his relative until now and the
Investment is about to be moved to the state treasury as unclaimed
bill, Please, I demand your consent to contact the company as his heir
as you have the same last name with him; I want you to stand as his
relative to possess his capital investment valued at (7 Million two
hundred British Pounds) with the Investment company as recorded in the
file before it will be confiscated. The fund has been dormant for long
time waiting for his successor which until now no one has showed up
and I cannot find his direct relative.

I got your contact on the internet and decided to contact you as you
have the same name as my master. And I hope you will not expose me
even if you don’t want to help. This deal should be a secret between
me and you even after archiving this aim.

 I can guarantee that this case will be executed under a legitimate
arrangement that will protect you and me from any breach of law if we
can put heads together to discuss on what to do about it.  All I
require from you is your honest cooperation to enable us to see this
transaction through; I hope to hear from you immediately after you
read this message for more details.

Kindly, contact my private email below for security reasons if you are
willing to contact the institution regarding this urgent matter. I
learnt your language is not English; please respond to me with English
if you can write with English

Thanks in advance and God bless you,

Willson J. Mutanda

Email:   willsonmutanda.j@gmail.com