nlrela
Junior Member
Posts: 56
|
Post by nlrela on Dec 7, 2006 23:08:06 GMT 7
Has anyone got the email notification working ?
I would have been glad to know that my RAID 5 was degraded after a reboot .....
I've tried as far as I know all settings with several email accounts (and providers), but until now I haven't succeeded.
What could be the restrictions for this functionality ?
I have installed firmware version 1.00.4.
Thanx for your feedback
|
|
|
Post by thecususer on Dec 8, 2006 1:26:21 GMT 7
Yes, I have the same problem as well.
|
|
jamis
Full Member
Posts: 109
|
Post by jamis on Dec 8, 2006 2:20:54 GMT 7
I think part of the problem is that you can't set the From: or Reply to: email address (its hard-coded) and many ISPs don't allow such spoofing. Unfortunately they haven't figured out a good way to report an error other than not getting the email None of their config options are valid to work with Gmail or Yahoo SMTP from what I can figure out either.
|
|
|
Post by omega on Dec 21, 2006 1:35:22 GMT 7
Hi,
I tried to figure out why E-Mail notification is not working....
The mail is sent with this command:
echo "From: xxx To: yyy Subject: foo bar
Some message to the Thecus N5200 user....
Regards " | /opt/bin/msmtp --from=thecus@192.168.1.100 --host=10.0.1.1 --port=25 --auth=off --user=av --password DEL av@my.dom.com
The command terminates with this error:
msmtp: envelope from address speicher@192.168.1.100 not accepted by the server msmtp: server message: 501 5.1.7 Bad sender address syntax msmtp: could not send mail
As you can see, the sender address "speicher@192.168.1.100" is not accepted by my SMTP server. When I call the same command with just "thecus" everything is OK.
I'll try to create a patch for this.....
Bye
Andreas
|
|
jamis
Full Member
Posts: 109
|
Post by jamis on Dec 21, 2006 2:00:13 GMT 7
You are on a roll, omega. Keep up the good work.
|
|
|
Post by marty on Dec 21, 2006 14:07:17 GMT 7
.... I'll try to create a patch for this..... ... Why not just email support with your patch, and ask them to apply to the next release? They should be happy if you did all the work for them.
|
|
|
Post by omega on Dec 21, 2006 20:02:53 GMT 7
Why not just email support with your patch, and ask them to apply to the next release? They should be happy if you did all the work for them. You are right .... but I don't want to wait for it too long.... I wanted it now! I really wonder how Thecus can provide this software... principially it is working, but some features are not working at all.... Regarding the fix for the E-Mail problem: I have bad news . Some parts of the software are stored in compressed image files (these are the .rom files in /cloopfs). They are loop-mounted read-only using the cloop filesystem. Thecus has modified the cloop filesystem source by an encryption feature, so I cannot create a new image containing the corrected scripts. Due to technical reasons it is not possible to write-mount this image files. Unfortunately unionfs is not available on the N5200, otherwise I could use it to place my own scripts above /app/img and /app/www. So for this problem, the only solution seems to be that everybody is sending an E-Mail to Thecus and ask for a fix. The more people asking the faster we should see a fix. And E-Mail notification is quite high priority, imho. Andreas
|
|
nlrela
Junior Member
Posts: 56
|
Post by nlrela on Dec 22, 2006 2:56:12 GMT 7
Great, great, great pity it won't work.
Keep up anyway the great work !
|
|
|
Post by omega on Dec 22, 2006 7:15:14 GMT 7
Tried unionfs on the N5200 but the module is not working.... Maybe something else comes into mind..... I've already sent an E-mail to Thecus asking for an official patch for my problems..... Good night Andreas
|
|
nlrela
Junior Member
Posts: 56
|
Post by nlrela on Dec 28, 2006 21:31:16 GMT 7
Accoridng ot Thecus support it should be working with the next release .... (1.00.06 ??)
|
|
|
Post by wildcargo on Dec 31, 2006 7:23:14 GMT 7
WTF this is a total s-hit box... i have to get patchs from 3rd party clowns the f-uck face that said the support is good can suck my BALLSACK..gET an asus,, write 59 meg a second read 52 meg a second,,, this is corn in the feces,, i only hope that the support gets elbo deep anal fisted
|
|
|
Post by tokyorob on Dec 31, 2006 11:03:52 GMT 7
Working Email would be nice .. given that I have the degraded raid problem at the moment..
but it looks like Thecus are trying and the regular firmware updates seem to improving the box
rob
|
|
|
Post by omega on Dec 31, 2006 21:35:51 GMT 7
wildcargoPlease don't bother us with your rude writing - nobody wants to read things expressed in that way and you don't comply to the rules of this forum anyway. Think about it and a happy new year.... Andreas
|
|
nogami
Junior Member
Posts: 68
|
Post by nogami on Jan 1, 2007 7:44:55 GMT 7
I have 1.00.4.10 running on a replacement box that I got from Thecus - I managed to get the email notification working with my own mailserver, but this may be impossible if you don't have your own server.
As Jamis noted, using the "thecus@192.168.1.100" doesn't work as many mailservers validate an incoming domain as legit before allowing a relay (even on a trusted network). Since the 192.168 block is for local use only, it gets tossed-out by the mailserver.
I managed to config my own mailserver to bypass the restriction and relay the notice properly, however that's not always an option. Thecus should allow setting the default sending domain by the user.
On a side note, my 1.00.4.10 box has been running for over a week now with no rebooting and no degraded stripe sets, which is promising.
|
|
|
Post by omega on Jan 3, 2007 0:08:58 GMT 7
I managed to config my own mailserver to bypass the restriction and relay the notice properly, however that's not always an option. Thecus should allow setting the default sending domain by the user. What MTA are you using? What did you change? No, this is not the problem. The problem is Thecus doesn't honour RFC 821: there you can read that a valid E-Mail envelope "MAIL TO:" or "RCPT FROM:" address needs to be enclosed in angle brackets AND needs to be in the form user@this.is.a.domain or user@[1.2.3.4] - the correct address would be <thecus@[192.168.1.100]>. So in the first row this is a syntax problem and not a security problem. So Thecus is doing both things wrong. But the fix is so easy and takes only 2 minutes of programming, so I really hope they will fix it soon. I was writing an e-mail about this issue to the support two weeks ago but until now no answer (too many holidays though). But one thing nogami points out is still true: there must be a chance to set the sending domain in the envelope FROM: address since most MTAs block unauthorized/unknown sender domains. Just using the IP address of the LAN port is not a acceptable solution. Andreas
|
|