do NOT reply off-list - never, reply below

Am 10.04.2012 06:07, schrieb Jon Miller:
>> Date: Sun, 8 Apr 2012 13:22:51 +0200
>> From: h.rei...@thelounge.net
>> To: postfix-users@postfix.org
>> Subject: Re: mail delivery system message
>>
>> Am 08.04.2012 13:01, schrieb Jon Miller:
>>> If u do not mind letting me know what I did wrong so I can fix it, I would 
>>> appreciate it. 
>>> Like to have the correct format in replying to this group.
>>
>> you could start with NOT write html messages and NOT
>> top post like it was told you several times and you
>> did both again in this reply
>>
>>>>> */etc/hosts*
>>>>> 127.0.0.1 mail.mmtnetworks.com.au mmtlnx
>>>>
>>>> add "localhost" to the above line
>>
>> you did not read this?
>> did you?
>>
>> wonder that you machine works at all after removing
>> the mapping "127.0.0.1 localhost" from /etc/hosts
>> because there are many network things rely on
>> resolving localhost
>>
>> this was the hughe mistake resulting in
>> "localhost: No address associated with hostname"
>>
> Added the localhost back the host line as instructed.  
> system had all sorts of errors from amavis
> 
> mail log:
> Apr 10 10:03:33 mmtlnx amavis[31961]: (31748-04) run_command: child process 
> [31961]: Error closing main::stdin: Bad file descriptor at /usr/sbin/amavisd 
> line 1872, <GEN26> line 215.\n
> Apr 10 10:03:33 mmtlnx amavis[31748]: (31748-04) TROUBLE in check_mail: 
> parts_decode_ext FAILED: parsing file(1) results - missing last 3 results at 
> (eval 79) line 154.
> Apr 10 10:03:33 mmtlnx amavis[31748]: (31748-04) PRESERVING EVIDENCE in 
> /var/spool/amavis/tmp/amavis-20120410T100333-31748
> Apr 10 10:03:33 mmtlnx postfix/smtp[31957]: 1D36926DBD: to=<j...@gmail.com>, 
> relay=127.0.0.1[127.0.0.1], delay=0, status=deferred (host 
> 127.0.0.1[127.0.0.1] said: 451 4.5.0 Error in processing, id=31748-04, 
> parts_decode_ext FAILED: parsing file(1) results - missing last 3 results at 
> (eval 79) line 154. (in reply to end of DATA command))
> 
> This resulted in me trying to put the postfix mail system back to it's 
> original state until I can find out what the issues are since it's regular 
> work as usual.
> So I stopped amavisd and spamd turned off the respective programs in 
> chkconfig and removed the information from the /etc/postfix/master.cf and 
> /etc/postfix/main.cf files and now I have the following error.
> Apr 10 10:21:53 mmtlnx postfix/qmgr[32608]: E5C632677B: 
> to=<jlmil...@mmtnetworks.com.au>, relay=none, delay=35333, status=deferred 
> (delivery temporarily suspended: transport is unavailable)
> 
> Apr 10 10:40:14 mmtlnx postfix/qmgr[32743]: warning: connect to transport 
> smtp-amavis: Connection refused
> 
> After looking this up in google it appears that the transport is having 
> issues, yet the only lines in my etc/postfix/transport file is:
> mail.mmtnetworks.com.au    smtp:[192.168.xxx.xxx]
> mail.jlorenzo.com.au       smtp:[192.168.xxx.xxx]
> 
> Not sure what is going on at this point.  Guess I should mention postfix and 
> the linux OS isn't my strong point (as if it couldn't be guessed by now), old 
> school Novell NetWare and GroupWise Windows OS. So I ask for some patience...
> That said I do have the The Book of Postfix by Ralf Hildebrandt and Patrick 
> Koetter and Julian Mailscanner Book... because I've had to trim down my 
> operation, a lot of the work is residing with me and that is fine.  Just have 
> to put a lot of time in to get my head around how Postfix works and how the 
> anti-virus e-mail protection systems work.  I saw one on a clients site that 
> had Postfix, Mailwatch and MailScanner running and it was what I like to be 
> able to see running on this server,and once I get my head around it I can see 
> it to my customers.
> 
> Ok, now that I have the transport file using the 2 lines above I seem to have 
> some mail coming in now.

after scuh a drastical change i would reboot the whole machine
really - there are cases where this even on unix makes sense
to avoid cachings, forgotten processes not restarted....

127.0.0.1 mail.mmtnetworks.com.au mmtlnx
this whole line is as bad as anything could be

127.0.0.1 is normally only localhost

the machine name himself becomes the /etc/hosts entry
with the ip DNS would resolve to avoid hughe problems
in dns outage

and after this basics you start configure services
maybe you made an additional config error which now gets
visible (if reboot does not help) or you should now
enter "localhost" at the end of this line to not
change "mail.mmtnetworks.com.au <-> 127.0.0.1" mapping
while no longer break "localhost -> 127.0.0.1" mapping

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to