Thanks All,
I fully accept that exim is as it is, and being an
(instrumentation-)developer
myself it's easy to see how we got here. As stated in my very first post,
I did make it all work by using "proper" ;-) entries in /etc/hosts,
hostname and mailname. This being my first email server instal
On 5/19/2013 3:45 AM, Klaus Doering wrote:
> Stan,
>
> Thank you for taking the time to explain your perspective. Maybe it is
> the tone of your teachings that tickle me, maybe it's just that I'm no
> big fan of sweeping statements a la "Don't do it, ever". As I described
Many folks with long ex
On Sun, May 19, 2013 at 6:21 PM, Klaus Doering
wrote:
>
> On 19/05/13 12:48, Arun Khan wrote:
>>
>> On Sun, May 19, 2013 at 2:15 PM, Klaus Doering
>> wrote:
>>>
>>> I agree that in a different setting, where there are many users,
>>> hundreds of emails per minute and other mission-critical stuff
On Du, 19 mai 13, 13:51:01, Klaus Doering wrote:
>
> This email server is not directly connected to the 'net, it sits behind
> a router. Thus, there is one external IP for which I've registered an "A"
> record and an "MX" record on a public DNS server, and then there is an
> internal IP server on
On 19/05/13 12:48, Arun Khan wrote:
On Sun, May 19, 2013 at 2:15 PM, Klaus Doering
wrote:
I agree that in a different setting, where there are many users,
hundreds of emails per minute and other mission-critical stuff is going
on, one needs to design the infrastructure a lot more carefully.
On Sun, May 19, 2013 at 2:15 PM, Klaus Doering
wrote:
>
> I agree that in a different setting, where there are many users,
> hundreds of emails per minute and other mission-critical stuff is going
> on, one needs to design the infrastructure a lot more carefully.
>
As a thumb rule, any system pro
Stan,
Thank you for taking the time to explain your perspective. Maybe it is
the tone of your teachings that tickle me, maybe it's just that I'm no
big fan of sweeping statements a la "Don't do it, ever". As I described
in my initial post, this thread concerns a small domestic setting. There
is
On 5/16/2013 2:17 PM, Klaus Doering wrote:
> Stan, Thank you for the teaching. Indeed, there are many books I should
> have read already, alas, there are a great many subjects about which
> important books are written. So, I go along and learn when things don't
> work as expected. Like now.
>
> Th
Joe,
Yes, I've set the "A" and the "MX" record to the same FQDN, and that is
also the HELO string. (at least now that I adjusted the entry in the
hosts file.)
Thanks,
Klaus
On 16/05/13 19:06, Joe wrote:
Apart from any other issue, please note that the HELO string provided
by your mailserver re
Stan, Thank you for the teaching. Indeed, there are many books I should
have read already, alas, there are a great many subjects about which
important books are written. So, I go along and learn when things don't
work as expected. Like now.
The story about using DHCP to assign fixed addresses doe
On Thu, 16 May 2013 09:02:57 +0100
Klaus Doering wrote:
>
> The RaspPi (running Raspbian, a version of Wheezy for the ARMHF
> architecture) also acts as a mail server, talking
> SMTP to the wider world using exim4. After I got an error message
> from some strict server telling me
>
> 504 5.
On 5/16/2013 3:02 AM, Klaus Doering wrote:
...
> Sorry long post. Can anybody shine light on this, and maybe even know
> how to make use of the DHCP provided
> domain name in exim?
First, using a DHCP server, in a consumer broadband router or otherwise,
to assign -sticky static- addresses and hos
Hi All, just joined this mailing list after years of lurking :-)
On my home network I run approx. 10 clients, mostly Debian powered (from
a fileserver and several laptops and
desktops to NSLU2s and a Raspberry PI). It is set-up such that the
router (Billion 7800N) also serves as a DHCP and as
t
13 matches
Mail list logo
