yeah, true. the IMAP client might think all remote messages are gone, and then flush the local cache... not nice :)
then we just need the protocol handling part from Courier, and report an error message to the user immediately after connect.
But anyway, Steven, why do you want to block pop/imap on a hotspot?
----- Original Message ----
From: Marc SCHAEFER schaefer@alphanet.ch To: Stanislav Sinyagin ssinyagin@yahoo.com Sent: Saturday, May 16, 2009 6:26:58 PM Subject: Re: [swinog] special mail solution?
On Fri, May 15, 2009 at 11:56:50AM -0700, Stanislav Sinyagin wrote:
then the daemon will report an error when trying to delete the message. As it's a hotspot device, we don't want its syslog overflown with such
things:)
The whole idea seems wrong, because you will be messing with the user agent message counter/message ID.
Aka the user agent will think the new state of the mailbox is the one you present, which might have mild implications with POP, but big ones with IMAP.
Just have an error message.
how about the simple solution to send an email to every mailbox, stop the server getting any new incoming mail and simply "leave everything alone".
I dont know the mailboxes ,-) I even dont know the configuration of the users ,-)
-steven
Andreas Fink wrote:
how about the simple solution to send an email to every mailbox, stop the server getting any new incoming mail and simply "leave everything alone".
swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
But anyway, Steven, why do you want to block pop/imap on a hotspot?
because i'm evil ,-) after I informed the customer by this mail (and a website) he can get access again to his mailbox. just want to inform that he might be virus infected or so ,-)
-steven
Hey Steven
Steven Glogger wrote:
But anyway, Steven, why do you want to block pop/imap on a hotspot?
because i'm evil ,-)
Or your company is. ;)
after I informed the customer by this mail (and a website) he can get access again to his mailbox. just want to inform that he might be virus infected or so ,-)
Couldn't that be known as 'man in the middle' attack? As I understand right, your server first will receive username/password credentials of a foreign user. So for every spammer, it will be veeery interesting to get that box hacked.
Regards, - Dan
On 18.05.2009, at 15:06, Daniel Kamm wrote:
Hey Steven
Steven Glogger wrote:
But anyway, Steven, why do you want to block pop/imap on a hotspot?
because i'm evil ,-)
Or your company is. ;)
after I informed the customer by this mail (and a website) he can get access again to his mailbox. just want to inform that he might be virus infected or so ,-)
Couldn't that be known as 'man in the middle' attack? As I understand right, your server first will receive username/password credentials of a foreign user. So for every spammer, it will be veeery interesting to get that box hacked.
And very annoying for every person using IMAP/s who sees a certificate error.
Usually when I see that, I assume that I'm not logged onto the hotspot correctly, and cancel the connection.
Many people will never see this funny little email.
Why not think of another way to provide the information, like at logon?
Chris
PS: there may be some legal ramifications for running a MITM attack as a matter of business practices. There's a similar thread going on at NANOG right now about how people have forced providers to stop using transparent proxies. You might want to read that.
-
Andreas Fink -
Chris Meidinger -
Daniel Kamm -
Stanislav Sinyagin -
Steven Glogger