Sponsored Content
The Lounge What is on Your Mind? Why older administrators prefer sendmail ? Post 302516676 by Perderabo on Sunday 24th of April 2011 08:42:17 PM
Old 04-24-2011
I am an older administrator who still uses Sendmail. I have about 20 years experience with it and I can solve any Sendmail problem I encounter. It was a nasty learning curve and I really don't want to do that again. Sendmail has had more than its share of problems over the years but now it seems pretty stable. It would be possible to switch to postfix but I don't see any reason to do that. Exchange is not even a possible option as far as I know... it doesn't run on Unix. Postfix is the only alternative I know... are there other MTA's available for Unix?

I have to say we Sendmail users probably should not chide Exchange on its security problems though.... people who live in glass houses shouldn't be throwing stones. Smilie
 

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Unix Administrators Schooling

Hi, I was wondering how everyone has gotten good their training in unix. Did anyone specialize in college/university or take a course at a computer institute. At my college you can't really sepcialize in unix, there is only 2 courses. The first unix course is all about shell programming and... (1 Reply)
Discussion started by: Astudent
1 Replies

2. Post Here to Contact Site Administrators and Moderators

Question to Forum Administrators ?

How can i track all my previous, current posts at one single place. How to do that ? Thanks in Advance !!1 (2 Replies)
Discussion started by: dreams5617
2 Replies

3. UNIX for Dummies Questions & Answers

why most of the people prefer linux nowadays y not solaris?

Hi, Anyone plz explain me, Now most of the people prefering linux over solaris. what are the main advantages in linux over solaris. Thanks muthulingaraja (3 Replies)
Discussion started by: muthulingaraja
3 Replies

4. AIX

Create Administrators

I think I've done all that is necessary to configure an account to administer a non-administrative group, but it doesn't work. One thing is strang is that when I log in as root, the group attributes in SMIT are like this: Group NAME Group ID ... (3 Replies)
Discussion started by: laurin1
3 Replies

5. Windows & DOS: Issues & Discussions

Do you prefer Quickbooks, Microsoft or another small business accounting software?

I am starting a small business. I need software to invoice and track payments, track income and expense and basically keep everything organized for tax time. I've read positive and negative on all small business accounting software, so now I'm really confused. Oh, my business is a service one, so I... (3 Replies)
Discussion started by: sunybck
3 Replies

6. What is on Your Mind?

How do you prefer to read books?

Time for a new poll. Just wondering how members in this forum prefer to read books. Paper E-reader Tablet Laptop/Desktop Smartphone Audiobook Not much of a reader Other A poll is added. If you select option: Other, please specify what it is. :b: (14 Replies)
Discussion started by: Yoda
14 Replies
Mail::Milter::Wrapper(3pm)				User Contributed Perl Documentation				Mail::Milter::Wrapper(3pm)

NAME
Mail::Milter::Wrapper - Perl extension for wrappering milter objects SYNOPSIS
use Mail::Milter::Wrapper; my $milter = ...; my $wrapper = new Mail::Milter::Wrapper($milter, &foo); use Sendmail::Milter; ... Sendmail::Milter::register('foo', $wrapper, SMFI_CURR_ACTS); DESCRIPTION
Mail::Milter::Wrapper wraps another milter, allowing for interception of the passed arguments and/or return code of the contained milter. METHODS
new(MILTER, CODEREF[, CALLBACK ...]) Creates a Mail::Milter::Wrapper object. MILTER is the milter to wrap, which may be a plain hash reference or an instance of a hashref object such as "Mail::Milter::Object". CODEREF is the wrapper subroutine. CALLBACKs, if specified, are named callbacks which are needed by the wrapper, even if the contained milter does not use them. The wrapper subroutine will be called with the following arguments, in this order: * reference to the wrapper * name of callback * subroutine reference to call into the wrapped milter * arguments for the callback (>= 0) This subroutine should ALWAYS pass the "close" callback through to the contained milter. Failure to do so may corrupt the contained milter's state information and cause memory leaks. As an example, a simple subroutine which just passes the callback through might be written as: sub callback_wrapper { shift; # don't need $this my $cbname = shift; my $callback_sub = shift; &$callback_sub(@_); } AUTHOR
Todd Vierling, <tv@duh.org> <tv@pobox.com> SEE ALSO
Mail::Milter, Sendmail::Milter perl v5.8.8 2004-02-26 Mail::Milter::Wrapper(3pm)
All times are GMT -4. The time now is 01:44 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy