OT Sendmail and Motorola smartphones

[Scott Silva]

on 4/16/2012 11:37 AM Ken A spake the following:
>
>
> On 4/16/2012 11:20 AM, Steve Campbell wrote:
>> Completely off topic - just curious if anyone has had problems similar.
>>
>> I've upgraded email servers from an old Centos 3 to a new Centos 6
>> sendmail server. Just recently our company renewed it's contract and all
>> smartphones were upgraded to the Motorola Milestone X2. These are used
>> by our sales staff when they're out in the field and are allowed to
>> relay through our servers using smtp auth.
>>
>> I have port 587 set up with smtp auth. I'm fairly certain that this was
>> working shortly after the upgrade, but now smtp to this port does not
>> work. It doesn't seem to matter what settings I put in the phone, my
>> maillog returns:
>>
>> sendmail[2765]: q3GG1Gng002765: 70-32-205-105.unassigned.ntelos.net
>> [70.32.205.105] did not issue MAIL/EXPN/VRFY/ETRN during connection to MSA.
>
> That usually means that the client isn't sending the authentication info -
> user & pass.
>
> Do you have one of these new phones to test this with?
>
> You could turn up logging in sendmail -
> define(`confLOG_LEVEL', `14')dnl
>
> Ken
>
>
>> I don't think it's sendmail because the sendmail.mc is identical to the
>> old server's file.
>>
>> I can set up an account using things like Thunderbird just fine, but
>> then I'm using our network, but I'm still able to use port 587.
>>
>> Originally the problem was with one of the dnsbl I was using. (Seems
>> that our provider had blocked their own IPs in one of the spamhaus.org
>> RBLs to protect themselves from spam and using that blocked us from
>> using the IPs they had assigned their smartphones). I switched from
>> zen.spamhaus.org to sbl-xbl.spamhaus.org and that fixed it for a while.
>>
>> My main question is about the Motorola Milestone mail client. Anyone
>> have an opinion on how reliable it is? Does it follow the settings I set
>> on it and has anyone run into problems using this phone as I'm trying to
>> use them?
>>
>> Thanks for any clues.
>>
>> steve campbell
>>
>>
>
I had something similar with some verizon android phones... the auth methods 
the phone supported didn't mesh with the auth methods that saslauth allowed... 
the md5 login wouldn't work, and the cram-md5 wouldn't either. I had to use a 
different mail app on the phones...