Sponsored Content
Top Forums UNIX for Advanced & Expert Users Restricting emails to particular domain name Post 302742651 by jim mcnamara on Tuesday 11th of December 2012 11:36:22 AM
Old 12-11-2012
You want only a single domain to be allowed when email is sent running on the unix box?

Assuming you are using sendmail --
sendmail is sometimes painful to deal with it has a configuration file, Eric Allman wrote a book on how to configure sendmail. Bryan Costales rewrote the 4th ed:

sendmail, 4th Edition: Bryan Costales, Claus Assmann, George Jansen, Gregory Neil Shapiro: 9780596510299: Amazon.com: Books

Alternatively consider doing this since you have only one.
Put an entry in /etc/hosts to redirect abc.com to localhost ( or to any other machine you want). The email will end up in the ~/dead.letter file for the user running the code.

This will block any email originating on the UNIX box from going to abc.com
 

10 More Discussions You Might Find Interesting

1. Cybersecurity

restricting access...

restricted access... Hi I need to restrict users shell access to only $HOME under /home for each user. I don't want them getting out of their own directories. From what I understand chroot is something I could use, but I want to avoid this since it involves creating symbolic links to a number... (9 Replies)
Discussion started by: alwayslearningunix
9 Replies

2. UNIX for Dummies Questions & Answers

Restricting access

I need to create a user that only has access to 1 directory (e.g. /vol/mita/test). The user needs to be able to rsh into that directory to run a script. The user should not be able to navigate to any other directories above /vol/mita/test. Any help would be appreciated! (4 Replies)
Discussion started by: ngagne
4 Replies

3. Cybersecurity

Restricting Telnet to IPs

Dear Experts, Is there a way to restrict telnet to specific IPs Thanks (6 Replies)
Discussion started by: geraldwilson
6 Replies

4. Solaris

restricting access

Hi All, I'm on Solaris 8, I need to provide Read-only access to a user to 2 directories only. Using rsh (restricted shell) as the user's login shell, I can restrict the user's access to a certain directory only, but how can I set in such a way that the user can access only the 2 directories... (4 Replies)
Discussion started by: max_min
4 Replies

5. AIX

sendmail only sends emails to its own domain

Hi, folks! I have a problem with an AIX 5.3 server running sendmail where it is able to send messages within its own domain just fine. This is being used for a web email service portion of a web site. However, when it attempts to send email to any other domain -- i.e., hotmail.com -- it... (3 Replies)
Discussion started by: jjwood64
3 Replies

6. UNIX for Dummies Questions & Answers

Restricting SSH usage

Hello, For one of our servers, we have had people trying to illegally loggon using the ssh service. My manager has asked me to restrict ssh access to users in our internal network but close ssh access to the "outside" world. Could someone at the very least point me to some resources on the... (7 Replies)
Discussion started by: mojoman
7 Replies

7. Windows & DOS: Issues & Discussions

How to: Linux BOX in Windows Domain (w/out joining the domain)

Dear Expert, i have linux box that is running in the windows domain, BUT did not being a member of the domain. as I am not the System Administrator so I have no control on the server in the network, such as modify dns entry , add the linux box in AD and domain record and so on that relevant. ... (2 Replies)
Discussion started by: regmaster
2 Replies

8. UNIX for Dummies Questions & Answers

Restricting SFTP access

Hello, I am using MySecureShell to chroot all sftp accesses. The problem that I have is that my boss does not want root to be able to use sftp. Root should still be able to ssh. Any ideas? (2 Replies)
Discussion started by: mojoman
2 Replies

9. Shell Programming and Scripting

restricting users

how can i make my users to not use particular commands in the network like:wall....... pl z help me regarding this (1 Reply)
Discussion started by: yashwanthguru
1 Replies

10. Solaris

Restricting use of su - (Solaris 11)

OK. So I can prevent remote systems from logging in as root by uncommenting the CONSOLE entry /etc/default/login. BUT, is there a way to stop su - (when already logged in as own user)? The way we do it is to set up sudoers so users who need access can do sudo su - (2 Replies)
Discussion started by: psychocandy
2 Replies
RC.SENDMAIL(8)						    BSD System Manager's Manual 					    RC.SENDMAIL(8)

