One difficulty here is that you're offering suggestions to "improve
Courier" rather than actually explaining what your problem is. That's
somewhat offensive to a developer, see:
http://www.catb.org/~esr/faqs/smart-questions.html#id3001405
http://www.catb.org/~esr/faqs/smart-questions.html#goal
Sam isn't going to want to change a single line of code until you
explain what the problem actually is and why Courier should be the one
to fix it. You should start by answering some of these questions: What
do the client's MX records actually look like, are they equal weight or
primary/secondary? What exactly happens when Courier tries to connect
to the primary? How about a session log of a server connection? What
delivery failures are users getting? Any custom configuration on your
end? etc.
Jay
--
Jay Lee
Network / Systems Administrator
Information Technology Dept.
Philadelphia Biblical University
--
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
