I have sendmail installed on a server running Ubuntu 10.04. I need to be able to send email to my companies email server from this machine, but I am not currently able to. A rep in the IP department determined that my issue was that the IP address my server is resolving for the company mail server is it's external address and I need to be connecting to it's internal address (due to the way they have routing rules configured). He gave me the IP address I need to connect to and instructed me to set mail.mycompany.com to resolve to this IP address. How do I accomplish this? (I tried /etc/hosts but found out very quickly that does not work for sendmail).
I admin a server which is running a number of web applications for a software dev team (source control, bug tracking, etc). The server has sendmail running solely as a transport to the departmental email server over which I have no control.
We have someone who is still in the department but no longer on the dev team so I need to configure the transport agent to redirect all outgoing email (which would be coming from these applications) to the person that has taken their place. I added an entry in /etc/aliases like such:
[email protected]: [email protected]
But when I run
/etc/init.d/sendmail newaliases
I get the following error:
/etc/mail/aliases: line 32: [email protected]... cannot alias non-local names
So clearly I'm doing something I shouldn't. Is there a way to get aliases to work with non-local names or alternatively is their a way to accomplish my goal of redirecting outgoing mail for this user to another one?
Technical Specs if the matter:
- Ubuntu 6.06
- sendmail 8.13 (ubuntu provided package)
I am attempting to configure Apache to host multiple django sites via mod_wsgi. The mod_wsgi setup tutorial gives an example configuration for this scenario where each app is in the same directory:
WSGIScriptAliasMatch ^/([^/]+) /usr/local/django/$1/apache/django.wsgi
<DirectoryMatch ^/usr/local/django/([^/]+)/apache>
Order deny,allow
Allow from all
</DirectoryMatch>
I'm trying to extend this example to add a password file created for each application to use http authentication. I figured I could do this by setting up a seperate parallel directory for each app and reference the matched directory name in the way that is done in WSGIScriptAliasMatch, like such:
WSGIScriptAliasMatch ^/([^/]+) /usr/local/django/$1/apache/django.wsgi
<DirectoryMatch ^/usr/local/django/([^/]+)/apache>
AuthType Basic
AuthUserFile /usr/local/django-auth/$1/users.passwd
AuthGroupFile /dev/null
Require valid-user
</DirectoryMatch>
I had assume that '$1' would expand to the parans matched by the regex for the DirectoryMatch, however I can't authenticate and my error log states:
No such file or directory: Could not open password file: /usr/local/django-auth/$1/users.passwd
So it seems like the '$1' isn't being expended to the matched app like I assumed it would. Is there any way to accomplish this? I don't want to have to add a new directive for each site as it pops up.
I currently have my apache server to authenticate via a password file created from htpasswd. Configured as such:
AuthType Basic
AuthName "Secured Site"
AuthUserFile "/etc/apache2/users.passwd"
How can I change this to authenticate via local system accounts and additionaly restrict to only a subset of local system accounts in a specified group?
I am looking for a list of actions that can performed that will result in a directories modification time being updated. Off the top of my head:
- Create a new file in the directory
- Delete a file in the directory
What am I missing?
I noticed a number of directories on my home server that I haven't touched in have had their modification time changed, though none of the files contained in these directories report a change in time.
I run an IDS (fcheck), and it did not report anything on the date of the directories' modification time. This is not surprising since the directories in question are in my home directory (which my IDS does not scan). I have grepped through auth.log and did not find any unauthorized access on the date in question and checked most configurations in /etc appear to be the same. How should I proceed next to determine if in fact my machine has been compromised?
The Samba documentation states quite clearly that is only capable of functioning as an NT4 style Primary Domain Controller and can not function as an Active Directory server. I manage a group of mixed systems (windows xp workstations and linux servers of various flavors), and looking to centralize authentication of various server applications as well as the client workstations. I am considering setting up a Samba server, but I can't find a feature break down between what would be offered by a PDC and an ADS to aid me in deciding if a Samba server would satisfy my goals. Does anyone know where I could find such a feature comparison?
Edit: The workstations are not currently on a domain. What ever active directory/samba configuration I introduce will be our group's initial foray into centralized authentication. This means setting up a Windows Server domain controller is a feasible option, but I'd prefer to do it with Samba as I am more Linux savy.
I need to find the last time that the
apt-get update
command was run on my server. How can I determine this information?
I have found plenty of resources/tutorials on installing OpenLDAP on Ubuntu, and I have successfully configured my server (up and running and successfully authenticating). My question relates to how I should setup the schema as I can not seem to find any useful resources on this. I am also starting to think I am trying to make LDAP do more then it was intended to do so please feel free to point this out if that is the case. Here is my scenario:
3 Servers with various LDAP capable applications on each (mostly web based) 3-5 classes of users (developers, interns, customers, managers, etc), each class of user requires access to a subset of all the applications
What I had thought to do is to assign each user to some 'role', and then grant application permission to the role rather then the user. That way when I add new users I only have to assign them a role rather then access to individual applications. Also that way if we added a new app or decided a class of users should have access to some existing application then it would only require updating the role rather then every user.
Is this some I can/should do with LDAP, or should I be looking at an alternative such as samba?