I think that postfix is your best route as well.
Just to clarify the log messages a little, when spamdyke issues a
DENIED_OTHER message, it's saying that something else (other than
spamdyke) rejected the message. This could be absolutely anything
further down the pipe. spamdyke is simply saying that "something other
than rejected the message, so I'm obeying that rejection".
In this case it appears to be eMPF that's doing the rejecting, but it
could also be chkuser, clamav, spamassassin etc. as far as spamdyke
knows. There should be a rejection message in the log just before
spamdyke's DENIED_OTHER that details the rejection.
HTH.
[email protected] wrote:
Thanks guys for all the input. I should be more descriptive with my
issue. First, my users do not connect to any email accounts on my
internal servers. I have different applications running on my internal
servers that need to send email to accounts on my external
(qmail-toaster). For instance, I run timetrex on one server. Users
login and clock in and out. Managers can send email to the time
administrator email account which resides on my external server
([email protected]). These are the emails that are failing in the
example logs I posted.
Thinking of what Jake was suggesting:
I added 192.168.105.110 to the whitelist_ip and
@local.solution-group.com to whitelist_rdns and whitelist_senders in
/etc/spamdyke. I still get the "11-10 16:07:45 spamdyke[27917]:
DENIED_OTHER from: [email protected] to: [email protected] origin_ip:
192.168.105.110 origin_rdns: " message in the smtp logfile on the
qmailtoaster.
I can say with 100% confidence that when I remove all entries from the
policy (eMPF) file on the external mail server - these emails are
successfully delivered. The issue is, timetrex and other application
have no configuration file where I can put the smtp username and
password. Since eMPF requires a user to authenticate (it has to know
who you are so it can apply a rule if applicable) it fails any message
that does not authenticate.
So, at this point, my best option is to follow the quickie guide to
installing postfix.
If anyone has anything else to add or suggest, I am all ears.
Thanks,
Dave
Jake Vickers wrote:
Eric Shubert wrote:
Good question. I don't know the answer to that off hand.
Michael Colvin wrote:
Oh, I totally agree, Eric. I guess my point was trying to find out
if there
was any reason they needed to do it that way... Really, the eMPF
functionality should be on his internal server, not the external relay
server... Then, the internal server could relay to the QMT w/o
having eMPF
on it, and the internal server would still limit user e-mails.
Unless of course the users also connect from externally...
Couldn't he also have the internal server relay via port 587 to the
toaster?
Does eMPF look at 587 traffic also?
I'm 99% sure that it does, since it's a patch applied to the smtp
daemon in a global sense.
Also, isn't this a Spamdyke config issue with the IP addres?
11-10 16:07:45 spamdyke[27917]: DENIED_OTHER from: [email protected] to:
[email protected] origin_ip: 192.168.105.110 origin_rdns:
It reads to me that it was denied because of "DENIED_OTHER" by
spamdyke for origin_rdns.
It's late, so correct me if I'm wrong.
--
-Eric 'shubes'
---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group
(www.vickersconsulting.com)
Vickers Consulting Group offers Qmailtoaster support and installations.
If you need professional help with your setup, contact them today!
---------------------------------------------------------------------------------
Please visit qmailtoaster.com for the latest news, updates, and packages.
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
