On Fri, 2005-04-22 at 15:20 +0200, Willy van Gulik wrote:
[...]
I own a car and didn't plugged the antenna so I m unable to receive any
FM Radio and so on. My building hasn't any antenna connection to cable
or whatever.
[...]
Sorry, this might be fully OT, but never mind.
Let's back up the
On Fri, 2005-07-15 at 10:00 +0200, Martin Ebnoether wrote:
Even here at GPS Technik AG, customers do call in.
We don't sell ADSL or do ADSL but people complain
anyway.
Also here customers called in saying I can't reach...
Cheers
- Dan
___
swinog
Hi Marco
On Tue, 2006-02-28 at 11:28 +0100, Marco Balmer wrote:
Has everyone experiences with good and bad blacklists for mail-servers?
For the moment I use the following three:
relays.ordb.org
sbl-xbl.spamhaus.org
bl.spamcop.net
What about dnsrbl.swinog.ch? :-D
or: dnsbl.sorbs.net is
EHLO
On Wed, 2006-07-26 at 08:21 +0200, Viktor Steinmann wrote:
- We all agree OoO should not be sent to Mailinglists. This can usually
be achieved by checking for precedence bulk and not replying to those.
The easiest way to achieve that, is to use a separate mail box to handle
mailing list
On Tue, 2006-08-15 at 17:35 +0200, Matthias Hertzog wrote:
We're facing a growing amount of automatically generated HTTP POST requests,
all containing spamvertising links
We are also struggling with this issue, but not only since a few days or
weeks. I get 3-6 abused forms each day!
IMO it's
On Fri, 2006-09-22 at 15:07 +0200, Gunther Stammwitz wrote:
Some performance measurements from Frankfurt:
Back to our studies, we tried to implement a system, that periodically
stores traceroutes from looking glass servers to some other endpoints.
The main goal was to display a map which shows
On Mon, 2006-11-27 at 17:58 +0100, Rene Luria wrote:
It is due to bounces coming from everywhere. Spamers using fake email
addresses from domains for which we are the MX.
The amount of such emails (which we almost all reject, user unknown,
etc.. because of the fake email addresses) is
On Thu, 2007-10-04 at 15:41 +0200, [EMAIL PROTECTED] wrote:
So what is your proposal?
there are several solutions:
a. quit the company
b. fire / mob the mcma (mentally challenged mail admin)
c. install your own mailexchanger and forward all mails to that one
d. slap the mcma until he
On Fri, 2007-11-02 at 21:46 +0100, Marco Meile wrote:
We have some Problems with the UCEProtect.net blacklist.
We considered UCEprotect as absolutely unreliable and unprofessional and
are ignoring listings there. And I think so are 'the big swiss ones'.
And for sure, it's impossible to handle
On Wed, 2007-11-07 at 10:54 +0100, Per Jessen wrote:
commercial
Nah, leave the spam-filtering to us :-)
The user and the ISP both have better things to do.
/commercial
:-D
- Dan
___
swinog mailing list
swinog@lists.swinog.ch
On Wed, 2007-11-07 at 12:29 +0100, Charles Buckley wrote:
The provider moved instantaneously to identify the offender and kick them
out. The compromised SMTP account is now closed. But, just as Sunrise,
they are not willing to pay the fee to SORBS to change the status on the
list.
As ISP
On Mon, 2007-11-26 at 14:39 -0800, Scott Weeks wrote:
Lynx says it all:
** Bad HTML!! ...snipped stuff here...
No wonder:
Taken out of 'the real site' shown in msie:
!-- index.php
Start von shop-pizza.novalku.com
äöü 07.10.01
--
!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01
Dear Claus
On Thu, 2008-01-17 at 02:41 +0100, Claus v. Wolfhausen wrote:
we have Level 1 listed the IP 195.162.162.159 spamming the list with
it's
stupid autoresponder,
so if swinog uses UCEPROTECT-Level 1 the loop should be broken now.
Tell me, that you are not really blocking IPs because
I've tested some connections I have access to with a pretty interesting
result:
- Two BB accesses within AS8404, one got access to [1], the other one
not!
- One ADSL behind AS21494 works fine.
- Upstream traffic over AS13030 works fine.
To me it seems like a large IP block on Akamai spread over
On Tue, 2008-01-29 at 01:05 -0800, Christian Jouas wrote:
8404 has some Akamai servers inhouse
This is it!
Changed nameserver to AS8404 nameservers, Sites had been available
again. So it seems that Akamai traffic is not allowed to cross AS8404
but has to be loaded from the Akamai servers within
On Tue, 2008-01-29 at 01:05 -0800, Christian Jouas wrote:
8404 has some Akamai servers inhouse
And we are using our own name servers which are not behind 8404 access
network. That could be the reason. Stdby...
- Dan
___
swinog mailing list
On Mar 12, 2008, at 9:08 AM, Matthias Hertzog wrote:
Does anyone else in here receives phone calls, that websites and
mailservers cannot be reached from bluewin ADSL?
Yes, we too. Customers report, that instead of our company site they
receive a my-space site with our logo on it.
Cheerz
On Oct 15, 2008, at 11:01 AM, Marco wrote:
we made the experience that not greylisting itself is the problem. the
problem are miss configured mailservers with wrong queue times or
servers interpreting the greylisting temp error code as an error.
There are times, where the sending MTAs queue
On Thu, 2008-11-13 at 11:39 +0100, Viktor Steinmann wrote:
alternative to managing IP addresses
on a Spreadsheet...
I personally prefer any Wiki to a Spreadsheet. It's able to handle
multiple users at a time, searchable, versionised and has about the same
clarity.
- Dan
Mike Kellenberger wrote:
totally correct, thanks! Looks like I'm the stupid SysAdmin as well... :-)
Actually, this problem is known since ages. I wonder, why you fall into
that right now.
But what I really realise is, that this list is populated by Swiss
Hosting Sysadmins from all important
Pascal,
Pascal Gloor wrote:
It should be Note that, like mirror.switch.ch and many other of our
services, this is reachable over IPv4 in addition to IPv6
As long as IPv6 is not availabe for the end user *by default* (and I
mean that as a broad hint for all the big xDSL and Cable providers),
Stanislav Sinyagin wrote:
last AprilMartin Blapp has presented a nice concept at SwiNOG:
instead of greylisting, the SMTP server delays the first OK response to
HELO/EHLO
for 30 seconds. That is usually enough for the vast majority of spambots to
give up.
On a heavy traffic mail server,
Hi Benjamin
Am 1/28/10 4:51 PM, schrieb Benjamin Schlageter:
Just running normal ISP services like dhcp, dns, webserver and so on.
Main focus is the long support, maybe I'll wait for 10.04 LTS - so I got
support to the year 2015:)
I run several Ubuntu Server boxes. For the services you
Am 2/21/10 10:49 AM, schrieb Alexandre Suter:
You can find 2.5 trays on e-bay though (look for the corresponding Sun
part number).
For HP ProLiant users, that one could be very handy:
http://www.pcp.ch/product-1a15080534.htm?parnr=12832879
Cheerz,
- Dan
Am 5/7/10 10:39 AM, schrieb Pascal Gloor:
Yet again a fantastic FAIL of an ALL-IN-ONE-CAN-ALSO-DO-COFFEE firewall.
As long as it doesn't fail to brew coffee, I thing that device is still
doing it's duty.
scnr,
- Dan
___
swinog mailing list
love to. I'm using Geoff Huston's BGP data for
the time being, but other pointers could be useful.
Thanks
T
On 5/18/10 2:50 PM, Daniel Kamm wrote:
Hello Thomas,
are you looking for BGP tables back on 2000? I remember I was using some
online BGP table archive for a study work of mine, but I cant
Dear Serge
On 11/11/2010 08:22 AM, Serge Droz wrote:
From different third parties we receive a fairly large number of URLs in
.ch/.li ccTLDs which distribute malware. We're talking a few hundred URLs per
week. In a first step SWITCH verifies that this claim is true.
On the first glance, this
On 11/11/2010 11:01 AM, Martin Jaggi wrote:
You did mention AEFV SR784.104. Art 14bis requires Switch to do this:
Die Registerbetreiberin muss einen Domain-Namen blockieren und die
diesbezügliche Zuweisung zu einem Namenserver aufheben:
a.
wenn der begründete Verdacht besteht, dass
Uhu!
On 06.04.2014 02:48, Matthias Hertzog wrote:
$ ping www.bluewin.ch
ping: cannot resolve www.bluewin.ch: Unknown host
The authoritative nameserver do not answer:
adnso1.bluewin.ch [195.186.196.180]
adnso2.bluewin.ch [195.186.196.190]
adnsz1.bluewin.ch [195.186.145.180]
adnsz2.bluewin.ch
Do any other also got troubles in messaging @bluewin.ch customers?
Nov 2 14:32:54 postfix/smtp[8102]: : to=,
relay=mxbw.lb.bluewin.ch[195.186.99.50]:25, delay=0.07,
delays=0/0/0.03/0.03, dsn=5.5.0, status=bounced (Protocol error: host
mxbw.lb.bluewin.ch[195.186.99.50] said: 250
Many thanks to Marcel Gschwandl, we are still investigating together the
root cause for these problems.
For a workaround, try to disable TLS for @bluewin.ch and @bluemail.ch
Postfix/main.cf
smtp_tls_policy_maps = hash:/etc/postfix/tls_policy
# cat tls_policy
bluewin.ch none
bluemail.ch none
On 19.03.2016 22:35, Gregor Riepl wrote:
Oder ein Script basteln das das Captcha löst und automatisiert das
Abuse-Formular ausfüllt...
Yes!! Automatically spamming Hotmail Abuse Desk with IP removal requests
for 127.0.0.0/8. Go ahead please!
Regards,
- Dan
Hey mates,
Sorry for off topic, but I've just got hoaxed by someone by adding one
of my email addy to quite a number of newsletter lists, manually. Though
most of them are on opt-in nicely. Seems like I've tread on someones
toes lately.
However, I am quite curious who it was or, at least,
33 matches
Mail list logo