Translations by Joel Addison
Joel Addison has submitted the following strings to this translation. Contributions are visually coded: currently used translations, unreviewed suggestions, rejected suggestions.
11. |
The following oversized messages were deleted on server %s account %s:
|
|
2011-11-21 |
The following oversized messages were deleted on server %s account %s:
|
|
12. |
The following oversized messages remain on server %s account %s:
|
|
2011-11-21 |
The following oversized messages remain on server %s account %s:
|
|
13. |
%d message %d octets long deleted by fetchmail.
%d messages %d octets long deleted by fetchmail.
|
|
2011-11-21 |
%d message %d octets long deleted by fetchmail.
%d messages %d octets long deleted by fetchmail.
|
|
14. |
%d message %d octets long skipped by fetchmail.
%d messages %d octets long skipped by fetchmail.
|
|
2011-11-21 |
%d message %d octets long skipped by fetchmail.
%d messages %d octets long skipped by fetchmail.
|
|
21. |
(%d octets)
|
|
2011-11-21 |
(%d octets)
|
|
22. |
(%d header octets)
|
|
2011-11-21 |
(%d header octets)
|
|
23. |
(%d body octets)
|
|
2011-11-21 |
(%d body octets)
|
|
28. |
fetchlimit %d reached; %d message left on server %s account %s
fetchlimit %d reached; %d messages left on server %s account %s
|
|
2011-11-21 |
fetchlimit %d reached; %d message left on server %s account %s
fetchlimit %d reached; %d messages left on server %s account %s
|
|
35. |
Fetchmail saw more than %d timeouts while attempting to get mail from %s@%s.
|
|
2011-11-21 |
Fetchmail saw more than %d timeouts while attempting to get mail from %s@%s.
|
|
36. |
This could mean that your mailserver is stuck, or that your SMTP
server is wedged, or that your mailbox file on the server has been
corrupted by a server error. You can run `fetchmail -v -v' to
diagnose the problem.
Fetchmail won't poll this mailbox again until you restart it.
|
|
2011-11-21 |
This could mean that your mailserver is stuck, or that your SMTP
server is wedged, or that your mailbox file on the server has been
corrupted by a server error. You can run `fetchmail -v -v' to
diagnose the problem.
Fetchmail won't poll this mailbox again until you restart it.
|
|
37. |
pre-connection command terminated with signal %d
|
|
2011-11-21 |
pre-connection command terminated with signal %d
|
|
38. |
pre-connection command failed with status %d
|
|
2011-11-21 |
pre-connection command failed with status %d
|
|
39. |
couldn't find HESIOD pobox for %s
|
|
2011-11-21 |
couldn't find HESIOD pobox for %s
|
|
40. |
Lead server has no name.
|
|
2011-11-21 |
Lead server has no name.
|
|
41. |
couldn't find canonical DNS name of %s (%s): %s
|
|
2011-11-21 |
couldn't find canonical DNS name of %s (%s): %s
|
|
42. |
%s connection to %s failed
|
|
2011-11-21 |
%s connection to %s failed
|
|
43. |
SSL connection failed.
|
|
2011-11-21 |
SSL connection failed.
|
|
44. |
Lock-busy error on %s@%s
|
|
2011-11-21 |
Lock-busy error on %s@%s
|
|
45. |
Server busy error on %s@%s
|
|
2011-11-21 |
Server busy error on %s@%s
|
|
46. |
Authorization failure on %s@%s%s
|
|
2011-11-21 |
Authorisation failure on %s@%s%s
|
|
47. |
(previously authorized)
|
|
2011-11-21 |
(previously authorised)
|
|
48. |
For help, see http://www.fetchmail.info/fetchmail-FAQ.html#R15
|
|
2011-11-21 |
For help, see http://www.fetchmail.info/fetchmail-FAQ.html#R15
|
|
50. |
Fetchmail could not get mail from %s@%s.
|
|
2011-11-21 |
Fetchmail could not get mail from %s@%s.
|
|
51. |
The attempt to get authorization failed.
Since we have already succeeded in getting authorization for this
connection, this is probably another failure mode (such as busy server)
that fetchmail cannot distinguish because the server didn't send a useful
error message.
|
|
2011-11-21 |
The attempt to get authorisation failed.
Since we have already succeeded in getting authorisation for this
connection, this is probably another failure mode (such as busy server)
that fetchmail cannot distinguish because the server didn't send a useful
error message.
|
|
52. |
However, if you HAVE changed your account details since starting the
fetchmail daemon, you need to stop the daemon, change your configuration
of fetchmail, and then restart the daemon.
The fetchmail daemon will continue running and attempt to connect
at each cycle. No future notifications will be sent until service
is restored.
|
|
2011-11-21 |
However, if you HAVE changed your account details since starting the
fetchmail daemon, you need to stop the daemon, change your configuration
of fetchmail, and then restart the daemon.
The fetchmail daemon will continue running and attempt to connect
at each cycle. No future notifications will be sent until service
is restored.
|
|
53. |
The attempt to get authorization failed.
This probably means your password is invalid, but some servers have
other failure modes that fetchmail cannot distinguish from this
because they don't send useful error messages on login failure.
The fetchmail daemon will continue running and attempt to connect
at each cycle. No future notifications will be sent until service
is restored.
|
|
2011-11-21 |
The attempt to get authorisation failed.
This probably means your password is invalid, but some servers have
other failure modes that fetchmail cannot distinguish from this
because they don't send useful error messages on login failure.
The fetchmail daemon will continue running and attempt to connect
at each cycle. No future notifications will be sent until service
is restored.
|
|
54. |
Repoll immediately on %s@%s
|
|
2011-11-21 |
Repoll immediately on %s@%s
|
|
56. |
Unknown login or authentication error on %s@%s
|
|
2011-11-21 |
Unknown login or authentication error on %s@%s
|
|
57. |
Authorization OK on %s@%s
|
|
2011-11-21 |
Authorisation OK on %s@%s
|
|
59. |
Fetchmail was able to log into %s@%s.
|
|
2011-11-21 |
Fetchmail was able to log into %s@%s.
|
|
60. |
Service has been restored.
|
|
2011-11-21 |
Service has been restored.
|
|
61. |
selecting or re-polling folder %s
|
|
2011-11-21 |
selecting or re-polling folder %s
|
|
62. |
selecting or re-polling default folder
|
|
2011-11-21 |
selecting or re-polling default folder
|
|
63. |
%s at %s (folder %s)
|
|
2011-11-21 |
%s at %s (folder %s)
|
|
64. |
%s at %s
|
|
2011-11-21 |
%s at %s
|
|
65. |
Polling %s
|
|
2011-11-21 |
Polling %s
|
|
66. |
%d message (%d %s) for %s
%d messages (%d %s) for %s
|
|
2011-11-21 |
%d message (%d %s) for %s
%d messages (%d %s) for %s
|
|
67. |
seen
seen
|
|
2011-11-21 |
seen
seen
|
|
68. |
%d message for %s
%d messages for %s
|
|
2011-11-21 |
%d message for %s
%d messages for %s
|
|
69. |
(%d octets).
|
|
2011-11-21 |
(%d octets).
|
|
70. |
No mail for %s
|
|
2011-11-21 |
No mail for %s
|
|
71. |
bogus message count!
|
|
2011-11-21 |
bogus message count!
|
|
73. |
socket
|
|
2011-11-21 |
socket
|
|
74. |
missing or bad RFC822 header
|
|
2011-11-21 |
missing or bad RFC822 header
|
|
75. |
MDA
|
|
2011-11-21 |
MDA
|
|
76. |
client/server synchronization
|
|
2011-11-21 |
client/server synchronisation
|
|
77. |
client/server protocol
|
|
2011-11-21 |
client/server protocol
|
|
78. |
lock busy on server
|
|
2011-11-21 |
lock busy on server
|
|
79. |
SMTP transaction
|
|
2011-11-21 |
SMTP transaction
|
|
80. |
DNS lookup
|
|
2011-11-21 |
DNS lookup
|