[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [cobalt-users] relaying denied for inbound mail from another server



Just following-up with Larry, last resort, you can edit /etc/mail/access
manually (needs to put towards the very end of the file) and add the domain

domain.com	RELAY


- Mike


On Thu, 16 Jan 2003, Larry Smith wrote:

> INRE Re: [cobalt-users] relaying denied for inbound mail from another server:
> > > Jan 16 21:46:13 myhostname sendmail[32440]: h0H2kDs32440:
> > > ruleset=check_rcpt, arg1=<damnit@xxxxxxxxxxxxxxxxxxx>,
> > > relay=bay2-dav30.bay2.hotmail.com [65.54.246.87], reject=550 5.7.1
> > > <damnit@xxxxxxxxxxxxxxxxxxx>... Relaying denied.  Please check your mail
> > > first or restart your mail session.
> >
> > This should be clear from the log info above, but the client is not trying
> > to send mail through the server, this is mail inbound to be delivered TO
> > this domain on the server.
> 
> Brandon,
> 
>   Check the virtusertable, access, etc (all tables in /etc/mail) and compare 
> "that" domain against a known working domain.  Generally I find that is where 
> the "error" is when I end up with something like this (most often my typo 
> somewhere along the line).  Unix tends to be "picky" about the name being 
> spelled exactly the same in all locations.....  No, I am not being snide, 
> just providing insight from my experience - I transposed two letters in a 
> "security-key" today and took a whole network down for about 30 minutes.  
> Took three of us looking it over multiple times before it was "noticed" that 
> in a fairly long keystring that "s19" and "s91" are not the same...
> 
> 
> -- 
> Larry Smith
> SysAd ECSIS.NET
> sysad@xxxxxxxxx
> 
> _____________________________________
> cobalt-users mailing list
> cobalt-users@xxxxxxxxxxxxxxx
> To subscribe/unsubscribe, or to SEARCH THE ARCHIVES, go to:
> http://list.cobalt.com/mailman/listinfo/cobalt-users
>