Ipfstatusmail (Status emails for IPFire)

General questions.
TimF
Posts: 83
Joined: June 10th, 2017, 7:27 pm

Re: Ipfstatusmail (Status emails for IPFire)

Post by TimF » December 14th, 2018, 4:08 pm

Hi Roberto,

It's mainly written in perl. There's a small amount of shell script in generate_signature.sh and some javascript in statusmail.cgi (which is sent to the web browser).

Tim

User avatar
Roberto Peña
Posts: 761
Joined: July 16th, 2014, 3:56 pm
Location: Bilbao (España)
Contact:

Re: Ipfstatusmail (Status emails for IPFire)

Post by Roberto Peña » December 16th, 2018, 8:14 pm

Hello TimF.

Could a module be created so that both the incoming GeoIP and the outgoing GeoIP appear in the report?

Maybe it can not be created since there is no log for it. But maybe you can do some of that magic that you know … >:D

Thanks for everything.
Image
Image

╔════════════════════════════════════════════════╗
Donate to improve IPFire: https://www.ipfire.org/donate
╚════════════════════════════════════════════════╝

TimF
Posts: 83
Joined: June 10th, 2017, 7:27 pm

Re: Ipfstatusmail (Status emails for IPFire)

Post by TimF » December 16th, 2018, 8:47 pm

Most of the information comes from the logs, so I don't know how to do this. I'm sure it's possible, so I'll have a think about it.

steph78630
Posts: 25
Joined: July 21st, 2018, 1:22 pm
Location: Paris (France)
Contact:

Re: Ipfstatusmail (Status emails for IPFire)

Post by steph78630 » December 17th, 2018, 8:39 am

Hi Tim,

a few days ago, I sent you several private messages with infos / requests concerning IPFStatusMail and for which I would need an answer please ...

Image

Image

╔══════════════════════════════════════════╗
║ Donate to improve IPFire : https://www.ipfire.org/donate
╚══════════════════════════════════════════╝

TimF
Posts: 83
Joined: June 10th, 2017, 7:27 pm

Re: Ipfstatusmail (Status emails for IPFire)

Post by TimF » December 17th, 2018, 8:06 pm

Sorry, I'd not looked at my private messages. I've replied now and set up notifications to avoid the problem in the future.

User avatar
Roberto Peña
Posts: 761
Joined: July 16th, 2014, 3:56 pm
Location: Bilbao (España)
Contact:

Re: Ipfstatusmail (Status emails for IPFire)

Post by Roberto Peña » February 15th, 2019, 8:07 am

Hi TimF.

I have a problem with a computer that installed the 126 and updated the 127 and the addon "ipfstatusmail" is not able to send emails.

In IPFire Mail Service, it works correctly and sends test mails, but when I set "ipfstatusmail", it does not send anything. They stay in queue in /var/spools/dma and do not exit.
Mails queued.jpg
I have tried to generate another signature key, without results. I have tried to reinstall the addon, without results.

I have manually deleted the messages in the queue and in the Mail Logs, the following appears:

Code: Select all

IPFire diagnostics
Sección: dma
Fecha: FEB 15, 2019

