Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > alt.os.linux.slackware > #26533 > unrolled thread

Product LockIn

Back to article view | Back to alt.os.linux.slackware

Contents

  Product LockIn no.top.post@gmail.com - 2016-03-25 12:54 +0000
    Re: Product LockIn Henrik Carlqvist <Henrik.Carlqvist@deadspam.com> - 2016-03-25 14:10 +0000
    Re: Product LockIn Rick Pikul/Chakat Firepaw <chakatfirepaw@gmail.com> - 2016-03-25 22:52 +0000
      Re: Product LockIn Unknown <dog@gmail.com> - 2016-03-26 12:53 +0000
        Re: Product LockIn The Natural Philosopher <tnp@invalid.invalid> - 2016-03-26 13:07 +0000
        Re: Product LockIn "Carlos E.R." <robin_listas@invalid.es> - 2016-03-26 15:18 +0100
          Re: Product LockIn The Natural Philosopher <tnp@invalid.invalid> - 2016-03-26 15:04 +0000
            Re: Product LockIn "Carlos E.R." <robin_listas@invalid.es> - 2016-03-26 21:25 +0100
              Re: Product LockIn The Natural Philosopher <tnp@invalid.invalid> - 2016-03-27 12:05 +0100
                Re: Product LockIn "Carlos E.R." <robin_listas@invalid.es> - 2016-03-27 15:57 +0200
                  Re: Product LockIn "Carlos E.R." <robin_listas@invalid.es> - 2016-03-29 12:26 +0200
                Re: Product LockIn Bit Twister <BitTwister@mouse-potato.com> - 2016-03-27 14:45 +0000
                  Re: Product LockIn The Natural Philosopher <tnp@invalid.invalid> - 2016-03-27 16:25 +0100
                    Re: Product LockIn Bit Twister <BitTwister@mouse-potato.com> - 2016-03-27 16:05 +0000
                      Re: Product LockIn "Carlos E. R." <robin_listas@invalid.es> - 2016-03-29 04:35 +0200
                      Re: Product LockIn Unknown <dog@gmail.com> - 2016-03-31 01:59 +0000
                        Re: Product LockIn Keith Keller <kkeller-usenet@wombat.san-francisco.ca.us> - 2016-03-30 21:15 -0700
                          Re: Product LockIn The Natural Philosopher <tnp@invalid.invalid> - 2016-03-31 11:05 +0100
                            Re: Product LockIn Ahem A Rivet's Shot <steveo@eircom.net> - 2016-03-31 13:11 +0100
                              Re: Product LockIn The Natural Philosopher <tnp@invalid.invalid> - 2016-03-31 15:35 +0100
                                Re: Product LockIn Charlie <cdknospam@msn.com> - 2016-03-31 12:10 -0400
                                  Re: Product LockIn The Natural Philosopher <tnp@invalid.invalid> - 2016-03-31 22:36 +0100
                            Re: Product LockIn rickman <gnuarm@gmail.com> - 2016-03-31 16:00 -0400
                              Re: Product LockIn The Natural Philosopher <tnp@invalid.invalid> - 2016-03-31 22:35 +0100
                                Re: Product LockIn rickman <gnuarm@gmail.com> - 2016-03-31 18:11 -0400
                                  Re: Product LockIn Graham. <alt.f7-fsks89j@yopmail.com> - 2016-04-04 22:26 +0100
                            Re: Product LockIn Keith Keller <kkeller-usenet@wombat.san-francisco.ca.us> - 2016-03-31 21:45 -0700
                          Re: Product LockIn Richard Owlett <rowlett@cloud85.net> - 2016-03-31 06:14 -0500
                          Re: Product LockIn Joe Beanfish <joebeanfish@nospam.duh> - 2016-03-31 13:24 +0000
                            Re: Product LockIn noel <deletethis@invalid.lan> - 2016-04-01 13:19 +1000
                            Re: Product LockIn Keith Keller <kkeller-usenet@wombat.san-francisco.ca.us> - 2016-03-31 21:52 -0700
                        Re: Product LockIn Chick Tower <c.tower@deadspam.com> - 2016-03-31 16:36 +0000
                          Re: Product LockIn "Carlos E.R." <robin_listas@invalid.es> - 2016-04-01 03:45 +0200
                    Re: Product LockIn Mark Carroll <mtbc@ixod.org> - 2016-03-27 18:14 +0100
                    Re: Product LockIn Joe <joe@jretrading.com> - 2016-03-27 20:52 +0100
                      Re: Product LockIn The Natural Philosopher <tnp@invalid.invalid> - 2016-03-28 01:12 +0100
                        Re: Product LockIn Mike Spencer <mds@bogus.nodomain.nowhere> - 2016-03-28 04:04 -0300
                        Re: Product LockIn Mark Carroll <mtbc@ixod.org> - 2016-03-28 08:32 +0100
                        Re: Product LockIn Joe <joe@jretrading.com> - 2016-03-28 11:47 +0100
                        Re: Product LockIn Aaron Baugher <aaron@baugher.biz> - 2016-03-28 07:07 -0500
                    Re: Product LockIn "Carlos E. R." <robin_listas@invalid.es> - 2016-03-29 04:32 +0200
          Re: Product LockIn no.top.post@gmail.com - 2016-03-28 02:55 +0000
            Re: Product LockIn "Carlos E. R." <robin_listas@invalid.es> - 2016-03-29 04:44 +0200
        Re: Product LockIn Bit Twister <BitTwister@mouse-potato.com> - 2016-03-26 19:05 +0000
        Re: Product LockIn Mike Spencer <mds@bogus.nodomain.nowhere> - 2016-03-26 16:37 -0300
    Re: Product LockIn sctvguy1 <sctvguy1@invalid.net> - 2016-03-30 14:37 +0000

