-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sandy Drobic wrote:
G T Smith wrote:
Per Jessen wrote:
Clayton wrote:
Is there some clearer documentation that anyone knows about, or some other info I can read up on? Or any obvious things that I may have missed? Port 25 on my router is forwarded... the Mail Relay is set to use port 25... not sure where to look next. Running a mailserver on a dynamic IP-address is difficult at best, but I guess it could work if your dyndns stuff is working.
Pardon!?... being doing this for a long time without major issues using DynDNS and setup is no more or less difficult than with a static address. It is an absolute must if you are running a personal mail
Uhm, are we talking about a client that is sending and receiving mail, or a server that is set up to fulfill the requirements of the corresponding RFCs?
Things are a bit more complex than that. The machine supports a number of client accounts plus some aliases that are used by a couple of secondary application to manage some classes of e-Mail communication, so while it functions as a simple 'hub' mail server and external relay for client machines, it also has some (semi-automated) client functionality. The DynDNS configuration is such that <host> and mail.<host> should act the same from external connections, however at the moment the local DNS configuration is such only the mail.<host> form will work locally (, <localhostname>.<localnet> functions as expected). The DynDNS name is a host on a DynDNS domain which is a factor in this difference of behaviour (I would expect different issues with DynDNS hosted personal domain). The original LAN was a bit more complex than current, and it is setup to handle phone and mobile connectivity from external and internal locations without the need to query an external DNS or route externally if the external name is used locally. So to some extent the mail setup is a test config. (At the moment it is being rebuilt after a rather messy hardware failure which has created a number of interesting issues that have made data recovery unexpectedly challenging :-) ).
For outgoing relay one would normally use your ISPs mail server, (or an independent smtp server in which case outgoing port info would usually need to be changed as many ISPs block outgoing port 25 traffic from anything but their own mail servers). Main issue with ISP smtp services is usually authentication.
Many ISPs do not allow more than a few mails within a minute or restrict the total number of mails per day that you can send.
The ISP (BT) I am currently connecting through has it services configured to only allow sending from a registered recipient (which presents some annoying niggles) and AFAIK imposes no such restrictions. (If you hit your usage limits as a result of such activity you may end up with an interesting bill, commercial services can operate in a similar manner). I suspect high e-Mail usage levels on a residential connection are likely to be flagged and you will 'politely' asked to transfer to the (much) more pricey commercial tariff (but I am not tempted to try this out :-) ). Most non-ISP smtp relay services seem to operate on such mail usage tariffs, but I am not aware of any UK based ISP operating such restrictions, except as an opportunity to increase revenue. Things may be different on other parts of the planet. At some point I expect UK governments desire to track eMail usage may complicate things if they succeed in getting the access they desire..... BTW It is important to check that ones ISP either supports (or allows) the use of DynDNS, not all do. - -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkpxbBwACgkQasN0sSnLmgKE0gCdEiuuF0sMAv4A9j4wAtEgydWJ 4FEAnAjcUPC74vVlVV3gsAjUDjviUtrO =tYxb -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org