Bug#271179: marked as done (Please update the exim4/uucp-README)
Debian Bug Tracking System
owner@bugs.debian.org
Thu, 16 Sep 2004 08:18:18 -0700
Your message dated Thu, 16 Sep 2004 10:47:24 -0400
with message-id <E1C7xXg-0000jV-00@newraff.debian.org>
and subject line Bug#271179: fixed in exim4 4.34-4sarge2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 11 Sep 2004 18:39:11 +0000
>From aba@not.so.argh.org Sat Sep 11 11:39:11 2004
Return-path: <aba@not.so.argh.org>
Received: from mail-out.m-online.net [212.18.0.9]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1C6CmE-0005Zy-00; Sat, 11 Sep 2004 11:39:10 -0700
Received: from mail.m-online.net (svr14.m-online.net [192.168.3.144])
by svr8.m-online.net (Postfix) with ESMTP id 092B2698EF
for <submit@bugs.debian.org>; Sat, 11 Sep 2004 20:38:37 +0200 (CEST)
Received: from sol.so.argh.org (ppp-62-245-210-44.mnet-online.de [62.245.210.44])
by mail.m-online.net (Postfix) with ESMTP id CB145124BFE
for <submit@bugs.debian.org>; Sat, 11 Sep 2004 20:38:36 +0200 (CEST)
Received: from aba by sol.so.argh.org with local (Exim 4.22 #1 (Debian) [+prerelease])
id 1C6Cle-00063p-CA
for <submit@bugs.debian.org>; Sat, 11 Sep 2004 20:38:34 +0200
Date: Sat, 11 Sep 2004 20:38:34 +0200
From: Andreas Barth <aba@not.so.argh.org>
To: submit@bugs.debian.org
Subject: Please update the exim4/uucp-README
Message-ID: <20040911183834.GD17485@mails.so.argh.org>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="xHFwDpU9dbj6ez1V"
Content-Disposition: inline
User-Agent: Mutt/1.3.28i
X-Editor: Vim http://www.vim.org/
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_20,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
--xHFwDpU9dbj6ez1V
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Package: exim4,uucp
Severity: wishlist
Hi,
can you please update the attached README (and Andreas, can you please
take a look from the exim4 point-of-view before, that I didn't do
anything silly).
Thanks,
Andi
--
http://home.arcor.de/andreas-barth/
PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C
--xHFwDpU9dbj6ez1V
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="README.Debian.UUCP"
How to put exim4 and uucp together
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
uucp is a traditional way to execute remote jobs (e.g. spool mails), and as
a lot of old things there are much more than one way to do it. However,
today, the ways to handle it have boiled down to more or less two different
ways.
Our recommendation is to use bsmtp/rsmtp wherever possible, because it
supports all kinds of mail addresses (also the empty ones in bounces), and
is also better from the security point of view.
A. On the sending side:
1. rmail with full adresses
rmail is the oldest way to transfer mail to a remote system. However, today
it is normally required to use adresses with full domains for that (well,
they look like any normal adress for you, and we don't tell about the other
way to not confuse you ;). If you want this, you can use this transport:
rmail:
debug_print = "T: rmail for $pipe_addresses"
driver=pipe
command = "uux -gC - -a$sender_address -r $host\!rmail $pipe_addresses"
return_fail_output
user=uucp
batch_max = 20
However, all recipients are handled via the command line, so you're
discouraged to use it.
2. bsmtp/rsmtp
This is a more efficient way to transfer mails. It works like sending SMTP
via a pipe, but instead of waiting for an answer, the SMTP is just batched;
from this is also the name batched SMTP or short bsmtp.
Furthermore, this way won't fail on adresses like " "@do.main. If you want
this, please use this, if the remote site uses rsmtp (e.g. is exim4):
rsmtp:
debug_print = "T: rsmtp for $pipe_addresses"
driver=pipe
command = /usr/bin/uux - -r -a$sender_address -gC $domain_data!rsmtp
use_bsmtp
return_fail_output
user=uucp
batch_max = 100
and this if it wants bsmtp as the command:
bsmtp:
debug_print = "T: bsmtp for $pipe_addresses"
driver=pipe
command = /usr/bin/uux - -r -a$sender_address -gC $domain_data!bsmtp
use_bsmtp
return_fail_output
user=uucp
batch_max = 100
Of course, these examples can be extended for e.g. compression (but you can
also use ssh for compression, if you want).
3. The router (smarthost)
If you have a leaf system (i.e. all your mail not for your local system
goes to a single remote system), you can just forward all non-local mail
to the remote uucp system. Please adopt the last line to the remote system,
and replace $domain_data by the name of your smarthost in the transport.
smarthost:
debug_print = "R: uucp_router for $local_part@$domain"
driver=accept
require_files = +/usr/bin/uux
domains = !+local_domains
transport = rsmtp
4. The router (non-smarthost)
In this case, you need a router that handles more than one remote
system. You can use this; please adopt the last line. Of course, it's
also possible to send mail via more than one way.
uucpsite:
debug_print = "R: uucp_router for $local_part@$domain"
driver=accept
require_files = +/usr/bin/uux
domains = wildlsearch;/etc/exim4/uucp
transport = rsmtp
The file /etc/exim4/uucp looks like:
*.do.main uucp.name.of.remote.side
B. On the receiving side
1. Allow uucp to use any envelope address
Depending how much you trust your local users, you might use trusted_users
and add uucp to it or use local_sender_retain=true and
local_from_check=false.
2. If you get batched smtp
Allow uucp to execute rsmtp via
commands rmail rnews rsmtp
in your /etc/uucp/sys, and ask the sending site to use rsmtp (and not
bsmtp) as the batched command.
That's it for now. Have fun, and you a flexible, robust and good
transmission way for your mails.
Andreas Barth <aba@not.so.argh.org>, 2004-09-11
--xHFwDpU9dbj6ez1V--
---------------------------------------
Received: (at 271179-close) by bugs.debian.org; 16 Sep 2004 14:55:32 +0000
>From katie@ftp-master.debian.org Thu Sep 16 07:55:24 2004
Return-path: <katie@ftp-master.debian.org>
Received: from newraff.debian.org [208.185.25.31] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1C7xfQ-0004Hg-00; Thu, 16 Sep 2004 07:55:24 -0700
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
id 1C7xXg-0000jV-00; Thu, 16 Sep 2004 10:47:24 -0400
From: Andreas Metzler <ametzler@debian.org>
To: 271179-close@bugs.debian.org
X-Katie: $Revision: 1.51 $
Subject: Bug#271179: fixed in exim4 4.34-4sarge2
Message-Id: <E1C7xXg-0000jV-00@newraff.debian.org>
Sender: Archive Administrator <katie@ftp-master.debian.org>
Date: Thu, 16 Sep 2004 10:47:24 -0400
Delivered-To: 271179-close@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
X-CrossAssassin-Score: 5
Source: exim4
Source-Version: 4.34-4sarge2
We believe that the bug you reported is fixed in the latest version of
exim4, which is due to be installed in the Debian FTP archive:
exim4-base_4.34-4sarge2_i386.deb
to pool/main/e/exim4/exim4-base_4.34-4sarge2_i386.deb
exim4-config_4.34-4sarge2_all.deb
to pool/main/e/exim4/exim4-config_4.34-4sarge2_all.deb
exim4-daemon-heavy_4.34-4sarge2_i386.deb
to pool/main/e/exim4/exim4-daemon-heavy_4.34-4sarge2_i386.deb
exim4-daemon-light_4.34-4sarge2_i386.deb
to pool/main/e/exim4/exim4-daemon-light_4.34-4sarge2_i386.deb
exim4_4.34-4sarge2.diff.gz
to pool/main/e/exim4/exim4_4.34-4sarge2.diff.gz
exim4_4.34-4sarge2.dsc
to pool/main/e/exim4/exim4_4.34-4sarge2.dsc
exim4_4.34-4sarge2_all.deb
to pool/main/e/exim4/exim4_4.34-4sarge2_all.deb
eximon4_4.34-4sarge2_i386.deb
to pool/main/e/exim4/eximon4_4.34-4sarge2_i386.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 271179@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Metzler <ametzler@debian.org> (supplier of updated exim4 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Thu, 16 Sep 2004 13:24:10 +0200
Source: exim4
Binary: eximon4 exim4-daemon-custom exim4-daemon-heavy exim4-base exim4 exim4-daemon-light exim4-config
Architecture: source i386 all
Version: 4.34-4sarge2
Distribution: testing-proposed-updates
Urgency: low
Maintainer: Exim4 Maintainers <pkg-exim4-maintainers@lists.alioth.debian.org>
Changed-By: Andreas Metzler <ametzler@debian.org>
Description:
exim4 - An MTA (Mail Transport Agent)
exim4-base - EXperimental Internal Mailer -- a Mail Transport Agent
exim4-config - Debian configuration for exim4
exim4-daemon-heavy - Exim (v4) with extended features, including exiscan-acl
exim4-daemon-light - Lightweight version of the Exim (v4) MTA
eximon4 - X monitor for the Exim (v4) mail transport agent
Closes: 269501 270578 270681 271179 271864
Changes:
exim4 (4.34-4sarge2) testing-proposed-updates; urgency=low
.
* hr (Croatian) translation of debconf templates by Krunoslav Gernhard
(Closes: #270578)
* remove osirusoft from dnsbl examples. Thanks to Greg Kochanski for
noticing. Add dnsbl disclaimer. (mh) (Closes: #269501)
[tpu rationale: safe change, only changes code in
/usr/share/doc/$package/examples ]
* Do not remove the Debian-exim user in "exim4-config.postrm purge".
Package dependencies are only effective for packages in status installed,
but it is clearly not sane to remove the user until all exim4-packages
are purged. e.g. this can completely break logrotate (Closes: #270681).
[tpu rationale: breaking logrotate is a serious issue, the bug is just not
severity serious yet because it requires a deliberate choice of selecting
some packages for purge and others only for uninstall]
* Update README.Debian.UUCP (thanks, Andreas Barth) (Closes: #271179)
* The hack to fix the infinite debconf loop on woody (#246742) broke
dpkg-reconfigure. Add an additional [ "reconfigure" != "$1" ] condition to
the abort clause. (Closes: #271864)
Files:
1da95ccfc303a98e868ac6c2d9210691 1074 mail important exim4_4.34-4sarge2.dsc
e58a7b4a2d4bc1dcf9b5ab69c4712887 480713 mail important exim4_4.34-4sarge2.diff.gz
0b3f3a80ae1ac33e86d098fe30bacead 786804 mail important exim4-base_4.34-4sarge2_i386.deb
1cbff8f5bb9dca54798440d3f533d2ba 346986 mail important exim4-daemon-light_4.34-4sarge2_i386.deb
74fdfd99fb27bd2452e56386a357f167 70320 mail optional eximon4_4.34-4sarge2_i386.deb
8cab6c76219ceb5da2d631c7658a0f0a 416586 mail optional exim4-daemon-heavy_4.34-4sarge2_i386.deb
0997f1cc3ad4800d833ec77d8ce5a09a 181736 mail important exim4-config_4.34-4sarge2_all.deb
c74933edb1653b980dbc737b7653d805 1208 mail important exim4_4.34-4sarge2_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFBSXyVHTOcZYuNdmMRAg4CAJ0VxJ9kVl1ca4L5cVCO2rv2K7YQQwCfVKhe
t0iaeiIbqEK1b5y0EURdz+Q=
=PBQX
-----END PGP SIGNATURE-----