Page 2 of 3 — ← Prev page 1 [2] 3  Next page →

#26577

On 3/31/2016 10:35 AM, The Natural Philosopher wrote:
>
> Oddly no one seems to attack the POP3 port much
Seems that is too old school.

[toc] | [prev] | [next] | [standalone]

#26581

On 31/03/16 17:10, Charlie wrote:
> On 3/31/2016 10:35 AM, The Natural Philosopher wrote:
>>
>> Oddly no one seems to attack the POP3 port much
> Seems that is too old school.
and indeed if they were, they would be unlikely to find any mail, since 
I download and delete every few minutes...

...an IMAP server on the other hand, acting as personal cloud. Ye gods. 
The blackmail material...!

-- 
Bureaucracy defends the status quo long past the time the quo has lost 
its status.

Laurence Peter

[toc] | [prev] | [next] | [standalone]

#26579

On 3/31/2016 6:05 AM, The Natural Philosopher wrote:
> On 31/03/16 05:15, Keith Keller wrote:
>> ["Followup-To:" header set to alt.os.linux.slackware.]
>> On 2016-03-31, Unknown <dog@gmail.com> wrote:
>>>
>>> The above complex elaborate description shows how the big
>>> US corparations are entrapping us to become another generation of
>>> <lucky strike addicts>.
>>
>> If you don't like gmail then don't use it.  Run your own SMTP server,
>
> I do
>
>> and try to fix it after you get pwn3d an hour later.
>
> I haven't been in 5 years...
>
> OTOH I do hold my hand up to that being my business before I retired...
>
> If anyone is interested in HOW to build a basic smtp/popmail type setup
> oin a virtual private server, I could probably detail the steps.

why are you cross posting this in comp.sys.raspberry-pi?

-- 

Rick

[toc] | [prev] | [next] | [standalone]

#26580

