Re: Getting around ISP SMTP firewall settings (Re: Submitting a new port if send-pr is broken)
Ted Mittelstaedt wrote: [deleted] Don't know but a dime is too much right now (I am personally living on $15/mo once the rent, food and connectivity is paid for [the wonders of a startup with no investors]). That is one reason why colo is not possible... yes I understand most of the hassles involved since I was the head sysadmin for a full service ISP in a former life (mid to late 90's). Well, I think your stuck paying money for a service, but there are some cheap ones out there. This guy is pretty cheap: http://www.domainmx.net/ This one is free - if you can deal with UUCP and the LD charges to access with it: http://www.bungi.com I have a similar "virtual company" with people all over the place. I was running everything locally at one time. Since my (FreeBSD) router is always up, and my provider keeps the IP the same it worked for me. There were some reverse DNS issues where incoming mail from say AOL wouldn't make it but for me it was "who cares". The senders I cared about worked. I since moved mail for my domains to http://www.csoft.net. These guys fit my budget ($15/mo), provide a static IP, let me pick FreeBSD as my server (vs. OpenBSD or Linux last time I checked; there may be other choices now.) I also get shell access which lets me port forward when needed to get around providers (or hotels) that block ports I need. Last I checked, there are no bandwidth or other restrictions. They are also very open source friendly. MikeC ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Getting around ISP SMTP firewall settings (Re: Submitting a new port if send-pr is broken)
>To be perfectly clear this isn't really receiving mail. Your >configuring a system at dydns.org or some other mail forwarder to >receive your mail for you then forward it on to your system using the >alternative port. Not what I am doing. I only suggested that to the original poster who has an inbound port25 restriction. I receive all my important email directly. >Frankly, unless you processing mail for a lot of people, there is no >benefit to running your own mailserver, and you really ought to be >using a client-server model for getting mail, as you are doing. The >OP just hasn't realized this yet. There are very good reasons why one might want to receive mail directly. I live and work aboard a trawler, I do not always have the same ISP for connectivity. At the home dock, I have DSL, underway, I have a satellite link, close to shore while cruising, or anchored, I have Sprint some marinas offer 80211, etc My "Important" email, like weather/navigation alerts, family e-mail, work related email is delivered directly to the on-board server, which has a name.servebbs.org, and is kept DNS's properly via dyndns. All of my outbound email is smart-hosted to another ISP on port 587 Start TLS. This way, I do not have to have any special access to any particular ISP to get and send email, it shows up immediately, and I am notified. Bob -- _ /o\ // \\ The ASCII \\ // Ribbon Campaign \V/ Against HTML /A\ eMail! // \\ signature.asc Description: PGP signature
RE: Getting around ISP SMTP firewall settings (Re: Submitting a new port if send-pr is broken)
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Aryeh M. > Friedman > Sent: Monday, November 26, 2007 11:40 PM > To: Ted Mittelstaedt > Cc: freebsd-questions@freebsd.org; Bob Richards > Subject: Re: Getting around ISP SMTP firewall settings (Re: Submitting a > new port if send-pr is broken) > > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > > > > > > Really, as others have said, it's easier to pay the money for the > > business line. How much extra do they want for it? > > Don't know but a dime is too much right now (I am personally living on > $15/mo once the rent, food and connectivity is paid for [the wonders > of a startup with no investors]). That is one reason why colo is not > possible... yes I understand most of the hassles involved since I was > the head sysadmin for a full service ISP in a former life (mid to late > 90's). > Well, I think your stuck paying money for a service, but there are some cheap ones out there. This guy is pretty cheap: http://www.domainmx.net/ This one is free - if you can deal with UUCP and the LD charges to access with it: http://www.bungi.com Is there any way you could get your webhoster to be a bit more flexible on their e-mail forwarding? If for example you could get them to forward your e-mail to a script run out of your .forward file on their webserver, you got it made. They might do that since it wouldn't require them to devote disk space to a mailbox on their server. You would write a perl script that would make a connection to a nonstandard port on your mailserver. Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Getting around ISP SMTP firewall settings (Re: Submitting a new port if send-pr is broken)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > > > Really, as others have said, it's easier to pay the money for the > business line. How much extra do they want for it? Don't know but a dime is too much right now (I am personally living on $15/mo once the rent, food and connectivity is paid for [the wonders of a startup with no investors]). That is one reason why colo is not possible... yes I understand most of the hassles involved since I was the head sysadmin for a full service ISP in a former life (mid to late 90's). - -- Aryeh M. Friedman Developer, not business, friendly http://www.flosoft-systems.com -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHS8nGJ9+1V27SttsRArd6AKCRhAduE7P7roZB4x+WohcR1NCUQQCfX6zu i1rqakoG9WshIdsHHYQQdt4= =lWnQ -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Getting around ISP SMTP firewall settings (Re: Submitting a new port if send-pr is broken)
> -Original Message- > From: Aryeh M. Friedman [mailto:[EMAIL PROTECTED] > Sent: Monday, November 26, 2007 10:02 PM > To: Aryeh M. Friedman > Cc: Ted Mittelstaedt; Bob Richards; freebsd-questions@freebsd.org > Subject: Re: Getting around ISP SMTP firewall settings (Re: Submitting a > new port if send-pr is broken) > > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Aryeh M. Friedman wrote: > > > > > Frankly, unless you processing mail for a lot of people, there is no > > > benefit to running your own mailserver, and you really ought to be > > > using a client-server model for getting mail, as you are doing. The > > > OP just hasn't realized this yet. > > > > Actually I am processing mail for over a dozen people and almost 100 > > diff addrs so it does make sense if it is possible. > > > > > > Oops forgot to mention there is a small set of complicating factors: > > 1. The people and addrs I process mail for all have the same domain > but live in locations all around the globe (virtual company) > > 2. The domain should/must be the same as the company's web page (see > my sig for addr) which is on a convention web hosting arrangement > > 3. As far I can all inbound/outbound smtp/http (25, 587, and 80) are > blocked by the ISP (they offer them under a business package that also > includes a static IP but currently that is too pricey) > You really need to clarify what you mean by inbound and outbound. I'll assume that by inbound, you mean you cannot have inbound connections to ports 25, 587, and 80. This is perfectly legitimate for a residential ISP connection. I'll assume that by outbound, you mean you cannot have outbound connections to ports 25, 587, and 80. This is silly. A block on an outbound connection to port 80 would mean you couldn't surf the web. I'll assume you mean that outbound port 25 is blocked to everywhere except for the ISP's own mailserver. That also is perfectly legitimate for a residential ISP connection. A block on an outbound port 587 connection has only ONE purpose, to prevent you from using a legitimate mailserver for sending mail other than the ISPs server. Servers on the Internet that respond to port 587 are only supposed to relay mail from AUTH connections to 587 so allowing ISP customers to use 587 is not a security or SPAM problem. 587 is not used for server-to-server mail traffic. If your ISP is indeed blocking outbound 587 then you have justifyable reasons to scream and bitch, and they do NOT have any justifyable reason to block it. None of the large cable or DLS providers block outbound 587 > 4. The ISP is the only one in my area (semi-rural) that offers high > speed bandwidth > > 5. Even though my web hoster offers mail forwarding it does not offer > mail box and/or mailing list hosting (having prepaid for 2 years and > only being 2 months into the deal I am not going to switch providers) There's plenty of ISP's on the Internet that offer mailboxes only. I can't fault your webhoster for not wanting to get into offering mailboxes. It is a speciality, just as webhosting is a speciality. What you really should have done, (of course hindsight is a great revealer) is to have contracted with an ISP where you could have colocated a server. For probably $100 a month you could have your own box with a public IP address and run a mailserver on it, hosted your website on it, and you could have modified it so that instead of port 587, you did auth-smtp on port 588 and then gotten around your ISP's block on outbound 587 (if infact, such exists) You really only have 2 non-business connection choices as I see it. First, contract with some ISP that will sell you a mailbox that will take domain mail. Next build a mailserver at your site that uses fetchmail to pop down that mail and port 587 to send it out. Last, on your site mailserver, setup a pop3 or imap server that uses a non-standard port#, then config your road warrior clients to use that port, or setup a webmail interface and use a URL like webmail.flosoft-systems.com:86/webmaillogin.cgi to access it. This assumes outbound port 110 and 587 are NOT blocked. If outbound port 587 and 110 ARE blocked, then you cannot do anything other than the colocated box that has all non-standard ports, OR say hell with it and work out a deal with an ISP to do virtual mailboxes and mailhosting. If you want to do that last, I'd be happy to pitch pricing to you for my employer off list. (as no doubt, many other list readers could) Really, as others have said, it's easier to pay the money for the business line. How much extra do they want for it? Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Getting around ISP SMTP firewall settings (Re: Submitting a new port if send-pr is broken)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Aryeh M. Friedman wrote: > > > Frankly, unless you processing mail for a lot of people, there is no > > benefit to running your own mailserver, and you really ought to be > > using a client-server model for getting mail, as you are doing. The > > OP just hasn't realized this yet. > > Actually I am processing mail for over a dozen people and almost 100 > diff addrs so it does make sense if it is possible. > > Oops forgot to mention there is a small set of complicating factors: 1. The people and addrs I process mail for all have the same domain but live in locations all around the globe (virtual company) 2. The domain should/must be the same as the company's web page (see my sig for addr) which is on a convention web hosting arrangement 3. As far I can all inbound/outbound smtp/http (25, 587, and 80) are blocked by the ISP (they offer them under a business package that also includes a static IP but currently that is too pricey) 4. The ISP is the only one in my area (semi-rural) that offers high speed bandwidth 5. Even though my web hoster offers mail forwarding it does not offer mail box and/or mailing list hosting (having prepaid for 2 years and only being 2 months into the deal I am not going to switch providers) - -- Aryeh M. Friedman Developer, not business, friendly http://www.flosoft-systems.com -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHS7K8J9+1V27SttsRAoO0AKCaofoaJd+fg0qNXQDYaQ7lcBkeswCglitn W0VpYc+LO3eronkojgV9lwc= =UWBT -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Getting around ISP SMTP firewall settings (Re: Submitting a new port if send-pr is broken)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > > Frankly, unless you processing mail for a lot of people, there is no > benefit to running your own mailserver, and you really ought to be > using a client-server model for getting mail, as you are doing. The > OP just hasn't realized this yet. Actually I am processing mail for over a dozen people and almost 100 diff addrs so it does make sense if it is possible. - -- Aryeh M. Friedman Developer, not business, friendly http://www.flosoft-systems.com -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHS7CnJ9+1V27SttsRArGMAJ4xhax13Nd/ikb2CSQikEJVmrAzRwCeLxhT jz/Qhcjy8jmzwq/QP8g0i7g= =9928 -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Getting around ISP SMTP firewall settings (Re: Submitting a new port if send-pr is broken)
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Bob Richards > Sent: Monday, November 26, 2007 3:45 AM > To: freebsd-questions@freebsd.org > Subject: Re: Getting around ISP SMTP firewall settings (Re: Submitting a > new port if send-pr is broken) > > > On Mon, 26 Nov 2007 13:15:59 +0200 > Giorgos Keramidas <[EMAIL PROTECTED]> wrote: > > > > > I don't think there's an easy way to set up the local Sendmail > > installation to *receive* email from the world without some sort of > > `static address' though. > > Actually there is an easy way, I do it here at my work station which is > on a boat, and uses many different modes of connectivity. All of which > are floating IPs. > > Get a domain name at dyndns. ANYTHING.servebbs.com/net/org. (it's free) > > You can also DNS any domain you own for about $29.00/Year, and simply > MX your mail to your dynamic domain machine on a variety of alternative > ports. > To be perfectly clear this isn't really receiving mail. Your configuring a system at dydns.org or some other mail forwarder to receive your mail for you then forward it on to your system using the alternative port. You can just as easily set up a mailbox on the dydns server (or whoever will sell you a mailbox - tons of ISPs will do it) and fetchmail your mail via POP3 from it. > Install ddclient on your machine; it will keep your IP updated at > dyndns. > > Install an mta, like sendmail, and smart-host it to your ISP; or > smart-host it to dyndns if your ISP can't/won't do it. > > I have been doing this for about 2 years now, and have had no problems > at all. > I'm sure you don't because in effect your doing exactly the same thing that any typical e-mail client does - your offloading the heavy lifting of receiving mail - the spam and antivirus filtering - to a real mailserver somewhere on the Internet. Frankly, unless you processing mail for a lot of people, there is no benefit to running your own mailserver, and you really ought to be using a client-server model for getting mail, as you are doing. The OP just hasn't realized this yet. Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Getting around ISP SMTP firewall settings (Re: Submitting a new port if send-pr is broken)
On Mon, 26 Nov 2007 13:15:59 +0200 Giorgos Keramidas <[EMAIL PROTECTED]> wrote: > > I don't think there's an easy way to set up the local Sendmail > installation to *receive* email from the world without some sort of > `static address' though. Actually there is an easy way, I do it here at my work station which is on a boat, and uses many different modes of connectivity. All of which are floating IPs. Get a domain name at dyndns. ANYTHING.servebbs.com/net/org. (it's free) You can also DNS any domain you own for about $29.00/Year, and simply MX your mail to your dynamic domain machine on a variety of alternative ports. Install ddclient on your machine; it will keep your IP updated at dyndns. Install an mta, like sendmail, and smart-host it to your ISP; or smart-host it to dyndns if your ISP can't/won't do it. I have been doing this for about 2 years now, and have had no problems at all. Bob -- _ /o\ // \\ The ASCII \\ // Ribbon Campaign \V/ Against HTML /A\ eMail! // \\ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Getting around ISP SMTP firewall settings (Re: Submitting a new port if send-pr is broken)
> On November 26, 2007 at 04:00AM Aryeh M. Friedman wrote: > > You should be able to set up a local mailer/MTA (sendmail, postfix, > > etc.) and tell it to use your ISP's mail server on TCP port 25, and it > > all should just "magically work" unless they require SMTP AUTH (not many > > do from what I've seen; they base authentication on the source IP of > > customers). > > > > sendmail refers to this feature as SMART_HOST, while postfix refers to > > it as a transport destination (see transport(5)). > > I have not set the MTA up yet for it but I did test it with > thunderbird... an other question how can I set it up that I can > receive mail (dynamic IP and 25 inbound is blocked)? If you attempt to send mail using a dynamic IP, it is going to be blocked by most MTAs since it fails reverse DNS checking. I am assuming that you are attempting to bypass your ISP. You have to get a static IP from your provider. With port 25 presently blocked, you might consider using something like mail relaying/forwarding from a service like DYNDNS: http://www.dyndns.com/. -- Gerard ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Getting around ISP SMTP firewall settings (Re: Submitting a new port if send-pr is broken)
On 2007-11-26 04:00, "Aryeh M. Friedman" <[EMAIL PROTECTED]> wrote: >BTW I a redirected this to -questions >> You should be able to set up a local mailer/MTA (sendmail, postfix, >> etc.) and tell it to use your ISP's mail server on TCP port 25, and >> it all should just "magically work" unless they require SMTP AUTH >> (not many do from what I've seen; they base authentication on the >> source IP of customers). >> >> sendmail refers to this feature as SMART_HOST, while postfix refers >> to it as a transport destination (see transport(5)). > > I have not set the MTA up yet for it but I did test it with > thunderbird... an other question how can I set it up that I can > receive mail (dynamic IP and 25 inbound is blocked)? Thunderbird doesn't necessarily go through an SMTP connection to the local host, so it may work with or without a local MTA installation & setup (depending on which host you forward outgoing email). If you set up Thunderbird to use `localhost' for outgoing email, then you have to also configure a local MTA (Sendmail, Postfix, or qmail are popular choices). I don't think there's an easy way to set up the local Sendmail installation to *receive* email from the world without some sort of `static address' though. To do that, you would have to work with your ISP, so that: * Your address does not change semi-randomly or ramdonly. * Your fully qualified domain resolves correctly and its MX records point to your static IP address. * Your incoming port 25 traffic is not filtered. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
