Hi, we plan to support SPF soon. Shure it's not perfect as long as the majority of ISPs will not take part or the entries are just wrong or very open. But that's only a question of time and "critical mass". As soon as this is reached, everybody not using it will be "punished" with bad spam filter results and that's a selling point.
For customer with internet connections outside our IP ranges and port 25 blocked, we just give our customer an alternative port on our mailserver. For the customer its a part of the "access" data they get anyway. They can then either send with "POP before SMTP" or "SMTP with auth". In plus our limits (size/mail, receivers/mail, mails/time etc) are normaly higher than with a "cheap" access provider and already because of this, we recommend the customer to send through us. I don't realy see a need for a script or something else...but maybe I've missed something... Regards Ralf Zenklusen Dipl. El-Ing HTL --- BAR Informatik AG Gliserallee 16 CH-3902 Brig-Glis Schweiz Tel: +41 27 922 4848 Fax: +41 27 922 4849 www.barinformatik.ch www.rhone.ch -----Urspr�ngliche Nachricht----- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Auftrag von Daniel Lorch Gesendet: Mittwoch, 4. August 2004 14:57 An: [EMAIL PROTECTED] Betreff: Re: [swinog] Implementing SPF Hi > An other problem will arise if ISPs force there customers to use > there own SMTP relay server because they are blocking outbound > traffic to tcp/25. So this customers can not use the SMTP relay > server of there domain hosting provider with SMTP Auth (and > hopefully TLS) on tcp/25. Valid point. One of the ideas we came up with was to provide customers with a mail address they could send a mail to. A script would then parse the headers and add the server(s) found to the SPF record. Only caveat: some ISPs use more than one IP address for outbound mail so you can never be sure you got all servers in your list. That's why you all need to adopt SPF. There is a "include" directive in SPF which would allow us to include, say bluewin's or tiscali's outbound mailservers, _given that they provide these records_. http://spf.pobox.com/mechanisms.html#include > I see still to many problems with systems like SPF, to much work > for only a little advantage. Because if big domains like gmx or > yahoo just put 0.0.0.0/0 in the SPF DNS entry it is just useless. Consider it a stub record - as much as SA 3.0's implementation of SPF is .. well .. not yet perfect :) The wider SPF has been adopted, the more sense it will make to support it. Or do you know of any other technology which would allow you to do what SPF does? Use your imagination - tell customers they can protect their domains from abuse when they enable SPF. That's another selling point! -- Kind Regards Daniel Lorch Positive Feedback Cycle Engineer Hostpoint GmbH � � � �| The Data Residence � �| Z�rcherstrasse 2 � � �| 8640 Rapperswil � � � | Schweiz Tel �+41 55 220 0404 �| Fax �+41 55 220 0409 �| www.hostpoint.ch _______________________________________________ swinog mailing list [EMAIL PROTECTED] http://lists.init7.net/cgi-bin/mailman/listinfo/swinog _______________________________________________ swinog mailing list [EMAIL PROTECTED] http://lists.init7.net/cgi-bin/mailman/listinfo/swinog