On 31/03/16 21:00, rickman wrote:
> On 3/31/2016 6:05 AM, The Natural Philosopher wrote:
>> On 31/03/16 05:15, Keith Keller wrote:
>>> ["Followup-To:" header set to alt.os.linux.slackware.]
>>> On 2016-03-31, Unknown <dog@gmail.com> wrote:
>>>>
>>>> The above complex elaborate description shows how the big
>>>> US corparations are entrapping us to become another generation of
>>>> <lucky strike addicts>.
>>>
>>> If you don't like gmail then don't use it.  Run your own SMTP server,
>>
>> I do
>>
>>> and try to fix it after you get pwn3d an hour later.
>>
>> I haven't been in 5 years...
>>
>> OTOH I do hold my hand up to that being my business before I retired...
>>
>> If anyone is interested in HOW to build a basic smtp/popmail type setup
>> oin a virtual private server, I could probably detail the steps.
>
> why are you cross posting this in comp.sys.raspberry-pi?
>
Because that's where I read it first?

I don't susbscribe to alt.os.linux.slackware

-- 
Bureaucracy defends the status quo long past the time the quo has lost 
its status.

Laurence Peter

[toc] | [prev] | [next] | [standalone]

#26582

On 3/31/2016 5:35 PM, The Natural Philosopher wrote:
> On 31/03/16 21:00, rickman wrote:
>> On 3/31/2016 6:05 AM, The Natural Philosopher wrote:
>>> On 31/03/16 05:15, Keith Keller wrote:
>>>> ["Followup-To:" header set to alt.os.linux.slackware.]
>>>> On 2016-03-31, Unknown <dog@gmail.com> wrote:
>>>>>
>>>>> The above complex elaborate description shows how the big
>>>>> US corparations are entrapping us to become another generation of
>>>>> <lucky strike addicts>.
>>>>
>>>> If you don't like gmail then don't use it.  Run your own SMTP server,
>>>
>>> I do
>>>
>>>> and try to fix it after you get pwn3d an hour later.
>>>
>>> I haven't been in 5 years...
>>>
>>> OTOH I do hold my hand up to that being my business before I retired...
>>>
>>> If anyone is interested in HOW to build a basic smtp/popmail type setup
>>> oin a virtual private server, I could probably detail the steps.
>>
>> why are you cross posting this in comp.sys.raspberry-pi?
>>
> Because that's where I read it first?
>
> I don't susbscribe to alt.os.linux.slackware

I don't see a post you are replying to.

-- 

Rick

[toc] | [prev] | [next] | [standalone]

#26602

On Thu, 31 Mar 2016 18:11:53 -0400, rickman <gnuarm@gmail.com> wrote:

>On 3/31/2016 5:35 PM, The Natural Philosopher wrote:
>> On 31/03/16 21:00, rickman wrote:
>>> On 3/31/2016 6:05 AM, The Natural Philosopher wrote:
>>>> On 31/03/16 05:15, Keith Keller wrote:
>>>>> ["Followup-To:" header set to alt.os.linux.slackware.]
>>>>> On 2016-03-31, Unknown <dog@gmail.com> wrote:
>>>>>>
>>>>>> The above complex elaborate description shows how the big
>>>>>> US corparations are entrapping us to become another generation of
>>>>>> <lucky strike addicts>.
>>>>>
>>>>> If you don't like gmail then don't use it.  Run your own SMTP server,
>>>>
>>>> I do
>>>>
>>>>> and try to fix it after you get pwn3d an hour later.
>>>>
>>>> I haven't been in 5 years...
>>>>
>>>> OTOH I do hold my hand up to that being my business before I retired...
>>>>
>>>> If anyone is interested in HOW to build a basic smtp/popmail type setup
>>>> oin a virtual private server, I could probably detail the steps.
>>>
>>> why are you cross posting this in comp.sys.raspberry-pi?
>>>
>> Because that's where I read it first?
>>
>> I don't susbscribe to alt.os.linux.slackware
>
>I don't see a post you are replying to.
Nor do I, and I'm also reading this via E-S. One of Ray's servers
crashed whilst he was away on holiday.



-- 

Graham.

%Profound_observation%

[toc] | [prev] | [next] | [standalone]

#26586

