Hey Stephen,
Could you get this company to send you the log that IronMail generates for each incoming e-mail so you can see what points these emails are receiving for each filter? I have done a lot of work with getting Imail to play nice with IronMail and these logs are extremely valuable. If you can get the log I can probably help you reduce your points to where your e-mails won't get quarantined or deleted. There are some general things you should have in place that will help: 1. a valid SPF record 2. make sure your OHN in Imail matches your MX record 3. make sure your reverse DNS resolves properly I've found that if these are in place that you should be able to get through the filter, even on a forward, without getting quarantined. This depends on how aggressively the company has configured their filters though as well. If you get the log, post what you are being flagged for and we can go from there. Josh ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stephen Guluk Sent: Friday, July 20, 2007 9:33 AM To: [email protected] Subject: [IMail Forum] Forwarded email rejected as spoofed Hello, We are getting some of our clients emails blocked by a spam program called Ironmail. What happens is someone sends mail to one of our customers and they have a setting on their account to forward to the account protected by the Ironmail application. The end location sees an email that says it's coming from some other location rather than the account forwarding the email. So it must be spam and is rejected. Is there a way to make iMail say the sender is the account that created the fwd and retain that truth in the process so as to not look spoofed? The way this is being caught is that the sender is of the same domain as the forwarded recipient so they know the ip address delivering mail is not from their server making it easy to stand out. I would expect that latter spam traps would also be able to see a fwd as not being from the account that passes the email and create a reason for concern. Here's is how the problem arises: [EMAIL PROTECTED] sends to one of my customers that has a forward to their domain1.com account. Joes email hits our server and is then re-routed via a fwd to the domain1.com account of the recipient but the email is basically relayed as it still is saying it's from [EMAIL PROTECTED] when it was actually send (as a forward) from [EMAIL PROTECTED] I've tried to get a whitelisting from the company they are forwarding to but they are the same ones that are trying to put smaller companies like myself out of business and not allow their subdivisions to use outside hosting vendors like myself, so the whitelist was denied. Regards, Steve Guluk SGDesign (949) 661-9333 ICQ: 7230769
