[swinog] Energie Wasser Bern Telecom is hiring
Dear all Energie Wasser Bern (ewb) Telecom is hiring a project manager for our darkfiber backbone. For further details visit this link: http://www.jobs.ch/inserate-detail/Information-technology-Telecom/Projec t-management/Projektleiter-in-Telekommunikation--/Energie-Wasser-Bern/Be rn/1832261/58/1/0 Please send applications to the contact mentioned in the job ad. Regards, Energie Wasser Bern Ruedi Hofer Network Engineer Monbijoustrasse 11, Postfach 3001 Bern ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] RBL's (again) (Was: Anyone from Green here?)
> Don't blame greylisting for this behavior. > > Queue-and-retry was an option but it is mandatory since RFC-2821. > > The very obsolete RFC-821 stated that "clients should retry". > In the old RFC-2119 it was explained that "should" means recommended. > The actual RFC-2821 states clearly that: > - "the SMTP client retains responsibility for delivery of the message" > - "the SMTP client is encouraged to try again" > - "mail that cannot be transmitted immediately MUST be queued and > periodically retried by the sender." > > You'd rather blame the lazy programmers who don't cares about RFCs and other > standards ! > fully agreed. thats a bad argument against greylisting. if php scripts or other webserver stuff, like newsletter servers, etc.. use their own MTA which is most likely a fancy carp script, as you said, then its actually not the ISPs problem if a mail won't get delivered. we have a lot of webservers with php mailforms, newsletter scripts, customer carp scripts, etc... smtp port to the internet is blocked from all servers by local and sector firewalls. they must use the local sendmail. the local sendmail on each server has a smarthost configured which is our relay mail server cluster where we're also doing greylisting. no problem with that at all. greets from Barcelona Marco > Daniele > > > Tonnerre Lombard wrote: > >> The problem is that your users go to web sites and subscribe their mail >> addresses to newsletters generated by PHP programmers. As expected, a >> lot of these try to deliver the mail directly to the destination host >> from the PHP script using some Pear SMTP crap module, rather than local >> sendmail. A typical dialog looks about like this: >> >> Out: 220 planck.ngas.ch ESMTP Postfix (2.5.1) >> In: HELO gmail.com >> Out: 250 planck.ngas.ch >> In: MAIL FROM: <[EMAIL PROTECTED]> >> Out: 250 2.1.0 Ok >> In: RCPT TO: <[EMAIL PROTECTED]> >> Out: 450 4.7.0 You are greylisted for 300 seconds >> In: DATA >> Out: 554 Error: No valid recipients >> In: From [EMAIL PROTECTED] >> Out: 221 2.0.0 error: I can break rules, too. goodbye. >> >> Not very problematic for the mail server but of course the PHP script >> does _not_ attempt redelivery. And your users go to gmail, because >> there they get the mail. Not sure that's desirable for you. >> >> That's the problem I am seeing with Greylisting, and I have discovered >> that methods like rejecting SPAM after DATA can be way more effective >> if the SPAM filter databases are sufficiently trained and the RBLs well >> chosen. >> >> Tonnerre >> >> >> >> >> ___ >> swinog mailing list >> swinog@lists.swinog.ch >> http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog >> > > ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
[swinog] Expatriate Position for ICT Security Specialists
The following *long-term expatriate* positions are open In comprehensive projects on the Arabian peninsula: 1. International Project Manager eGovernment Security http://crypto.ch/index.php?id=266 https://www.xing.com/marketplace/postings/show/290845 2. Head of Security Operation Center (eGovernment) / Leiter Security Operation Center in einem Golfstaat https://www.xing.com/marketplace/postings/show/290830 3. Integration Engineering Specialist für Sicherheitskomponenten in komplexen Datennetzen http://crypto.ch/index.php?id=264 https://www.xing.com/marketplace/postings/show/290841 4. International Solution Architect Middle East / Schweizer Solution Architect Netzwerksicherheit Middle East http://www.infoguard.ch/docs/dokumente/InfoGuard_SolArcME.pdf https://www.xing.com/marketplace/postings/show/288868 You can also find overviews about those and similar open positions on Xing: https://www.xing.com/marketplace/home/postings/list/6877234 https://www.xing.com/marketplace/home/postings/list/3263329 Swiss citizenship is preferred, but not mandatory. Currently, I am on site and can provide some first-hand "technical" information. Please send applications to the contacts indicated in the pages referenced above. Thank you for your attention.. Regards, Rolf ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] RBL's (again) (Was: Anyone from Green here?)
Salut, Daniele, On Thu, 16 Oct 2008 00:05:38 +0200, Daniele Guazzoni wrote: > You'd rather blame the lazy programmers who don't cares about RFCs > and other standards ! I think that blame is for people who don't care about solutions. I care for my users and their ability to receive the mail they want, as long as it is reasonable. While I do think that these scripts are broken and terribly wrong, I have no power over their programmers and cannot make them change the scripts. I, however, also don't have the authority to tell my users not to want to receive that newsletter. So you see, what I am saying is that greylisting prevents users from receiving these mails, not that these mails are good or correctly sent. But being a solution oriented provider, this is a clear reason why I cannot use greylisting. Tonnerre signature.asc Description: PGP signature ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] RBL's (again) (Was: Anyone from Green here?)
Salut, Marco, On Thu, 16 Oct 2008 15:22:39 +0200, Marco wrote: > fully agreed. thats a bad argument against greylisting. if php scripts > or other webserver stuff, like newsletter servers, etc.. use their own > MTA which is most likely a fancy carp script, as you said, then its > actually not the ISPs problem if a mail won't get delivered. Technically, this is perfectly right, and personally I would like to see everyone writing such scripts burn in hell. But if your users insist on receiving the mail, you will either have to disable greylisting or to get a better set of customers. This is basically the "collision" between "lazy technicians" coming up with "excuses why they're not responsible" and "stupid users who cannot do things right". I'm afraid that the purely technical point of view is not worth a dime if your users look for alternative providers. Do you see what I mean? Tonnerre signature.asc Description: PGP signature ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