["Followup-To:" header set to alt.os.linux.slackware.]
On 2016-03-31, The Natural Philosopher <tnp@invalid.invalid> wrote:
> On 31/03/16 05:15, Keith Keller wrote:
>> ["Followup-To:" header set to alt.os.linux.slackware.]
>> On 2016-03-31, Unknown <dog@gmail.com> wrote:
>>
>> If you don't like gmail then don't use it.  Run your own SMTP server,
>> and try to fix it after you get pwn3d an hour later.
>
> I haven't been in 5 years...

No, but the OP would be.

--keith

-- 
kkeller-usenet@wombat.san-francisco.ca.us
(try just my userid to email me)
AOLSFAQ=http://www.therockgarden.ca/aolsfaq.txt
see X- headers for PGP signature information

[toc] | [prev] | [next] | [standalone]

#26573

On 3/30/2016 11:15 PM, Keith Keller wrote:
> ["Followup-To:" header set to alt.os.linux.slackware.]
> On 2016-03-31, Unknown <dog@gmail.com> wrote:
>>
>> The above complex elaborate description shows how the big
>> US corparations are entrapping us to become another generation of
>> <lucky strike addicts>.
>
> If you don't like gmail then don't use it.  Run your own SMTP server,
> and try to fix it after you get pwn3d an hour later.
>
> --keith
>

With "free" services you get almost your money's worth ;)

[toc] | [prev] | [next] | [standalone]

#26575

On Wed, 30 Mar 2016 21:15:35 -0700, Keith Keller wrote:

> ["Followup-To:" header set to alt.os.linux.slackware.]
> On 2016-03-31, Unknown <dog@gmail.com> wrote:
>>
>> The above complex elaborate description shows how the big US
>> corparations are entrapping us to become another generation of
>><lucky strike addicts>.
> 
> If you don't like gmail then don't use it.  Run your own SMTP server,
> and try to fix it after you get pwn3d an hour later.
> 
> --keith

Ok, let's turn the paranoia dial down just a little.

I've been running my own SMTP servers on Linux since the 90's without
a single successful break-in. Not that my personal server is a large
or particularly interesting target, but most of the break-ins I've
heard about are due to idiotic passwords, procedures, and people.
Those are far easier to exploit than most of the software vulnerabilities.

[toc] | [prev] | [next] | [standalone]

#26585

On Thu, 31 Mar 2016 13:24:03 +0000, Joe Beanfish wrote:

> On Wed, 30 Mar 2016 21:15:35 -0700, Keith Keller wrote:
> 
>> ["Followup-To:" header set to alt.os.linux.slackware.]
>> On 2016-03-31, Unknown <dog@gmail.com> wrote:
>>>
>>> The above complex elaborate description shows how the big US
>>> corparations are entrapping us to become another generation of
>>><lucky strike addicts>.
>> 
>> If you don't like gmail then don't use it.  Run your own SMTP server,
>> and try to fix it after you get pwn3d an hour later.
>> 
>> --keith
> 
> Ok, let's turn the paranoia dial down just a little.
> 
> I've been running my own SMTP servers on Linux since the 90's without a
> single successful break-in. Not that my personal server is a large or
> particularly interesting target, but most of the break-ins I've heard
> about are due to idiotic passwords, procedures, and people.
> Those are far easier to exploit than most of the software
> vulnerabilities.

Well said.

[toc] | [prev] | [next] | [standalone]

#26587

On 2016-03-31, Joe Beanfish <joebeanfish@nospam.duh> wrote:
> On Wed, 30 Mar 2016 21:15:35 -0700, Keith Keller wrote:
>> On 2016-03-31, Unknown <dog@gmail.com> wrote:
>> 
>> If you don't like gmail then don't use it.  Run your own SMTP server,
>> and try to fix it after you get pwn3d an hour later.
>
> Ok, let's turn the paranoia dial down just a little.

I apologize; it's not paranoia, it's an indictment of the OP's ability
to do anything competently.  Obviously someone who knows what they're
doing can run an SMTP server with low(ish) risk, as long as he monitors
the various spam block lists regularly.

I should also clarify that the larger risk is of getting ''pwn3d'' by
spammers, not pwn3d by an intruder.  I still count that as a pwning
because your resources are being used in a way you most certainly did
not authorize or desire.

