Sponsored Content
Full Discussion: Sendmail question
Top Forums UNIX for Advanced & Expert Users Sendmail question Post 27708 by AlarIT.Def on Thursday 5th of September 2002 11:51:25 AM
Old 09-05-2002
Error try procmail scripts

You can use procmail config file for run external script. This script can do anything.
Procmail check all mail (outgoing and incoming).
Smilie I think this help you.

Image
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Sendmail question

I'm using sendmail to send a attachment which works good. I send the To Cc Subject Attachment. Question is does anyone know how to put a voting botton in the script when sending the email I want the Approve;Reject button. (2 Replies)
Discussion started by: Dan Savarino
2 Replies

2. UNIX for Advanced & Expert Users

Sendmail user question

Hi All I am trying to deal with a problem. Any suggestions would be helpful! I have sendmail running on a Redhat 8 box and is serving about 75 e-mail accounts. Version Info: OS:Red Hat Linux release 8.0 (Psyche) sendmail-8.12.8-9.80 sendmail-cf-8.12.8-9.80 There are a few users that... (0 Replies)
Discussion started by: skotapal
0 Replies

3. UNIX for Dummies Questions & Answers

Sendmail question

I apologize for asking what I'm sure is a basic question, but I have an automated script that will send a file using sendmail to a list of e-mail accounts. When one or more of those e-mail accounts is bad, it bounces the message back to the account that is executing the script. How can I... (2 Replies)
Discussion started by: Jake513
2 Replies

4. UNIX for Dummies Questions & Answers

Solaris 9 Sendmail Question

hello to all, I'm a newbie to configuring sendmail. I have a solaris 9 server that is also set up as a NIS master server. My 1st question is how do properly set up sendmail to work in conjuntion with NIS users, so I need to set up sendmail in a certain way or can I just set it up normally. Also... (5 Replies)
Discussion started by: GLJ@USC
5 Replies

5. UNIX for Dummies Questions & Answers

Sendmail question

Hello to all, I configured sendmail on a solaris 9 system the same as another server that the one I configured will replace. I transferred all the required files from the original system to the new one as well ar the /var/mail directory. The sendmail daemon is running however when I try to... (4 Replies)
Discussion started by: GLJ@USC
4 Replies

6. Solaris

Sendmail Question

Hi Guys, Quick question re sendmail and mail queues. If the sendmail deamon is stopped i.e. set up to execute and stop at certain intervals from crontab, and the sendmail command is invoked the mail is queued in the clientmqueue directory. Then the next time sendmail is executed the mails... (2 Replies)
Discussion started by: KenLynch
2 Replies

7. Solaris

Sendmail Question

Yes Folks, Quick question. Is it possible to send multiple attachments with sendmail and if so how? Thinking here in terms of sending multiple .pdf files as attachments. I can do it with one but how do I do it for multiples. Slainte, (1 Reply)
Discussion started by: KenLynch
1 Replies

8. Solaris

sendmail question

Hello all, On my solaris 9 I have this process running smmsp 29138 1 0 Apr 17 ? 0:00 /usr/lib/sendmail -Ac -q15m root 29137 1 0 Apr 17 ? 0:00 /usr/lib/sendmail -q15m if i use the command /usr/bin/mconnect connecting to host localhost (127.0.0.1), port... (0 Replies)
Discussion started by: Hugues
0 Replies

9. UNIX for Advanced & Expert Users

sendmail config question

I configured Solaris 10 server to send all mails to our exchange server via D{MTAHost} in submit.cf. but now I don't get internal messages like cron output. what can I do? (2 Replies)
Discussion started by: amozofer
2 Replies

10. BSD

OpneBSD 5.3 sendmail question

I have a basic OpenBSD 5.3 system installed as 64 bit on an old Sun Blade 100. Yes, it does work fine! It has XFCE, R, Firefox 3.6, nano installed. I have to say that 5.3 is much better than 5.0 or 5.1, and R works very well on it. Anyway, onto the main question. Could someone provide me with... (2 Replies)
Discussion started by: RichardET
2 Replies
KERNEL-IMG.CONF(5)					      Debian GNU/Linux manual						KERNEL-IMG.CONF(5)

