Strange Celldata Issue

I have had a couple of customers call saying they were
having problems 
collecting their mail from the SM server from their
cellphones. To be 
honest, I brushed them off saying things like we can not
support the 
iPhone, etc. All earthbound, fixed wireless, even satellite
customers 
connect with no problem, and have been for years.

But now it's happening to me and not only am I very
inconvenienced, I 
also can run tests to try and isolate the cause.

Here's what happens in my experience:

I'm using a Windows Mobile 6.0 PDA (the HTC Advantage
X7500), on the 
AT&T cellular networks, either EDGE or 3G depending on
my location. I 
have the same issue trying to retrieve mail from the mail
server in POP3 
mode as in IMAP mode, and with two different mail clients
(Flexmail and 
the default, MS Outlook): The PDA application says
Connecting ... but 
never does. Looking in the mail.log or in the pop.log or the
imap.log I 
can not find any reference to the attempt to connect at all.
Yet if I 
simply do a telnet on port 110, there is no problem, I get
the normal 
response OK, and of course it shows in the log.

This issue MAY have surfaced around the time I upgraded SM
from 3.8k2 to 
3.9c.1.

I have a temporary workaround of forwarding all my mail to
another mail 
server on a different network from where I can collect and
send without 
any problem, using the same mail client, OS, hardware and
settings, but 
that's not a solution.

Anyone have any ideas or similar experiences?

We have just started having the same problem.  The user is
connecting 
through the Verizon network and I have traced it to an Orb
reject.  It 
seems that the entire Verizon wireless network is listed.  I
am looking 
for a solution that does not include skipping the RBL/Orb

Lee

Peter Dyke wrote:
> I have had a couple of customers call saying they were
having problems 
> collecting their mail from the SM server from their
cellphones. To be 
> honest, I brushed them off saying things like we can
not support the 
> iPhone, etc. All earthbound, fixed wireless, even
satellite customers 
> connect with no problem, and have been for years.
>
> But now it's happening to me and not only am I very
inconvenienced, I 
> also can run tests to try and isolate the cause.
>
> Here's what happens in my experience:
>
> I'm using a Windows Mobile 6.0 PDA (the HTC Advantage
X7500), on the 
> AT&T cellular networks, either EDGE or 3G depending
on my location. I 
> have the same issue trying to retrieve mail from the
mail server in 
> POP3 mode as in IMAP mode, and with two different mail
clients 
> (Flexmail and the default, MS Outlook): The PDA
application says 
> Connecting ... but never does. Looking in the mail.log
or in the 
> pop.log or the imap.log I can not find any reference to
the attempt to 
> connect at all. Yet if I simply do a telnet on port
110, there is no 
> problem, I get the normal response OK, and of course it
shows in the log.
>
> This issue MAY have surfaced around the time I upgraded
SM from 3.8k2 
> to 3.9c.1.
>
> I have a temporary workaround of forwarding all my mail
to another 
> mail server on a different network from where I can
collect and send 
> without any problem, using the same mail client, OS,
hardware and 
> settings, but that's not a solution.
>
> Anyone have any ideas or similar experiences?
>
>
>

How so an ORB reject - on POP?

