doc-el commit 1002:b7259d959140 - Complete initial translation o...

freebsd-doc-el at lists.hellug.gr freebsd-doc-el at lists.hellug.gr
Sun Nov 9 06:50:05 EET 2008


changeset: 1002:b7259d959140
user:      sonic at theone.dyndns.org
date:      2008-11-04 13:07 +0200
details:   http://hg.hellug.gr/freebsd/doc-el/?cmd=changeset;node=b7259d959140

description:
	Complete initial translation of section 29.2 (mail chapter)

diffstat:

1 file changed, 79 insertions(+), 71 deletions(-)
el_GR.ISO8859-7/books/handbook/mail/chapter.sgml |  150 +++++++++++-----------

diffs (200 lines):

diff -r 9d2434e1ab68 -r b7259d959140 el_GR.ISO8859-7/books/handbook/mail/chapter.sgml
--- a/el_GR.ISO8859-7/books/handbook/mail/chapter.sgml	Tue Nov 04 10:37:34 2008 +0200
+++ b/el_GR.ISO8859-7/books/handbook/mail/chapter.sgml	Tue Nov 04 13:07:36 2008 +0200
@@ -270,117 +270,125 @@
         <secondary>receiving</secondary>
       </indexterm>
 
-      <para>Receiving mail for your domain is done by the mail host.  It
-	will collect all mail sent to your domain and store it
-	either in <filename>mbox</filename> (the default method for storing mail) or Maildir format, depending
-	on your configuration.
-	Once mail has been stored, it may either be read locally using
-	applications such as &man.mail.1; or
-	<application>mutt</application>, or remotely accessed and
-	collected using protocols such as 
-	<acronym>POP</acronym> or <acronym>IMAP</acronym>.
-	This means that should you only
-	wish to read mail locally, you are not required to install a
-	<acronym>POP</acronym> or <acronym>IMAP</acronym> server.</para>
+      <para>Ï mailhost åßíáé õðåýèõíïò ãéá ôçí ëÞøç mail ðïõ ðñïïñßæåôáé ãéá
+	ôïí ôïìÝá óáò.  Èá óõëëÝîåé üëï ôï mail ðïõ Ýñ÷åôáé ðñïò ôïí ôïìÝá,
+	êáé èá ôï áðïèçêåýóåé åßôå óôï
+	<filename>mbox</filename> (ôçí ðñïåðéëåãìÝíç ìÝèïäï ãéá áðïèÞêåõóç
+	mail) Þ óå ìïñöÞ Maildir, áíÜëïãá ìå ôéò ñõèìßóåéò ðïõ Ý÷åôå êÜíåé.
+	Áðü ôç óôéãìÞ ðïõ ôï mail Ý÷åé áðïèçêåõèåß, ìðïñåßôå åßôå íá ôï
+	äéáâÜóåôå ôïðéêÜ, ÷ñçóéìïðïéþíôáò åöáñìïãÝò üðùò ôï
+	&man.mail.1; Þ ôï <application>mutt</application>, Þ íá ôï äåßôå
+	ìÝóù áðïìáêñõóìÝíçò óýíäåóçò, ÷ñçóéìïðïéþíôáò êÜðïéï ðñùôüêïëëï üðùò
+	ôï <acronym>POP</acronym> Þ ôï <acronym>IMAP</acronym>.
+	Áõôü óçìáßíåé üôé áí åðéèõìåßôå íá äéáâÜæåôå ôï mail óáò ìüíï ôïðéêÜ,
+	äåí ÷ñåéÜæåôáé íá åãêáôáóôÞóåôå åîõðçñåôçôÞ
+	<acronym>POP</acronym> Þ <acronym>IMAP</acronym>.</para>
 
       <sect3 id="pop-and-imap">
-        <title>Accessing remote mailboxes using <acronym>POP</acronym> and <acronym>IMAP</acronym></title>
+        <title>Ðñüóâáóç óå ÁðìáêñõóìÝíåò Èõñßäåò ìÝóù <acronym>POP</acronym> 
+	  êáé <acronym>IMAP</acronym></title>
 
         <indexterm><primary>POP</primary></indexterm>
         <indexterm><primary>IMAP</primary></indexterm>
