search for: hessler

There are a couple of jerks that are tying to dictionary attack my email server, and one of the vectors is pop3/imap logins. Something I would like to do in dovecot, but can't seem to find, is the ability to disconnect after a certain number of errors. The vast majority of my users (i.e. me) don't hand-type POP3 or IMAP transactions, but when we do, we know how to spell things

I am seeing a problem where users are limited to 6 imap logins total. One of my users has a bunch of phones and computers, and wants them all on at the same time. I'm looking through my configuration, and I cannot see a limit on how many times a single user can connect. He is connecting from different IPs. Any ideas? My logs show the following error when they attempt to auth for a 7th

...pecified. For the most part it is working, but every so often, the auth freaks out for one (random) account. The error for one example is below: Aug 18 11:13:12 gir dovecot: login: Authentication process 21082 doesn't exist Aug 18 11:13:12 gir dovecot: pop3-login: Internal login failure: phessler [208.201.244.164] This happens on both v4 and v6 connections, but infrequently. If you try again immediatly, it works. If I do a `ps -p 21082` I can see the process (dovecot-auth). This does not happen when I have only one dovecot process running. What is the best way to have multiple dovecot...

I cannot download emails that are larger than 10k. I can download them fine with test32. I am running test35 on OpenBSD/macppc -current. I am downloading the files with Sylpheed-Claws 0.9.9claws on OpenBSD/macppc -current (different machines), over pop3-ssl on IPv6. Problem still occurs with IPv4. On the large files, the download hangs at 4.0k. Multiple small emails work fine. -- A day

Sometimes I'll get an email from a luser which will cause the POP3 daemon to sig11. The email "appears" to be legal. The sig11s only happen on specific emails, and once I remove the emails from the server, the rest can be downloaded. I gzipped the email, and its at http://theapt.org/bogusemail.gz. While this example is international spam, the sig11s happen with real emails too.

Nov 18 17:29:54 gir dovecot: imap-login: Login: jmcvetta [69.106.50.255] Nov 18 17:30:02 gir dovecot: IMAP(jmcvetta): file mail-index-transaction.c: line 247 (mail_index_expunge): assertion failed: (!t->view->external) Nov 18 17:30:02 gir dovecot: child 31094 (imap) killed with signal 6 I saw this in my maillog. I have no idea what that user is doing, but I can harrass him and find out if

