Translations by Jukka Kolehmainen

Jukka Kolehmainen has submitted the following strings to this translation. Contributions are visually coded: currently used translations, unreviewed suggestions, rejected suggestions.

126 of 26 results
1.
Checking if %s is really the same node as %s
2006-05-16
Checking if %s is really the same node as %s↵
2.
Yes, their IP addresses match
2006-05-16
Yes, their IP addresses match↵
3.
No, their IP addresses don't match
2006-05-16
No, their IP addresses don't match
6.
could not decode BASE64 challenge
2006-05-16
could not decode BASE64 challenge↵
7.
decoded as %s
2006-05-16
decoded as %s↵
8.
kerberos error %s
2006-05-16
kerberos error %s↵
19.
couldn't fetch headers, message %s@%s:%d (%d octets)
2006-05-16
couldn't fetch headers, message %s@%s:%d (%d octets)↵
24.
message %s@%s:%d was not the expected length (%d actual != %d expected)
2006-05-16
message %s@%s:%d was not the expected length (%d actual != %d expected)↵
25.
retained
2006-05-16
retained↵
26.
flushed
2006-05-16
flushed↵
27.
not flushed
2006-05-16
not flushed↵
29.
timeout after %d seconds waiting to connect to server %s.
2006-05-16
timeout after %d seconds waiting to connect to server %s.↵
30.
timeout after %d seconds waiting for server %s.
2006-05-16
timeout after %d seconds waiting for server %s.↵
31.
timeout after %d seconds waiting for %s.
2006-05-16
timeout after %d seconds waiting for %s.↵
32.
timeout after %d seconds waiting for listener to respond.
2006-05-16
timeout after %d seconds waiting for listener to respond.↵
33.
timeout after %d seconds.
2006-05-16
timeout after %d seconds.↵
35.
Fetchmail saw more than %d timeouts while attempting to get mail from %s@%s.
2006-05-16
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-05-16
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.↵
38.
pre-connection command failed with status %d
2006-05-16
pre-connection command failed with status %d↵
39.
couldn't find HESIOD pobox for %s
2006-05-16
couldn't find HESIOD pobox for %s↵
40.
Lead server has no name.
2006-05-16
Lead server has no name.↵
43.
SSL connection failed.
2006-05-16
SSL connection failed.↵
44.
Lock-busy error on %s@%s
2006-05-16
Lock-busy error on %s@%s↵
45.
Server busy error on %s@%s
2006-05-16
Server busy error on %s@%s↵
46.
Authorization failure on %s@%s%s
2006-05-16
Authorization failure on %s@%s%s↵
47.
(previously authorized)
2006-05-16
(previously authorized)