From: Rob Brewer <ipfire-devel@grantura.co.uk>
To: development@lists.ipfire.org
Subject: Re: sendEmail-1.56-1
Date: Sun, 10 Feb 2019 17:49:51 +0000 [thread overview]
Message-ID: <q3po7v$3dd$1@tuscan3.grantura.co.uk> (raw)
In-Reply-To: <D8912B44-1081-41E7-A77C-68C313DB5362@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1824 bytes --]
Hi Michael
Michael Tremer wrote:
> No. Please change the patch accordingly and submit again.
>
Updated.....
--- lfs/sendEmail 2019-02-03 09:52:33.517456033 +0000
+++ lfs/sendEmail.2 2019-02-10 16:21:30.662927661 +0000
@@ -63,8 +63,8 @@
@$(PREBUILD)
@rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar zxf $(DIR_DL)/$(DL_FILE)
cd $(DIR_APP) && cp -pvf sendEmail /usr/local/bin
- chown root.nobody /usr/local/bin/sendEmail
- chmod 04750 /usr/local/bin/sendEmail
+ chown root.root /usr/local/bin/sendEmail
+ chmod 755 /usr/local/bin/sendEmail
@rm -rf $(DIR_APP)
@$(POSTBUILD)
> Regarding the IPCop add-on: Please do not use sendEmail. It does not do
> the job.
>
Unfortunately the logsend addon was built around sendEmail with lots of
bash scripts and since as it is available as an IPFire addon it would seem
to make sense to use it to minimize to the changes required.
> We have dma, a small mail agent that can be configured over the web-ui. It
> does proper bounce handling and will try to send the email again in case
> the first attempt failed. sendEmail doesn’t do that.
I did look at dma and did consider it as an alternative mta but I could not find
any documentation on how to interface with IPFire's dma for sending emails. I will
look again if someone can point me to something about dma I have overlooked.
I relay sendEmail through my own mail server (sendmail) so I don't have bounce
problems and would expect users who don't have their own mta to use their ISPs
server to handle any bounce problems.
I can say that I haven't had any problems with sendEmail sending logs to Dshield
over the last 14 years even though the data has increased ~50 times since then.
Rob
next prev parent reply other threads:[~2019-02-10 17:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-02 18:47 sendEmail-1.56-1 Bob Brewer
2019-02-06 11:13 ` sendEmail-1.56-1 Michael Tremer
2019-02-06 21:35 ` sendEmail-1.56-1 Rob Brewer
2019-02-08 12:29 ` sendEmail-1.56-1 Michael Tremer
2019-02-10 17:49 ` Rob Brewer [this message]
2019-02-10 22:00 ` sendEmail-1.56-1 Rob Brewer
2019-02-13 17:25 ` sendEmail-1.56-1 Michael Tremer
2019-02-13 22:49 ` [PATCH] sendEmail Rob Brewer
2019-02-14 11:06 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='q3po7v$3dd$1@tuscan3.grantura.co.uk' \
--to=ipfire-devel@grantura.co.uk \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox