William L. Maltby wrote:
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Well, I tried you suggestion to my previous email, and they didn't work. Now, I'm sure it's because I'm not experienced in sendmail.
Mark
On Fri, 2006-07-21 at 08:24 -0700, Mark Schoonover wrote:
William L. Maltby wrote:
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Well, I tried you suggestion to my previous email, and they didn't work. Now, I'm sure it's because I'm not experienced in sendmail.
Me too! But I did some reading, looked at things,... and do have an extensive *general* background. So there's probably some other piece of the puzzle that's not right or is different.
There's lots of experienced folks here though. I bet if you posted in the form of some background, a starting description of the pertinent components in your setup, snippets of logs, etc. they would jump in and help.
At least, that's been my observation. Fridays may be the exception though.
I'll also try and help, within my limits.
Mark _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Fri, 2006-07-21 at 08:24 -0700, Mark Schoonover wrote:
William L. Maltby wrote:
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Well, I tried you suggestion to my previous email, and they didn't work.
Are you sure? When I first tried, I thought so too! I had forgotten than sendmail has a feature, "Irritate the user while testing", that delays repeat attempts to contact the remote. It is a progressive delay.
Have you done a find on the /var/spool/mqueue? From and end-user POV, "It's broken" may be proper. From and admin/config, it maybe be "Which part is broken?" is proper. There's sendmail itself, it has a mail submission portion, a queue manager and all depends on name/IP resolution (bind usually). This implies a lot opportunities for configs to let you down.
Now, I'm sure it's because I'm not experienced in sendmail.
There is only one *experienced* sendmailer in the world! ;-) He justifiably stays in hiding I think!
Mark
<snip sig stuff>
On 7/21/06, Mark Schoonover schoon@amgt.com wrote:
Now, I'm sure it's because I'm not experienced in sendmail.
TTL, you don't have to be :)
Use WLM's simple way or use the recipe at http://www.postfix.org/STANDARD_CONFIGURATION_README.html#null_client (see below the sig for the relevant excerpt).
Postfix isn't H E A V Y (quite the contrary); if you like, I can post
ps auxw | grep -i sendmail
and
ps auxw | grep -i postfix
so you can see for yourself what is H E A V Y and what is lite.
Plus, you keep open the options to corral the folks on your LAN so you won't have to worry about getting off the top few lines at senderbase.org.
rgds/ldv
http://www.postfix.org/STANDARD_CONFIGURATION_README.html#null_client says in part:
In this example we assume that the Internet domain name is "example.com" and that the machine is named "nullclient.example.com". As usual, the examples show only parameters that are not left at their default settings.
1 /etc/postfix/main.cf: 2 myorigin = $mydomain 3 relayhost = $mydomain 4 inet_interfaces = 127.0.0.1 5 local_transport = error:local delivery is disabled 6 7 /etc/postfix/master.cf: 8 Comment out the local delivery agent entry
Translation:
*
Line 2: Send mail as "user@example.com" (instead of "user@nullclient.example.com"), so that nothing ever has a reason to send mail to "user@nullclient.example.com". *
Line 3: Forward all mail to the mail server that is responsible for the "example.com" domain. This prevents mail from getting stuck on the null client if it is turned off while some remote destination is unreachable. *
Line 4: Do not accept mail from the network. *
Lines 5-8: Disable local mail delivery. All mail goes to the mail server as specified in line 3.
On Fri, 21 Jul 2006 13:35:32 -0500 "Larry Vaden" vaden@texoma.net wrote:
Postfix isn't H E A V Y (quite the contrary); if you like, I can post
ps auxw | grep -i sendmail
and
ps auxw | grep -i postfix
so you can see for yourself what is H E A V Y and what is lite.
Actually the problem is not whether Postix is lite or heavy, the problem is the way people configure Postfix and make it do too many thing such as RegEx matching... then Postfix will gobble has many resources it can.