09:05:07 dma[20fe9.9deb360]:  lost queue file `/var/spool/dma/Q20fe9.9deb360'
09:05:07 dma[20fe9.9deb360]:  remote delivery deferred: write error
09:05:07 dma[2104b.8c01360]:  remote delivery deferred: write error
09:03:45 dma[213e8.9273360]:  lost queue file `/var/spool/dma/Q213e8.9273360'
09:03:45 dma[213e8.9273360]:  remote delivery deferred: write error
09:00:07 dma[213e6.976e360]:  lost queue file `/var/spool/dma/Q213e6.976e360'
09:00:07 dma[213e6.976e360]:  remote delivery deferred: write error
08:58:18 dma[20c41.9014360]:  lost queue file `/var/spool/dma/Q20c41.9014360'
08:58:18 dma[20c41.9014360]:  remote delivery deferred: write error
08:54:36 dma[20fe9.9deb360]:  using SMTP authentication for user info@northsecure.es
08:54:36 dma[20fe9.9deb360]:    Server supports LOGIN authentication
08:54:36 dma[20fe9.9deb360]:    Server supports CRAM-MD5 authentication
08:54:36 dma[20fe9.9deb360]:    Server does not support STARTTLS
08:54:36 dma[20fe9.9deb360]:  Server greeting successfully completed
08:54:36 dma[20fe9.9deb360]:  SSL initialization successful
08:54:36 dma[20fe9.9deb360]:    Server supports LOGIN authentication
08:54:36 dma[20fe9.9deb360]:    Server supports CRAM-MD5 authentication
08:54:36 dma[20fe9.9deb360]:    Server supports STARTTLS
08:54:36 dma[20fe9.9deb360]:  Server greeting successfully completed
08:54:36 dma[20fe9.9deb360]:  trying remote delivery to smtp.strato.com [81.169.145.132] pref 0
08:54:36 dma[20fe9.9deb360]:  connect to smtp.strato.com [2a01:238:20a:202:55f0::1132] failed: Cannot assign requested address
08:54:36 dma[20fe9.9deb360]:  trying remote delivery to smtp.strato.com [2a01:238:20a:202:55f0::1132] pref 0
08:54:36 dma[20fe9.9deb360]:  using smarthost (smtp.strato.com:587)
08:54:36 dma[20fe9.9deb360]:  trying delivery
08:54:30 dma[2104b.8c01360]:  using SMTP authentication for user info@northsecure.es
08:54:30 dma[2104b.8c01360]:    Server supports LOGIN authentication
08:54:30 dma[2104b.8c01360]:    Server supports CRAM-MD5 authentication
08:54:30 dma[2104b.8c01360]:    Server does not support STARTTLS
08:54:30 dma[2104b.8c01360]:  Server greeting successfully completed
08:54:30 dma[2104b.8c01360]:  SSL initialization successful
08:54:29 dma[2104b.8c01360]:    Server supports LOGIN authentication
08:54:29 dma[2104b.8c01360]:    Server supports CRAM-MD5 authentication
08:54:29 dma[2104b.8c01360]:    Server supports STARTTLS
08:54:29 dma[2104b.8c01360]:  Server greeting successfully completed
08:54:29 dma[2104b.8c01360]:  trying remote delivery to smtp.strato.com [81.169.145.132] pref 0
08:54:29 dma[2104b.8c01360]:  connect to smtp.strato.com [2a01:238:20a:202:55f0::1132] failed: Cannot assign requested address
08:54:29 dma[2104b.8c01360]:  trying remote delivery to smtp.strato.com [2a01:238:20a:202:55f0::1132] pref 0
08:54:29 dma[2104b.8c01360]:  using smarthost (smtp.strato.com:587)
08:54:29 dma[2104b.8c01360]:  trying delivery
08:54:29 dma[2104b]:  mail to=<contacto@northsecure.es> queued as 2104b.8c01360
08:54:29 dma[2104b]:  new mail from user=nobody uid=99 envelope_from=<bs@afilegsa.com>
08:53:16 dma[213e8.9273360]:  using SMTP authentication for user info@northsecure.es
08:53:16 dma[213e8.9273360]:    Server supports LOGIN authentication
08:53:16 dma[213e8.9273360]:    Server supports CRAM-MD5 authentication
08:53:16 dma[213e8.9273360]:    Server does not support STARTTLS
08:53:16 dma[213e8.9273360]:  Server greeting successfully completed
08:53:16 dma[213e8.9273360]:  SSL initialization successful
08:53:16 dma[213e8.9273360]:    Server supports LOGIN authentication
08:53:16 dma[213e8.9273360]:    Server supports CRAM-MD5 authentication
08:53:16 dma[213e8.9273360]:    Server supports STARTTLS
08:53:16 dma[213e8.9273360]:  Server greeting successfully completed
08:53:15 dma[213e8.9273360]:  trying remote delivery to smtp.strato.com [81.169.145.132] pref 0
08:53:15 dma[213e8.9273360]:  connect to smtp.strato.com [2a01:238:20a:202:55f0::1132] failed: Cannot assign requested address
08:53:15 dma[213e8.9273360]:  trying remote delivery to smtp.strato.com [2a01:238:20a:202:55f0::1132] pref 0
08:53:15 dma[213e8.9273360]:  using smarthost (smtp.strato.com:587)
08:53:15 dma[213e8.9273360]:  trying delivery
08:53:15 dma[213e8]:  mail to=<contacto@northsecure.es> queued as 213e8.9273360
08:53:15 dma[213e8]:  new mail from user=nobody uid=99 envelope_from=<bs@afilegsa.com>
08:49:32 dma[213e6.976e360]:  using SMTP authentication for user info@northsecure.es
08:49:32 dma[213e6.976e360]:    Server supports LOGIN authentication
08:49:32 dma[213e6.976e360]:    Server supports CRAM-MD5 authentication
08:49:32 dma[213e6.976e360]:    Server does not support STARTTLS
08:49:32 dma[213e6.976e360]:  Server greeting successfully completed
08:49:32 dma[213e6.976e360]:  SSL initialization successful
08:49:32 dma[213e6.976e360]:    Server supports LOGIN authentication
08:49:32 dma[213e6.976e360]:    Server supports CRAM-MD5 authentication
08:49:32 dma[213e6.976e360]:    Server supports STARTTLS
08:49:32 dma[213e6.976e360]:  Server greeting successfully completed
08:49:32 dma[213e6.976e360]:  trying remote delivery to smtp.strato.com [81.169.145.132] pref 0
08:49:32 dma[213e6.976e360]:  connect to smtp.strato.com [2a01:238:20a:202:55f0::1132] failed: Cannot assign requested address
08:49:32 dma[213e6.976e360]:  trying remote delivery to smtp.strato.com [2a01:238:20a:202:55f0::1132] pref 0
08:49:32 dma[213e6.976e360]:  using smarthost (smtp.strato.com:587)
08:49:32 dma[213e6.976e360]:  trying delivery
08:49:32 dma[213e6]:  mail to=<contacto@northsecure.es> queued as 213e6.976e360
08:49:32 dma[213e6]:  new mail from user=nobody uid=99 envelope_from=<bs@afilegsa.com>
08:47:41 dma[20c41.9014360]:  using SMTP authentication for user info@northsecure.es
08:47:41 dma[20c41.9014360]:    Server supports LOGIN authentication
08:47:41 dma[20c41.9014360]:    Server supports CRAM-MD5 authentication
08:47:41 dma[20c41.9014360]:    Server does not support STARTTLS
08:47:41 dma[20c41.9014360]:  Server greeting successfully completed
08:47:40 dma[20c41.9014360]:  SSL initialization successful
08:47:40 dma[20c41.9014360]:    Server supports LOGIN authentication
08:47:40 dma[20c41.9014360]:    Server supports CRAM-MD5 authentication
08:47:40 dma[20c41.9014360]:    Server supports STARTTLS
08:47:40 dma[20c41.9014360]:  Server greeting successfully completed
08:47:40 dma[20c41.9014360]:  trying remote delivery to smtp.strato.com [81.169.145.132] pref 0
08:47:40 dma[20c41.9014360]:  connect to smtp.strato.com [2a01:238:20a:202:55f0::1132] failed: Cannot assign requested address
08:47:40 dma[20c41.9014360]:  trying remote delivery to smtp.strato.com [2a01:238:20a:202:55f0::1132] pref 0
08:47:40 dma[20c41.9014360]:  using smarthost (smtp.strato.com:587)
08:47:40 dma[20c41.9014360]:  trying delivery
08:47:40 dma[20c41]:  mail to=<contacto@northsecure.es> queued as 20c41.9014360
08:47:40 dma[20c41]:  new mail from user=nobody uid=99 envelope_from=<bs@afilegsa.com>
08:42:36 dma[20fe9.9deb360]:  remote delivery deferred: write error
08:36:08 dma[20c1b.8540360]:  delivery successful
08:36:08 dma[20c1b.8540360]:  using SMTP authentication for user info@northsecure.es
08:36:08 dma[20c1b.8540360]:    Server supports LOGIN authentication
08:36:08 dma[20c1b.8540360]:    Server supports CRAM-MD5 authentication
08:36:08 dma[20c1b.8540360]:    Server does not support STARTTLS
08:36:08 dma[20c1b.8540360]:  Server greeting successfully completed
08:36:08 dma[20c1b.8540360]:  SSL initialization successful
08:36:08 dma[20c1b.8540360]:    Server supports LOGIN authentication
08:36:08 dma[20c1b.8540360]:    Server supports CRAM-MD5 authentication
08:36:08 dma[20c1b.8540360]:    Server supports STARTTLS
08:36:08 dma[20c1b.8540360]:  Server greeting successfully completed
08:36:07 dma[20c1b.8540360]:  trying remote delivery to smtp.strato.com [81.169.145.132] pref 0
08:36:07 dma[20c1b.8540360]:  connect to smtp.strato.com [2a01:238:20a:202:55f0::1132] failed: Cannot assign requested address
08:36:07 dma[20c1b.8540360]:  trying remote delivery to smtp.strato.com [2a01:238:20a:202:55f0::1132] pref 0
08:36:07 dma[20c1b.8540360]:  using smarthost (smtp.strato.com:587)
08:36:07 dma[20c1b.8540360]:  trying delivery
08:36:07 dma[20c1b]:  mail to=<contacto@northsecure.es> queued as 20c1b.8540360
08:36:07 dma[20c1b]:  new mail from user=nobody uid=99 envelope_from=<bs@afilegsa.com>
08:32:08 dma[20fe9.9deb360]:  using SMTP authentication for user info@northsecure.es
08:32:08 dma[20fe9.9deb360]:    Server supports LOGIN authentication
08:32:08 dma[20fe9.9deb360]:    Server supports CRAM-MD5 authentication
08:32:08 dma[20fe9.9deb360]:    Server does not support STARTTLS
08:32:08 dma[20fe9.9deb360]:  Server greeting successfully completed
08:32:08 dma[20fe9.9deb360]:  SSL initialization successful
08:32:07 dma[20fe9.9deb360]:    Server supports LOGIN authentication
08:32:07 dma[20fe9.9deb360]:    Server supports CRAM-MD5 authentication
08:32:07 dma[20fe9.9deb360]:    Server supports STARTTLS
08:32:07 dma[20fe9.9deb360]:  Server greeting successfully completed
08:32:07 dma[20fe9.9deb360]:  trying remote delivery to smtp.strato.com [81.169.145.132] pref 0
08:32:07 dma[20fe9.9deb360]:  connect to smtp.strato.com [2a01:238:20a:202:55f0::1132] failed: Cannot assign requested address
08:32:07 dma[20fe9.9deb360]:  trying remote delivery to smtp.strato.com [2a01:238:20a:202:55f0::1132] pref 0
08:32:07 dma[20fe9.9deb360]:  using smarthost (smtp.strato.com:587)
08:32:07 dma[20fe9.9deb360]:  trying delivery
08:27:07 dma[20fe9.9deb360]:  remote delivery deferred: write error
08:21:26 dma[213e6.82b3360]:  lost queue file `/var/spool/dma/Q213e6.82b3360'
08:21:26 dma[213e6.82b3360]:  remote delivery deferred: write error
08:17:47 dma[213e4.96e2360]:  lost queue file `/var/spool/dma/Q213e4.96e2360'
08:17:47 dma[213e4.96e2360]:  remote delivery deferred: write error
08:16:38 dma[20fe9.9deb360]:  using SMTP authentication for user info@northsecure.es
08:16:38 dma[20fe9.9deb360]:    Server supports LOGIN authentication
08:16:38 dma[20fe9.9deb360]:    Server supports CRAM-MD5 authentication
08:16:38 dma[20fe9.9deb360]:    Server does not support STARTTLS
08:16:38 dma[20fe9.9deb360]:  Server greeting successfully completed
08:16:38 dma[20fe9.9deb360]:  SSL initialization successful
08:16:38 dma[20fe9.9deb360]:    Server supports LOGIN authentication
08:16:38 dma[20fe9.9deb360]:    Server supports CRAM-MD5 authentication
08:16:38 dma[20fe9.9deb360]:    Server supports STARTTLS
08:16:38 dma[20fe9.9deb360]:  Server greeting successfully completed
08:16:37 dma[20fe9.9deb360]:  trying remote delivery to smtp.strato.com [81.169.145.132] pref 0
08:16:37 dma[20fe9.9deb360]:  connect to smtp.strato.com [2a01:238:20a:202:55f0::1132] failed: Cannot assign requested address
08:16:37 dma[20fe9.9deb360]:  trying remote delivery to smtp.strato.com [2a01:238:20a:202:55f0::1132] pref 0
08:16:37 dma[20fe9.9deb360]:  using smarthost (smtp.strato.com:587)
08:16:37 dma[20fe9.9deb360]:  trying delivery
08:16:37 dma[20fe9]:  mail to=<contacto@northsecure.es> queued as 20fe9.9deb360
08:16:37 dma[20fe9]:  new mail from user=nobody uid=99 envelope_from=<bs@afilegsa.com>
08:15:48 dma[20fe9.8e30360]:  delivery successful
08:15:47 dma[20fe9.8e30360]:  using SMTP authentication for user info@northsecure.es
08:15:47 dma[20fe9.8e30360]:    Server supports LOGIN authentication
08:15:47 dma[20fe9.8e30360]:    Server supports CRAM-MD5 authentication
08:15:47 dma[20fe9.8e30360]:    Server does not support STARTTLS
08:15:47 dma[20fe9.8e30360]:  Server greeting successfully completed
08:15:47 dma[20fe9.8e30360]:  SSL initialization successful
08:15:47 dma[20fe9.8e30360]:    Server supports LOGIN authentication
08:15:47 dma[20fe9.8e30360]:    Server supports CRAM-MD5 authentication
08:15:47 dma[20fe9.8e30360]:    Server supports STARTTLS
08:15:47 dma[20fe9.8e30360]:  Server greeting successfully completed
08:15:47 dma[20fe9.8e30360]:  trying remote delivery to smtp.strato.com [81.169.145.132] pref 0
08:15:47 dma[20fe9.8e30360]:  connect to smtp.strato.com [2a01:238:20a:202:55f0::1132] failed: Cannot assign requested address
08:15:47 dma[20fe9.8e30360]:  trying remote delivery to smtp.strato.com [2a01:238:20a:202:55f0::1132] pref 0
08:15:47 dma[20fe9.8e30360]:  using smarthost (smtp.strato.com:587)
08:15:47 dma[20fe9.8e30360]:  trying delivery
08:15:47 dma[20fe9]:  mail to=<contacto@northsecure.es> queued as 20fe9.8e30360
08:15:47 dma[20fe9]:  new mail from user=nobody uid=99 envelope_from=<bs@afilegsa.com>
08:15:44 dma[20fe9.94ea360]:  lost queue file `/var/spool/dma/Q20fe9.94ea360'
08:15:44 dma[20fe9.94ea360]:  remote delivery deferred: write error
08:10:52 dma[213e6.82b3360]:  using SMTP authentication for user info@northsecure.es
08:10:52 dma[213e6.82b3360]:    Server supports LOGIN authentication
08:10:52 dma[213e6.82b3360]:    Server supports CRAM-MD5 authentication
08:10:52 dma[213e6.82b3360]:    Server does not support STARTTLS
08:10:52 dma[213e6.82b3360]:  Server greeting successfully completed
08:10:52 dma[213e6.82b3360]:  SSL initialization successful
08:10:52 dma[213e6.82b3360]:    Server supports LOGIN authentication
08:10:52 dma[213e6.82b3360]:    Server supports CRAM-MD5 authentication
08:10:52 dma[213e6.82b3360]:    Server supports STARTTLS
08:10:52 dma[213e6.82b3360]:  Server greeting successfully completed
08:10:51 dma[213e6.82b3360]:  trying remote delivery to smtp.strato.com [81.169.145.132] pref 0
08:10:51 dma[213e6.82b3360]:  connect to smtp.strato.com [2a01:238:20a:202:55f0::1132] failed: Cannot assign requested address
08:10:51 dma[213e6.82b3360]:  trying remote delivery to smtp.strato.com [2a01:238:20a:202:55f0::1132] pref 0
08:10:51 dma[213e6.82b3360]:  using smarthost (smtp.strato.com:587)
08:10:51 dma[213e6.82b3360]:  trying delivery
08:10:51 dma[213e6]:  mail to=<contacto@northsecure.es> queued as 213e6.82b3360
08:10:51 dma[213e6]:  new mail from user=nobody uid=99 envelope_from=<bs@afilegsa.es>
08:08:26 dma[213e6.824a360]:  delivery successful
08:08:26 dma[213e6.824a360]:  using SMTP authentication for user info@northsecure.es
08:08:26 dma[213e6.824a360]:    Server supports LOGIN authentication
08:08:26 dma[213e6.824a360]:    Server supports CRAM-MD5 authentication
08:08:26 dma[213e6.824a360]:    Server does not support STARTTLS
08:08:26 dma[213e6.824a360]:  Server greeting successfully completed
08:08:26 dma[213e6.824a360]:  SSL initialization successful
08:08:25 dma[213e6.824a360]:    Server supports LOGIN authentication
08:08:25 dma[213e6.824a360]:    Server supports CRAM-MD5 authentication
08:08:25 dma[213e6.824a360]:    Server supports STARTTLS
08:08:25 dma[213e6.824a360]:  Server greeting successfully completed
08:08:25 dma[213e6.824a360]:  trying remote delivery to smtp.strato.com [81.169.145.132] pref 0
08:08:25 dma[213e6.824a360]:  connect to smtp.strato.com [2a01:238:20a:202:55f0::1132] failed: Cannot assign requested address
08:08:25 dma[213e6.824a360]:  trying remote delivery to smtp.strato.com [2a01:238:20a:202:55f0::1132] pref 0
08:08:25 dma[213e6.824a360]:  using smarthost (smtp.strato.com:587)
08:08:25 dma[213e6.824a360]:  trying delivery
08:08:25 dma[213e6]:  mail to=<contacto@northsecure.es> queued as 213e6.824a360
08:08:25 dma[213e6]:  new mail from user=nobody uid=99 envelope_from=<bs@afilegsa.es>
08:07:20 dma[213e4.96e2360]:  using SMTP authentication for user info@northsecure.es
08:07:20 dma[213e4.96e2360]:    Server supports LOGIN authentication
08:07:20 dma[213e4.96e2360]:    Server supports CRAM-MD5 authentication
08:07:20 dma[213e4.96e2360]:    Server does not support STARTTLS
08:07:20 dma[213e4.96e2360]:  Server greeting successfully completed
08:07:20 dma[213e4.96e2360]:  SSL initialization successful
08:07:19 dma[213e4.96e2360]:    Server supports LOGIN authentication
08:07:19 dma[213e4.96e2360]:    Server supports CRAM-MD5 authentication
08:07:19 dma[213e4.96e2360]:    Server supports STARTTLS
08:07:19 dma[213e4.96e2360]:  Server greeting successfully completed
08:07:19 dma[213e4.96e2360]:  trying remote delivery to smtp.strato.com [81.169.145.132] pref 0
08:07:19 dma[213e4.96e2360]:  connect to smtp.strato.com [2a01:238:20a:202:55f0::1132] failed: Cannot assign requested address
08:07:19 dma[213e4.96e2360]:  trying remote delivery to smtp.strato.com [2a01:238:20a:202:55f0::1132] pref 0
08:07:19 dma[213e4.96e2360]:  using smarthost (smtp.strato.com:587)
08:07:19 dma[213e4.96e2360]:  trying delivery
08:07:19 dma[213e4]:  mail to=<contacto@northsecure.es> queued as 213e4.96e2360
08:07:19 dma[213e4]:  new mail from user=nobody uid=99 envelope_from=<bs@afilegsa.es>
08:05:18 dma[20fe9.94ea360]:  using SMTP authentication for user info@northsecure.es
08:05:18 dma[20fe9.94ea360]:    Server supports LOGIN authentication
08:05:18 dma[20fe9.94ea360]:    Server supports CRAM-MD5 authentication
08:05:18 dma[20fe9.94ea360]:    Server does not support STARTTLS
08:05:18 dma[20fe9.94ea360]:  Server greeting successfully completed
08:05:18 dma[20fe9.94ea360]:  SSL initialization successful
08:05:18 dma[20fe9.94ea360]:    Server supports LOGIN authentication
08:05:18 dma[20fe9.94ea360]:    Server supports CRAM-MD5 authentication
08:05:18 dma[20fe9.94ea360]:    Server supports STARTTLS
08:05:18 dma[20fe9.94ea360]:  Server greeting successfully completed
08:05:18 dma[20fe9.94ea360]:  trying remote delivery to smtp.strato.com [81.169.145.132] pref 0
08:05:18 dma[20fe9.94ea360]:  connect to smtp.strato.com [2a01:238:20a:202:55f0::1132] failed: Cannot assign requested address
08:05:18 dma[20fe9.94ea360]:  trying remote delivery to smtp.strato.com [2a01:238:20a:202:55f0::1132] pref 0
08:05:17 dma[20fe9.94ea360]:  using smarthost (smtp.strato.com:587)
08:05:17 dma[20fe9.94ea360]:  trying delivery
08:05:17 dma[20fe9]:  mail to=<contacto@northsecure.es> queued as 20fe9.94ea360
08:05:17 dma[20fe9]:  new mail from user=nobody uid=99 envelope_from=<bs@afilegsa.es>
08:00:01 dma[213e2.9174360]:  delivery successful
08:00:00 dma[213e2.9174360]:  using SMTP authentication for user info@northsecure.es
08:00:00 dma[213e2.9174360]:    Server supports LOGIN authentication
08:00:00 dma[213e2.9174360]:    Server supports CRAM-MD5 authentication
08:00:00 dma[213e2.9174360]:    Server does not support STARTTLS
08:00:00 dma[213e2.9174360]:  Server greeting successfully completed
08:00:00 dma[213e2.9174360]:  SSL initialization successful
08:00:00 dma[213e2.9174360]:    Server supports LOGIN authentication
08:00:00 dma[213e2.9174360]:    Server supports CRAM-MD5 authentication
08:00:00 dma[213e2.9174360]:    Server supports STARTTLS
08:00:00 dma[213e2.9174360]:  Server greeting successfully completed
08:00:00 dma[213e2.9174360]:  trying remote delivery to smtp.strato.com [81.169.145.132] pref 0
08:00:00 dma[213e2.9174360]:  connect to smtp.strato.com [2a01:238:20a:202:55f0::1132] failed: Cannot assign requested address
08:00:00 dma[213e2.9174360]:  trying remote delivery to smtp.strato.com [2a01:238:20a:202:55f0::1132] pref 0
08:00:00 dma[213e2.9174360]:  using smarthost (smtp.strato.com:587)
08:00:00 dma[213e2.9174360]:  trying delivery
08:00:00 dma[213e2]:  mail to=<contacto@northsecure.es> queued as 213e2.9174360
08:00:00 dma[213e2]:  new mail from user=nobody uid=99 envelope_from=<bs@afilegsa.es>
What could I look?.

Thanks.
Image
Image

╔════════════════════════════════════════════════╗
Donate to improve IPFire: https://www.ipfire.org/donate
╚════════════════════════════════════════════════╝

TimF
Posts: 83
Joined: June 10th, 2017, 7:27 pm

Re: Ipfstatusmail (Status emails for IPFire)

Post by TimF » February 16th, 2019, 6:20 pm

Hi Roberto,

Unfortunately I've temporarily lost my internet access at home, so I can't upgrade to core 127 and test it myself. There should be no reason why the test mail works and the Status mail doesn't, since they both send mail the same way. When I get my internet access back I'll update to core 127 and give it a try.

The only thing I can see from the log is that dma attempts to connect to 81.169.145.132 and then suddenly switches to using an IP6 address. Since IPFire 2 doesn't support IP6 this fails. I have no idea why it should suddenly switch to IP6.

Tim

User avatar
Roberto Peña
Posts: 761
Joined: July 16th, 2014, 3:56 pm
Location: Bilbao (España)
Contact:

Re: Ipfstatusmail (Status emails for IPFire)

Post by Roberto Peña » February 16th, 2019, 8:57 pm

Hello TimF.

Maybe it's a problem with DragonFly, unbound, DNS filtering, DNS resolution or SMTP User validation, since configuring "Mail Service" with Gmail seems to work. The funny thing is that with the Strato account (https://www.strato.es/) it does not work, in other IPFire it works. Black lists? Public IP cached. It's curious.

I have another IPFire that does not send any mail test of "Service Mail" no matter how I configure it, I do not know what to think.

Black lists ?.

I have machines updated to 127 (all others) that work ok.

Thank you for your patience.
Image
Image

╔════════════════════════════════════════════════╗
Donate to improve IPFire: https://www.ipfire.org/donate
╚════════════════════════════════════════════════╝

User avatar
Roberto Peña
Posts: 761
Joined: July 16th, 2014, 3:56 pm
Location: Bilbao (España)
Contact:

Re: Ipfstatusmail (Status emails for IPFire)

Post by Roberto Peña » February 20th, 2019, 7:52 am

SOLVED. It´s works!!!.

The problem was the Unbound issues:

viewtopic.php?f=27&t=22332

Once solved, everything started to work correctly.

Grettings
Image
Image

╔════════════════════════════════════════════════╗
Donate to improve IPFire: https://www.ipfire.org/donate
╚════════════════════════════════════════════════╝

User avatar
Roberto Peña
Posts: 761
Joined: July 16th, 2014, 3:56 pm
Location: Bilbao (España)
Contact:

Re: Ipfstatusmail (Status emails for IPFire)

Post by Roberto Peña » April 8th, 2019, 10:00 am

Hi TimF.

I have bad news...

In one IPFire with 128 core version an your addon update (I have seen that you have recently updated the Addon) I see these errors and do not send anything: (this errors appear in /var/log/httpd/error_log)

Code: Select all

[Mon Apr  8 11:55:00 2019] statusmail.cgi: "my" variable $button masks earlier declaration in same scope at /srv/web/ipfire/cgi-bin/statusmail.cgi line 677.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 177.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 194.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value $cgiparams{"KEY_ACTION"} in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 200.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 215.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 219.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 226.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 230.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 234.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 238.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 245.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 245.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value $cgiparams{"CONTACT_ACTION"} in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 268.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value $cgiparams{"CONTACT_ACTION"} in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 272.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value $cgiparams{"CONTACT_ACTION"} in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 279.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 286.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 290.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value $schedule{"period-unit"} in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 903.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value $schedule{"period-unit"} in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 904.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value $schedule{"period-unit"} in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 905.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value $schedule{"period-unit"} in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 906.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value in concatenation (.) or string at /srv/web/ipfire/cgi-bin/statusmail.cgi line 908.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value in concatenation (.) or string at /srv/web/ipfire/cgi-bin/statusmail.cgi line 908.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value within %schedule in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 1074.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value within %schedule in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 1074.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value within %schedule in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 1074.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value within %schedule in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 1074.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value within %schedule in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 1074.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value within %schedule in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 1074.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value within %schedule in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 1074.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value within %schedule in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 1074.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value within %schedule in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 1074.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value within %schedule in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 1074.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value within %schedule in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 1074.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value within %schedule in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 1074.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value within %schedule in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 1074.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value within %schedule in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 1074.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value within %schedule in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 1074.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value within %schedule in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 1074.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value within %schedule in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 1074.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value within %schedule in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 1074.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value within %schedule in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 1074.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value within %schedule in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 1074.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value within %schedule in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 1074.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value within %schedule in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 1074.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value within %schedule in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 1074.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value within %schedule in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 1074.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value within %schedule in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 1074.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value within %schedule in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 1074.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value within %schedule in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 1074.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value within %schedule in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 1074.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value within %schedule in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 1074.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value within %schedule in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 1074.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value within %schedule in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 1074.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value within %schedule in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 1074.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value within %schedule in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 1074.
[Mon Apr  8 11:55:02 2019] statusmail.cgi: Use of uninitialized value in string eq at /srv/web/ipfire/cgi-bin/statusmail.cgi line 1169.
What could be the problem?.

Thanks for all.

Regards.
Image
Image

╔════════════════════════════════════════════════╗
Donate to improve IPFire: https://www.ipfire.org/donate
╚════════════════════════════════════════════════╝

TimF
Posts: 83
Joined: June 10th, 2017, 7:27 pm

Re: Ipfstatusmail (Status emails for IPFire)

Post by TimF » April 8th, 2019, 8:33 pm

Hi Roberto,

At first glance, it doesn't seem to be picking up the settings and language files properly.

Can you run check that the language files are in /var/ipfire/addon-lang and run update-lang-cache from the command line.

Can you check that there are contact-settings and schedule-settings files in /var/ipfire/statusmail. The contents should be something like:

Code: Select all

$schedules = {
               'Error check report' => {
                                         'enable_system-status-services' => 'off',
                                         'enable_graph-memory-swap' => 'off',
                                         'enable_system-status-processes' => 'off',
                                         'enable_network-firewall-ipaddresses' => 'on',
                                         'enable_services-urlfilter-destination' => 'off',
                                         ...
                                       },
                'Another name' => {
                                         ...
                                       }
                  };
(lots of lines omitted)

The contact-settings file should have the same general form.

Tim

User avatar
Roberto Peña
Posts: 761
Joined: July 16th, 2014, 3:56 pm
Location: Bilbao (España)
Contact:

Re: Ipfstatusmail (Status emails for IPFire)

Post by Roberto Peña » April 9th, 2019, 5:49 am

Hi TimF.

Thanks for your quick response. The problem of not sending emails, does not seem to be your problem. Apparently, Strato, considers certain mails as "spam".

The funny thing is that with the same configuration, others IPFire send emails perfectly.

Greetings and thanks for everything.

P.D .: I will look at what you tell me to try to solve these errors that I have mentioned.

Update: I have run "update-lang-cache" and the file you mentioned seems to be correct.
Image
Image

╔════════════════════════════════════════════════╗
Donate to improve IPFire: https://www.ipfire.org/donate
╚════════════════════════════════════════════════╝

User avatar
Roberto Peña
Posts: 761
Joined: July 16th, 2014, 3:56 pm
Location: Bilbao (España)
Contact:

Re: Ipfstatusmail (Status emails for IPFire)

Post by Roberto Peña » April 27th, 2019, 12:59 pm

Hello TimF, how are you ?.

I see that you have made a series of improvements and you have not said anything. They are interesting.

Perhaps, with the Core 131 version you have some problem with the IDS section, since you have changed to Suricata as you well know. I mention the changes:

The route where the Log is located is: "/var/log/suricata/fast.log"

And the structure is like the attachment:
fast.log
(438.17 KiB) Downloaded 32 times
Thanks for your dedication.

Greetings.
Image
Image

╔════════════════════════════════════════════════╗
Donate to improve IPFire: https://www.ipfire.org/donate
╚════════════════════════════════════════════════╝

TimF
Posts: 83
Joined: June 10th, 2017, 7:27 pm

Re: Ipfstatusmail (Status emails for IPFire)

Post by TimF » April 27th, 2019, 2:46 pm

HI Roberto,

I've submitted a series of patches to add statusmail to the IPFire core; the changes I've made in github are in preparation for this. Inevitable there are changes to be made between an external add-on, which has to be independent of the system, and one which is properly integrated. So the new code in github is to handle this (and to move files about as required when the installer is run). The developers need to review the code before including it (and there's quite a lot of code). Once I know what has to be changed I can then finalise the changes in github, which will mean anyone who's got the old version installed can run the github installer which will ensure that settings etc are kept when it's finally in the mainline.

In the meantime, I've uploaded the Suricata plugin. If you run:

Code: Select all

wget https://github.com/timfprogs/ipfstatusmail/raw/next/plugins/services_intrusion_prevention_system.pm
and then put the plugin in the correct directory (/var/ipfire/statusmail/plugins or /usr/lib/statusmail/plugins), you'll get an additional entry in the WUI.

User avatar
Roberto Peña
Posts: 761
Joined: July 16th, 2014, 3:56 pm
Location: Bilbao (España)
Contact:

Re: Ipfstatusmail (Status emails for IPFire)

Post by Roberto Peña » May 16th, 2019, 1:21 pm

Hi TimF.

I have reinstalled using the NEXT and the plugin for Suricata appears correctly, but when I launch the task to make the report, nothing related to the IDS / IPS appears.

I have executed the following and this error appears:

Code: Select all

[root@bs statusmail]# ./test_plugin.pl /usr/lib/statusmail/plugins/services_intrusion_prevention_system.pm
Plugin /usr/lib/statusmail/plugins/services_intrusion_prevention_system.pm has no option name specified
No valid plugins found
[root@bs statusmail]#
Regards.
Image
Image

╔════════════════════════════════════════════════╗
Donate to improve IPFire: https://www.ipfire.org/donate
╚════════════════════════════════════════════════╝

Post Reply