Read the article to know more about Sendmail Genericstable. At Bobcares, with our Server Management Service, we can handle the Sendmail issues.
Sendmail Genericstable: Introduction
The Sendmail alias handling system includes the “genericstable” feature, which is in conjunction with the “generics” function.
Sendmail Genericstable: Working
1. Sendmail is frequently set up to use local user accounts (such as "username@localhost"
or "username@yourdomain.local"
) for sending emails. It’s possible that these addresses are inappropriate to use as sender addresses in outgoing emails.
2. We can specify a mapping between local sender addresses and desired sender addresses using the “genericstable”. This file contains this mapping.
3. The mapping will be in a text file with the name “genericstable.” A mapping between a local user address to a desired sender address is specified for each line in this file.
4. We must convert the file into a Sendmail-compatible hash map file after creating or modifying it:
hash genericstable < genericstable
5. Change the mapping in the Sendmail setup file to use it when rebuilding sender addresses. Add the following lines in the Sendmail setup file:
FEATURE(`genericstable', `hash -o /etc/mail/genericstable.db')dnl
GENERICS_DOMAIN(`example.local')dnl
Change “example.local” to the domain that best suits the setup.
6. In order for changes to the Sendmail setup to take effect, we must restart Sendmail.
[Need to know more? Get in touch with us if you have any further inquiries.]
Conclusion
With the above setup, Sendmail can check the “genericstable” mapping whenever sending an outgoing email to see if the sender address corresponds to any local user address. If it finds a match, the mapping’s related address will be used in place of the sender’s address.
PREVENT YOUR SERVER FROM CRASHING!
Never again lose customers to poor server speed! Let us help you.
Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.
var google_conversion_label = "owonCMyG5nEQ0aD71QM";
0 Comments