08-13-2009
Restrictive mail implementation problem
Any tips on this problem will be greatly appreciated.
I need to build a Linux mailserver, that needs to meet the following requirements:
- 3 usergroups: endusers, supervisors, and management
- Endusers will be on a local Linux mailserver
- Supervisors and management will be on Google Apps
- Endusers must not be able to e-mail each other or anyone in general on the Internet, but should not be able to receive e-mail from the Internet at large.
- Endusers only can e-mail supervisors and management, and receive e-mail from supervisors and management
I'm leaning towards a Linux + Postfix server, and looking through the Postfix documentation for creative use of Relay directives, and through Sourceforge for some communication package that fits the bill. Something like RT would just about fit the bill, or even a creative BB implementation.
How could I build this?
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
Below a try to send an email to a local user can be seen. I can NOT send e-mail anywhere, but I receive email perfectly.
<pre>
isgsi01(root)10: mail aris < /home/aris/mail2send
dbm map "Alias0": unsafe map file /etc/mail/aliases: No such file or directory
</pre>
..... but the... (3 Replies)
Discussion started by: guest100
3 Replies
2. UNIX for Dummies Questions & Answers
When I try to use the CLI mail, I get the following error. What's wrong?
Welcome to Darwin!
% mail root
Subject: test
test
.
EOT
% /etc/mail/sendmail.cf: line 81: fileclass: cannot open /etc/mail/local-host-names: Group writable directory
Do I just need to change the... (1 Reply)
Discussion started by: chenly
1 Replies
3. OS X (Apple)
i have mac os x 2.2 jaguar and Mail wont open any links? When i click on them it just does nothing. does anybody know why/how to fix it? please help me..
thanks, blip (4 Replies)
Discussion started by: Blip
4 Replies
4. Linux
Hello,
When I try this
echo “This will go into the body of the mail.” | mail -s “Hello world” e.tekin@abc.com
I m having this problem
Feb 8 09:05:41 xxx sendmail: n1884jFR027821: from=<root@xxx>, size=731, class=0, nrcpts=1, msgid=<200902080804.n1884
j3U025399@xxx>, proto=ESMTP,... (7 Replies)
Discussion started by: sunsail
7 Replies
5. Red Hat
Hi,
i've a redhat linux 9 upadated by redhat from 7 version to 9 version. A couple of days ago i was a problem with my mail, in other words i'm not able to get any email nor to send any email. I've a proxy configuration and i tried to set iptables in order to verify the port. The 110,255 and 995... (1 Reply)
Discussion started by: pintalgi
1 Replies
6. UNIX for Advanced & Expert Users
I am uxing HP UX mailx, I want to send mail with:
1) to list
2) cc list
3) sender address
4) mail body
5) subject
6) attachment
I am using :
(cat cc_list; cat mail_body; ux2dos file_1 | uuencode attachment.txt)|mailx -m -s "subject" -r sender@abc.com recepient@abc.com
cc_list... (2 Replies)
Discussion started by: gautamadak
2 Replies
7. Shell Programming and Scripting
I have a file with most of the lines formatted in this way:
testaccount:D#%G%^V&:MeMyselfandI:memyselfandi@somesite.com:11/242012:192.168.1.1,192.168.1.2,192.168.1.3,192.168.1.4,192.168.1.5
There are a few lines with:
... (2 Replies)
Discussion started by: metallica1973
2 Replies
8. Solaris
hi all
please help me with the following
i am new to solaris
i want to umount /test mount point and make it 8gb each i.e. /test1 and /test2 and using SVM wants to make RAID5
bash-3.00# df -h
Filesystem size used avail capacity Mounted on
/dev/dsk/c0t0d0s0 6.9G ... (2 Replies)
Discussion started by: nikhil kasar
2 Replies
9. Post Here to Contact Site Administrators and Moderators
I am trying to write a shell script that generates links to a website. Not to spam it. The code necessarily adds things that are links, and so get rejected.
In the end I have up, and have not written the post.
Whilst I apprecaite you want to avoid spam, could you not implement something so... (1 Reply)
Discussion started by: drkirkby
1 Replies
LEARN ABOUT SUSE
exim_lock
EXIM_LOCK(8) System Manager's Manual EXIM_LOCK(8)
NAME
exim_lock - Mailbox maintenance
SYNOPSIS
exim_lock [options]mailbox-file
DESCRIPTION
The exim_lock utility locks a mailbox file using the same algorithm as Exim. For a discussion of locking issues, see section 25.2.
exim_lock can be used to prevent any modification of a mailbox by Exim or a user agent while investigating a problem. The utility requires
the name of the file as its first argument. If the locking is successful, the second argument is run as a command (using C's "system()"
function); if there is no second argument, the value of the SHELL environment variable is used; if this is unset or empty, /bin/sh is run.
When the command finishes, the mailbox is unlocked and the utility ends. The following options are available:
-fcntl Use "fcntl()" locking on the open mailbox.
-interval
This must be followed by a number, which is a number of seconds; it sets the interval to sleep between retries (default 3).
-lockfile
Create a lock file before opening the mailbox.
-mbx Lock the mailbox using MBX rules.
-q Suppress verification output.
-retries
This must be followed by a number; it sets the number of times to try to get the lock (default 10).
-timeout
This must be followed by a number, which is a number of seconds; it sets a timeout to be used with a blocking "fcntl()" lock. If it
is not set (the default), a non-blocking call is used.
-v Generate verbose output.
If none of -fcntl, -lockfile or -mbx are given, the default is to create a lock file and also use "fcntl()" locking on the mailbox,
which is the same as Exim's default. The use of -fcntl requires that the file be writable; the use of -lockfile requires that the
directory containing the file be writable. Locking by lock file does not last for ever; Exim assumes that a lock file is expired if
it is more than 30 minutes old.
The -mbx option is mutually exclusive with -fcntl. It causes a shared lock to be taken out on the open mailbox, and an exclusive
lock on the file /tmp/.n.m where n and m are the device number and inode number of the mailbox file. When the locking is released,
if an exclusive lock can be obtained for the mailbox, the file in /tmp is deleted.
The default output contains verification of the locking that takes place. The -v option causes some additional information to be
given. The -q option suppresses all output except error messages.
A command such as
exim_lock /var/spool/mail/spqr
runs an interactive shell while the file is locked, whereas
exim_lock -q /var/spool/mail/spqr <<End
<some commands>
End
runs a specific non-interactive sequence of commands while the file is locked, suppressing all verification output. A single command can
be run by a command such as
exim_lock -q /var/spool/mail/spqr "cp /var/spool/mail/spqr /some/where"
Note that if a command is supplied, it must be entirely contained within the second argument - hence the quotes.
BUGS
This manual page needs a major re-work. If somebody knows better groff than us and has more experience in writing manual pages, any patches
would be greatly appreciated.
SEE ALSO
exim(8), /usr/share/doc/exim4-base/
AUTHOR
This manual page was stitched together from spec.txt by Andreas Metzler <ametzler at downhill.at.eu.org>, for the Debian GNU/Linux system
(but may be used by others).
March 26, 2003 EXIM_LOCK(8)