-	<para>In order to access mailboxes remotely, you are required to
-	  have access to a <acronym>POP</acronym> or <acronym>IMAP</acronym>
-	  server.  These protocols allow users to connect to their mailboxes from
-	  remote locations with ease.  Though both
-	  <acronym>POP</acronym> and <acronym>IMAP</acronym> allow users
-	  to remotely access mailboxes, <acronym>IMAP</acronym> offers
-	  many advantages, some of which are:</para>
+	<para>Ãéá íá Ý÷åôå áðïìáêñõóìÝíç ðñüóâáóç óôéò èõñßäåò ôá÷õäñïìåßïõ,
+	  åßíáé áðáñáßôçôï íá Ý÷åôå ðñüóâáóç óå Ýíá åîõðçñåôçôÞ
+	  <acronym>POP</acronym> Þ <acronym>IMAP</acronym>.  Ôá ðñùôüêïëëá
+	  áõôÜ, åðéôñÝðïõí óôïõò ÷ñÞóôåò íá óõíäÝïíôáé óôéò èõñßäåò ôïõò
+	  áðü áðüáóôáóç, ìå ìåãÜëç åõêïëßá.  Êáé ôá äýï ðñùôüêïëëá
+	  (<acronym>POP</acronym> êáé <acronym>IMAP</acronym>) åðéôñÝðïõí
+	  óôïõò ÷ñÞóôåò áðïìáêñõóìÝíç ðñüóâáóç óôéò èõñßäåò ôïõò, áëëÜ ôï
+	  <acronym>IMAP</acronym> ðñïóöÝñåé áñêåôÜ ðëåïíåêôÞìáôá, ïñéóìÝíá
+	  áðü ôá ïðïßá öáßíïíôáé ðáñáêÜôù:</para>
 
         <itemizedlist>
           <listitem>
-	    <para><acronym>IMAP</acronym> can store messages on a remote
-	      server as well as fetch them.</para>
+	    <para>Ôï <acronym>IMAP</acronym> ìðïñåß íá áðïèçêåýóåé ìçíýìáôá
+	      óå Ýíá áðïìáêñõóìÝíï åîõðçñåôçôÞ, üðùò åðßóçò êáé íá ôá
+	      áíáêôÞóåé.</para>
           </listitem>
 
           <listitem>
-	    <para><acronym>IMAP</acronym> supports concurrent updates.</para>
+	    <para>Ôï <acronym>IMAP</acronym> õðïóôçñßæåé ôáõôü÷ñïíåò
+	      åíçìåñþóåéò.</para>
           </listitem>
 
           <listitem>
-	    <para><acronym>IMAP</acronym> can be extremely useful over
-	      low-speed links as it allows users to fetch the structure
-	      of messages without downloading them; it can also
-	      perform tasks such as searching on the server in
-	      order to minimize data transfer between clients and
-	      servers.</para>
+	    <para>Ôï <acronym>IMAP</acronym> ìðïñåß íá öáíåß åîáéñåôéêÜ
+	      ÷ñÞóéìï óå óõíäÝóåéò ÷áìçëÞò ôá÷ýôçôáò, êáèþò åðéôñÝðåé óôïõò
+	      ÷ñÞóôåò íá êáôåâÜóïõí ôç äïìÞ ôùí ìçíõìÜôùí, ÷ùñßò íá
+	      êáôåâÜóïõí ôï ðåñéå÷üìåíï.  Ìðïñåß åðßóçò íá åêôåëÝóåé
+	      åñãáóßåò üðùò åýñåóç ìçíõìÜôùí áðåõèåßáò óôïí åîõðçñåôçôÞ,
+	      åëá÷éóôïðïéþíôáò ìå áõôü ôïí ôñüðï ôç ìåôáöïñÜ äåäïìÝíùí
+	      ìåôáîý ôùí ðåëáôþí êáé ôùí åîõðçñåôçôþí.</para>
           </listitem>
 
         </itemizedlist>
 
-        <para>In order to install a <acronym>POP</acronym> or
-	  <acronym>IMAP</acronym> server, the following steps should be
-	  performed:</para>
+        <para>Ãéá íá åãêáôáóôÞóåôå Ýíá åîõðçñåôçôÞ <acronym>POP</acronym> Þ
+	  <acronym>IMAP</acronym> èá ðñÝðåé íá áêïëïõèÞóåôå ôá åðüìåíá
+	  âÞìáôá:</para>
 
         <procedure>
 	  <step>
-	    <para>Choose an <acronym>IMAP</acronym> or
-	      <acronym>POP</acronym> server that best suits your needs.
-	      The following <acronym>POP</acronym> and
-	      <acronym>IMAP</acronym> servers are well known and serve
-	      as some good examples:</para>
+	    <para>ÅðéëÝîôå Ýíá åîõðçñåôçôÞ <acronym>IMAP</acronym> Þ
+	      <acronym>POP</acronym> ðïõ íá åîõðçñåôåß ôéò áíÜãêåò óáò.
+	      Ïé ðáñáêÜôù åîõðçñåôçôÝò <acronym>POP</acronym> êáé
+	      <acronym>IMAP</acronym> åßíáé áñêåôÜ äéáäåäïìÝíïé êáé áðïôåëïýí
+	      êáëÜ ðáñáäåßãìáôá:</para>
 