NAME
rc.sendmail -- sendmail(8) startup script DESCRIPTION
The rc.sendmail script is used by /etc/rc at boot time to start sendmail(8). It is meant to be sendmail(8) specific and not a generic script for all MTAs. It is only called by /etc/rc if the rc.conf(5) mta_start_script variable is set to /etc/rc.sendmail. The rc.sendmail script can take an optional argument specifying the action to perform. The available actions are: start Starts both the MTA and the MSP queue runner. stop Stops both the MTA and the MSP queue runner. restart Restarts both the MTA and the MSP queue runner. start-mta Starts just the MTA. stop-mta Stops just the MTA. restart-mta Restarts just the MTA. start-mspq Starts just the MSP queue runner. stop-mspq Stops just the MSP queue runner. restart-mspq Restarts just the MSP queue runner. If no action is specified, start is assumed. The rc.sendmail script is also used by /etc/mail/Makefile to enable the Makefile's start, stop, and restart targets. RC.CONF VARIABLES The following variables affect the behavior of rc.sendmail. They are defined in /etc/defaults/rc.conf and can be changed in /etc/rc.conf. sendmail_enable (str) If set to ``YES'', run the sendmail(8) daemon at system boot time. If set to ``NO'', do not run a sendmail(8) daemon to listen for incoming network mail. This does not preclude a sendmail(8) daemon listening on the SMTP port of the loopback interface. The ``NONE'' option is deprecated and should not be used. It will be removed in a future release. sendmail_cert_create (str) If sendmail_enable is set to ``YES'', create a signed certificate /etc/mail/certs/host.cert representing /etc/mail/certs/host.key by the CA certificate in /etc/mail/certs/cacert.pem. This will enable connecting hosts to negotiate START- TLS allowing incoming email to be encrypted in transit. sendmail(8) needs to be configured to use these generated files. The default configuration in /etc/mail/freebsd.mc has the required options in it. sendmail_cert_cn (str) If sendmail_enable is set to ``YES'' and sendmail_cert_create is set to ``YES'', this is the Common Name (CN) of the certifi- cate that will be created. If sendmail_cert_cn is not set, the system's hostname will be used. If there is no hostname set, ``amnesiac'' will be used. sendmail_flags (str) If sendmail_enable is set to ``YES'', these are the flags to pass to the sendmail(8) daemon. sendmail_submit_enable (bool) If set to ``YES'' and sendmail_enable is set to ``NO'', run sendmail(8) using sendmail_submit_flags instead of sendmail_flags. This is intended to allow local mail submission via a localhost-only listening SMTP service required for running sendmail(8) as a non-set-user-ID binary. Note that this does not work inside jail(2) systems, as jails do not allow binding to just the localhost interface. sendmail_submit_flags (str) If sendmail_enable is set to ``NO'' and sendmail_submit_enable is set to ``YES'', these are the flags to pass to the sendmail(8) daemon. sendmail_outbound_enable (bool) If set to ``YES'' and both sendmail_enable and sendmail_submit_enable are set to ``NO'', run sendmail(8) using sendmail_outbound_flags instead of sendmail_flags. This is intended to allow local mail queue management for systems that do not offer a listening SMTP service. sendmail_outbound_flags (str) If both sendmail_enable and sendmail_submit_enable are set to ``NO'' and sendmail_outbound_enable is set to ``YES'', these are the flags to pass to the sendmail(8) daemon. sendmail_msp_queue_enable (bool) If set to ``YES'', start a client (MSP) queue runner sendmail(8) daemon at system boot time. As of sendmail 8.12, a separate queue is used for command line submissions. The client queue runner ensures that nothing is left behind in the submission queue. sendmail_msp_queue_flags (str) If sendmail_msp_queue_enable is set to ``YES'', these are the flags to pass to the sendmail(8) daemon. These variables are used to determine how the sendmail(8) daemons are started: # MTA if (${sendmail_enable} == NONE) # Do nothing else if (${sendmail_enable} == YES) start sendmail with ${sendmail_flags} else if (${sendmail_submit_enable} == YES) start sendmail with ${sendmail_submit_flags} else if (${sendmail_outbound_enable} == YES) start sendmail with ${sendmail_outbound_flags} endif # MSP Queue Runner if (${sendmail_enable} != NONE && [ -r /etc/mail/submit.cf] && ${sendmail_msp_queue_enable} == YES) start sendmail with ${sendmail_msp_queue_flags} endif To completely prevent any sendmail(8) daemons from starting, you must set the following variables in /etc/rc.conf: sendmail_enable="NO" sendmail_submit_enable="NO" sendmail_outbound_enable="NO" sendmail_msp_queue_enable="NO" SEE ALSO
rc.conf(5), rc(8), sendmail(8) HISTORY
The rc.sendmail file appeared in FreeBSD 4.6. BSD
October 19, 2013 BSD
All times are GMT -4. The time now is 05:08 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy