Re: missing nullmailer feature in dma(8)/dmagent
Bezüglich Baptiste Daroussin's Nachricht vom 03.11.2014 13:20 (localtime):
> On Mon, Nov 03, 2014 at 12:52:04PM +0100, Harald Schmalzbauer wrote:
>> Bezüglich Harald Schmalzbauer's Nachricht vom 28.10.2014 17:54
>> (localtime):
>>> Bezüglich Baptiste Daroussin's Nachricht vom 28.10.2014 17:44 (localtime):
>>> …
The NULLCLIENT feature should exactly be what you are looking for, no?
As written in the manpage:
Bypass aliases and local delivery, and instead forward all mails to
the defined `SMARTHOST'. `NULLCLIENT' requires `SMARTHOST' to be
set.
>>> Doh… should try harder getting more sleep ;-)
>>> Sorry for the noise, seems indeed to be exactly what I was looking for.
>>> Can't explain why I missed that, thanks!
>> Ahh, now I can explain ;-)
>> It's the port's version (v0.9_1,1) which lacks this feature.
>> I saw on github that you added this functionality in February 2014, but
>> VERSION wasn't bumped since June 2013.
>> So I guess the port does checkout an outdated version?
>>
>> Thanks,
>>
>> -Harry
>>
> That is it, but I lack motivation to work on it. If one want to take
> maintainership on it and update it, please help yourself
Fair enough. Unfortunately both, time and skills are limited; sufficient
to help myself, though.
For anyone intersted, attached is a diff which does a quick'n'dirty
dma-devel (copy mail/dma to inofficial/dma-devel and apply the patch).
Packaging works, can't tell anything about the condition of the GitHub
code from Sep, 8th 2014 (commit
b1056e4384472dbbedd6b075819abd6154ac0d69) but I don't expect regressions
so will use it and would report if I found problems.
Thanks,
-Harry
diff -ur mail/dma/Makefile inofficial/dma-devel/Makefile
--- mail/dma/Makefile 2014-11-03 14:24:47.430297295 +0100
+++ inofficial/dma-devel/Makefile 2014-11-03 15:12:43.791680603 +0100
@@ -1,22 +1,26 @@
# Created by: Daniel Roethlisberger
# $FreeBSD: head/mail/dma/Makefile 367307 2014-09-04 19:26:24Z antoine $
-PORTNAME= dma
-PORTVERSION= v0.9
-PORTREVISION= 1
-PORTEPOCH= 1
+PORTNAME= dma-devel
+PORTVERSION= v0.10
+#PORTREVISION= 1
+#PORTEPOCH= 1
CATEGORIES= mail ipv6
EXTRACT_SUFX=
+CONFLICTS_INSTALL= dma-*
MAINTAINER= b...@freebsd.org
COMMENT= DragonFly Mail Agent, a small MTA for local/outbound mail
+VALID_CATEGORIES+= inofficial
+
LICENSE= BSD3CLAUSE
USE_OPENSSL= yes
USE_GITHUB= yes
-GH_COMMIT= 2bb8bcb
+GH_PROJECT= dma
+GH_COMMIT= b1056e4
GH_ACCOUNT= corecode
GH_TAGNAME= ${GH_COMMIT}
diff -ur mail/dma/distinfo inofficial/dma-devel/distinfo
--- mail/dma/distinfo 2014-11-03 14:24:47.450316423 +0100
+++ inofficial/dma-devel/distinfo 2014-11-03 14:59:00.438986799 +0100
@@ -1,2 +1,2 @@
-SHA256 (dma-v0.9) = 6c99d5975a2a1072f74b3209ad0a2b89558274de39bd3e03400f94a242b436f2
-SIZE (dma-v0.9) = 45611
+SHA256 (dma-devel-v0.10) = 05348aa91e838d819627a31db82afbdb4edba5fa4a81e90992616e031761eea2
+SIZE (dma-devel-v0.10) = 33985
signature.asc
Description: OpenPGP digital signature
Re: missing nullmailer feature in dma(8)/dmagent
Hi! [ports/mail/dma] > > >> The NULLCLIENT feature should exactly be what you are looking for, no? > > >> As written in the manpage: [...] > > Ahh, now I can explain ;-) > > It's the port's version (v0.9_1,1) which lacks this feature. > > I saw on github that you added this functionality in February 2014, but > > VERSION wasn't bumped since June 2013. > > So I guess the port does checkout an outdated version? > That is it, but I lack motivation to work on it. If one want to take > maintainership on it and update it, please help yourself I'll have a look at it, but it does not build with 9.1-amd64 or 8.4-i386 in poudriere (it does build on 10.0). -- p...@opsec.eu+49 171 3101372 6 years to go ! ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: missing nullmailer feature in dma(8)/dmagent
On Mon, Nov 03, 2014 at 12:52:04PM +0100, Harald Schmalzbauer wrote: > Bezüglich Harald Schmalzbauer's Nachricht vom 28.10.2014 17:54 > (localtime): > > Bezüglich Baptiste Daroussin's Nachricht vom 28.10.2014 17:44 (localtime): > > … > >> The NULLCLIENT feature should exactly be what you are looking for, no? > >> As written in the manpage: > >> > >> > >> Bypass aliases and local delivery, and instead forward all mails to > >> the defined `SMARTHOST'. `NULLCLIENT' requires `SMARTHOST' to be > >> set. > >> > > Doh… should try harder getting more sleep ;-) > > Sorry for the noise, seems indeed to be exactly what I was looking for. > > Can't explain why I missed that, thanks! > > Ahh, now I can explain ;-) > It's the port's version (v0.9_1,1) which lacks this feature. > I saw on github that you added this functionality in February 2014, but > VERSION wasn't bumped since June 2013. > So I guess the port does checkout an outdated version? > > Thanks, > > -Harry > That is it, but I lack motivation to work on it. If one want to take maintainership on it and update it, please help yourself Bapt pgpzz7NIVJTGr.pgp Description: PGP signature
Re: missing nullmailer feature in dma(8)/dmagent
Bezüglich Harald Schmalzbauer's Nachricht vom 28.10.2014 17:54 (localtime): > Bezüglich Baptiste Daroussin's Nachricht vom 28.10.2014 17:44 (localtime): > … >> The NULLCLIENT feature should exactly be what you are looking for, no? >> As written in the manpage: >> >> >> Bypass aliases and local delivery, and instead forward all mails to >> the defined `SMARTHOST'. `NULLCLIENT' requires `SMARTHOST' to be >> set. >> > Doh… should try harder getting more sleep ;-) > Sorry for the noise, seems indeed to be exactly what I was looking for. > Can't explain why I missed that, thanks! Ahh, now I can explain ;-) It's the port's version (v0.9_1,1) which lacks this feature. I saw on github that you added this functionality in February 2014, but VERSION wasn't bumped since June 2013. So I guess the port does checkout an outdated version? Thanks, -Harry signature.asc Description: OpenPGP digital signature
Re: missing nullmailer feature in dma(8)/dmagent
Bezüglich Baptiste Daroussin's Nachricht vom 28.10.2014 17:44 (localtime): … > The NULLCLIENT feature should exactly be what you are looking for, no? > As written in the manpage: > > > Bypass aliases and local delivery, and instead forward all mails to > the defined `SMARTHOST'. `NULLCLIENT' requires `SMARTHOST' to be > set. > Doh… should try harder getting more sleep ;-) Sorry for the noise, seems indeed to be exactly what I was looking for. Can't explain why I missed that, thanks! -Harry signature.asc Description: OpenPGP digital signature
Re: missing nullmailer feature in dma(8)/dmagent
On Tue, Oct 28, 2014 at 11:30:49AM +0100, Harald Schmalzbauer wrote: > Hello, > > I haven't found a way to instruct dma(8) to also forward unqualified > recipients to the relayhost. It always delivers unqualified addresses > locally (if not translated by "aliases"). > > ssmtp(8) provides an option to define a recipient address for all local > recipients who's ID is <1000. > nullmailer(7) does exactly what I want, it doesn't care about the host > part of the recipient address, it just passes it over. > > I'm missing an option for dma(8), which disables local delivery > completely, or like ssmtp, optionally only for ids <1000 resp. not > existing local users. > > Why?: > Maintaining aliases at each machine is too expensive. > My aim is that any operator or daemon of any (human-users-less) machine > can simply drop mails to 'chief' or 'root' or 'monitor'. Then there are > MSAs (I don't call them mailhub, in my world a mailhub stores email, > which often is called a "mailhost"), and only these MSAs care about > recipient aliasing and delivery to mailhub or relayhost. With that setup > I have exactly one (resp. each redundant MSA) place to maintain aliases > and/or other forwarding rules/mailertables etc. Since most smtp-agent > implementations handle multiple A records – although I haven't found one > which evaluates MX records – and I have more than one MSA, I can pretty > reliably guaranteee that any failing machine/device/daemon can drop a > note which won't get lost. If I did aliasing on the mailhub instead at > the interposed MSA, I'd loose poor mans' redundancy… > > According to dma(8) on 11-current, it's the same like in ports > (mail/dma), which I used for testing. > I like the decision to replace sendmail, since almost any time in the > past when I really needed to use the fullfeatured MTA capabilities, I > had to replace base sendmail with a SASL extended version… > But I'd still need to spread nullmailer(7) with current's dma featrues > in 11. > The NULLCLIENT feature should exactly be what you are looking for, no? As written in the manpage: Bypass aliases and local delivery, and instead forward all mails to the defined `SMARTHOST'. `NULLCLIENT' requires `SMARTHOST' to be set. regards, Bapt pgp7xmOusYA0m.pgp Description: PGP signature
missing nullmailer feature in dma(8)/dmagent
Hello, I haven't found a way to instruct dma(8) to also forward unqualified recipients to the relayhost. It always delivers unqualified addresses locally (if not translated by "aliases"). ssmtp(8) provides an option to define a recipient address for all local recipients who's ID is <1000. nullmailer(7) does exactly what I want, it doesn't care about the host part of the recipient address, it just passes it over. I'm missing an option for dma(8), which disables local delivery completely, or like ssmtp, optionally only for ids <1000 resp. not existing local users. Why?: Maintaining aliases at each machine is too expensive. My aim is that any operator or daemon of any (human-users-less) machine can simply drop mails to 'chief' or 'root' or 'monitor'. Then there are MSAs (I don't call them mailhub, in my world a mailhub stores email, which often is called a "mailhost"), and only these MSAs care about recipient aliasing and delivery to mailhub or relayhost. With that setup I have exactly one (resp. each redundant MSA) place to maintain aliases and/or other forwarding rules/mailertables etc. Since most smtp-agent implementations handle multiple A records – although I haven't found one which evaluates MX records – and I have more than one MSA, I can pretty reliably guaranteee that any failing machine/device/daemon can drop a note which won't get lost. If I did aliasing on the mailhub instead at the interposed MSA, I'd loose poor mans' redundancy… According to dma(8) on 11-current, it's the same like in ports (mail/dma), which I used for testing. I like the decision to replace sendmail, since almost any time in the past when I really needed to use the fullfeatured MTA capabilities, I had to replace base sendmail with a SASL extended version… But I'd still need to spread nullmailer(7) with current's dma featrues in 11. Thanks, -Harry signature.asc Description: OpenPGP digital signature