-	      <itemizedlist>
-	        <listitem>
-		  <para><application>qpopper</application>;</para>
-	        </listitem>
+	    <itemizedlist>
+	      <listitem>
+		<para><application>qpopper</application>;</para>
+	      </listitem>
 
-	        <listitem>
-		  <para><application>teapop</application>;</para>
-	        </listitem>
+	      <listitem>
+		<para><application>teapop</application>;</para>
+	      </listitem>
 
-	        <listitem>
-		  <para><application>imap-uw</application>;</para>
-	        </listitem>
+	      <listitem>
+		<para><application>imap-uw</application>;</para>
+	      </listitem>
 
-	        <listitem>
-		  <para><application>courier-imap</application>;</para>
-	        </listitem>
-	      </itemizedlist>
-
+	      <listitem>
+		<para><application>courier-imap</application>;</para>
+	      </listitem>
+	    </itemizedlist>
 	  </step>
 
           <step>
-	    <para>Install the <acronym>POP</acronym> or
-	      <acronym>IMAP</acronym> daemon of your choosing from the
-	      ports
-	      collection.</para>
+	    <para>ÅãêáôáóôÞóôå ôï äáßìïíá <acronym>POP</acronym> Þ
+	      <acronym>IMAP</acronym> ôçò åðéëïãÞò óáò, áðü ôçí ÓõëëïãÞ ôùí
+	      Ports.</para>
 	  </step>
 
 	  <step>
-	    <para>Where required, modify <filename>/etc/inetd.conf</filename>
-	      to load the <acronym>POP</acronym> or
-	      <acronym>IMAP</acronym> server.</para>
+	    <para>Áí ÷ñåéÜæåôáé, ôñïðïðïéÞóôå ôï áñ÷åßï
+	      <filename>/etc/inetd.conf</filename> ãéá íá öïñôþóåôå ôïí
+	      åîõðçñåôçôÞ <acronym>POP</acronym> Þ
+	      <acronym>IMAP</acronym>.</para>
 	  </step>
         </procedure>
 
 	<warning>
-	  <para>It should be noted that both <acronym>POP</acronym> and
-	    <acronym>IMAP</acronym> transmit information, including
-	    username and password credentials in clear-text.  This means
-	    that if you wish to secure the transmission of information
-	    across these protocols, you should consider tunneling
-	    sessions over &man.ssh.1;.  Tunneling sessions is
-	    described in <xref linkend="security-ssh-tunneling">.</para>
+	  <para>Èá ðñÝðåé íá óçìåéþóïõìå üôé ôüóï ôï <acronym>POP</acronym>
+	    üóï êáé ôï <acronym>IMAP</acronym> ìåôáäßäïõí ðëçñïöïñßåò üðùò
+	    ôï üíïìá ÷ñÞóôç êáé ôïí êùäéêü óå ìïñöÞ áðëïý êåéìÝíïõ.  Áõôü
+	    óçìáßíåé üôé áí èÝëåôå íá áóöáëßóåôå ôç ìåôÜäïóç ðëçñïöïñéþí
+	    ìÝóù áõôþí ôùí ðñùôïêüëëùí, èá ðñÝðåé íá ðåñÜóåôå áõôÝò ôéò
+	    óõíäÝóåéò ìÝóù ôïõ &man.ssh.1; (tunneling).  Ç äéáäéêáóéá áõôÞ
+	    ðåñéãñÜöåôáé ìå ëåðôïìÝñåéá óôï
+	    <xref linkend="security-ssh-tunneling">.</para>
         </warning>
       </sect3>
 
       <sect3 id="local">
-        <title>Accessing local mailboxes</title>
+        <title>Ðñüóâáóç óå ÔïðéêÝò Èõñßäåò Ôá÷õäñïìåßïõ</title>
 
-	<para>Mailboxes may be accessed locally by directly utilizing
-	  <acronym>MUA</acronym>s on the server on which the mailbox
-	  resides.  This can be done using applications such as
-	  <application>mutt</application> or &man.mail.1;.
+	<para>Ìðïñåßôå íá Ý÷åôå ôïðéêÞ ðñüóâáóç óôéò èõñßäåò ôá÷õäñïìåßïõ
+	  ÷ñçóéìïðïéþíôáò áðåõèåßáò ôá <acronym>MUA</acronym>s óôïí
+	  åîõðçñåôçôÞ ðïõ åßíáé áðïèçêåõìÝíåò.  Áõôü ìðïñåß íá ãßíåé
+	  ÷ñçóéìïðïéþíôáò åöáñìïãÝò üðùò ôï
+	  <application>mutt</application> Þ ôï &man.mail.1;.
 	</para>
       </sect3>
     </sect2>


More information about the Freebsd-doc-el mailing list