On 5/14/2008 8:31 AM, Lee McMullen wrote:
> We have just started having the same problem.  The user
is connecting 
> through the Verizon network and I have traced it to an
Orb reject.  It 
> seems that the entire Verizon wireless network is
listed.  I am 
> looking for a solution that does not include skipping
the RBL/Orb
>
> Lee
>
> Peter Dyke wrote:
>> I have had a couple of customers call saying they
were having 
>> problems collecting their mail from the SM server
from their 
>> cellphones. To be honest, I brushed them off saying
things like we 
>> can not support the iPhone, etc. All earthbound,
fixed wireless, even 
>> satellite customers connect with no problem, and
have been for years.
>>
>> But now it's happening to me and not only am I very
inconvenienced, I 
>> also can run tests to try and isolate the cause.
>>
>> Here's what happens in my experience:
>>
>> I'm using a Windows Mobile 6.0 PDA (the HTC
Advantage X7500), on the 
>> AT&T cellular networks, either EDGE or 3G
depending on my location. I 
>> have the same issue trying to retrieve mail from
the mail server in 
>> POP3 mode as in IMAP mode, and with two different
mail clients 
>> (Flexmail and the default, MS Outlook): The PDA
application says 
>> Connecting ... but never does. Looking in the
mail.log or in the 
>> pop.log or the imap.log I can not find any
reference to the attempt 
>> to connect at all. Yet if I simply do a telnet on
port 110, there is 
>> no problem, I get the normal response OK, and of
course it shows in 
>> the log.
>>
>> This issue MAY have surfaced around the time I
upgraded SM from 3.8k2 
>> to 3.9c.1.
>>
>> I have a temporary workaround of forwarding all my
mail to another 
>> mail server on a different network from where I can
collect and send 
>> without any problem, using the same mail client,
OS, hardware and 
>> settings, but that's not a solution.
>>
>> Anyone have any ideas or similar experiences?
>>
>>
>>
>
>
>

This is what is showing up in the logs.  I think it has more
to do with 
the cell phone trying to connect to SMTP and somehow killing
the whole 
connection it is repeatable.  If the user checks his phone
he is 
actually receiving a "Orbs Reject 550" error.  As
I said it is strange.

Lee

Peter Dyke wrote:
> How so an ORB reject - on POP?
>
> On 5/14/2008 8:31 AM, Lee McMullen wrote:
>> We have just started having the same problem.  The
user is connecting 
>> through the Verizon network and I have traced it to
an Orb reject.  
>> It seems that the entire Verizon wireless network
is listed.  I am 
>> looking for a solution that does not include
skipping the RBL/Orb
>>
>> Lee
>>
>> Peter Dyke wrote:
>>> I have had a couple of customers call saying
they were having 
>>> problems collecting their mail from the SM
server from their 
>>> cellphones. To be honest, I brushed them off
saying things like we 
>>> can not support the iPhone, etc. All
earthbound, fixed wireless, 
>>> even satellite customers connect with no
problem, and have been for 
>>> years.
>>>
>>> But now it's happening to me and not only am I
very inconvenienced, 
>>> I also can run tests to try and isolate the
cause.
>>>
>>> Here's what happens in my experience:
>>>
>>> I'm using a Windows Mobile 6.0 PDA (the HTC
Advantage X7500), on the 
>>> AT&T cellular networks, either EDGE or 3G
depending on my location. 
>>> I have the same issue trying to retrieve mail
from the mail server 
>>> in POP3 mode as in IMAP mode, and with two
different mail clients 
>>> (Flexmail and the default, MS Outlook): The PDA
application says 
>>> Connecting ... but never does. Looking in the
mail.log or in the 
>>> pop.log or the imap.log I can not find any
reference to the attempt 
>>> to connect at all. Yet if I simply do a telnet
on port 110, there is 
>>> no problem, I get the normal response OK, and
of course it shows in 
>>> the log.
>>>
>>> This issue MAY have surfaced around the time I
upgraded SM from 
>>> 3.8k2 to 3.9c.1.
>>>
>>> I have a temporary workaround of forwarding all
my mail to another 
>>> mail server on a different network from where I
can collect and send 
>>> without any problem, using the same mail
client, OS, hardware and 
>>> settings, but that's not a solution.
>>>
>>> Anyone have any ideas or similar experiences?
>>>
>>>
>>>
>>
>>
>>
>

I now have two reported cases of SMTP transactions that
cannot be 
completed, in our direction, from a supplier and customer,
that sound 
quite similar. What version of Surgemail are you Running. 
I'm running 
the latest, 3.9e
ben


Lee McMullen wrote:
> This is what is showing up in the logs.  I think it has
more to do 
> with the cell phone trying to connect to SMTP and
somehow killing the 
> whole connection it is repeatable.  If the user checks
his phone he is 
> actually receiving a "Orbs Reject 550" error.
 As I said it is strange.
