Translations by Jeff Bailes
Jeff Bailes has submitted the following strings to this translation. Contributions are visually coded: currently used translations, unreviewed suggestions, rejected suggestions.
| 1. |
Checking if %s is really the same node as %s
|
|
| 2006-09-27 |
Checking if %s is really the same node as %s
|
|
| 2. |
Yes, their IP addresses match
|
|
| 2006-09-27 |
Yes, their IP addresses match
|
|
| 3. |
No, their IP addresses don't match
|
|
| 2006-09-27 |
No, their IP addresses don't match
|
|
| 4. |
nameserver failure while looking for '%s' during poll of %s: %s
|
|
| 2006-09-28 |
nameserver failure while looking for '%s' during poll of %s: %s
|
|
| 5. |
nameserver failure while looking for `%s' during poll of %s.
|
|
| 2006-09-27 |
nameserver failure while looking for `%s' during poll of %s.
|
|
| 6. |
could not decode BASE64 challenge
|
|
| 2006-09-27 |
could not decode BASE64 challenge
|
|
| 7. |
decoded as %s
|
|
| 2006-09-27 |
decoded as %s
|
|
| 8. |
kerberos error %s
|
|
| 2006-09-27 |
kerberos error %s
|
|
| 9. |
krb5_sendauth: %s [server says '%*s']
|
|
| 2006-09-27 |
krb5_sendauth: %s [server says '%*s']
|
|
| 10. |
Subject: Fetchmail oversized-messages warning
|
|
| 2006-09-28 |
Subject: Fetchmail oversized-messages warning
|
|
| 11. |
The following oversized messages were deleted on server %s account %s:
|
|
| 2006-09-28 |
The following oversized messages were deleted on server %s account %s:
|
|
| 12. |
The following oversized messages remain on server %s account %s:
|
|
| 2006-09-28 |
The following oversized messages remain on server %s account %s:
|
|
| 15. |
skipping message %s@%s:%d
|
|
| 2006-09-27 |
skipping message %s@%s:%d
|
|
| 16. |
skipping message %s@%s:%d (%d octets)
|
|
| 2006-09-27 |
skipping message %s@%s:%d (%d octets)
|
|
| 17. |
(length -1)
|
|
| 2006-09-27 |
(length -1)
|
|
| 18. |
(oversized)
|
|
| 2006-09-27 |
(oversized)
|
|
| 19. |
couldn't fetch headers, message %s@%s:%d (%d octets)
|
|
| 2006-09-27 |
couldn't fetch headers, message %s@%s:%d (%d octets)
|
|
| 20. |
reading message %s@%s:%d of %d
|
|
| 2006-09-27 |
reading message %s@%s:%d of %d
|
|
| 21. |
(%d octets)
|
|
| 2006-09-28 |
(%d octets)
|
|
| 22. |
(%d header octets)
|
|
| 2006-09-28 |
(%d header octets)
|
|
| 24. |
message %s@%s:%d was not the expected length (%d actual != %d expected)
|
|
| 2006-09-27 |
message %s@%s:%d was not the expected length (%d actual != %d expected)
|
|
| 25. |
retained
|
|
| 2006-09-27 |
retained
|
|
| 26. |
flushed
|
|
| 2006-09-27 |
flushed
|
|
| 27. |
not flushed
|
|
| 2006-09-27 |
not flushed
|
|
| 28. |
fetchlimit %d reached; %d message left on server %s account %s
fetchlimit %d reached; %d messages left on server %s account %s
|
|
| 2006-09-28 |
fetchlimit %d reached; %d message left on server %s account %s
fetchlimit %d reached; %d messages left on server %s account %s
|
|
| 29. |
timeout after %d seconds waiting to connect to server %s.
|
|
| 2006-09-27 |
timeout after %d seconds waiting to connect to server %s.
|
|
| 30. |
timeout after %d seconds waiting for server %s.
|
|
| 2006-09-27 |
timeout after %d seconds waiting for server %s.
|
|
| 31. |
timeout after %d seconds waiting for %s.
|
|
| 2006-09-27 |
timeout after %d seconds waiting for %s.
|
|
| 32. |
timeout after %d seconds waiting for listener to respond.
|
|
| 2006-09-27 |
timeout after %d seconds waiting for listener to respond.
|
|
| 33. |
timeout after %d seconds.
|
|
| 2006-09-27 |
timeout after %d seconds.
|
|
| 34. |
Subject: fetchmail sees repeated timeouts
|
|
| 2006-09-28 |
Subject: fetchmail sees repeated timeouts
|
|
| 35. |
Fetchmail saw more than %d timeouts while attempting to get mail from %s@%s.
|
|
| 2006-09-27 |
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.
|
|
| 2006-09-27 |
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 failed with status %d
|
|
| 2006-09-27 |
pre-connection command failed with status %d
|
|
| 38. |
couldn't find HESIOD pobox for %s
|
|
| 2006-09-27 |
couldn't find HESIOD pobox for %s
|
|
| 39. |
Lead server has no name.
|
|
| 2006-09-27 |
Lead server has no name.
|
|
| 41. |
%s connection to %s failed
|
|
| 2006-09-27 |
%s connection to %s failed
|
|
| 42. |
Subject: Fetchmail unreachable-server warning.
|
|
| 2006-09-28 |
Subject: Fetchmail unreachable-server warning.
|
|
| 43. |
Fetchmail could not reach the mail server %s:
|
|
| 2006-09-28 |
Fetchmail could not reach the mail server %s:
|
|
| 44. |
SSL connection failed.
|
|
| 2006-09-27 |
SSL connection failed.
|
|
| 45. |
Lock-busy error on %s@%s
|
|
| 2006-09-27 |
Lock-busy error on %s@%s
|
|
| 46. |
Server busy error on %s@%s
|
|
| 2006-09-27 |
Server busy error on %s@%s
|
|
| 47. |
Authorization failure on %s@%s%s
|
|
| 2006-09-27 |
Authorisation failure on %s@%s%s
|
|
| 48. |
(previously authorized)
|
|
| 2006-09-27 |
(previously authorised)
|
|
| 49. |
Subject: fetchmail authentication failed on %s@%s
|
|
| 2006-09-28 |
Subject: fetchmail authentication failed on %s@%s
|
|
| 50. |
Fetchmail could not get mail from %s@%s.
|
|
| 2006-09-27 |
Fetchmail could not get mail from %s@%s.
|
|
| 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.
|
|
| 2006-09-27 |
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
|
|
| 2006-09-27 |
Repoll immediately on %s@%s
|
|
| 55. |
Unknown login or authentication error on %s@%s
|
|
| 2006-09-27 |
Unknown login or authentication error on %s@%s
|
|
| 56. |
Authorization OK on %s@%s
|
|
| 2006-09-27 |
Authorisation OK on %s@%s
|
|
