Sponsored Content
Operating Systems Solaris sendmail "root... User address required." error Post 302123876 by reborg on Wednesday 27th of June 2007 02:57:37 PM
Old 06-27-2007
What is being suggested is that you use the standard client configuration and do not attempt to directly relay all mail.

Instead you construct an alias for each non-local user in /etc/mail/aliases eg:

Code:
john:   john@example.com

then type in 'newaliases' to build the alias list.

This will be relayed to the mailhost, you then do not alias the local delivery accounts such as root. Mail will then be relayed to the fully qualified name, and non relayed mail will stay local.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Possible to give non root user sudo to "crontab -l"

Does anyone know if this is possible? I want to give some users access to root's crontab but only with a read privilege. Is this possible to do or can only root or people with full root sudo view root's cron? (4 Replies)
Discussion started by: LordJezoX
4 Replies

2. OS X (Apple)

Ho do I masquerade the "user@user.local" address in mail/mailx?

Hi, I'm brand new here and looking for a solution: I'm using mail or mailx. The default reply address is «myshortusername@mylongusername.local» which makes absolutely no sense for anybody receiving my emails. But how do I change it? There seem to be many solutions but none for Mac OS X.... (0 Replies)
Discussion started by: gczychi
0 Replies

3. Red Hat

error"warning: user owen does not exist - using root"?

I am trying to install openmotif22-2.2.3-18.src.rpm, after I typed in " rpm -i openmotif22-2.2.3-18.src.rpm" the following message comes out: warning: user owen does not exist - using root warning: group owen does not exist - using root I am install openmotif under root account. Do... (2 Replies)
Discussion started by: fishwater00
2 Replies

4. UNIX for Advanced & Expert Users

How to allow particular user only to login as a root using "ssh" ?

Q1 I want to allow particular user only to login into root using ssh. I have set PermitRootLogin no for security purpose but I want to allow some of the users to login as a root using ssh how to do this? I have tried with Allowusers user1 user2 its working for only the user1 and... (3 Replies)
Discussion started by: ungalnanban
3 Replies

5. Solaris

"! bad user (root)" in cron log

I am getting the following error in the cron log: ! bad user (root) Wed Sep 22 14:30:00 2010 < root 8989 c Wed Sep 22 14:30:00 2010 rc=1 What does this mean? (5 Replies)
Discussion started by: jastanle84
5 Replies

6. Red Hat

Sendmail saying "user unknown" after setting up MX

Hi Friends, I set up the sendmail in my perosnal home lab. I am using mutt to send the email in between the machines. Everything is working fine if i send email like <username>@<hostname>. Now i set up the MX record for my domain "home.com" and then i was trying to send the email to like... (2 Replies)
Discussion started by: Rohit Bhanot
2 Replies

7. AIX

Change "root" to "root.admin" in outgoing e-mails

Our AIX servers send e-mails which have the "from" address set to "root@company.com" for our root user ("C{M}company.com" in /etc/sendmail.cf). The problem is that when bad e-mails are sent out or rejected by remote servers, they are being returned and delivered to e-mail box of "Mary Root". ... (2 Replies)
Discussion started by: kah00na
2 Replies

8. Shell Programming and Scripting

Root running a script calling to scp using user "xyz" is not authenticating!

Close duplicate thread. (0 Replies)
Discussion started by: denissi
0 Replies

9. UNIX for Beginners Questions & Answers

How to run root level command , if user has "su -" permission in sudoers provided?

I am looking t run root level command on multiple servers, but all servers have only "su - " permission available in sudoers. please help me if any way that I can run command using help of "su -" My script for hosts in `cat hosts.txt`; do echo "###########################Server Name-... (5 Replies)
Discussion started by: yash_message
5 Replies
MAKEHOSTEDDOMAINS(8)					      Double Precision, Inc.					      MAKEHOSTEDDOMAINS(8)

