Topic: SME 6.0.1 Post Install

[tcarroll]

Happy New Year everyone!

I have been pretty quiet over the last couple of years because SME 5.6 did everything I needed and ran flawlesly, until I messed up a few things.  

In any case, I conducted a fresh install of v6.0.1.  The details of my setup are in my signature.  I must say I think the 6.01 version is a major improvement over the previous version - nice job contribs community!

First issue is that users cannot get mail (pop3 or webmail) from the server.  I am using Outlook 2003 behind the server on the network and my server is mail.carrollweb.net.  What is strange is that no matter what I do, change the user password (account is not locked), delete and recreate the account, etc. it will not accept the username/password when logging into the mail server.  Outlook is telling me the server responds with "ERR-Authorization failed."  However, if I change the username to admin and insert the admin password it will pull the admin mail down with no problems...

Second problem is that my messages log file is growing incredibly large with the following entry:

Jan  3 13:33:35 server kernel: denylog:IN=eth0 OUT= MAC=00:c0:9f:07:8d:fe:00:05:00:e7:b6:30:08:00 SRC=70.242.49.96 DST=66.91.33.150 LEN=809 TOS=0x00 PREC=0x00 TTL=115 ID=47123 PROTO=UDP SPT=31885 DPT=1026 LEN=789
Jan  3 13:36:47 server kernel: denylog:IN=eth0 OUT= MAC=00:c0:9f:07:8d:fe:00:05:00:e7:b6:30:08:00 SRC=66.131.125.5 DST=66.91.33.150 LEN=48 TOS=0x00 PREC=0x00 TTL=109 ID=3029 DF PROTO=TCP SPT=4008 DPT=1025 WINDOW=16384 RES=0x00 SYN URGP=0

My setup for the ethernet is swapped, eth0 is my external nic.  It appears to me that this might be someone trying to get a DHCP address from my system?  I have no idea what this is, but it did not appear in my SME 5.6 logs.  Should I be concerned?

Thirdly, my dyndns is not working.  I tried running the script manually and it gives an error "ppp0: error fetching interface information: Device not found."  I know my external nic is eth0, so I have no idea why the script is hard coded to look at ppp0 unless ppp0 is bound to the outbound nic.

I have installed the smeplus.sh update script and I used it to update the system.  I also installed Darrell May's raidmonitor contrib as well as JesperKnudsen's SpamFilter contrib.

I appreciate any help anyone can give me here.

[CharlieBrady]

In any case, I conducted a fresh install of v6.0.1.  The details of my setup are in my signature.  I must say I think the 6.01 version is a major improvement over the previous version

Why do you think so? Other than appearance, there's very little difference from 6.0.

Second problem is that my messages log file is growing incredibly large with the following entry:

Jan  3 13:33:35 server kernel: denylog:IN=eth0 OUT= MAC=00:c0:9f:07:8d:fe:00:05:00:e7:b6:30:08:00 SRC=70.242.49.96 DST=66.91.33.150 LEN=809 TOS=0x00 PREC=0x00 TTL=115 ID=47123 PROTO=UDP SPT=31885 DPT=1026 LEN=789
Jan  3 13:36:47 server kernel: denylog:IN=eth0 OUT= MAC=00:c0:9f:07:8d:fe:00:05:00:e7:b6:30:08:00 SRC=66.131.125.5 DST=66.91.33.150 LEN=48 TOS=0x00 PREC=0x00 TTL=109 ID=3029 DF PROTO=TCP SPT=4008 DPT=1025 WINDOW=16384 RES=0x00 SYN URGP=0

My setup for the ethernet is swapped, eth0 is my external nic.   It appears to me that this might be someone trying to get a DHCP address from my system?

I see no sign of DHCP accesses. One of those log messages is an inbound UDB packet. The other is a TCP connection attempt. Both are to ports where you have no service listening. They're harmless traffic, and unavoidable on the Internet these days.

I have no idea what this is, but it did not appear in my SME 5.6 logs.  Should I be concerned?

I can't explain the difference. And no.

Thirdly, my dyndns is not working.  I tried running the script manually and it gives an error "ppp0: error fetching interface information: Device not found."  I know my external nic is eth0, so I have no idea why the script is hard coded to look at ppp0 unless ppp0 is bound to the outbound nic.

What script are you running? Did you once have an ADSL connection?

[tcarroll]

Thanks Charlie - I like the new server manager for one, but I also like the new directory structure in /home/e-smith.

I see no sign of DHCP accesses. One of those log messages is an inbound UDB packet. The other is a TCP connection attempt. Both are to ports where you have no service listening. They're harmless traffic, and unavoidable on the Internet these days.

Hmmm...  I wonder what changed between the two versions.  It seems that SME 5.6 filtered these entries because I certainly did not have them two days ago when I was running SME 5.6.

Quote:

Thirdly, my dyndns is not working. I tried running the script manually and it gives an error "ppp0: error fetching interface information: Device not found." I know my external nic is eth0, so I have no idea why the script is hard coded to look at ppp0 unless ppp0 is bound to the outbound nic.
 

What script are you running? Did you once have an ADSL connection?

Fresh install with a cable connection.  I tried to manually run the script dyndns (I pay commercial dyndns service) located in /sbin/e-smith/dynamic-dns/ It times out, therefore I had to go in manually to dyndns.com to update my IP address.

[tcarroll]

First issue is that users cannot get mail (pop3 or webmail) from the server. I am using Outlook 2003 behind the server on the network and my server is mail.carrollweb.net. What is strange is that no matter what I do, change the user password (account is not locked), delete and recreate the account, etc. it will not accept the username/password when logging into the mail server. Outlook is telling me the server responds with "ERR-Authorization failed." However, if I change the username to admin and insert the admin password it will pull the admin mail down with no problems...

After further investigation of the log files and muuy curiosity as to why admin would work, but not the user, I found that the security attributes we invalid on the user folders.  This may have been a result of me bringing the user folders over from the backup.  It appears to be working fine with both Pop-3 as well as Webmail now.