Sorry, I'm not that good in spoofing :)
On 08/08/2007 18:22, Oded Arbel wrote:
On Wed, 2007-08-08 at 18:05 +0200, Moshe Leibovitch wrote:
On 08/08/2007 16:37, Oded Arbel wrote:
On Wed, 2007-08-08 at 17:08 +0200, Moshe Leibovitch wrote:
The problem is that the mail server running the mail domain comany.com
doesn't like to receive e-mail from addresses in the form of
server.comany.com (where server.company.com is local host name that is
not visible on the internet) - because it doesn't accept mail from
"domains" that it can't resolve. So mail from <[EMAIL PROTECTED]>
to <[EMAIL PROTECTED]> gets rejected.
Can any one suggest a better method of getting my log reports ? I
rather
not have an alias for '[EMAIL PROTECTED]' on the mail server - its a
good
address for a spam trap, but probably nothing else.
Either define mynetworks to include all local networks thus whitelist
them or use access list by domain ( with or without wild card ).
I'm assuming your talking about the mail server here ? I rather not mess
with the mail server - lets just assume I don't have control of it - but
in anyway its not local to the network with the private server on it, so
I don't want to white list anything.
It's all about configuring the server. Am I missing something? If your
main.cf is configured with the means, then all you need to change are
the data files G.E access db, header checks db, etc.
You can change aliases, can you? same thing.
Are you still talking about the company's domain mail server, or about
the private server? If its the former then its not much of an option -
the mail domain is hosted on a shared server and changing its
configuration is out of the question. I can add the [EMAIL PROTECTED]
alias - but I rather not do that as I explained above - and that's
probably the only type of changes that I can do to the mail server.
I'm looking for a possible solution on how to configure the private
server's local MTA so that it can send e-mail to the domain's mail
server (which will be unchanged) without the need to add the private
server's fully qualified host name to a public DNS (which may not always
be possible anyway, as I might want to use servers w/o a fully qualified
host name at all). I'm looking for a general solution that I can deploy
for this problem on multiple private servers that send mail to different
mail servers - most have a similar behavior of blocking emails with what
looks like obviously fake From addresses.
I though you were talking about using reject_unknown_sender_domain
restriction, not just rbl's.
Yea, its probably that, not that I remember.
--
Moshe Leibovitch
CEO
MLN Computerized Systems Ltd.
Email: [EMAIL PROTECTED]
Skype: Moshe.Leibovitch
Mobile: +972-546-484411
Phone: +972-3-5407371
Fax: +972-3-5407371
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
