Possible fixes:
1) Swap the order of the RemoteDelivery and RemoteAddrNotInNetwork
matchers
2) Use only ip addresses for RemoteAddressNotInNetwork
If they don't work,
3) Check that DNS can resolve the name of your mailserver to its IP
address.
Charles
fractals wrote:
>
> Hi,
>
> I just got the following message:
>
> <snip>
> The preceeding message was received by us from 194.183.224.155. It could not
> be delivered to the specified recipient, and could not be returned
> to the given sender. It is probably spam. Possibilities include:
>
> 1) 194.183.224.155 is an open SMTP relay.
> 2) 194.183.224.155 the smarthost for an open SMTP relay.
> 3) 194.183.224.155 is relaying correctly for a spamming customer.
> 4) 194.183.224.155 is the spammer's host.
> 5) 194.183.224.155 has a broken mailing list with bad envelope sender.
> 6) 194.183.224.155 will not accept bounces, violates RFC-2505.
> 7) 194.183.224.155 might be infected by an email virus.
>
> Please check the headers carefully and make your own conclusions.
> Check your host's relaying status here:
>
> ORBS http://lookup.orbs.org/verify.php3?address=194.183.224.155
> RSS http://www.mail-abuse.org/cgi-bin/nph-rss?194.183.224.155
> RBL http://www.mail-abuse.org/cgi-bin/lookup?194.183.224.155
>
> We reserve the right to refuse mail from known open relays, undeliverable
> addresses, or domains which refuse bounces. Until then, you may receive
> additional notices. You usually will not receive more than one notice per
> host in a 24-hr period.
>
> How we determined who to contact: If the hostname could be found (PTR),
> and it resolved to 194.183.224.155, it was used to query whois.abuse.net for
> the correct complaint address. Otherwise, the SOA record was used instead
> of the hostname. If this failed, mail was sent to
> postmaster@[194.183.224.155].
> If you feel this message has reached you in error, let us know and we'll
> look into it. Also see http://www.abuse.net.
>
> So that you can see the entire path the message took through our
> system, the original bounce messages are reproduced below.
>
> Hi. This is the qmail-send program at kyle.comstar.net.
> I tried to deliver a bounce message to this address, but the bounce bounced!
> </snip>
>
> I don't get this. Can someone help me. Is it possible to check if James is
> being correctly configured (i.e. is not an open relay)? And how ?
>
> This is the last attempt to configure James so it's not vulnerable to this
> kind of things. It may be incorrect/correct. What do you guys think ? I must
> really get this ! Help !
>
> <!-- Processor CONFIGURATION SAMPLE: transport is a sample custom
> processor for local or remote delivery -->
> <processor name="transport">
> <!-- Is the recipient is for a local account, deliver it
> locally -->
> <mailet match="RecipientIsLocal" class="LocalDelivery">
> </mailet>
> <!-- If the host is handled by this server and it did not
> get locally delivered, this is an invalid recipient -->
> <mailet match="HostIsLocal" class="ToProcessor">
> <processor>error</processor>
> </mailet>
> <!-- Attempt remote delivery using the specified repository
> for the spool, using delay time to retry delivery and the maximum number of
> retries -->
> <mailet match="All" class="RemoteDelivery">
> <outgoing> file://../var/mail/outgoing/ </outgoing>
> <delayTime> 21600000 </delayTime>
> <maxRetries> 5 </maxRetries>
> </mailet>
> <!-- This matcher-mailet pair can prevent relaying... if you
> change this, you risk making your mail
> server an open relay point for spammers .
> NOTE 1: the order of matcher-mailets is important: it must come
> after valid local recipients have
> been dealt with but before any attempt is made to delivery the
> mail remotely.
> NOTE 2: Add your own network, if you want to relay mail
> outwards -->
> <mailet match="RemoteAddrNotInNetwork=127.0.0.1,
> urbanium.tv.*" class="ToProcessor">
> <processor> spam </processor>
> </mailet>
> </processor>
>
> Thanks in advance,
>
> Candide
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
