sendmail on FreeBSD


 
Thread Tools Search this Thread
Operating Systems BSD sendmail on FreeBSD
# 1  
Old 01-24-2006
sendmail on FreeBSD

Dear all,

I have been using freebsd 5.4 for 2 months using fetchmail to retrieve mails and using sendmail to send mails.
I have no problem with fetchmail to retrieve mails from pop3 server.
And most of the time I have no problem with sendmail.
But recently I found that I could not send mails to freebsd-stable@freebsd.org.
Actually sendmail is a mail server (not a client), which sends mails directly from my host to other mail servers without relaying and SMTP is a server-to-server protocol, which requires reverse DNS to gain full functionality.
Correct me, if I'm wrong.
I found that rDNS was not supported to the given IP address and PTR record was not found (I don't know so much about them).
So my sendmail can not work with some destination servers.
How to config rDNS? Shall I call ISP?
Does relay help me solve this problem? And how to config it?

More info: I'm on dual stack; dynamic IPv4 and static IPv6 (6bone).
Somebody who experienced this problem please point me out.

Thanks in advance,
Jaguar
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Solaris

Clarifying sendmail configuration - sendmail-client offline

Hi all, I have read about sendmail running as 2 separate process. 1 as a MSP, and the other as the real daemon or MTA. In my current configuration, the sendmail-client is disabled. Both submit.cf and sendmail.cf are left as default untouch I do not specified any mailhost... (3 Replies)
Discussion started by: javanoob
3 Replies

2. UNIX for Advanced & Expert Users

Need help with sendmail email filtering on FreeBSD

Hi All, Sorry, for the double posting. Don't know how to move to a different forum. I am very new to Unix. I have a test server running FreeBSD 10.1 and SendMail 8.14.9. I need to filter incoming emails based on the sender's email address or domain and forward them to another address on a... (1 Reply)
Discussion started by: simplemind
1 Replies

3. UNIX for Advanced & Expert Users

Sendmail questions, SCO 5.0.6 sendmail 8.11.0

I am running SCO 5.0.6 and using sendmail 8.11.0 and having issues with smtp authentication. When trying to send mail the following message will kick back. (reason: 530 5.7.1 Authentication required) 530 5.7.1 Authentication required Not sure what needs to be tweeked in sendmail.cf but I... (1 Reply)
Discussion started by: ziggy6
1 Replies

4. Fedora

FreeBSD

I'm using Windows mostly and the only *nix thing I used during my life was cygwin (I like command line :)). But currently I have (by an occasion) a DVD with latest FreeBSD. I don't know why, but I want to install it... But probably, this OS is too difficult for a beginner. I heard, it's used on... (3 Replies)
Discussion started by: TeenageWerewolf
3 Replies

5. Programming

Application crashes in FreeBSD 7.1 while working ok in FreeBSD 6.3

Hello there, My mulithreaded application (which is too large to represent the source code here) is crashing after installing FreeBSD 7.1-RELEASE/amd64. It worked properly on others machines (Dual Cores with 4GB of RAM - FreeBSD 6.2-RELEASE/i386). The current machine has 2x Core 2 Duo... (1 Reply)
Discussion started by: Seenquev
1 Replies

6. BSD

please help me in FreeBSD

Hi to all, Iam doing a project in Free BSD and i am stuck with a puzzle. Please any one of you clarify my doubt : How to add a mechanism to check the status of the file system which alerts the root user via. email if any single partition is greater than 90% full. This alert should include the... (3 Replies)
Discussion started by: tadakamalla
3 Replies

7. BSD

FreeBSD 5.2.1

I want someone tell me the positives and negatives points of FreeBSD 5.2.1, if someone help me, i thanks a lot! (4 Replies)
Discussion started by: israel
4 Replies

8. UNIX for Dummies Questions & Answers

FreeBSD

What is FreeBSD, who does use Free? (3 Replies)
Discussion started by: cyberangel
3 Replies

9. UNIX for Dummies Questions & Answers

Freebsd 4.5

i am new at unix and am VERY confused about the compression processes. what progs do i need to unzip and zip files? there must be a standard one similar to winzip? (1 Reply)
Discussion started by: Mindscan
1 Replies

10. UNIX for Dummies Questions & Answers

FreeBSD

I am on AOL now,and i am using 56 k,i was gonna install FreeBSD,but i dont know if aol works on BSD,or my modem. Do they work on BSD? (2 Replies)
Discussion started by: kita
2 Replies
Login or Register to Ask a Question
fetchmail_selinux(8)					     SELinux Policy fetchmail					      fetchmail_selinux(8)

NAME
fetchmail_selinux - Security Enhanced Linux Policy for the fetchmail processes DESCRIPTION
Security-Enhanced Linux secures the fetchmail processes via flexible mandatory access control. The fetchmail processes execute with the fetchmail_t SELinux type. You can check if you have these processes running by executing the ps command with the -Z qualifier. For example: ps -eZ | grep fetchmail_t ENTRYPOINTS
The fetchmail_t SELinux type can be entered via the fetchmail_exec_t file type. The default entrypoint paths for the fetchmail_t domain are the following: /usr/bin/fetchmail PROCESS TYPES
SELinux defines process types (domains) for each process running on the system You can see the context of a process using the -Z option to ps Policy governs the access confined processes have to files. SELinux fetchmail policy is very flexible allowing users to setup their fetch- mail processes in as secure a method as possible. The following process types are defined for fetchmail: fetchmail_t Note: semanage permissive -a fetchmail_t can be used to make the process type fetchmail_t permissive. SELinux does not deny access to per- missive process types, but the AVC (SELinux denials) messages are still generated. BOOLEANS
SELinux policy is customizable based on least access required. fetchmail policy is extremely flexible and has several booleans that allow you to manipulate the policy and run fetchmail with the tightest access possible. If you want to allow all daemons to write corefiles to /, you must turn on the daemons_dump_core boolean. Disabled by default. setsebool -P daemons_dump_core 1 If you want to enable cluster mode for daemons, you must turn on the daemons_enable_cluster_mode boolean. Enabled by default. setsebool -P daemons_enable_cluster_mode 1 If you want to allow all daemons to use tcp wrappers, you must turn on the daemons_use_tcp_wrapper boolean. Disabled by default. setsebool -P daemons_use_tcp_wrapper 1 If you want to allow all daemons the ability to read/write terminals, you must turn on the daemons_use_tty boolean. Disabled by default. setsebool -P daemons_use_tty 1 If you want to deny any process from ptracing or debugging any other processes, you must turn on the deny_ptrace boolean. Enabled by default. setsebool -P deny_ptrace 1 If you want to allow all domains to use other domains file descriptors, you must turn on the domain_fd_use boolean. Enabled by default. setsebool -P domain_fd_use 1 If you want to allow all domains to have the kernel load modules, you must turn on the domain_kernel_load_modules boolean. Disabled by default. setsebool -P domain_kernel_load_modules 1 If you want to allow all domains to execute in fips_mode, you must turn on the fips_mode boolean. Enabled by default. setsebool -P fips_mode 1 If you want to enable reading of urandom for all domains, you must turn on the global_ssp boolean. Disabled by default. setsebool -P global_ssp 1 If you want to allow confined applications to run with kerberos, you must turn on the kerberos_enabled boolean. Enabled by default. setsebool -P kerberos_enabled 1 If you want to allow confined applications to use nscd shared memory, you must turn on the nscd_use_shm boolean. Enabled by default. setsebool -P nscd_use_shm 1 MANAGED FILES
The SELinux process type fetchmail_t can manage files labeled with the following file types. The paths listed are the default paths for these file types. Note the processes UID still need to have DAC permissions. cluster_conf_t /etc/cluster(/.*)? cluster_var_lib_t /var/lib/pcsd(/.*)? /var/lib/cluster(/.*)? /var/lib/openais(/.*)? /var/lib/pengine(/.*)? /var/lib/corosync(/.*)? /usr/lib/heartbeat(/.*)? /var/lib/heartbeat(/.*)? /var/lib/pacemaker(/.*)? cluster_var_run_t /var/run/crm(/.*)? /var/run/cman_.* /var/run/rsctmp(/.*)? /var/run/aisexec.* /var/run/heartbeat(/.*)? /var/run/cpglockd.pid /var/run/corosync.pid /var/run/rgmanager.pid /var/run/cluster/rgmanager.sk fetchmail_uidl_cache_t /var/lib/fetchmail(/.*)? /var/mail/.fetchmail-UIDL-cache fetchmail_var_run_t /var/run/fetchmail.* root_t / /initrd sendmail_log_t /var/log/mail(/.*)? /var/log/sendmail.st.* FILE CONTEXTS
SELinux requires files to have an extended attribute to define the file type. You can see the context of a file using the -Z option to ls Policy governs the access confined processes have to these files. SELinux fetchmail policy is very flexible allowing users to setup their fetchmail processes in as secure a method as possible. STANDARD FILE CONTEXT SELinux defines the file context types for the fetchmail, if you wanted to store files with these types in a diffent paths, you need to execute the semanage command to sepecify alternate labeling and then use restorecon to put the labels on disk. semanage fcontext -a -t fetchmail_etc_t '/srv/fetchmail/content(/.*)?' restorecon -R -v /srv/myfetchmail_content Note: SELinux often uses regular expressions to specify labels that match multiple files. The following file types are defined for fetchmail: fetchmail_etc_t - Set files with the fetchmail_etc_t type, if you want to store fetchmail files in the /etc directories. fetchmail_exec_t - Set files with the fetchmail_exec_t type, if you want to transition an executable to the fetchmail_t domain. fetchmail_home_t - Set files with the fetchmail_home_t type, if you want to store fetchmail files in the users home directory. Paths: /root/.fetchmailrc, /home/[^/]*/.fetchmailrc fetchmail_initrc_exec_t - Set files with the fetchmail_initrc_exec_t type, if you want to transition an executable to the fetchmail_initrc_t domain. fetchmail_log_t - Set files with the fetchmail_log_t type, if you want to treat the data as fetchmail log data, usually stored under the /var/log direc- tory. fetchmail_uidl_cache_t - Set files with the fetchmail_uidl_cache_t type, if you want to store the files under the /var/cache directory. Paths: /var/lib/fetchmail(/.*)?, /var/mail/.fetchmail-UIDL-cache fetchmail_var_run_t - Set files with the fetchmail_var_run_t type, if you want to store the fetchmail files under the /run or /var/run directory. Note: File context can be temporarily modified with the chcon command. If you want to permanently change the file context you need to use the semanage fcontext command. This will modify the SELinux labeling database. You will need to use restorecon to apply the labels. COMMANDS
semanage fcontext can also be used to manipulate default file context mappings. semanage permissive can also be used to manipulate whether or not a process type is permissive. semanage module can also be used to enable/disable/install/remove policy modules. semanage boolean can also be used to manipulate the booleans system-config-selinux is a GUI tool available to customize SELinux policy settings. AUTHOR
This manual page was auto-generated using sepolicy manpage . SEE ALSO
selinux(8), fetchmail(8), semanage(8), restorecon(8), chcon(1), sepolicy(8) , setsebool(8) fetchmail 14-06-10 fetchmail_selinux(8)