it would be most kind if one or more of you could take a look at the new
sa-exim package I've prepared, thereby adopting it. (But don't upload it yet;
I'd like upstream to acknowledge that he knows that I'm adopting it first.)
It can be found at http://www.kibibyte.se/download/debian/, or downloaded
directly with dget http://www.kibibyte.se/download/debian/sa-exim_4.2.1-3.dsc
From changelog.Debian:
* New maintainer (Closes: #352533).
* Updated package description to explain what SA-Exim can do that
exim-daemon-heavy can't, and vice versa (Closes: #378732).
* Added German debconf template translation (Closes: #399963).
Thanks to Matthias Julius.
* Updated Swedish debconf templates.
* Repackaged against pristine upstream tarball.
* Encourage use of ACL variables in sa-exim.conf. Also exclude ::1
from SA scanning.
There are no changes in executable code at this time.
--
Magnus Holmgren holm...@lysator.liu.se
(No Cc of list mail needed, thanks)
I'll upload this.
Thanks for giving sa-exim some love!
--
·''`. If I can't dance to it, it's not my revolution
: :' : -- Emma Goldman
`. `' Proudly running Debian GNU/Linux (unstable)
`- www.amayita.com www.malapecora.com www.chicasduras.com
--
To UNSUBSCRIBE, email to debian-ment...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Just a sec ... I just remembered that I should upgrade the Standards-Version.
There are also a couple of issues with the greylistclean script. I think I'm
gonna move it from /usr/sbin to /usr/share/sa-exim to avoid having to supply
a manpage for it (it's not supposed to be run manually anyway). Further, the
greylistclean crontab expects spamd to be run as, and therefore the
greylisting tuplets in /var/spool/sa-exim to be owned by, "nobody", who
shouldn't own any files at all. That's of course configurable, but it's not a
recommended default. I don't think sa-exim should put greylisting tuplets and
archived mail under /var/spool, but /var/lib. I don't know if the maintainer
script hacking needed is worth it, though.
--
Magnus Holmgren holm...@lysator.liu.se
(No Cc of list mail needed, thanks)
"Exim is better at being younger, whereas sendmail is better for
Scrabble (50 point bonus for clearing your rack)" -- Dave Evans
Too late, I just uploaded, release often, release soon!
I also emailed you about several issues.
> There are also a couple of issues with the greylistclean script. I
> think I'm gonna move it from /usr/sbin to /usr/share/sa-exim to avoid
> having to supply a manpage for it (it's not supposed to be run
> manually anyway). Further, the greylistclean crontab expects spamd to
> be run as, and therefore the greylisting tuplets in /var/spool/sa-exim
> to be owned by, "nobody", who shouldn't own any files at all. That's
> of course configurable, but it's not a recommended default. I don't
> think sa-exim should put greylisting tuplets and archived mail under
> /var/spool, but /var/lib. I don't know if the maintainer script
> hacking needed is worth it, though.
Just ping me when you have something ready, you can do it privately to
me, and I will upload.
Happy hacking!
Nope, not this time. Is it possible to overwrite files already in the archive,
and if so, how? Do I have to modify the upstream version? Neither the NMG
(chapter 8/9) nor the Developer's Reference (5.4, 5.6) are entirely clear on
this matter (it's probably not a common thing to do), but DR section 5.4
suggests that it's possible. Hovever, inst...@ftp-master.d.o said
> Rejected: md5sum and/or size mismatch on existing copy of
> sa-exim_4.2.1.orig.tar.gz.
> Rejected: can not overwrite existing copy of 'sa-exim_4.2.1.orig.tar.gz'
> already in the archive.
I trust Amaya to have uploaded the .orig.tar.gz matching the .changes entry.