NAME
kernel-img.conf - site wide configuration file for kernel image packages SYNOPSIS
/etc/kernel-img.conf DESCRIPTION
The file /etc/kernel-img.conf is a simple file looked at by the kernel image post installation process to allow local options for handling some aspects of the installation, overriding the defaults built into the image itself. The format of the file is a simple VAR=VALUE pair. Boolean values may be specified as Yes, True, 1, and No, False, 0, and are case insensi- tive. This file is automatically created by the installation script in certain circumstances. At the moment, the user modifiable variables supported are: postinst_hook DEPRECATED: Set this variable to a script to be executed during installation. The path can be a relative path if the script lives in a safe path -- that is, if it lives in /bin, /sbin, /usr/bin, or /usr/sbin, or must be an absolute path instead. Before calling this script, the env variable STEM shall be set to the value of the --stem argument (or the default value, linux), and KERNEL_PACK- AGE_VERSION shall be set to the version of the kernel-package that created the package. This script shall be called with two argu- ments, the first being the version of the kernel image, and the second argument being the location of the kernel image itself. Errors in the script shall cause the postinst to fail. Since debconf is in use before the script is called, this script should issue no diagnostic messages to stdout -- while the postinst does call db_stop, debconf does not restore stdout, so messages to stdout disappear. An example script for grub users is present in /usr/share/doc/kernel-package/ directory. This script is run after the scripts in /etc/kernel/postinst.d directory. postrm_hook DEPRECATED: Set this variable to a script to be executed in the postrm (that is, after the image has been removed) after all the remove actions have been performed. The path can be a relative path if the script lives in a safe path -- that is, if it lives in /bin, /sbin, /usr/bin, or /usr/sbin, or must be an absolute path instead. The environment variable KERNEL_PACKAGE_VERSION shall be set to the version of the kernel-package that created the package. This script shall be called with two arguments, the first being the version of the kernel image, and the second argument being the location of the kernel image itself. Errors in the script shall produce a warning message, but shall be otherwise ignored. Since debconf is in use before the script is called, this script should issue no diagnostic messages to stdout -- while the postinst does call db_stop, debconf does not restore stdout, so messages to stdout disappear. This script is run after the scripts in /etc/kernel/postrm.d directory. preinst_hook DEPRECATED: Set this variable to a script to be executed before the package is unpacked, and can be used to put in additional checks. The path can be a relative path if the script lives in a safe path -- that is, if it lives in /bin, /sbin, /usr/bin, or /usr/sbin, or must be an absolute path instead. The environment variable KERNEL_PACKAGE_VERSION shall be set to the version of the kernel-package that created the package. This script shall be called with two arguments, the first being the version of the kernel image, and the second argument being the location of the kernel image itself. This script is run after the scripts in /etc/ker- nel/preinst.d directory. prerm_hook DEPRECATED: Set this variable to a script to be executed before the package files are removed (so any added files may be removed) . The path can be a relative path if the script lives in a safe path -- that is, if it lives in /bin, /sbin, /usr/bin, or /usr/sbin, or must be an absolute path instead. The environment variable KERNEL_PACKAGE_VERSION shall be set to the version of the kernel-pack- age that created the package. This script shall be called with two arguments, the first being the version of the kernel image, and the second argument being the location of the kernel image itself. Errors in the script shall cause the prerm to fail. Since debconf is in use before the script is called, this script should issue no diagnostic messages to stdout -- while the postinst does call db_stop, debconf does not restore stdout, so messages to stdout disappear. This script is run after the scripts in /etc/ker- nel/prerm.d directory. src_postinst_hook DEPRECATED: Unlike the other hook variables, this is meant for a script run during the post inst of a docs, headers or a source package. Using this hook for the headers package is now being deprecated, at some point the headers post install script shall only run the header_postinst_hook. The path can be a relative path if the script lives in a safe path -- that is, if it lives in /bin, /sbin, /usr/bin, or /usr/sbin, or must be an absolute path instead. The environment variable KERNEL_PACKAGE_VERSION shall be set to the version of the kernel-package that created the package. This script shall be called with two arguments, the first being the name of the package being installed (could be kernel source or headers), and the second argument being the version of the package being installed. Errors in the script shall cause the postinst to fail. This script is run after the scripts in /etc/ker- nel/src_postinst.d directory. header_postinst_hook DEPRECATED: Unlike the other hook variables, this is meant for a script run during the post inst of a headers package only. The path can be a relative path if the script lives in a safe path -- that is, if it lives in /bin, /sbin, /usr/bin, or /usr/sbin, or must be an absolute path instead. The environment variable KERNEL_PACKAGE_VERSION shall be set to the version of the kernel-package that created the package. This script shall be called with two arguments, the first being the name of the package being installed, and the second argument being the version of the package being installed. Errors in the script shall cause the postinst to fail. This script is run after the scripts in /etc/kernel/header_postinst.d directory. clobber_modules If set, the preinst shall silently try to move /lib/modules/version out of the way if it is the same version as the image being installed. Use at your own risk. This variable is unset by default. warn_reboot This variable can be used to turn off the warning given when installing a kernel image which is the same version as the currently running version. If the modules list is changed, the modules dependencies may have been changed, and the modules for the new kernel may not run correctly on the running kernel if the kernel ABI has changed in the meanwhile. It is a good idea to reboot, and this is a note to remind you. If you know what you are doing, you can set this variable to no. This variable is set by default. relink_build_link This option manipulates the build link created by recent kernels. If the link is a dangling link, and if a the corresponding kernel headers appear to have been installed on the system, a new symlink shall be created to point to them. The default is to relink the build link (YES). force_build_link This option manipulates the build link created by recent kernels. If the link is a dangling link, a new symlink shall be created to point to kernel headers data in /usr/src, whether they have been installed or not. The default is unset, we don't create potentially dangling symlinks by default. relink_src_link This option manipulates the source link created by recent kernels. If the link is a dangling link it is deleted at install time. The default is to relink (delete) the source link (YES). silent_modules This option has been put in for the people who are vastly irritated on being warned about preexisting modules directory /lib/mod- ules/$version. That directory may belong to an old or defunct kernel image package, in which case problems may arise with leftover modules in that directory tree, or the directory may legitimately exist due to a independent modules package being installed for this kernel version that has already been unpacked. In this latter case the existence of the directory is benign. If you set this variable, you shall no longer be given a chance to abort if a preexisting modules directory /lib/modules/$version is detected. This is unset by default. ignore_depmod_err If set, does not prompt to continue after a depmod problem in the postinstall script. This facilitates automated installs, though it may mask a problem with the kernel image. A diagnostic is still issued. This is unset be default. FILES
The file described here is /etc/kernel-img.conf. SEE ALSO
make(1), make-kpkg(1), kernel-pkg.conf(5), The GNU Make manual BUGS
There are no bugs. Any resemblance thereof is delirium. Really. AUTHOR
This manual page was written by Manoj Srivastava <srivasta@debian.org>, for the Debian GNU/Linux system. Debian Aug 20 2009 KERNEL-IMG.CONF(5)
All times are GMT -4. The time now is 12:49 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy