Basic SABnzbd+ Setup – SAB for short.

There are plenty of tutorials out there which cover configuring a normal SAB installation so I won’t cover that here. What I am going to do is make my SAB available through a web accessible passworded page, this can be accomplished with default SAB features by putting a web username/password in the general configuration section. However I find it annoying to have to enter the password when I’m on my internal 192.168 home network just to make it protected from the outside, and I don’t like the way it presents the username/password prompt in a website form rather than an generic apache pop-up. I’m sure open accessibility could be fixed in the SABnzbd+ code but I’m not a pro python hacker yet so I’ll just stick to what I know.

Basically I want a generic pop-up password that is only for people outside my network so I’m not bothered with SAB passwords while at home (And I can’t get nzbdStatus to work with a pass enabled). The htpasswd also acts as a bit of camouflage and additional security. There are some concepts which aren’t covered here which are required, you need to know how to configure your own SAB servers, Portforwarding or Firewall/iptables.

If you’re using a router, you’re going to want to make sure you’re not port forwarding the default SAB port of 8080 (which would make it wide open) and only are forwarding the apache2 port you setup for the SAB proxy. If you’re not on an internal IP subnet and have a static IP assigned directly to the linux machine you’re doing this on then I expect you have enough knowledge of IPTables to block the SAB port and allow the proxy port.

(more…)

I like to have interfaces and description, not one or the other. So I do this. Use your favorite editor to open indexmaker: vi /usr/bin/indexmaker

Find this part:

for ($$opt{section}) {
# ...Skip ahead to descr...
/^descr(iption)?$/ &&
do{
$section = "No Description for $item";
$$rcfg{setenv}{$item} =~ /MRTG_INT_DESCR="(.+?)"/ #"
and $section = $1;
$$rcfg{pagetop}{$item} =~
m,<td>Description:</td>\s*<td>\Q$section\E\s*([^< ][^>]+?)

,i
and $section = $1;
last;
};


The first “and $section = $1;” is a catch all to assign the interface name if there’s no description. The second one overwrites it, replacing the int name if it does find a description. So all you need to do is modify the second instance of “and $section = $1;” to:

and $section = $section . " - " . $1;

And your MRTG index is infinitely improved!

Can’t send from certain locations and keep having to turn on/off outgoing server SMTP Authentication in outlook 2007? You might see this error too: “None of the Authentication Methods Supported By This Client Are Supported By Your Server”

My Answer: Goto Email Accounts, Change the problem account, More Settings, Outgoing Server tab, and check outgoing server require authentication and choose “Log on to incoming mail server before sending mail” instead of “Use same settings as incoming” – Outlook 2007 is the first and only mail program to require any of our mail servers to use this setting. So far I’ve only confirmed the problem to be on older sendmail servers. There can be other solutions to this error message but this is one I find most often resolves it.

The Question: As a systems administrator I take calls for our tech support queue and one user called with a really odd problem. Basically it’s detailed here:

http://thepursuitofalife.com/outlook-2007-error-none-of-the-authentication-methods-supported-by-this-client-are-supported-by-your-server/

Like the above link describes the user would have to disable SMTP auth in certain locations (That’s a workaround, not the solution), even though all our servers require SMTP authentication. The above link eventually shares the true solution but it’s buried under many comments thanking the poster for the work around. So I decided to help fellow googlers by making this post.

Update: Comments about other people’s experience with this error made me want to add my further experience with it. I’ve seen this error a lot more often since I first made this post and am convinced it’s really some sort of bug with Outlook 2007. Some people cannot get rid of the error and have to continually switch between “Log on to incoming mail server before sending mail” and “Use same settings as incoming” to keep outlook sending correctly. Whereas if they switch to Windows Mail (The Vista and Windows 7 equivalent of outlook express) they never need to do anything but set ‘use same settings as incoming’ and never have any problem sending. If it’s not a ‘2007 Bug’ then it’s definitely a Outlook 2007 incompatibility with certain MTAs – specifically (maybe just older) sendmail – our postfix servers don’t seem to have this bug, but like I just said only 2007 has this incompatibility so you can’t entirely blame sendmail.