OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
RE: no delivering to procmail

From: MrC (lists-postfixcappella.us)
Date: Tue Mar 06 2007 - 14:41:41 CST


> > Show logs and "postconf -n" output (NOT "postconf") of a
> misdelivered
> > message.
>
> Oh, sorry. No problem.
> This is my postconf -n output:
>
> ...
>
> Does this help a little more?
> Regards, Christophorus
>

It appears you are relaying to yourself on the wrong port, and thus looping:

Mar 6 21:07:45 communicator postfix/smtp[17247]: A6DBE362F8:
to=<dhlpodsemanticedge.com>, relay=127.0.0.1[127.0.0.1], delay=1,
status=sent (250 2.6.0 Ok, id=17307-01, from MTA: 250 Ok: queued as
E3FA53AB1A)

Shouldn't this be:

    127.0.0.1[127.0.0.1]:10024

It appears you have a mail loop:

Mar 6 21:07:39 communicator amavis[17028]: (17028-10) Passed CLEAN,
[62.169.3.87] <Navigatorsemanticedge.com> -> <dhlpodsemanticedge.com>,
Message-ID: <19364989.3271173211640513.JavaMail.SYSTEMDHL-DM-1-1>, Hits: -

...

Mar 6 21:07:45 communicator amavis[17307]: (17307-01) Passed CLEAN,
[62.169.3.87] <Navigatorsemanticedge.com> -> <dhlpodsemanticedge.com>,
Message-ID: <19364989.3271173211640513.JavaMail.SYSTEMDHL-DM-1-1>, Hits: -

A mailq should show plenty of messages...

MrC