NAME
makehosteddomains - Build a database of hosted domains SYNOPSIS
makehosteddomains DESCRIPTION
makehosteddomains rebuilds the contents of the /etc/courier/hosteddomains.dat database from the contents of /etc/courier/hosteddomains. This can be either a file or a directory. If it's a directory, the contents of all the files in this directory are simply concatenated. The makehosteddomains script must be run in order for any changes to /etc/courier/hosteddomains to take effect. The function of /etc/courier/hosteddomains is very similar to the one of /etc/courier/locals. Both configuration files specify a list of domains that are considered to be local domains - domains whose mailboxes are stored locally. The difference is that domains listed in /etc/courier/locals are removed from addresses before their mailbox is looked up. For example, if the domain "example.com" is listed in /etc/courier/locals, then the address <user@example.com> is delivered to a local mailbox named "user". If this domain is listed, instead, in /etc/courier/hosteddomains, then the address <user@example.com> is delivered to a local mailbox named "user@example.com". Usually you would use /etc/courier/locals to specify domains that correspond to your local system accounts, that are looked up in your system's password database. The /etc/courier/hosteddomains file is usually used when you have database-based virtual domains, that are maintained via an LDAP or a MySQL server. The Courier mail server's LDAP and MySQL authentication modules will use the full E-mail address to query the LDAP or MySQL server for the location of the local mailbox that correspond to the E-mail address. The Courier mail server's authuserdb authentication module can also use full E-mail addresses. Contents of hosteddomains The file /etc/courier/hosteddomains simply contains a list of domains, one per line, for example: domain.com example.org Each domain can optionally be followed by a single tab character, in order to specify an alias for a domain, for example: domain.com mail.domain.com<TAB>domain.com example.com<TAB>domain.com First, we list the domain "domain.com" as a hosted domain. Then, we also list the domain "mail.domain.com", which is an alias for domain.com. The Courier mail server will take any address of the form <address@mail.domain.com>, rewrite it as <address@domain.com>, and attempt to deliver the mail to a local mailbox for that name. The third entry does the same for "example.com"; mail addressed to <address@example.com> is delivered to the local mailbox <address@domain.com>. alias@hosteddomain This is a special local mail delivery rule for hosteddomain-listed domains. This rule allows the Courier mail server accept mail to any address@hosteddomain, where "hosteddomain" is a domain listed in the hosteddomains file, but there is no corresponding account for address@hosteddomain. To provide delivery instructions for any non-existing address in a hosteddomain-listed domain: 1) Create the local address alias@hosteddomain. For example, if the hosteddomains file contains "example.com", create the local account alias@example.com. This should be a normal account, with its own home directory, userid and groupid. 2) Create $HOME/.courier-default file in this account, containing the delivery instructions. See the dot-courier(5)[1] manual page for available delivery instructions. NOTE that alias@example.com must be a real account, not a mail alias. If you want to forward alias@example.com to another address, put forwarding instructions in the .courier-default file. However, alias@example.com can be a clone of another account (with the same home directory, userid, and groupid). "WILDCARD DNS" Wildcard DNS is supported for hosteddomains by placing a single period character before the domain name. For example, the hosted domain entry ".domain.com" will cause the Courier mail server to accept mail for "anything.domain.com". The Courier mail server will accept mail for <address@any.thing.domain.com> and attempt to deliver it to the local mailbox <address@any.thing.domain.com>, and if that fails then attempt to deliver the mail to the local mailbox <address@.thing.domain.com>, then finally <address@.domain.com> Note There is a period after the '@' character. If you want all mail for "any.thing.domain.com" to be delivered as though it were sent to "domain.com", you should define an alias for the domain, for example: domain.com .domain.com<TAB>domain.com SEE ALSO
esmtpd(8)[2]. AUTHOR
Sam Varshavchik Author NOTES
1. dot-courier(5) [set $man.base.url.for.relative.links]/dot-courier.html 2. esmtpd(8) [set $man.base.url.for.relative.links]/esmtpd.html Courier Mail Server 08/30/2011 MAKEHOSTEDDOMAINS(8)
All times are GMT -4. The time now is 11:48 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy