search for: kack

...50926daef51b50e000025ab05f8 12718 5a09f50926daef51b50e000025ab05f8 15653 5a09f50926daef51b50e000025ab05f8 15697 Moreove, when playing with HEADER Reply-To it shows some strange behaviour, note the differences with the ":" : doveadm search -u exampleuser SUBJECT blubbs HEADER Reply-to kacke at example.com f64cf50926daef51b50e000025ab05f8 2231 f64cf50926daef51b50e000025ab05f8 2781 5a09f50926daef51b50e000025ab05f8 13620 5a09f50926daef51b50e000025ab05f8 15763 doveadm search -u exampleuser SUBJECT blubbs HEADER Reply-to: kacke at example.com f64cf50926daef51b50e000025ab05f8 2231 5a09f5...

...put_teil)[1],1]==""|is.na(input_teil[dim(input_teil)[1], 1])) input_teil<-input_teil[1:(dim(input_teil)[1]-1),] else k=dim(input_teil)[1]+1 } enddatum[i]<-as.character(input_teil[dim(input_teil)[1],1]) beobachtungen[i]<-dim(input_teil)[1] } # Und wandle nun die ganze Kacke in Daten um for(i in 1:length(dateinamen)){ startdatum[i]<-as.date(startdatum[[i]]) enddatum[i]<-as.date(enddatum[[i]]) } #Baue einen Datensatz laenge complete_history<-data.frame(NA,nrow=laenge, ncol=length(dateinamen)+1) #1. Spalte: von niedrigsten Startdatum bis höchs...

I'm trying to formulate a strategy for our interconnected Asterisk IAX peers to failover to the PSTN in the event of a DDoS. We currently use them like this: DID--->PRI--->Primary Asterisk--->IAX--->On-site Asterisk--->SIP This works fine, and everyone is happy. One of my concerns, though, is if we get DDoS'd - which happens probably once every couple of years. I'd