Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
For a project that I have been assigned to, I need to send emails to a business partner (business_partner.com) from one production server. However, my emails neither reach their destination nor bounce back to me.
Working with our business partner's IT support, the following error was discovered in their maillogs:
Quote:
chqsmt05 postfix/smtpd[1605]: NOQUEUE: reject: MAIL from unknown
[hidden_ip_address]: 450 4.1.8 <ddwmadm@pxclpd30.hidden_domain_name.com>: Sender address rejected: Domain not found;
My IT support guys believe it is the cause of the problem. We created an alias but it made no change. Would adding my public internet email address to "trusted-users" file (we use sendmail) help?
For a project that I have been assigned to, I need to send emails to a business partner (business_partner.com) from one production server. However, my emails neither reach their destination nor bounce back to me.
Working with our business partner's IT support, the following error was discovered in their maillogs:
Further analysis by my IT support shows that emails are successfully sent out ("Message accepted for delivery"):
My IT support guys believe it is the cause of the problem. We created an alias but it made no change. Would adding my public internet email address to "trusted-users" file (we use sendmail) help?
No, it won't help, and MAN does this sound familiar.
Faced the exact same issue a few years back...one of our internal mail relays (the one that shoveled things along to the Internet), had a rule change. It quit accepting server.domain.com, no matter WHAT. It would only take domain.com...and only if that was on the list of allowed domains. What you're looking for is a domain rewrite rule/masquerade.
Since your subject line says sendmail, I'll assume you're using it. If you generate your sendmail.cf file via the M4 pre-processor, shove these things in:
Or, if you're naughty, edit the .mc file directly:
Code:
C{M}'server.domain.com'
# who I masquerade as (null for no masquerading) (see also $=M)
DMdomain.com
Bounce the sendmail service later. Nothing you add on your side will make their system accept it...seems that your business partner has domain-filtering in place. So, either correct the domain using the above, or get them to add a rule on their mail server to allow the mail through. It's getting dropped from further progress from THEIR side.
I was gonna have my sysadmin change our sendmail config like so:
1) sendmail.mc
2) sendmail.cf
Are saying that won't take care of my problem??
Don't know, since I don't know about the rest of your infrastructure, how it's configured, or what the remote email system is expecting/wanting to see to allow incoming mail. If the upstream smarthost has a different sending domain than your server now, and that domain is accepted by the remote system, then yes, it'll work.
A smarthost is just another mail server that will simply handle mail. Defining one on a box will only make ALL the mail go to that mail server. From the messages you posted, the DOMAIN you're passing along is what's getting rejected by the other mail server. The remote server has to either allow the domain, or you have to modify the domain to match what they want.
To put it another way, think of the remote mail server as a building. Your mail needs to go to an office IN that building, but you don't have a key (valid domain). Right now you're going to the front door (the messages are coming from your server)...if you define a smart host they'll just go to the back door. And you STILL won't have a key.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.