sendmail: trusted-users or aliases?
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:
Quote:
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? How can I solve this? Al. |
Quote:
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: Code:
MASQUERADE_AS(domain.com)dnl Code:
C{M}'server.domain.com' |
Quote:
1) sendmail.mc Quote:
Quote:
|
Quote:
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. |
All times are GMT -5. The time now is 04:33 PM. |