On Tue, Nov 16, 2010 at 01:47:26PM -0500, Victor Duchovni wrote:
> On Tue, Nov 16, 2010 at 06:39:49PM +0000, Chris G wrote:
>
> > > It sounds like you have both Postfix and Sendmail on the same systems,
> > > and perhaps confused about which MTA is handling which mail.
> >
> > When I say 'sendmail' I just mean the postfix executable of that name
> > which is used by mutt (amoung others) to send mail from the system.
> > I have enver had 'real' sendmail installed on these systems.
>
> What logs on the client provide supporting evidence that Postfix
> handled the mail from Mutt? That's the first place to look. Not on
> the receiving server. Please post the client-side logs.
>
Here's what appears in mail.log when I send a mail from mutt on
dps.zbmc.eu which is 192.168.1.2 :-
Nov 16 18:53:31 dps postfix/pickup[2366]: A6AC610034B: uid=1000 from=<chris>
Nov 16 18:53:31 dps postfix/cleanup[2707]: A6AC610034B:
message-id=<[email protected]>
Nov 16 18:53:31 dps postfix/qmgr[1124]: A6AC610034B:
from=<[email protected]>, size=459, nrcpt=1 (queue active)
Nov 16 18:53:32 dps postfix/smtp[2709]: A6AC610034B:
to=<[email protected]>, relay=zbmc.eu[84.45.228.40]:25, delay=0.49,
delays=0.31/0.01/0.04/0.13, dsn=5.7.1, status=bounced (host
zbmc.eu[84.45.228.40] said: 554 5.7.1 <[email protected]>: Relay access denied
(in reply to RCPT TO command))
Nov 16 18:53:32 dps postfix/cleanup[2707]: 22BF9100354:
message-id=<[email protected]>
Nov 16 18:53:32 dps postfix/bounce[2710]: A6AC610034B: sender non-delivery
notification: 22BF9100354
Nov 16 18:53:32 dps postfix/qmgr[1124]: 22BF9100354: from=<>, size=2280,
nrcpt=1 (queue active)
Nov 16 18:53:32 dps postfix/local[2711]: 22BF9100354:
to=<[email protected]>, relay=local, delay=0.33,
delays=0.27/0.01/0/0.05, dsn=2.0.0, status=sent (delivered to command:
procmail -a "$EXTENSION")
Nov 16 18:53:32 dps postfix/qmgr[1124]: A6AC610034B: removed
Nov 16 18:53:32 dps postfix/qmgr[1124]: 22BF9100354: removed
I'm pretty certain that the message is only getting as far as
mws.zbmc.eu (which is the relayhost that dps.zbmc.eu should be using)
and it there that it's being rejected.
> > > Wrong question. The right question is:
> > >
> > > - Now that I know that the traffic is coming from the reported
> > > IP address, how do I identify the sending client and either
> > > allow it to send from that IP or reconfigure it to use a different
> > > IP address.
> >
> > I'm pretty sure I know the client, it's dps.zbmc.eu, and I want to
> > "reconfigure it to use a different IP address.". I think that's the
> > question I'm looking for an answer to.
>
> Well, this is a client-side question, and you are looking on the server.
> So now focus on the client.
>
> --
> Viktor.
--
Chris Green