>
> Lee
>
> Peter Dyke wrote:
>> How so an ORB reject - on POP?
>>
>> On 5/14/2008 8:31 AM, Lee McMullen wrote:
>>> We have just started having the same problem. 
The user is 
>>> connecting through the Verizon network and I
have traced it to an 
>>> Orb reject.  It seems that the entire Verizon
wireless network is 
>>> listed.  I am looking for a solution that does
not include skipping 
>>> the RBL/Orb
>>>
>>> Lee
>>>
>>> Peter Dyke wrote:
>>>> I have had a couple of customers call
saying they were having 
>>>> problems collecting their mail from the SM
server from their 
>>>> cellphones. To be honest, I brushed them
off saying things like we 
>>>> can not support the iPhone, etc. All
earthbound, fixed wireless, 
>>>> even satellite customers connect with no
problem, and have been for 
>>>> years.
>>>>
>>>> But now it's happening to me and not only
am I very inconvenienced, 
>>>> I also can run tests to try and isolate the
cause.
>>>>
>>>> Here's what happens in my experience:
>>>>
>>>> I'm using a Windows Mobile 6.0 PDA (the HTC
Advantage X7500), on 
>>>> the AT&T cellular networks, either EDGE
or 3G depending on my 
>>>> location. I have the same issue trying to
retrieve mail from the 
>>>> mail server in POP3 mode as in IMAP mode,
and with two different 
>>>> mail clients (Flexmail and the default, MS
Outlook): The PDA 
>>>> application says Connecting ... but never
does. Looking in the 
>>>> mail.log or in the pop.log or the imap.log
I can not find any 
>>>> reference to the attempt to connect at all.
Yet if I simply do a 
>>>> telnet on port 110, there is no problem, I
get the normal response 
>>>> OK, and of course it shows in the log.
>>>>
>>>> This issue MAY have surfaced around the
time I upgraded SM from 
>>>> 3.8k2 to 3.9c.1.
>>>>
>>>> I have a temporary workaround of forwarding
all my mail to another 
>>>> mail server on a different network from
where I can collect and 
>>>> send without any problem, using the same
mail client, OS, hardware 
>>>> and settings, but that's not a solution.
>>>>
>>>> Anyone have any ideas or similar
experiences?
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>
>

Hi,

I had the same situation.  I use g_orbs_late
"TRUE" just so the 
connection does not get 'cut off' immediately if the IP is
listed.

Tito



Lee McMullen wrote:
> This is what is showing up in the logs.  I think it has
more to do with 
> the cell phone trying to connect to SMTP and somehow
killing the whole 
> connection it is repeatable.  If the user checks his
phone he is 
> actually receiving a "Orbs Reject 550" error.
 As I said it is strange.
> 
> Lee
> 
> Peter Dyke wrote:
>> How so an ORB reject - on POP?
>>
>> On 5/14/2008 8:31 AM, Lee McMullen wrote:
>>> We have just started having the same problem. 
The user is connecting 
>>> through the Verizon network and I have traced
it to an Orb reject.  
>>> It seems that the entire Verizon wireless
network is listed.  I am 
>>> looking for a solution that does not include
skipping the RBL/Orb
>>>
>>> Lee
>>>
>>> Peter Dyke wrote:
>>>> I have had a couple of customers call
saying they were having 
>>>> problems collecting their mail from the SM
server from their 
>>>> cellphones. To be honest, I brushed them
off saying things like we 
>>>> can not support the iPhone, etc. All
earthbound, fixed wireless, 
>>>> even satellite customers connect with no
problem, and have been for 
>>>> years.
>>>>
>>>> But now it's happening to me and not only
am I very inconvenienced, 
>>>> I also can run tests to try and isolate the
cause.
>>>>
>>>> Here's what happens in my experience:
>>>>
>>>> I'm using a Windows Mobile 6.0 PDA (the HTC
Advantage X7500), on the 
>>>> AT&T cellular networks, either EDGE or
3G depending on my location. 
>>>> I have the same issue trying to retrieve
mail from the mail server 
>>>> in POP3 mode as in IMAP mode, and with two
different mail clients 
>>>> (Flexmail and the default, MS Outlook): The
PDA application says 
>>>> Connecting ... but never does. Looking in
the mail.log or in the 
>>>> pop.log or the imap.log I can not find any
reference to the attempt 
>>>> to connect at all. Yet if I simply do a
telnet on port 110, there is 
>>>> no problem, I get the normal response OK,
and of course it shows in 
>>>> the log.
>>>>
>>>> This issue MAY have surfaced around the
time I upgraded SM from 
>>>> 3.8k2 to 3.9c.1.
>>>>
>>>> I have a temporary workaround of forwarding
all my mail to another 
>>>> mail server on a different network from
where I can collect and send 
>>>> without any problem, using the same mail
client, OS, hardware and 
>>>> settings, but that's not a solution.
>>>>
>>>> Anyone have any ideas or similar
experiences?
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
> 
> 
> 

