Hi, I sent a translation request for my new package, dma (ITP #511410) - http://mentors.debian.net/debian/pool/main/d/dma/dma_0.0.2009.02.11-1.dsc the DragonFly Mail Agent - to the i18n list, and Simon Paillard and Christian Perrier kindly suggested that a proofreading would be a good first step :) So, here it is - please find attached to this message some control files for the dma package: - control - README.Debian (a somewhat lengthy one, since the Debian package differs somewhat from DragonFlyBSD's dma in its operation) - templates Thanks in advance for any advice you may offer on the wording! G'luck, Peter PS. Please CC me on replies, since I'm not subscribed to this list. -- Peter Pentchev roam@ringlet.net roam@space.bg roam@FreeBSD.org PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 If this sentence were in Chinese, it would say something else.
Source: dma
Section: mail
Priority: optional
Maintainer: Peter Pentchev <roam@ringlet.net>
Build-Depends: debhelper (>= 7.0.50), byacc, flex, hardening-wrapper, liblockfile-dev, libssl-dev, pmake, quilt, po-debconf
Standards-Version: 3.8.1
Homepage: http://devel.ringlet.net/mail/dma/
Vcs-Svn: http://svn.ringlet.net/svn/ringlet/mail/dma/trunk/dma-pkg/debian/
Vcs-Browser: http://svn.ringlet.net/cgi-bin/viewvc/viewvc.cgi/ringlet/mail/dma/trunk/dma-pkg/debian/
Package: dma
Architecture: any
Depends: liblockfile1 (>> 1.01), ${shlibs:Depends}, ${misc:Depends}
Provides: mail-transport-agent
Conflicts: mail-transport-agent
Replaces: mail-transport-agent
Recommends: safecat
Description: the DragonFly Mail Agent, a lightweight MTA
The DragonFly Mail Agent is a small Mail Transport Agent (MTA),
designed for home and office use. It accepts mails from locally
installed Mail User Agents (MUA) and delivers the mails either locally
or to a remote destination. Remote delivery includes several features
like TLS/SSL support and SMTP authentication.
.
dma is not intended as a replacement for real, big MTAs like Sendmail,
Postfix, or Exim. Consequently, dma does not listen on port 25 for
incoming connections.
dma for Debian -------------- 1. Deferred delivery by default The dma mail transfer agent may operate in two modes - immediate and deferred. In both cases, a new dma process is spawned for the delivery of each outgoing message, and this process lives on until the message is either successfully delivered or it times out after five days. In immediate delivery mode, the new dma process is spawned as soon as the message is submitted to the queue. In deferred mode, which is the default for the Debian package, the message is left in the queue and will only be processed when dma is invoked separately with the "-q" command-line option. I personally prefer this delivery mode - even though there may be slight delays, the queue must still be processed periodically anyway (if an immediate delivery is deferred, the message is still left on the queue), so there's no harm done in always doing it that way. Hence, the Debian package of dma installs a cron job that attempts to flush the queue every five minutes. Note that this does NOT mean that message delivery will be attempted every five minutes! Once the queue is flushed, a separate dma instance is spawned for each still-unhandled message, and it takes care of reasonable exponential back-off in case of delivery problems. 2. Smarthost operation by default - needs to be configured! For the present, the dma mail transfer agent does not really handle direct MX lookups very well. It is highly recommended that you only use it with a smarthost configured via the SMARTHOST directive in the /etc/dma/dma.conf file. Note that the default SMARTHOST value of "mail.example.com" is virtually guaranteed not to work, as per the special status of the "example.com" domain according to RFC 2606 :) 3. Double-bounce handling By default, the dma mail transfer agent does not really handle double bounces - it aborts the delivery with a critical syslog message. This, combined with the Debian package's default of "flush the queue every five minutes", may pose something of a strain on the mail server :) Thus, the Debian version of dma adds a new feature - you may specify an external program to handle double bounces with the DBOUNCEPROG directive in the /etc/dma/dma.conf file. Also included is a sample program, dbounce-simple-safecat, which uses the safecat utility to copy the bounce message into a Maildir-structured storage, /var/spool/mail/dma-bounces by default. Its functionality will be extended in the future to allow more configuration and to possibly parse the message to make it actually mailbox-compatible - for the present, the copied file still has the dma internal format, which is plain text, but is not really a mailbox :) -- Peter Pentchev <roam@ringlet.net> Tue, 10 Mar 2009 12:04:48 +0200
Template: shared/mailname Type: string _Description: Mailname of your system: This is the fully-qualified host name of the computer running dma. It defaults to the output of "hostname --fqdn". Template: dma/relayhost Type: string _Description: Smarthost: This is the name of a remote server to which to send each message. If it is left blank, dma will try to deliver all messages by itself; however, for the present it cannot really handle MX record lookups. The default is a host named "mail" in the same domain as your computer. Template: dma/dbounceprog Type: string _Description: A program to handle double-bounces: This is the name of a program that dma will invoke when a bounced message bounces in its own right. Leave this blank if you like dma's default behavior of simply aborting the delivery, or specify the name or full path to a program that will process the double-bounce message.
Attachment:
pgpaGwP44ShaK.pgp
Description: PGP signature