Sponsored Content
Full Discussion: Restrict mail from Sendmail
Operating Systems Linux Restrict mail from Sendmail Post 302288047 by otheus on Monday 16th of February 2009 10:14:09 AM
Old 02-16-2009
Basically, you want a blackhole list for email addresses, rather than domains.

Question: what happens if 1 week from now, that account suddenly exists and accepts mail?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

blocking mail using sendmail

Hi, I am using sendmail 8.9.1 and trying to block email from certain domain/user. How could I do that? TQ (4 Replies)
Discussion started by: liyas
4 Replies

2. UNIX for Dummies Questions & Answers

Sendmail - forwarding mail

quick question. I have a webserver that has various scripts for user registration and ect on it. I want to post (mail) these to myself - however I am a bit stuck on how to configure sendmail to do this. The hosting partner that I use has provided me with the use of their relay to send on the... (1 Reply)
Discussion started by: warrend
1 Replies

3. UNIX for Advanced & Expert Users

Forwarding mail with sendmail

Hello, I need to forward mail wich are in some users mailbox. The .forward redirection is working for all new mails but not for old. Is someone know how to do this ? Thanks (2 Replies)
Discussion started by: annececile
2 Replies

4. Solaris

sendmail mail server help

Hello guys, Am trying to enable/start sendmail in Solaris 10. I tried using scvadm and also did it using the /etc/init.d/sendmail restart but no effect. Just returns to the prompt. No errors nothing. I checked if it is running using ps -eaf | grep sendmail, not running :( . I checked the logs... (9 Replies)
Discussion started by: rcmrulzz
9 Replies

5. UNIX for Advanced & Expert Users

Sendmail help for nobody mail box

Hi there all, I got a small tiny problem of not remambering how this worked. I get when I mail to a non existing mailbox I get a return failer to nobody@domain.bla wich will end up in root@domain.bla What I want is to get it to /dev/NULL so I dont get a messege when I mailed to a non existing... (0 Replies)
Discussion started by: draco
0 Replies

6. Shell Programming and Scripting

mail or sendmail ?

1. I need to send emails using a shell script on linux. I want to use the most widespread method (the preferred method). Is one considered deprecated in favor of the other? Which, mail or sendmail ? 2. Now, without trying to favor mail in the first question: How can I include a From: mail... (1 Reply)
Discussion started by: limmer
1 Replies

7. Shell Programming and Scripting

how to know the mail sent status using sendmail

Hi, I am using sendmail command to send mail This is the command i am using cat <filename> | /usr/lib/sendmail -v <emailid> I will put the contents in the file as body of the email I want the subject also to be printed in the email I want to know whether email has been successfully... (1 Reply)
Discussion started by: trichyselva
1 Replies

8. Shell Programming and Scripting

Restrict the mail upon first failure mail.

Hi, I have a application which send mail to the respective client upon success or failure case of file transfer, upon success there is no problem. But in case of failure that application is running again in cron job,so still success of file transfer the client will get the failure notification.... (5 Replies)
Discussion started by: posix
5 Replies

9. UNIX for Dummies Questions & Answers

Does the mail command use sendmail?

The question is, Does the mail comman actually send using sendmail or something else? So I am trying to test if sendmail is set up. I used... cat testemail.txt | mail -s "test mail" myemail@test.com I used my email though I didn't get an error, but didn't get the email either. ... (2 Replies)
Discussion started by: wondernate
2 Replies

10. Proxy Server

How to send mail (sendmail) for php mail()?

PHP mail() function doesn't work. Nor does sendmail: loaded system configuration file /etc/msmtprc ignoring user configuration file /home/xi/.msmtprc: No such file or directory falling back to default account using account default from /etc/msmtprc host = xsi port = 25 proxy host = (not... (1 Reply)
Discussion started by: Xcislav
1 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 04:20 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy