Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Problem With Dynamix E-mail configuration

Featured Replies

There exists a problem with the way that the e-mail notification program is configured in Dynamix in version 6B12.  I have two servers running here.  One is on ver5.0.6 and the other one is on ver 6b12.  The email notification works for version 5.0.6 and it does not work for version 6b12.  I have included screen snapshots of both configurations for reference. 

Version 6b12 returns the following error after the test on the 'STMP Setting' page: :

 

554 5.1.8 - Domain of sender address does not exist [R0107008

 

WeeboTech suggested using the following command to troubleshoot the problem.

 

echo -e "Subject: Test Mail\n\n"  | sendmail -d [email protected]

 

The result of this command are:

 

root@Rose:~# echo -e "Subject: Test Mail\n\n"  | sendmail -d [email protected]
[<-] 220 mail-server-domain ESMTP mail service ready
[->] EHLO Rose
[<-] 250 8BITMIME
[->] AUTH LOGIN
[<-] 334 **********
[->] ************************
[<-] 334 **************
[<-] 235 2.0.0 Authed. Go on.
[->] MAIL FROM:<root@Rose>
[<-] 554 5.1.8 - Domain of sender address does not exist [R0107008]
sendmail: 554 5.1.8 - Domain of sender address does not exist [R0107008]
root@Rose:~#

 

Notice the "MAIL FROM" is "<root@Rose>"

 

From the research that I have done it appears that many e-mail providers have rules (to prevent their server from being used by E-mail spammers) and one of these rules is that the address of the sender must have a valid domain name and "Rose" is not a valid domain name!

 

I believe the issue could be addressed by changing the parameters that are being passed to the e-mail program to specify sending E-mail address as the field in the "MAIL FROM" parameter.

Email_Setup_5.0.6.JPG.82810d1980250e6e9fdd8033f25a2077.JPG

Email-smtp-error.JPG.b78d85f001272485fe7471782f5ba85b.JPG

I'm having the same problem with Comcast.  All fields in the Notification UI are filled in properly.  My install is a plain vanilla beta12 install with only unMenu installed on top of it (and the only package installed via unMenu is Screen).

  • 2 weeks later...

The email notification works for version 5.0.6 and it does not work for version 6b12.  I have included screen snapshots of both configurations for reference.

Changes have been made to the v6 email implementation, and become available in an upcoming version. These should address the earlier observations of mails not being sent.

 

  • Author

Changes have been made to the v6 email implementation, and become available in an upcoming version. These should address the earlier observations of mails not being sent.

 

Great News.  This is perhaps a minor issue in the development cycle but it would be a much larger issue if not corrected before ver 6.0.1 final  was released. 

Same type of problem for me (RCPT TO:<[email protected]> (550 Sender verify failed)), and my email notification works for version 5x and 6b5/6.

 

For a quick fix, I have modify /etc/ssmtp/ssmtp.conf to add the following lines :

rewriteDomain=myRealDomainForEmail.com
hostname=localhost

Same type of problem for me (RCPT TO:<[email protected]> (550 Sender verify failed)), and my email notification works for version 5x and 6b5/6.

 

For a quick fix, I have modify /etc/ssmtp/ssmtp.conf to add the following lines :

rewriteDomain=myRealDomainForEmail.com
hostname=localhost

 

This got me half-way there.  With this fix I went from [->] MAIL FROM:<root@tower> to [->] MAIL FROM:<[email protected]>.

 

Here's my edited ssmtp.conf:

 

# Generated
[email protected]
Mailhub=smtp.comcast.net:587
UseTLS=YES
UseSTARTTLS=YES
AuthMethod=login
AuthUser=myemail
AuthPass=mypass
rewriteDomain=comcast.net
hostname=localhost

 

 

There's clearly a bug, it's not using

Root=

.  Is there anything else I can put in ssmtp.conf to over-ride the actual email account as well as the domain?

 

Thanks.

 

I've got

Root=

as the first line in ssmtp.conf (generated by Dynamix), but I haven't tried changing it to

root=

to see if it is case sensitive... I'll give that a try.

Try the following by adding the below lines to the /etc/ssmtp/ssmtp.conf file.

 

rewriteDomain=<yourdomain-name>

FromLineOverride=YES

 

 

  • Author

Try the following by adding the below lines to the /etc/ssmtp/ssmtp.conf file.

 

rewriteDomain=<yourdomain-name>

FromLineOverride=YES

 

That seems to solve my problem.  It even sent a e-mail to my yahoo account from my regular e-mail provider! 

 

Now, I will have to copy that file back to the flash drive so if I reboot, I can restore the configuration.  (Will there be any problems with that?) 

Try the following by adding the below lines to the /etc/ssmtp/ssmtp.conf file.

 

rewriteDomain=<yourdomain-name>

FromLineOverride=YES

 

That seems to solve my problem.  It even sent a e-mail to my yahoo account from my regular e-mail provider! 

 

Now, I will have to copy that file back to the flash drive so if I reboot, I can restore the configuration.  (Will there be any problems with that?)

And if you use your go file to copy it from the flash drive to /etc, do you do that before or after emhttp? I am guessing after since emhttp is probably creating ssmtp.conf from the dynamix.cfg file.
  • Author

Try the following by adding the below lines to the /etc/ssmtp/ssmtp.conf file.

 

rewriteDomain=<yourdomain-name>

FromLineOverride=YES

 

That seems to solve my problem.  It even sent a e-mail to my yahoo account from my regular e-mail provider! 

 

Now, I will have to copy that file back to the flash drive so if I reboot, I can restore the configuration.  (Will there be any problems with that?)

And if you use your go file to copy it from the flash drive to /etc, do you do that before or after emhttp? I am guessing after since emhttp is probably creating ssmtp.conf from the dynamix.cfg file.

 

I was actually planing to do it manually after boot-up as I don't reboot that often.  I know I could put it in the go file but I am hoping  ::)  that we have an update of the webGUI soon which should make all of this unnecessary. 

I am hoping  ::)  that we have an update of the webGUI soon which should make all of this unnecessary.

;D ;D ;D ;D That's rather amusing.

The correction has been made, waiting for LT to release.

 

One remark upfront: you need to re-apply the SMTP settings to make things work !

 

  • Author

The correction has been made, waiting for LT to release.

 

I was really hoping that webGUI updates was not tied to the releases of the base.  I thought this was the idea behind the plug-in concept was that fixes to plug-ins would not be delayed until the next release of the the entire system.  Or is there a alpha testing cycle that most of us are unaware of?

The correction has been made, waiting for LT to release.

 

I was really hoping that webGUI updates was not tied to the releases of the base.  I thought this was the idea behind the plug-in concept was that fixes to plug-ins would not be delayed until the next release of the the entire system.  Or is there a alpha testing cycle that most of us are unaware of?

The holidays and business duties have held us up from getting out the release. A number of us had family events to attend to and we just recently incorporated the business, so there have been a number of accounting and legal matters to attend to as well.  We are working diligently to get out an update to the webGui independent of another full software release.

 

Our apologies for the delay.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.