I'm sorry for not giving full information before. We set our mail server to use SMTP with TLS (port 587) and the outgoing server (of the mail client on android smart phone) as our server itself (in other words, not relaying through the provider server). Thank you for the suggestion.
Regards, Mario On Fri, Mar 9, 2012 at 4:59 PM, Nick Warr <n...@mobilia.it> wrote: > Il 09/03/2012 10.28, FC Mario Patty ha scritto: > > Hi, I wonder why spamassassin detects email sent from android to our mail > server as spams? I ran spamassassin -D < the_email and got result as below > > Content analysis details: (13.8 points, 4.0 required) > > pts rule name description > ---- ---------------------- > -------------------------------------------------- > 2.2 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net > [Blocked - see < > http://www.spamcop.net/bl.shtml?118.97.95.30>] > 2.9 RCVD_IN_XBL RBL: Received via a relay in Spamhaus XBL > [118.97.95.30 listed > in zen.spamhaus.org] > 4.5 HELO_LOCALHOST HELO_LOCALHOST > 1.2 SPF_NEUTRAL SPF: sender does not match SPF record (neutral) > 2.9 TVD_SPACE_RATIO BODY: TVD_SPACE_RATIO > 0.1 RDNS_NONE Delivered to trusted network by a host with no > rDNS > > I checked spamcop.net and spamhaus.org and found 118.97.95.30 in both > sites and had delisted them, but I guess it was going to happen again. This > ip address is legit and just listed there today so I think perhaps email > sent this morning has triggered this ip to get listed there (but I'm not > sure why?). What can I do let emails from android smart-phone to arrive > safely in our mail server? Thank-you in advance. > > Regards, > Mario > > Configure your phone(s) to send directly through your SMTP server, via SSL > on port 465 (for example), instead of relaying through your phone > provider's SMTP server. >
