Translations by padmawan
padmawan has submitted the following strings to this translation. Contributions are visually coded: currently used translations, unreviewed suggestions, rejected suggestions.
| ~ |
This could mean that the root CA's signing certificate is not in the trusted CA certificate location, or that c_rehash needs to be run on the certificate directory. For details, please see the documentation of --sslcertpath and --sslcertfile in the manual page.
|
|
| 2019-09-06 |
Ini dapat berarti bahwa sertifikat penandatanganan root CA tidak berada di lokasi sertifikat CA yang dipercaya, atau c_rehash perlu dijalankan di direktori sertifikat. Untuk detail, silakan lihat dokumentasi --sslcertpath dan --sslcertfile di halaman manual.
|
|
| ~ |
fetchmail: Error: multiple "defaults" records in config file.
|
|
| 2010-06-23 |
fetchmail: Galat: banyak catatan "standar" di berkas pengaturan.
|
|
| 1. |
Checking if %s is really the same node as %s
|
|
| 2010-06-23 |
Memeriksa apakah %s memiliki node yang sama dengan %s
|
|
| 2. |
Yes, their IP addresses match
|
|
| 2010-06-23 |
Ya, alamat IP mereka cocok
|
|
| 3. |
No, their IP addresses don't match
|
|
| 2010-06-23 |
Tidak, alamat IP mereka tidak cocok
|
|
| 4. |
nameserver failure while looking for '%s' during poll of %s: %s
|
|
| 2010-06-23 |
server nama gagal ketika mencari '%s' selama penjajakan %s: %s
|
|
| 5. |
nameserver failure while looking for `%s' during poll of %s.
|
|
| 2010-06-23 |
server nama gagal ketika mencari `%s' selama penjajakan %s.
|
|
| 6. |
could not decode BASE64 challenge
|
|
| 2010-06-23 |
tak dapat mengawasandi tantangan BASE64
|
|
| 7. |
decoded as %s
|
|
| 2010-06-23 |
diawasandi sebagai %s
|
|
| 8. |
kerberos error %s
|
|
| 2010-06-23 |
galat kerberos %s
|
|
| 9. |
krb5_sendauth: %s [server says '%s']
|
|
| 2010-06-23 |
krb5_sendauth: %s [server berkata '%s']
|
|
| 11. |
The following oversized messages were deleted on server %s account %s:
|
|
| 2010-06-23 |
Pesan terlalu besar berikut dihapus di server %s akun %s:
|
|
| 12. |
The following oversized messages remain on server %s account %s:
|
|
| 2010-06-23 |
Pesan terlalu besar berikut tetap di server %s akun %s:
|
|
| 13. |
%d message %d octets long deleted by fetchmail.
%d messages %d octets long deleted by fetchmail.
|
|
| 2010-06-23 |
%d pesan %d oktet yang dihapus oleh fetchmail.
|
|
| 14. |
%d message %d octets long skipped by fetchmail.
%d messages %d octets long skipped by fetchmail.
|
|
| 2010-06-23 |
%d pesan %d oktet yang dilewati oleh fetchmail.
|
|
| 15. |
skipping message %s@%s:%d
|
|
| 2010-06-23 |
melewati pesan %s@%s:%d
|
|
| 16. |
skipping message %s@%s:%d (%d octets)
|
|
| 2010-06-23 |
melewati pesan %s@%s:%d (%d oktet)
|
|
| 18. |
(oversized)
|
|
| 2010-06-23 |
(terlalu besar)
|
|
| 19. |
couldn't fetch headers, message %s@%s:%d (%d octets)
|
|
| 2010-06-23 |
tak dapat mengambil tajuk, pesan %s@%s: %d (%d oktet)
|
|
| 20. |
reading message %s@%s:%d of %d
|
|
| 2010-06-23 |
membaca pesan %s@%s:%d dari %d
|
|
| 21. |
(%d octets)
|
|
| 2010-06-23 |
(%d oktet)
|
|
| 22. |
(%d header octets)
|
|
| 2010-06-23 |
(%d oktet tajuk)
|
|
| 23. |
(%d body octets)
|
|
| 2010-06-23 |
(%d oktet tubuh)
|
|
| 24. |
message %s@%s:%d was not the expected length (%d actual != %d expected)
|
|
| 2010-06-23 |
pesan %s@%s:%d bukan panjang yang diharapkan (%d sebenarnya != %d diharapkan)
|
|
| 25. |
retained
|
|
| 2010-06-23 |
tertahan
|
|
| 26. |
flushed
|
|
| 2010-06-23 |
terhapus
|
|
| 27. |
not flushed
|
|
| 2010-06-23 |
tak dihapus
|
|
| 28. |
fetchlimit %d reached; %d message left on server %s account %s
fetchlimit %d reached; %d messages left on server %s account %s
|
|
| 2010-06-23 |
batas ambil %d tercapai; %d pesan tertinggal di server %s akun %s
|
|
| 29. |
timeout after %d seconds waiting to connect to server %s.
|
|
| 2010-06-23 |
waktu habis setelah %d detik menunggu tersambung ke server %s.
|
|
| 30. |
timeout after %d seconds waiting for server %s.
|
|
| 2010-06-23 |
waktu habis setelah %d detik menunggu server %s.
|
|
| 31. |
timeout after %d seconds waiting for %s.
|
|
| 2010-06-23 |
waktu habis setelah %d detik menunggu %s.
|
|
| 32. |
timeout after %d seconds waiting for listener to respond.
|
|
| 2010-06-23 |
waktu habis setelah %d detik menunggu hingga pendengar merespon.
|
|
| 33. |
timeout after %d seconds.
|
|
| 2010-06-23 |
waktu habis setelah %d detik.
|
|
| 35. |
Fetchmail saw more than %d timeouts while attempting to get mail from %s@%s.
|
|
| 2010-06-23 |
Fetchmail melihat lebih dari %d waktu habis ketika coba mengambil surat dari%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.
|
|
| 2010-06-23 |
Ini dapat berarti bahwa server surat anda macet, atau server SMTP
tersekat, atau berkas kotak surat anda di server telah terkorupsi
oleh galat server. Anda dapat menjalankan `fetchmail -v -v' untuk
mendiagnosis masalah.
|
|
| 37. |
pre-connection command terminated with signal %d
|
|
| 2010-06-23 |
perintah pra-koneksi dimatikan dengan sinyal %d
|
|
| 38. |
pre-connection command failed with status %d
|
|
| 2010-06-23 |
perintah pra-koneksi gagal dengan status %d
|
|
| 39. |
couldn't find HESIOD pobox for %s
|
|
| 2010-06-23 |
tak dapat menemukan pobox HESIOD untuk %s
|
|
| 40. |
Lead server has no name.
|
|
| 2010-06-23 |
Awalan server tak memiliki nama.
|
|
| 41. |
couldn't find canonical DNS name of %s (%s): %s
|
|
| 2010-06-23 |
tak dapat menemukan nama DNS kanonik dari %s (%s): %s
|
|
| 42. |
%s connection to %s failed
|
|
| 2010-06-23 |
koneksi %s ke %s gagal
|
|
| 43. |
SSL connection failed.
|
|
| 2010-06-23 |
koneksi SSL gagal.
|
|
| 44. |
Lock-busy error on %s@%s
|
|
| 2010-06-23 |
Galat kunci-sibuk di %s@%s
|
|
| 45. |
Server busy error on %s@%s
|
|
| 2010-06-23 |
Galat server sibuk di %s@%s
|
|
| 46. |
Authorization failure on %s@%s%s
|
|
| 2010-06-23 |
Kegagalan otorisasi di %s@%s%s
|
|
| 47. |
(previously authorized)
|
|
| 2010-06-23 |
(sebelumnya telah diotorisasi)
|
|
| 48. |
For help, see http://www.fetchmail.info/fetchmail-FAQ.html#R15
|
|
| 2019-09-06 |
Untuk bantuan, lihat http://www.fetchmail.info/fetchmail-FAQ.html#R15
|
|
| 50. |
Fetchmail could not get mail from %s@%s.
|
|
| 2010-06-23 |
Fetchmail tak dapat mengambil surat dari %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.
|
|
| 2010-06-23 |
Usaha untuk mendapatkan otorisasi gagal.
Karena kami telah berhasil mendapatkan otorisasi untuk koneksi ini,
mungkin ini adalah mode gagal lainnya (misalnya server sibuk)
yang fetchmail tak dapat kenali karena server tidak mengirim pesan galat
yang cukup.
|
|
| 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.
|
|
| 2010-06-23 |
Tapi, jika anda TELAH mengubah detail akun anda sejak memulai jurik
fetchmail, anda harus menghentikan jurik, mengganti konfigurasi anda
pada fetchmail, lalu start ulang jurik.
Jurik fetchmail akan melanjutkan berjalan dan coba menyambung pada
tiap siklus. Tak ada pemberitahuan di masa depan yang akan dikirimkan
hingga layanan dipulihkan.
|
|