--keith

-- 
kkeller-usenet@wombat.san-francisco.ca.us
(try just my userid to email me)
AOLSFAQ=http://www.therockgarden.ca/aolsfaq.txt
see X- headers for PGP signature information

[toc] | [prev] | [next] | [standalone]

#26578

On 2016-03-31, Unknown wrote:
> Hi **,
>   Someone just tried to sign in to your Google Account **** from an app 
>  that doesn't meet modern security standards.
> Details:
> Monday, March 28, 2016 2:58 AM (GMT)
>   We strongly recommend that you use a secure app, like Gmail, to access 
>  your account. All apps made by Google meet these security standards. 
>  Using a less secure app, on the other hand, could leave your account 
>  vulnerable. Learn more.

What program did you use to cause this response?
-- 
                                 Chick Tower

For e-mail:  aols2 DOT sent DOT towerboy AT xoxy DOT net

[toc] | [prev] | [next] | [standalone]

#26583

On 2016-03-31 18:36, Chick Tower wrote:
> On 2016-03-31, Unknown wrote:
>> Hi **,
>>   Someone just tried to sign in to your Google Account **** from an app 
>>  that doesn't meet modern security standards.
>> Details:
>> Monday, March 28, 2016 2:58 AM (GMT)
>>   We strongly recommend that you use a secure app, like Gmail, to access 
>>  your account. All apps made by Google meet these security standards. 
>>  Using a less secure app, on the other hand, could leave your account 
>>  vulnerable. Learn more.
> 
> What program did you use to cause this response?

This is standard and new but known gmail behaviour.
Just ignore and disable what they call, IIRC, double security.
Basically, web based security.
They could instead user client certificates, which is standard but
little known.

-- 
Cheers, Carlos.

--- news://freenews.netfront.net/ - complaints: news@netfront.net ---

[toc] | [prev] | [next] | [standalone]

#26553

On 27 Mar 2016, The Natural Philosopher wrote:

> On 27/03/16 15:45, Bit Twister wrote:
(snip)
>> I can not prove that offhand, but I believe there is a fetchmail
>> option to have the mail remain on the server or not, your choice in
>> the fetchmail config file.

Yes, it's what keep/nokeep is about?

> Not with IMAP. The whole point of IMAP is that all the clients synch to 
> a single online server space.

You're sure of that? My memory of fetchmail is that it can delete them
from IMAP just fine on download and a look at the current docs seems to
confirm that. I even find threads from fetchmail users who are unhappy
that it is deleting their IMAP-accessed mail from the server!

> "IMAP was designed with the goal of permitting complete management of an 
> email box by multiple email clients, Therefore, clients generally leave 
> messages on the server until the user explicitly deletes them"

"Generally". For instance I grab my mail via IMAP using Gnus with
(setq mail-source-delete-incoming t) and that works just fine to
delete them.

> POP is a 'store till I download' protocol. Imap is not.

IMAP is very flexible.

(snip)
>> Replying or sending in that methodology no longer works because my
>> mail is being rejected because reverse dns look up fails because my MTA
>> is not in a registered domain or some such thing.
>
> MMm. you need a smart host then.

Absolutely.

> Oddly enough, getting a virtual private server for a fistful of dollars, 
> and a small fist at that - is no big deal and is probably te easiest way 
> to have your own domain and email setup entirely under your control, 
> independent from any ISP,  and accessible how you want and where you want.

That's exactly what I do, but it's not for those who don't want to learn
how to configure and maintain a mailserver. It's easy not to notice you
messed things up and can cause real problems if you did.

-- Mark

[toc] | [prev] | [next] | [standalone]

#26554

On Sun, 27 Mar 2016 16:25:46 +0100
The Natural Philosopher <tnp@invalid.invalid> wrote:


> 
> Not with IMAP. The whole point of IMAP is that all the clients synch
> to a single online server space.
> 
> "IMAP was designed with the goal of permitting complete management of
> an email box by multiple email clients, Therefore, clients generally
> leave messages on the server until the user explicitly deletes them"
> 
> 
> POP is a 'store till I download' protocol. Imap is not.
> 
> 
>

