DSM-G600, DNS-3xx and NSA-220 Hack Forum

I have the same problem and its even trying to connect to my own hosting server.....

Upon checking all mail logs - I never see a connection attempt from the box to my mail server......

I am at a loss on what to try and do about it - and Dlink has been no help....

Myk

shahkb -

For Windows network monitoring, you could take a look at PRTG (www.paessler.com) - this is an SNMP graphing tool, so if you don't have an SNMP enabled device, it might not work for you - if you don't, there's is some sort of sniffer built-in, which I have never used.  They offer a free, three sensor version, so all you stand to lose is your time.

I've been using the free version on my home network, and after adding the DNS-323 (back in January) I did set PRTG to monitor the traffic for quite a while, primarily to get an idea of what the read/write throughput was - I did not notice and unusual activity and have not experienced network perfomance issues.

I was fiddling with my email settings - kind of attempting to simulate some of the problems, and on three occasions, when I clicked the test button, the dialog said sending and after a minute or so, failed, when in actual fact, the mail was sent - but - what I remembered was this - when initially setting up the email alerts, I could not get it to work, and the trick was to click "Save settings" before clicking "Test email"

Maybe you could try that and see if it works for you.

Sorry if this is a stupid question, but have you tried both the Account and Anonymous settings in the DNS email setup?

I have come to the conclusion that my dns box email program is hosed.  Watching network traffic when clicking on the test email button - there is NO traffic other than the web comming out of the box. 

I am going to have to figure out why the progra is not making any attempt to communicate with the outside world...

Myk

I was the guy reporting in an earlier post about the missing date header in mails created by the dns-323.

I tried to discuss the matter several times with the D-Link "support", but all they did was throwing meaningless standard questions like "what ISP do you use" and "how is your mail server configured".

I had already reported all this to them, - IN DETAILS, and also attached logs from the server indicating exactly what the problem was (the mail where rejected because the didn't containg any valid Date Headers)

Finally, I went over to the forum at smeserver.org, and asked the same questions...

If you read through the topic at http://contribs.org/viewtopic.php?p=165614#165614 you'll find a good explanation about what causes this misfunction, and also a suggestion for a solution (it works great for a Smeserver!)

I really don't give 5 cents for that joke support at D-link...

All I can suggest is that EVERYONE experiencing this problem file REPORTS to that joke support, - sooner or later they'll have to wake up and realize they'll have to act!

Best Regards:

//Lasse

shahkb wrote:

Hi,

Thank you. I have given up on dlink support - they asked me to return the box, however, after reading your post I decided to try fixing myself.

As a first step, I installed the fun_plug. Now I can telnet to the box. But I wasn't able to find email log and i don't really know much of linux to find out which program is called for emailing. I went to the web page you mentioned but it was not clear to me what was going on I couldn't find any file by the name
     17check_basicheaders
or any program called
     siganl-event email-update

Could you please give me some more lead? Which is the email service? Where is the log? Which configuration file if any that I should change.

Kilo

Well, I'll try to explain the problem for you:

The problem with the mails generated from the dns-323 is that they don't contain any Date Headers, - which is a NON STANDARD behaivour and by many smtp-servers denied.

The server I'm using is a Smeserver (see http://www.smeserver.org for more details), which is really a server based version of RHEL/Centos, running qpsmtpd as a front end for the smtp server...

In the case of Smeserver, the deamon qpsmtpd takes care of all the "sanity checks" even before allowing the incoming mail to actually enter the rest of the system...

The  17check_basicheaders & siganl-event email-update (really a typo, - should be "signal-event email-update") are specialized things ONLY useful in a Smeserver, thanks to the template system it's built on.

But what it's all about is a way to DISABLE the sanity check function  "check_basicheaders" in your mail server for a specific host, or as in my case for the entire internal lan (I'm using the server in a server/gateway mode)

The way to do this is not always very simple (shouldn't of course ever be necessary!!!) and depends on what system you're using.

What smtp server are you using???

Please refer to the documenation, or ask in relevant forums.....

Best Regards:

//Lasse

Last edited by jumba (2007-05-19 11:18:13)

I did a test when I got home today.... email alerts were working FINE... then I went into the LAN settings, and deleted the DNS IP addresses. Test emails now FAILED.... I was using the ISP's DNS addresses in there at first, and then I used my router's IP address, and it resolved fine... 10.10.5.25 in my case...

Well, I have figured out part of my problem.

The DNS box can not get outbound via port 25, but if I run via command line with params and change the port to 26 (I run a 2nd port because of isp port blocking) and the email will go thru, but with header probs as mentioned above, the email server is at least accepting the email but the date is comming up 12/31/69 4:00pm.....

whats weird - my email client goes out on port 25 just fine, but the dns box cant.

So my next attempt will be to see if I can modify the email.conf to use port 26 instead of 25.  I have to do this cause I do not use my ISP email servers at all, dont even have a account with them, just the cable service.

Will advise....

Obviously, we either talk about different issues here, or I'm unable to make myself clear enought in English!

The message I've tried to report here as well as to the poor Dlink support is simply:

The dlink dns-323 delivers mail with incomplete mail headers (the headers don't contain any Date Headers).
This is a NON STANDARD behaivour and is being refused by many (a growing number!) SMTP servers.

I reported earlier about a way to bypass this if you're running your own SMTP server, but that is of course nowhere near a "solution".

The only "solution" for this is that Dlink rewrite their software so that the headers of the generated mails follow defacto standard!!!

Hopefully, my message was a little more clear this time;-)

Best Regards:

//Lasse

Last edited by jumba (2007-05-21 20:06:03)

shahkb, can you confirm if you have entered the DNS info into the LAN settings page on your DNS-323?

Jumba, I am not quite sure why you are getting so bent out of shape. Good work with uncovering the issue with the date headers, but note that this is not the ONLY reason that the notifications may not work. In addition to that, the original poster hasn't mentioned anything about the date header issue other than asking you for further info about it. There-fore, my suggestion to check that the email & DNS info in properly set up would be the logical first thing to check... I wasn't even the first person to suggest this.

Besides that, the correction you gave (sorry if I am not correct about this) is for an INTERNAL SMTP server you may be using on your LAN, and the original poster clearly stated that they are using their ISP's SMTP server.

EDIT: Whoops... didn't refresh the page for a while, and missed shahkb's reply before I posted... /EDIT

Last edited by Ethereal_Dragon (2007-05-21 21:58:07)

shahkb wrote:

Hi,

Yes, I checked network settings on DNS-323. It is set to be a DHCP client, and the information it picked on DNS servers is accurate. IP address of both DNS1 & 2 are exactly as in my PC (which is also set to be a DHCP client).

Thanks,
Kilo

Does the default gateway match also?