On Sat, 2003-09-27 at 09:48, Charles Blundell wrote:
on Fri, Sep 26, 2003 at 11:35:02PM +0100, Matt Parker wrote:
I got all the way through, but only on mx4.hotmail.com. No joy on mx1. Is there anyway I can force postfix to use mx4 or is it just pot-luck which server I get?
make sure you have:
transport_maps = hash:/etc/postfix/transport
in /etc/postfix/main.cf then add to /etc/postfix/transport:
hotmail.com smtp:[mx4.hotmail.com]
then run: # postmap /etc/postfix/transport # postfix check # postfix reload
(though you would be better off if you could rely on the mx records for hotmail.com...)
fwiw, mx1.hotmail.com times out on connect: postfix should be trying other mx's. but i see that hotmail lists them all at the same preference. odd.
That worked to connect to mx4 but unfortunately I'm still getting the same message from hotmail:-
Sep 27 11:35:17 ben postfix/smtp[16249]: 065813B4E0: to=cowboy_bob500@hotmail.com, relay=mx4.hotmail.com[65.54.254.151], delay=41, status=deferred (lost connection with mx4.hotmail.com[65.54.254.151] while sending MAIL FROM)
Don't know why it works manually via telnet but postfix gets cut off. Grrr. Damn Microsoft...
Thanks for the help,
Matt
On 2003-09-27 11:41:12 +0100 Matt Parker matt@mpcontracting.co.uk wrote:
Don't know why it works manually via telnet but postfix gets cut off.
Does it work if you use your upstream ISP's mail relay? If "ben" is in a DUL, it may be hotmail using bizarre controls.
On Sat, 2003-09-27 at 19:51, MJ Ray wrote:
On 2003-09-27 11:41:12 +0100 Matt Parker matt@mpcontracting.co.uk wrote:
Don't know why it works manually via telnet but postfix gets cut off.
Does it work if you use your upstream ISP's mail relay? If "ben" is in a DUL, it may be hotmail using bizarre controls.
Well, I made sure it was OK with my ISP and routed the hotmail.com domain through their mail server and now I'm sending mail to Hotmail. Why do Microsoft make things so difficult?
Thanks for the help,
Matt
PS - I'll try and make it to one of the Norwich meetings one of these days...
The following ramblings come with some free software....
My client recently asked me to quote for a job that involves writing C code for Linux. Although I've been using the operating system for some while and have done a good deal of C programming in the past, I'd not previously married the two, so having a few days to spare decided it would be a good time to resurrect my lapsed skills.
I started looking around for a project to learn on and on an ancient archive CD came across a text editor I first wrote in about 1985 and which hasn't been touched since 1992. This seemed a good place to start.
I don't have any books on C programming for Linux, and the ones at Amazon etc. are expensive. Then I came across a free book at
http://www.advancedlinuxprogramming.com/
which I rate as a first-class introduction to the subject and I thoroughly recommend it to anyone else wanting to do 'C'.
Back to the text editor, dubbed VUE (Very Useful Editor). This is a simple text editor for the (Linux) console. Many people who, like me, have only the occasional need for text editing in the console, find vi counter-intuitive and emacs too heavy. Both require frequent recourse to the manual unless they are used regularly.
I first wrote VUE in the mid 1980s in an attempt to emulate some of the features of the (then) new Apple Macintosh, but as a text-only product for the system I was using at the time. I particularly wanted a modeless editor and one that incorporates help as a natural part of the way it works. In these days of GUI interfaces, heavy text editing is catered for by a wealth of products, with little need to use console-based editors like vi and emacs. If like me you're an occasional user of the console you might find VUE works for you, or you might find it irritating and limited. If the latter, the source is supplied for you do do better with.
VUE is currently available for download at http://www.zen18103.zen.co.uk/vue/index.html.
-- GT
"Graham Trott" gt@pobox.com writes:
I don't have any books on C programming for Linux, and the ones at Amazon etc. are expensive. Then I came across a free book at
http://www.advancedlinuxprogramming.com/
which I rate as a first-class introduction to the subject and I thoroughly recommend it to anyone else wanting to do 'C'.
I had a brief look and was somewhat underwhelmed. Some complaints include:
* The readlink() example contains a buffer overrun! (Triggered by links longer than 255 characters.)
* They don't seem very hot on error handling, a vital part of writing half-way decent software. Calling fsync() and ignoring the return value is the most eggregious example I noticed, (it'll just slow your program down without making it reliable in the intended way) but it seems to be a common problem in many parts of the book.
* They misdocument access() - it doesn't tell you whether you can read/write/etc the file, it tells you whether the real UID/GID the process is running under can access them, which is different in a setuid/setgid program.
* They seem confused about the reasons to avoid using system() and the contexts in which to do so; you don't avoid it because it's hard to predict what the shell is but because the behaviour of the shell is influenced by many environment variables etc., which means you have to thoroughly sanitize the environment before calling it if there are any kind of security boundaries involved, and system() doesn't do this.
They do at least point out the quoting problems for system/popen.
* The 'security hole: programs with execute permissions' part seems completely confused. Yes, a user could copy a program, add execute bits, and run it, but that wouldn't permit them to do anything they couldn't do by compiling the programs themselves (or compiling it elsewhere and uploading it); if that's a security hole then frankly you have worse things to worry about.
"Richard Kettlewell" rjk@terraraq.org.uk:
I had a brief look and was somewhat underwhelmed. Some complaints include: <<<<<<
All very valid points, but it's a bit like a skiing expert pointing out the limitations of the snowplough on black slopes. Novice skiers just want to get moving and leave the 'proper technique' stuff till later. Likewise with programming. Sure, I could go spend £50 on a book from Amazon, and once I get serious I may well do that. But in this case all I wanted was something that told me where the compiler was and how to do elementary stuff. And I didn't want to pay for the privilege.
(I suggest you don't look too hard at the insides of my text editor; it probably breaks every guideline in the book.)
-- GT
On 2003-10-10 14:11:31 +0100 Graham Trott gt@pobox.com wrote:
But in this case all I wanted was something that told me where the compiler was and how to do elementary stuff. And I didn't want to pay for the privilege.
Seeing as this has been made available for free under a very liberal copyright licence, can I suggest that you consider making a small payment in kind and report the bugs that Richard described? Even better, you could submit patchfiles for the code listings that fix those bugs, which may be a useful learning experience in its own right (and I don't pretend to know them). Sadly, they don't seem to offer the source code to the main book, so you can't easily patch the bugs in that.
"Graham Trott" gt@pobox.com writes:
"Richard Kettlewell" rjk@terraraq.org.uk:
>
I had a brief look and was somewhat underwhelmed. Some complaints include: <<<<<<
All very valid points, but it's a bit like a skiing expert pointing out the limitations of the snowplough on black slopes. Novice skiers just want to get moving and leave the 'proper technique' stuff till later. Likewise with programming. Sure, I could go spend £50 on a book from Amazon, and once I get serious I may well do that. But in this case all I wanted was something that told me where the compiler was and how to do elementary stuff. And I didn't want to pay for the privilege.
I was addressing the book as a whole, not your personal uses for it.
On 1/1/1970, "Graham Trott" gt@pobox.com wrote:
The following ramblings come with some free software....
My client recently asked me to quote for a job that involves writing C code for Linux. Although I've been using the operating system for some while and have done a good deal of C programming in the past, I'd not previously married the two, so having a few days to spare decided it would be a good time to resurrect my lapsed skills.
Book gets some good reviews on Amazon. I think it's probably misnamed as an Advanced books from what people say but I've taken a quick look and it seems very interesing.
I think we've just found a future speaker and topic for a forthcoming meeting. how about it Graham I'd love to hear your experieces and a quick tutorial on how to write and compile a basic C program under Linux, and maybe some of the gottchas and the things you like and dislike about Linux as a development environment.
Keith
On Fri, 10 Oct 2003 16:51:12 +0100 kpwatson@pop3.ukfsn.org wrote:
On 1/1/1970, "Graham Trott" gt@pobox.com wrote:
The following ramblings come with some free software....
My client recently asked me to quote for a job that involves writing C code for Linux. Although I've been using the operating system for some while and have done a good deal of C programming in the past, I'd not previously married the two, so having a few days to spare decided it would be a good time to resurrect my lapsed skills.
Book gets some good reviews on Amazon. I think it's probably misnamed as an Advanced books from what people say but I've taken a quick look and it seems very interesing.
I think we've just found a future speaker and topic for a forthcoming meeting. how about it Graham I'd love to hear your experieces and a quick tutorial on how to write and compile a basic C program under Linux, and maybe some of the gottchas and the things you like and dislike about Linux as a development environment.
Keith
Its a great book it is a good alternative to Stevens (Very old but a classic), the book repeatedly (well I remember twice) states error handling has been removed for clarity in the examples. I have it on my desktop at work, If you are new to UNIX C programming and dont have Stevens then buy this book or Stevens.
The thing I most dislike is the C++ compiler and the STL support, C is fine in gcc.
ctags, vi/nedit/emacs, gdb/ddd/gvd, automake/autoconf/make are not as nice as Delphi or I imagine other IDE environments for developing code fast , and the speed of updates to libraries, the lack of binary compatibility, and the poor support for Posix pthread library are my current moans.
Still both rpm's and deb's beat instalation systems I have seen for windows, and I wont go back to windows through choice.
Regards
Owen
-
Graham Trott -
kpwatson＠pop3.ukfsn.org -
Matt Parker -
MJ Ray -
MJ Ray -
owen.churchcowley -
Richard Kettlewell