I was looking at some new mobile phones, and apparently there is a form of IMAP that is optimized for mobiles called M-IMAP. Its not a rush (since I'm not even sure the phones will be out before Q2), but it'd be a cool thing to have. The spec is in the following PDF. http://www.3gpp2.org/Public_html/specs/X.S0016-311_v1.0_022404.pdf -- Klein bottle for sale ... inquire within.

On 2007 Jul 26 (Thu) at 09:32:00 -0400 (-0400), Jared Smith wrote: :On Wed, 2007-07-25 at 15:06 -0700, Peter Hessler wrote: :> ;; dialtone in the background isn't there any more :> ;; dialed '305' :> ;; everything from here is exactly as expected. : :OK, I missed this in the first email you sent... Asterisk is playing :dialtone *on top* of the background message the first time around? That...

On 2007 Jul 26 (Thu) at 09:32:00 -0400 (-0400), Jared Smith wrote: :On Wed, 2007-07-25 at 15:06 -0700, Peter Hessler wrote: :> ;; dialtone in the background isn't there any more :> ;; dialed '305' :> ;; everything from here is exactly as expected. : :OK, I missed this in the first email you sent... Asterisk is playing :dialtone *on top* of the background message the first time around? That...

On 2007 Jul 26 (Thu) at 09:32:00 -0400 (-0400), Jared Smith wrote: :On Wed, 2007-07-25 at 15:06 -0700, Peter Hessler wrote: :> ;; dialtone in the background isn't there any more :> ;; dialed '305' :> ;; everything from here is exactly as expected. : :OK, I missed this in the first email you sent... Asterisk is playing :dialtone *on top* of the background message the first time around? That...

On 2007 Jul 26 (Thu) at 09:32:00 -0400 (-0400), Jared Smith wrote: :On Wed, 2007-07-25 at 15:06 -0700, Peter Hessler wrote: :> ;; dialtone in the background isn't there any more :> ;; dialed '305' :> ;; everything from here is exactly as expected. : :OK, I missed this in the first email you sent... Asterisk is playing :dialtone *on top* of the background message the first time around? That...

On 2007 Jul 26 (Thu) at 09:32:00 -0400 (-0400), Jared Smith wrote: :On Wed, 2007-07-25 at 15:06 -0700, Peter Hessler wrote: :> ;; dialtone in the background isn't there any more :> ;; dialed '305' :> ;; everything from here is exactly as expected. : :OK, I missed this in the first email you sent... Asterisk is playing :dialtone *on top* of the background message the first time around? That...

On 2007 Jul 26 (Thu) at 09:32:00 -0400 (-0400), Jared Smith wrote: :On Wed, 2007-07-25 at 15:06 -0700, Peter Hessler wrote: :> ;; dialtone in the background isn't there any more :> ;; dialed '305' :> ;; everything from here is exactly as expected. : :OK, I missed this in the first email you sent... Asterisk is playing :dialtone *on top* of the background message the first time around? That...

On 2007 Jul 26 (Thu) at 09:32:00 -0400 (-0400), Jared Smith wrote: :On Wed, 2007-07-25 at 15:06 -0700, Peter Hessler wrote: :> ;; dialtone in the background isn't there any more :> ;; dialed '305' :> ;; everything from here is exactly as expected. : :OK, I missed this in the first email you sent... Asterisk is playing :dialtone *on top* of the background message the first time around? That...

On 2007 Jul 26 (Thu) at 09:32:00 -0400 (-0400), Jared Smith wrote: :On Wed, 2007-07-25 at 15:06 -0700, Peter Hessler wrote: :> ;; dialtone in the background isn't there any more :> ;; dialed '305' :> ;; everything from here is exactly as expected. : :OK, I missed this in the first email you sent... Asterisk is playing :dialtone *on top* of the background message the first time around? That...

On 2007 Jul 26 (Thu) at 09:32:00 -0400 (-0400), Jared Smith wrote: :On Wed, 2007-07-25 at 15:06 -0700, Peter Hessler wrote: :> ;; dialtone in the background isn't there any more :> ;; dialed '305' :> ;; everything from here is exactly as expected. : :OK, I missed this in the first email you sent... Asterisk is playing :dialtone *on top* of the background message the first time around? That...

On 2007 Jul 26 (Thu) at 09:32:00 -0400 (-0400), Jared Smith wrote: :On Wed, 2007-07-25 at 15:06 -0700, Peter Hessler wrote: :> ;; dialtone in the background isn't there any more :> ;; dialed '305' :> ;; everything from here is exactly as expected. : :OK, I missed this in the first email you sent... Asterisk is playing :dialtone *on top* of the background message the first time around? That...

On 2007 Jul 26 (Thu) at 09:32:00 -0400 (-0400), Jared Smith wrote: :On Wed, 2007-07-25 at 15:06 -0700, Peter Hessler wrote: :> ;; dialtone in the background isn't there any more :> ;; dialed '305' :> ;; everything from here is exactly as expected. : :OK, I missed this in the first email you sent... Asterisk is playing :dialtone *on top* of the background message the first time around? That...

On 2007 Jul 26 (Thu) at 09:32:00 -0400 (-0400), Jared Smith wrote: :On Wed, 2007-07-25 at 15:06 -0700, Peter Hessler wrote: :> ;; dialtone in the background isn't there any more :> ;; dialed '305' :> ;; everything from here is exactly as expected. : :OK, I missed this in the first email you sent... Asterisk is playing :dialtone *on top* of the background message the first time around? That...

...1 signalling = fxs_ks channel => 9 context=from-zaptel group=0 signalling = fxs_ks channel => 10 context=from-zaptel group=0 signalling = fxs_ks channel => 11 context=from-zaptel group=0 signalling = fxs_ks channel => 12 === end of zapata.conf === $ cat extensions.conf [globals] PHESSLER=SIP/phessler FAXMACHINE=SIP/faxmachine OUTBOUNDTRUNK=Zap/g0 ;; inbound faxes [from-fax-line] exten => s,1,Dial(${FAXMACHINE},20) exten => s,n,Hangup() ;; define a macro to handle everyone the same ;; this way we only have to update one place ;; call it with 'Macro(user,${USERNAME}) [mac...