QEmail Server not sending email because of "Spam Assassin?"

thread: 13 messages  |  last: a year ago  |  started: wednesday, march 10, 2010, 11:02 am pst


#1  |  kingwithin (San Francisco, CA) United States of America
Wednesday, March 10, 2010, 11:02 AM PST

I am not sending bulk emails, just emails to my own domain, and now cannot send emails because of Spam Assassin?

What can I do to remedy this?

Thanks.  Pretty urgent, our application does send out email and notification as essential to the functionality.

#2  |  Mike Ho (Sunnyvale, CA) United States of America Qcodo Administrator
Wednesday, March 10, 2010, 9:46 PM PST

If your own email server is blocking emails from your own webserver due to Spam assassin, simply whitelist your web server in spam assassin to let it through.

#3  |  kingwithin (San Francisco, CA) United States of America
Thursday, March 11, 2010, 3:50 PM PST

Can I change the SMTP to use smtp.gmail.com, it doesn't use Port 25 but I believe it is TLS.  Any restrictions?

Anyone done that before?

public static $SmtpServer = 'localhost';

       /**
        * Port of the SMTP Service on the SmtpServer, usually 25
        *
        * @var integer SmtpPort
        */
       public static $SmtpPort = 25;


I assume I would need to change it in the core?  But what happens if I upgrade?  Is there a config file I could use instead?

#4  |  kingwithin (San Francisco, CA) United States of America
Thursday, March 11, 2010, 4:06 PM PST

This is puzzling to me -- it gets called by the Spam Assassin trap for one typ eof email from the application, but other types it's fine...usually the emails to new entities are the ones getting spammmed...went to spamassassing.org but couldn't find place to white-list IP.

#5  |  Mike Ho (Sunnyvale, CA) United States of America Qcodo Administrator
Friday, March 12, 2010, 10:21 AM PST

Quick note -- Please don't keep double posting your messages in the forums, it makes it tougher to keep a track of the threads.

Another question, which version of qcodo are you using?  Please note that there have been some fixes and things with the QEmailServer class in the 0.4.x releases, several of them in fact.  Not sure if any one of them might resolve your issue or not.  See the Changelog for more info.

In terms of using gmail to send out -- you can do it, but note that QEmailServer only makes unencrypted connections.  I believe Gmail is now enforcing SMTP over SSL.  If not, then you should be able to use it just fine, just be sure to provide your login information to QEmailServer.

Lastly, for questions involving SPAMAssassin, I would suggest that you go to hte Spam Assassin website for more info with that.  If you are having issues with it, and if your smtp server is truly an internal-only smtp server used to send out email from your website, why not just go ahead and disable it?

#6  |  Mike Ho (Sunnyvale, CA) United States of America Qcodo Administrator
Friday, March 12, 2010, 10:41 AM PST

Two other quick questions --

Is this happening on ALL emails?  Or just some?  If some, what's the percentage?

Second, are you sending messages in plaintext?  Or are you using HTML as well / providing attachments?  Just a note that there was an issue that was emailed to me by two different users with regards to some issues with invalid headers and MIME boundaries when emailing with HTML and/or attachments.  Not sure if that would trigger a SPAM Assassin issue though, but just a head's up with that.

#7  |  kingwithin (San Francisco, CA) United States of America
Friday, March 12, 2010, 10:45 AM PST

Hi,

Actually it is NOT to all emails.  It is only to one specific module of emails and will use some of the ways you are suggestion to drill down.

Is there a “best practice” that I can just plop in place to use within the qcodo context?

#8  |  kingwithin (San Francisco, CA) United States of America
Friday, March 12, 2010, 10:47 AM PST

To the earlier message - I hadn't seen a response so reposted with a better and more detailed post to get better traction.

I did go to Spam Assassin, maybe I am on the wrong site, but there didn't appear to be a way to white-list the IP.

The emails are ultimately intended to be outbound for customers, though for testing purposes only going internally.

#9  |  Zbyszek Czarnecki (Warsaw, PL) Poland
Wednesday, March 17, 2010, 5:14 AM PDT

Actually QEmailServer sends malformed html messages (no QuotedPrintable encoding ), and perhaps thats why SpamAssasin marks them as spam.

bugfixed QEmailServer:
http://github.com/klucznik/qcodo

Maybe it helps, won't hurt though.

#10  |  Mike Ho (Sunnyvale, CA) United States of America Qcodo Administrator
Thursday, March 18, 2010, 9:04 AM PDT

Thanks Zbyszek... is this something you're recommending to be put back into Core?

Also, I see that you have a bunch of additional changes as well (not just for QEmailServer) -- are those things you're recommending for core as well?  Please let me know.



Copyright © 2005 - 2012, Quasidea Development, LLC
This open-source framework for PHP is released under the terms of The MIT License.