only internal processes ( i.e. those residing on the 172.16.*.* network ) should be sending mail to [EMAIL PROTECTED]
but for whatever reason they always end up in the relay-denied directory. Which is a little frustrating as I think I shoud have everything setup correctly to do this. I'm going to take your suggestion ( it's a cleaner solution than what I've done anyway ), and hopefully it resolves my problem. Thanks for you help on this. cheers, jason. On Fri, 18 Feb 2005 14:38:37 -0000, Daniel Perry <[EMAIL PROTECTED]> wrote: > Yeah, that should work for allowing people on those ips to relay, and send > mails that are forwarded to gmail. However, any mail coming from any other > ip would not get forwarded as it would be not in those ip ranges. ie. if i > sent an email to [EMAIL PROTECTED] via my smtp server it would get > blocked. > > I would that you use authorisation, but set 172.16.*.* as an authorised > address, and remove that mailet. That way: > - anyone can send email to local addresses > - anyone can send email to local addresses that get forwarded > - anyone on 172.16.* can use it as an smtp relay without any authorisation > - anyone outside that ip range trying to relay mail will be forced to > authorise themselves. > > Daniel. > > > -----Original Message----- > > From: Jason Clark [mailto:[EMAIL PROTECTED] > > Sent: 18 February 2005 14:09 > > To: Daniel Perry > > Cc: James Users List > > Subject: Re: queue analysis > > > > > > I don't really want a 'totally open relay', but I would like to > > authorize a few hosts to use it as an smtp server ( similar to the way > > you add an entry in the access file in sendmail ) > > > > I thought that : > > > > <mailet match="RemoteAddrNotInNetwork=127.0.0.1,172.16.*.*" > > class="ToProcessor"> > > <processor> relay-denied </processor> > > <notice>550 - Requested action not taken: relaying denied</notice> > > </mailet> > > > > would allow this to happen. > > > > cheers, > > jason. > > > > > > On Fri, 18 Feb 2005 11:08:40 -0000, Daniel Perry > > <[EMAIL PROTECTED]> wrote: > > > No idea about mail analysis tools, but i think your problem is > > as follows: > > > > > > Mail comes in to: [EMAIL PROTECTED] > > > Gets changed to: [EMAIL PROTECTED] by your forwarder. > > > > > > Gets caught by: (assuming you have it enables) > > > > > > <mailet match="RemoteAddrNotInNetwork=127.0.0.1" class="ToProcessor"> > > > <processor> relay-denied </processor> > > > <notice>550 - Requested action not taken: relaying denied</notice> > > > </mailet> > > > > > > This mailet is there so that any mail put into the system that > > is not for > > > local delivery, and was not put there by localhost will be > > denied relaying. > > > (Note, open relay very very bad!) > > > > > > If you have smtp authentication enabled, then you can safely > > comment out the > > > above, as any mail not for the local machine will have to be > > authorised when > > > it enters james. > > > > > > Daniel. > > > > > > > > > > -----Original Message----- > > > > From: Jason Clark [mailto:[EMAIL PROTECTED] > > > > Sent: 17 February 2005 19:56 > > > > To: [email protected] > > > > Subject: queue analysis > > > > > > > > > > > > Are there any good queue analysis tools I can use to view the status > > > > of my mail queues? > > > > > > > > in postfix the mailq command give some useful information. > > > > > > > > I'm asking because I have a rule setup to: > > > > > > > > <mailet match="[EMAIL PROTECTED]" class="Forward"> > > > > <forwardto>[EMAIL PROTECTED]</forwardto> > > > > </mailet> > > > > > > > > > > > > I have this setup immeadiatley after : <processor name="root"> > > > > > > > > > > > > there's no mention in the log that the mail was forwarded to > > > > [EMAIL PROTECTED], but if I look in the /var/mail/relay-denied, I look > > > > in the file XXXXXXXX.Repository.FileObjectStore and find the > > > > [EMAIL PROTECTED] address. > > > > > > > > Any ideas why that would be? If I could at least get a bit more > > > > information out of the system, at the current time, I don't even have > > > > anything in my logs. > > > > > > > > Cheers, > > > > jason. > > > > > > > > --------------------------------------------------------------------- > > > > 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] > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