I can understand SMTP and ORBS issues (the other mail server
I'm 
forwarding to uses the same ORBS, and I'm authenticating to
the main SM 
server for sending without any problem) - but the issue I'm
seeing is 
with POP or IMAP.


On 5/14/2008 9:23 AM, Tito Macapinlac wrote:
> Hi,
>
> I had the same situation.  I use g_orbs_late
"TRUE" just so the 
> connection does not get 'cut off' immediately if the IP
is listed.
>
> Tito
>
>
>
> Lee McMullen wrote:
>> This is what is showing up in the logs.  I think it
has more to do 
>> with the cell phone trying to connect to SMTP and
somehow killing the 
>> whole connection it is repeatable.  If the user
checks his phone he 
>> is actually receiving a "Orbs Reject 550"
error.  As I said it is 
>> strange.
>>
>> Lee
>>
>> Peter Dyke wrote:
>>> How so an ORB reject - on POP?
>>>
>>> On 5/14/2008 8:31 AM, Lee McMullen wrote:
>>>> We have just started having the same
problem.  The user is 
>>>> connecting through the Verizon network and
I have traced it to an 
>>>> Orb reject.  It seems that the entire
Verizon wireless network is 
>>>> listed.  I am looking for a solution that
does not include skipping 
>>>> the RBL/Orb
>>>>
>>>> Lee
>>>>
>>>> Peter Dyke wrote:
>>>>> I have had a couple of customers call
saying they were having 
>>>>> problems collecting their mail from the
SM server from their 
>>>>> cellphones. To be honest, I brushed
them off saying things like we 
>>>>> can not support the iPhone, etc. All
earthbound, fixed wireless, 
>>>>> even satellite customers connect with
no problem, and have been 
>>>>> for years.
>>>>>
>>>>> But now it's happening to me and not
only am I very 
>>>>> inconvenienced, I also can run tests to
try and isolate the cause.
>>>>>
>>>>> Here's what happens in my experience:
>>>>>
>>>>> I'm using a Windows Mobile 6.0 PDA (the
HTC Advantage X7500), on 
>>>>> the AT&T cellular networks, either
EDGE or 3G depending on my 
>>>>> location. I have the same issue trying
to retrieve mail from the 
>>>>> mail server in POP3 mode as in IMAP
mode, and with two different 
>>>>> mail clients (Flexmail and the default,
MS Outlook): The PDA 
>>>>> application says Connecting ... but
never does. Looking in the 
>>>>> mail.log or in the pop.log or the
imap.log I can not find any 
>>>>> reference to the attempt to connect at
all. Yet if I simply do a 
>>>>> telnet on port 110, there is no
problem, I get the normal response 
>>>>> OK, and of course it shows in the log.
>>>>>
>>>>> This issue MAY have surfaced around the
time I upgraded SM from 
>>>>> 3.8k2 to 3.9c.1.
>>>>>
>>>>> I have a temporary workaround of
forwarding all my mail to another 
>>>>> mail server on a different network from
where I can collect and 
>>>>> send without any problem, using the
same mail client, OS, hardware 
>>>>> and settings, but that's not a
solution.
>>>>>
>>>>> Anyone have any ideas or similar
experiences?
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>
>>
>>
>
>