But it must always be possible to delete email from a server,
whatever protocol is used. IMAP allows downloading followed by
deletion, with the default of non-deletion, POP is the other way
around. Either can be used to leave mail on the server or remove all of
it.

-- 
Joe

[toc] | [prev] | [next] | [standalone]

#26556

On 27/03/16 20:52, Joe wrote:
> On Sun, 27 Mar 2016 16:25:46 +0100
> The Natural Philosopher <tnp@invalid.invalid> wrote:
>
>
>>
>> Not with IMAP. The whole point of IMAP is that all the clients synch
>> to a single online server space.
>>
>> "IMAP was designed with the goal of permitting complete management of
>> an email box by multiple email clients, Therefore, clients generally
>> leave messages on the server until the user explicitly deletes them"
>>
>>
>> POP is a 'store till I download' protocol. Imap is not.
>>
>>
>>
>
> But it must always be possible to delete email from a server,
> whatever protocol is used. IMAP allows downloading followed by
> deletion, with the default of non-deletion, POP is the other way
> around.

No it isnt. You must send a pop server an express DELE command

Either can be used to leave mail on the server or remove all of
> it.
>
My limited experience of IMAP suggests that only when you delete mail on 
the client, does it delete it on the server.

Just downloading it is not enough, and if you delete it on the client, 
then its gone , so if you want to keep mail on the client but not on the 
server you can't do it.


-- 
To ban Christmas, simply give turkeys the vote.

[toc] | [prev] | [next] | [standalone]

#26558

The Natural Philosopher <tnp@invalid.invalid> writes:

> My limited experience of IMAP suggests that only when you delete mail on 
> the client, does it delete it on the server.

   RFC  1176
   ---------
   Interactive Mail Access Protocol - Version 2

   Additionally, IMAP2 offers several facilities for managing
   individual message state and the mailbox as a whole beyond the
   simple "delete message" functionality of POP.
   [...]

   The client can alter certain data (currently only the flags) by a
   STORE command.  As an example, a message is deleted from a mailbox
   by a STORE command that includes the \DELETED flag as a flag being
   set.

   Other client operations include copying a message to another
   mailbox (COPY command), permanently removing deleted messages
   (EXPUNGE command), checking for new messages (CHECK command), and
   searching for messages that match certain criteria (SEARCH
   command).
   [...]

   STORE sequence data value

   The STORE command alters data associated with a message in the
   mailbox. 
   [snip]
   EXAMPLE:  A003 STORE 2:4 +FLAGS (\DELETED)
   marks messages 2, 3, and 4 for deletion.
   [...]

   EXPUNGE

   The EXPUNGE command permanently removes all messages with the
   \DELETED flag set in its flags from the mailbox. 
   [snip]

So unlike POP3, IMAP doesn't have a delete command per se.  You can
mark messages with the DELETED  flag.  IMAP does have an EXPUNGE
command that actually deletes/removes a message from the server.

It looks like it depends on (1) what the client software actually says
to the server when you tell the client to do $SOMETHING and (2)
whether or not the server supports or allows you to execute
RFC-defined commands.

An example of (1) would be a client that issues a STORE command to set
the delete flag followed by an EXPUNGE command when you delete your
local copy versus another client that only deletes & expunges on the
server after explicit directions from the client's user.

An example of (2) would be the allegation that GMail keeps your email
forever regardless of what you do with the their (or any?) client.
Just disabling the EXPUNGE command or causing it to do somthing other
than actual expurgation should be easy enough for a entity the size of
Gwwgle. 



-- 
Mike Spencer                  Nova Scotia, Canada

[toc] | [prev] | [next] | [standalone]

#26559

On 28 Mar 2016, The Natural Philosopher wrote:
(snip)
> My limited experience of IMAP suggests that only when you delete mail on 
> the client, does it delete it on the server.
>
> Just downloading it is not enough, and if you delete it on the client, 
> then its gone , so if you want to keep mail on the client but not on the 
> server you can't do it.

