On Fri, Oct 26, 2012 at 04:09:15PM -0600, RYAN M. vAN GINNEKEN wrote: > Hello I am tring to get incoming email relay working using a > transport file first off is this the correct way to get email to go > from some...@gmail.com - using gmail could be anywhere >>> > m...@tryingtogetincomingrelayworking.com on mx2.mail.com - my relay > server >>> me@tryingtogetincomingrelayworking on mx1.mail.com - my > main mail server
Sic semper mungis, as the ancient Romans might have said if they had our acronym "MUNG": Mash Until No Good. Tryingtogetincomingrelayworking.com does not exist, and you quite surely are not mail.com. > Something is going wrong and i keep getting this error on the relay > server, obviously it is stopping mail and i get nothing in the logs > for the main server. Please help > > Relay access denied; from=<me.myem...@gmail.com> > to=<m...@tryingtogetincomingrelayworking.com> proto=ESMTP > helo=<mail-vb0-f46.google.com> Apparently you are the MX host for the munged domain (we cannot check, because we don't know what domain it is), but that domain isn't listed among any of your address class definitions. (We cannot check that, either.) Since you mention relay_recipient_maps below, it's likely that you wanted to list this domain in relay_domains. http://www.postfix.org/ADDRESS_CLASS_README.html#relay_domain_class http://www.postfix.org/postconf.5.html#relay_domains > some details > m...@tryingtogetincomingrelayworking.com is on the main mail server > that we can call mx1.mail.com so is a different domain, however > with your setup i do not think this should matter? Also the real No idea what that means. > hostname of the relay system is ns1.someserver.com, but i have > added myhostname = mx2.mail.com to the below to main.cf will > $domain work like this? Nor that. And ns1.someserver.com is a real name. Don't steal real Internet names that you do not control. The following is NOT "postconf -n". See for posting guidelines: http://www.postfix.org/DEBUG_README.html#mail > myhostname = mx2.mail.com > alias_maps = hash:/etc/aliases > alias_database = hash:/etc/aliases > myorigin = /etc/mailname We can't guess what's in there. > #mydestination = ns1.someserver.com mx1.someserver.com, > localhost.someserver.com, localhost > mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 > mailbox_size_limit = 0 > recipient_delimiter = + > inet_interfaces = all > inet_protocols = ipv4 > > relayhost = mx1.mail.com > relay_domains = $mydomain We can't guess what this is, either. It could be "mail.com" according to the misinformation you provided, but again, we know you are not mail.com. No evidence was presented which suggests that your "tryingtogetincomingrelayworking.com" is listed in relay_domains. > virtual_alias_maps = hash:/etc/postfix/virtual > relay_recipient_maps = hash:/etc/postfix/relay_recipients > transport_maps = hash:/etc/postfix/transport > > relay_recipients looks like this > m...@tryingtogetincomingrelayworking.com OK > > my virtual looks like this > me m...@tryingtogetincomingrelayworking.com This rewrites me@$myorigin to m...@tryingtogetincomingrelayworking.com. Don't use unqualified names in maps unless you fully understand what they are, > my transport looks like this > mx2.mail.com smtp :[mx1.mail.com] -------------------^ The space in there before the colon is wrong. And again, no listing is shown for "tryingtogetincomingrelayworking.com", so where would you relay that mail even if you did accept it? > All hashed of course -- http://rob0.nodns4.us/ -- system administration and consulting Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
