I take that as good advice - i appreciate it.
I reckon i could do that.
from your earlier wisdom
might i be correct in think that i need to customize
# echo "{submission.server.com}:587 {user:passwd}" \
to something like
# echo "{smtp.fuse.net}:587 {myFuseUser:myFuseUserPasswd}" \
and
relayhost = {submission.server.com}:587
to
relayhost = {smtp.fuse.net}:587
where smtp.fuse.net = the (dsl) isp mailServer - Not my local machine
taster.local
and
myFuseUser:myFuseUserPasswd = a valid user /psswd on that server
Thanks!
jims
Eric Shubert wrote:
Postfix lets you easily control this on the sender's end. See the
myorigin parameter. That's where the proper fix is.
FWIW, sendmail is terribly antiquated. Reminds me of assembler macros.
If you would have implemented postfix (days ago), you'd be done with
this by now.
Jim Shupert wrote:
Friends,
here is the result of a qmlog smtp -t 100 ( i sifted through that
for a reference to the 'other' machine )
09-02 12:35:46 CHKUSER rejected sender: from <[email protected]::>
remote <mail-out2.fuse.net:unknown:
216.68.8.171> rcpt <> : invalid sender MX domain
09-02 12:35:58 CHKUSER rejected sender: from <[email protected]::>
remote <mail-out2.fuse.net:unknown:
216.68.8.171> rcpt <> : invalid sender MX domain
so my Q might be ::: can I make CHKUSER allow the sender of
[email protected].
maybe if I recompile CHKUSER ( i am thinking much like I recompiled
it to allow blackberriness (\) )
might that work? -- do you think? and what would i 'say' when i
recompile chckuser?
what i am doing : I have a simple machine on a DSL ( fuse is ma bell
here ) on that machine I am croning a perl that monitors several
websites ( from *outside* my 2-T1 connections ) and that machine
(taster) is running sendMail that sends -- upon alarm an email to the
fuse mail server
and of course. My QMT does the chckuser and sees a conflict between
[email protected] from mail-out2.fuse.net ... or that is what i
*think is happening. note changing my domain (hosts file) on taster
to taster.fuse.net didn't work.
thanks
Eric Shubert wrote:
In a typical configuration, it would be hitting your smtp server
port 25, which you would see in your smtp log:
# qmlog -lc fuse\.net
Jim Shupert wrote:
Friends, :: an update ::
I have retained the postfix how to in case i need it....
I got my thing working via sendmail ( 'cause i was close ) and
using the providers mailserver.( smtp.fuse.net )
basically i am able to monitor our servers ( like I am outside the
network ) via this dsl
and I can send an email that I can get on my mobile device
so i can get to my fuse account ( the dsl Ma Bell folks here in
cincy )
and I have THAT account set to forward mail to my pps account (
that uses a qmail toaster mail server )
I reckon -- qmail sees that as , well ... i do not know -- but it
never gets to my inside
( but , i am basically happy - cause I can have my desk clinet also
looking at my fuse and --it also rings in my pocket....so..it is
workable )
I was wondering what logs I might look at to see if this 'fuse
relay ' is hitting my qmail toaster server?
I reckon I will never get the messages to - just come through.
Thanks
Eric Shubert wrote:
Hey Jim,
I just happened to be doing this today, so here are my notes on
how to set up postfix to send mail out from a generic server, like
for logwatch output and such (that would otherwise go to
r...@localhost).
{replace what's in braces, and remove braces}
# yum install postfix
# yum remove sendmail
# cd /etc/pki/tls/certs
# make postcert.pem
# echo "{submission.server.com}:587 {user:passwd}" \
> /etc/postfix/sasl_passwd
# chmod 600 /etc/postfix/sasl_passwd
# chown root:root /etc/postfix/sasl_passwd
# postmap /etc/postfix/sasl_passwd
Edit /etc/aliases if desired, then do newaliases command:
root: sysadmin
# newaliases
Edit /etc/postfix/main.cf, changing these from the default values
(this was CentOS5.3):
myorigin = $mydomain
#mydestination =
mynetworks_style = host
relayhost = {submission.server.com}:587
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
smtp_sasl_security_options =
smtp_use_tls = yes
smtp_tls_CAfile = /etc/pki/tls/certs/postcert.pem
smtp_tls_session_cache_database =
btree:/var/run/smtp_tls_session/cache
# service postfix start
# chkconfig postfix on
That should do it.
Note, this configuration relies on hostname being set correctly
for your domain. If it's not, you'll need to change the myorigin
variable appropriately.
Please let us know whether or not this works for you.
Eric Shubert wrote:
That's not telling us much. I sure don't know, and don't care to
know sendmail. If you'd try using postfix again we might be of
more help. For what you need, postfix isn't a bad choice.
Certainly better than sendmail.
Jim Shupert wrote:
it is centos 4.7 running sendmail ( what came with it ) I
started to install postfix because I am a bit more farmilur with
that than send mail.
Postfix was what i was using before i found -- the best
mailserver solution of qmailtoaster...
anyways
I can email with a client ( evolution ) and that does come through
even though I am using sendmail. the smtp server is one from the
isp - a dsl modem etc.
I can command line send mail ( sendmail ) to a gmail account -
but not mu internal domain
I was wondering about MX or Reverse DNS -
here is the full header of the client ( evolution ) email that
does come through
X-Account-Key: account2
X-UIDL: 1251407849.13380.sifter.pps-inc.com,S=1797
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
X-Mozilla-Keys:
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: (qmail 13378 invoked by uid 89); 27 Aug 2009 21:17:29
-0000
Received: by simscan 1.3.1 ppid: 13371, pid: 13373, t: 0.1506s
scanners: attach: 1.3.1 clamav: 0.95.2
/m:51/d:9450 spam: 3.2.5
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on
sifter.pps-inc.com
X-Spam-Level:
X-Spam-Status: No, score=0.1 required=4.0 tests=BAYES_50,RDNS_NONE
autolearn=no version=3.2.5
Received: from unknown (HELO mail-out1.fuse.net) (216.68.8.175)
by sifter.pps-inc.com with SMTP; 27 Aug 2009 21:17:29 -0000
Received-SPF: pass (sifter.pps-inc.com: SPF record at
zoomtown.com designates 216.68.8.175 as permitted sender)
Return-Path: <[email protected]>
X-CNFS-Analysis: v=1.0 c=1 a=_0eaEcvx3pEA:10
a=Qu4MKinT0AcdTVkTjP4A:9 a=Er_04BcmBtQYP8STtf3EGQ6vdGwA:4
X-CM-Score: 0
X-Scanned-by: Cloudmark Authority Engine
Authentication-Results: ecout1 [email protected];
spf=unknown
Authentication-Results: ecout1 [email protected];
auth=pass (LOGIN)
Received-SPF: error (ecout1: 208.102.118.162 is neither
permitted nor denied by domain of zoomtown.com
Received: from [208.102.118.162] ([208.102.118.162:50880]
helo=[172.17.0.10])
by ecout1 (envelope-from <[email protected]>)
(ecelerity 2.2.2.43 r()) with ESMTPA
id C1/DC-11180-8E7F69A4; Thu, 27 Aug 2009 17:17:29 -0400
Subject: jupiter999
From: ppsBnet <[email protected]>
Reply-To: [email protected]
To: [email protected]
Organization: theppsgroup
Date: Thu, 27 Aug 2009 17:13:02 -0400
Message-Id: <[email protected]>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.3 (2.12.3-8.el5_2.3)
thanks
------------------------------------------------------------------------
No virus found in this incoming message.
Checked by AVG - www.avg.com Version: 8.5.409 / Virus Database:
270.13.75/2340 - Release Date: 09/01/09 20:03:00
------------------------------------------------------------------------
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.409 / Virus Database: 270.13.75/2341 - Release Date: 09/02/09 05:50:00