Of course you can if your client retains a local copy as mine is
configured to. Both POP3 and IMAP allow retrieval from the server and
deletion on the server as separate actions. What the client does on its
side is its choice regardless of by which protocol it does it.

-- Mark

[toc] | [prev] | [next] | [standalone]

#26560

On Mon, 28 Mar 2016 01:12:52 +0100
The Natural Philosopher <tnp@invalid.invalid> wrote:

> On 27/03/16 20:52, Joe wrote:
> > On Sun, 27 Mar 2016 16:25:46 +0100
> > The Natural Philosopher <tnp@invalid.invalid> wrote:
> >
> >  
> >>
> >> Not with IMAP. The whole point of IMAP is that all the clients
> >> synch to a single online server space.
> >>
> >> "IMAP was designed with the goal of permitting complete management
> >> of an email box by multiple email clients, Therefore, clients
> >> generally leave messages on the server until the user explicitly
> >> deletes them"
> >>
> >>
> >> POP is a 'store till I download' protocol. Imap is not.
> >>
> >>
> >>  
> >
> > But it must always be possible to delete email from a server,
> > whatever protocol is used. IMAP allows downloading followed by
> > deletion, with the default of non-deletion, POP is the other way
> > around.  
> 
> No it isnt. You must send a pop server an express DELE command

Which a POP3 client will do by default, unless the user has
specifically requested that messages will be kept on the server.
Fetchmail will do it by default, unless the --keep directive is used.

> 
> Either can be used to leave mail on the server or remove all of
> > it.
> >  
> My limited experience of IMAP suggests that only when you delete mail
> on the client, does it delete it on the server.
> 
But how does it know? The client must tell the server this.

> Just downloading it is not enough, and if you delete it on the
> client, then its gone , so if you want to keep mail on the client but
> not on the server you can't do it.
> 
> 
When you change the status of a message on the client, such as by
deleting it, the client will typically send a STORE command to alter the
flags of the message on the server copy. The /deleted flag is set, and
the next EXPUNGE command will delete everything from the server with
this flag set.

But a specialist program such as a downloader does not have to behave in
the same way as a desktop client. It would be no problem at all for
fetchmail (and I don't know for sure how it behaves) to retrieve a
message, pass it to its local MTA or other delivery destination, and
when it received confirmation that the message has been accepted, to
set the IMAP server's /deleted flag for that message.

Sorry, I did have to look it up again, but some years ago I wrote some
PHP to pull database updates from a local IMAP server, where they had
been securely sent by a script running on a master SQL server elsewhere.

-- 
Joe

[toc] | [prev] | [next] | [standalone]

#26561

The Natural Philosopher <tnp@invalid.invalid> writes:

> My limited experience of IMAP suggests that only when you delete mail on the
> client, does it delete it on the server.
>
> Just downloading it is not enough, and if you delete it on the client, then
> its gone , so if you want to keep mail on the client but not on the server
> you can't do it.

Some mail clients do try to keep their local folders synced with the remote,
because they assume that's what the user wants: he can login with various
clients and see the same content.  But nothing about IMAP requires that.

My fetchmail is configured to get mail from two IMAP servers (and a few POP3
servers).  In one case, it has the 'keep' option specified, so it gets a
message, spools it out to SMTP at localhost (which is qmail which sends it on
to my maildir), then moves on to the next message.

In the other case, it doesn't have the 'keep' option set, so it gets a
message, spools it out to SMTP at localhost -- and then (if that was
successful) tells the server to delete it, then moves on to the next message.

In both cases, fetchmail is the "client," yet it has no idea what local copies
of anything I have, so it certainly can't tell the server what to keep/delete
based on that.


-- 
Aaron -- aaron.baugher.biz

[toc] | [prev] | [next] | [standalone]

Page 2 of 3 — ← Prev page 1 [2] 3  Next page →

Back to top | Article view | alt.os.linux.slackware

csiph-web