Re: Fwd: Mail delivery failed: returning message to sender

[songbird]

Victor Munoz wrote:

>  Hello.
>
> I'm using XEmacs 21.4.24 and gnome-terminal 3.26.2 in sid. And I can't copy
> a text from the terminal and paste it into XEmacs. I have tried marking the
> text and then middle button; Shift-Ctrl-C and then right-button to get the
> 'paste' option; and some other combinations of these. Nothing works.
...
> Any ideas I should try?

  xclip?


  songbird

Fwd: Mail delivery failed: returning message to sender

[Victor Munoz]

 Hello.

I'm using XEmacs 21.4.24 and gnome-terminal 3.26.2 in sid. And I can't copy
a text from the terminal and paste it into XEmacs. I have tried marking the
text and then middle button; Shift-Ctrl-C and then right-button to get the
'paste' option; and some other combinations of these. Nothing works.

However, I seem to be able to copy in all directions using other
applications. From the terminal to Emacs, to firefox, etc. And from xemacs
to everyone else, including the terminal!

Depending on how I try to copy and then paste, I get messages from xemacs
such as "timed out waiting for reply from selection owner", "received the
wrong selection type in SelectionNotify", or simply "Mark set", and then
nothing happens. Via Google I found this site:
http://archive.oreilly.com/pub/post/quick_tip_for_linux_users_havi.html,
where some configuration for emacs is suggested, but did not work for me.

Any ideas I should try?

Victor

Re: Configuring Exim for mail delivery

[Liam O'Toole]

On 2016-10-02, Brian  wrote:
> On Sun 02 Oct 2016 at 21:41:50 +0900, Mark Fletcher wrote:
>
>> On Sun, Oct 02, 2016 at 12:52:44PM +0100, Brian wrote:
>> > 
>> > I have the same setup and all customisations (apart from hubbed_hosts)
>> > have been done via debconf. TBH, I cannot see why /etc/hosts should be
>> > consulted because I thought there is first a check for an MX record and
>> > then an attempt to resolve the host *using the DNS* if there was none.
>> > 
>> > Your instructions are clear so I can continue to try more customising
>> > via debconf.
>> > 
>> > mo appears to have had no more success than I have. Don't know about
>> > Mark.
>> > 
>> > -- 
>> > Brian 
>> > 
>> 
>> That's twice you've mentioned conf.d now, bear in mind in a 
>> defaults-accepting Debian installation of exim4, it's not used.
>
> It shouldn't make any difference whether the split configuration is used
> or not for what we are doing.
>
> A defaults-accepting installation would use "local delivery only; not on
> a network". Obviously this would not suit testing mail delivery to other
> machines on the LAN. It was at this first page I made my mistake!
>
> I chose "Internet site.." because that is the way I always send
> mail. No wonder I got "Unrouteable address". Was it clear that I should
> have used "mail sent by smarthost.." (Liam?)?. Mystery solved. I've
> not tested extensively but I can get mail to go to a user on another
> machine.

§2.1 of /usr/share/doc/exim4-base/README.Debian.html (from exim4-base)
provides some assistance.

>
> I'm not enamoured of this technique because it does not suit my mail
> setup. So I will stick with the more versatile hubbed_hosts.
>
> Thanks for all the clues.
>

At least your curiosity has been satisfied. :)

-- 

Liam

Re: Configuring Exim for mail delivery

[Mark Fletcher]

On Sun, Oct 02, 2016 at 09:17:58AM -0400, Gene Heskett wrote:
> On Sunday 02 October 2016 08:41:50 Mark Fletcher wrote:
> 
> > On Sun, Oct 02, 2016 at 12:52:44PM +0100, Brian wrote:
> > > [Some snipping. Not too much, I hope].
> > >
> > > On Sun 02 Oct 2016 at 01:05:20 +0100, Liam O'Toole wrote:
> > > > On 2016-10-01, Brian  wrote:
> > > > > Exim's default behaviour, as has been mentioned a couple of
> > > > > times in this thread, is to use DNS; nsswitch is not involved.
> > > >
> > > > Doing an strace on the exim command shows that /etc/nsswitch is
> > > > consulted first, then /etc/resolv.conf (followed by a DNS lookup
> > > > of the smarthost).
> > >
> > > This is what I cannot get round. I'm prepared to accept that my
> > > understanding may be defective but when I see "driver = dnslookup"
> > > in router/200_exim4-config_primary it fits what I observe. Which is
> > > why I use a hubbed_hosts file to manually route mail to machines on
> > > the LAN.
> > >
> > > > > This is a default
> > > > > exim install; no files in conf.d altered. How about you?
> > > >
> > > > No alterations I can remember, and 'dpkg --verify' reports no
> > > > changes to exim4-related files. All customisations have been done
> > > > via debconf. I am reluctant to divulge those customisations here,
> > > > but I can tell you that the settings are not particularly exotic.
> > > > One host on the local network is configured to use my ISP's SMTP
> > > > server as its smarthost, while the other hosts in turn use the
> > > > former as their smarthost.
> > >
> > > I have the same setup and all customisations (apart from
> > > hubbed_hosts) have been done via debconf. TBH, I cannot see why
> > > /etc/hosts should be consulted because I thought there is first a
> > > check for an MX record and then an attempt to resolve the host
> > > *using the DNS* if there was none.
> > >
> > > Your instructions are clear so I can continue to try more
> > > customising via debconf.
> > >
> > > mo appears to have had no more success than I have. Don't know about
> > > Mark.
> > >
> > > --
> > > Brian
> >
> > That's twice you've mentioned conf.d now, bear in mind in a
> > defaults-accepting Debian installation of exim4, it's not used.
> >
> > Mark
> 
> Uuh, Mark, here on an up to date wheezy install, with exim4's default 
> config untouched, it does indeed exist, as /etc/exim4/conf.d, and its 
> populated with quite a few subdirs.
> =

Yup, here too. But it is not being used.

Mark

Re: Configuring Exim for mail delivery

[Brian]

On Sun 02 Oct 2016 at 21:41:50 +0900, Mark Fletcher wrote:

> On Sun, Oct 02, 2016 at 12:52:44PM +0100, Brian wrote:
> > 
> > I have the same setup and all customisations (apart from hubbed_hosts)
> > have been done via debconf. TBH, I cannot see why /etc/hosts should be
> > consulted because I thought there is first a check for an MX record and
> > then an attempt to resolve the host *using the DNS* if there was none.
> > 
> > Your instructions are clear so I can continue to try more customising
> > via debconf.
> > 
> > mo appears to have had no more success than I have. Don't know about
> > Mark.
> > 
> > -- 
> > Brian 
> > 
> 
> That's twice you've mentioned conf.d now, bear in mind in a 
> defaults-accepting Debian installation of exim4, it's not used.

It shouldn't make any difference whether the split configuration is used
or not for what we are doing.

A defaults-accepting installation would use "local delivery only; not on
a network". Obviously this would not suit testing mail delivery to other
machines on the LAN. It was at this first page I made my mistake!

I chose "Internet site.." because that is the way I always send
mail. No wonder I got "Unrouteable address". Was it clear that I should
have used "mail sent by smarthost.." (Liam?)?. Mystery solved. I've
not tested extensively but I can get mail to go to a user on another
machine.

I'm not enamoured of this technique because it does not suit my mail
setup. So I will stick with the more versatile hubbed_hosts.

Thanks for all the clues.

-- 
Brian.

Re: Configuring Exim for mail delivery

[Gene Heskett]

On Sunday 02 October 2016 08:41:50 Mark Fletcher wrote:

> On Sun, Oct 02, 2016 at 12:52:44PM +0100, Brian wrote:
> > [Some snipping. Not too much, I hope].
> >
> > On Sun 02 Oct 2016 at 01:05:20 +0100, Liam O'Toole wrote:
> > > On 2016-10-01, Brian  wrote:
> > > > Exim's default behaviour, as has been mentioned a couple of
> > > > times in this thread, is to use DNS; nsswitch is not involved.
> > >
> > > Doing an strace on the exim command shows that /etc/nsswitch is
> > > consulted first, then /etc/resolv.conf (followed by a DNS lookup
> > > of the smarthost).
> >
> > This is what I cannot get round. I'm prepared to accept that my
> > understanding may be defective but when I see "driver = dnslookup"
> > in router/200_exim4-config_primary it fits what I observe. Which is
> > why I use a hubbed_hosts file to manually route mail to machines on
> > the LAN.
> >
> > > > This is a default
> > > > exim install; no files in conf.d altered. How about you?
> > >
> > > No alterations I can remember, and 'dpkg --verify' reports no
> > > changes to exim4-related files. All customisations have been done
> > > via debconf. I am reluctant to divulge those customisations here,
> > > but I can tell you that the settings are not particularly exotic.
> > > One host on the local network is configured to use my ISP's SMTP
> > > server as its smarthost, while the other hosts in turn use the
> > > former as their smarthost.
> >
> > I have the same setup and all customisations (apart from
> > hubbed_hosts) have been done via debconf. TBH, I cannot see why
> > /etc/hosts should be consulted because I thought there is first a
> > check for an MX record and then an attempt to resolve the host
> > *using the DNS* if there was none.
> >
> > Your instructions are clear so I can continue to try more
> > customising via debconf.
> >
> > mo appears to have had no more success than I have. Don't know about
> > Mark.
> >
> > --
> > Brian
>
> That's twice you've mentioned conf.d now, bear in mind in a
> defaults-accepting Debian installation of exim4, it's not used.
>
> Mark

Uuh, Mark, here on an up to date wheezy install, with exim4's default 
config untouched, it does indeed exist, as /etc/exim4/conf.d, and its 
populated with quite a few subdirs.
=
gene@coyote:~$ ls -l /etc/exim4/conf.d
total 28
drwxr-xr-x 2 root root 4096 Apr  4 21:35 acl
drwxr-xr-x 2 root root 4096 Apr  4 21:35 auth
drwxr-xr-x 2 root root 4096 Apr  4 21:35 main
drwxr-xr-x 2 root root 4096 Apr  4 21:35 retry
drwxr-xr-x 2 root root 4096 Apr  4 21:35 rewrite
drwxr-xr-x 2 root root 4096 Apr  4 21:35 router
drwxr-xr-x 2 root root 4096 Apr  4 21:35 transport
==
Based on the dates, I have to assume exim4 was pulled in as a dependency 
of something else I installed recently since this wheezy install is 
around 2 years old now. It's installation did not effect how my machine 
runs that I am aware of. According to htop, no daemon of that name is 
currently running.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Configuring Exim for mail delivery

[Mark Fletcher]

On Sun, Oct 02, 2016 at 12:52:44PM +0100, Brian wrote:
> [Some snipping. Not too much, I hope].
> 
> On Sun 02 Oct 2016 at 01:05:20 +0100, Liam O'Toole wrote:
> 
> > On 2016-10-01, Brian  wrote:
> > >
> > > Exim's default behaviour, as has been mentioned a couple of times in
> > > this thread, is to use DNS; nsswitch is not involved.
> > 
> > Doing an strace on the exim command shows that /etc/nsswitch is
> > consulted first, then /etc/resolv.conf (followed by a DNS lookup of the
> > smarthost).
> 
> This is what I cannot get round. I'm prepared to accept that my
> understanding may be defective but when I see "driver = dnslookup" in
> router/200_exim4-config_primary it fits what I observe. Which is why I
> use a hubbed_hosts file to manually route mail to machines on the LAN.
> 
> > > This is a default
> > > exim install; no files in conf.d altered. How about you?
> > 
> > No alterations I can remember, and 'dpkg --verify' reports no changes to
> > exim4-related files. All customisations have been done via debconf. I am
> > reluctant to divulge those customisations here, but I can tell you that
> > the settings are not particularly exotic. One host on the local network
> > is configured to use my ISP's SMTP server as its smarthost, while the
> > other hosts in turn use the former as their smarthost.
> 
> I have the same setup and all customisations (apart from hubbed_hosts)
> have been done via debconf. TBH, I cannot see why /etc/hosts should be
> consulted because I thought there is first a check for an MX record and
> then an attempt to resolve the host *using the DNS* if there was none.
> 
> Your instructions are clear so I can continue to try more customising
> via debconf.
> 
> mo appears to have had no more success than I have. Don't know about
> Mark.
> 
> -- 
> Brian 
> 

That's twice you've mentioned conf.d now, bear in mind in a 
defaults-accepting Debian installation of exim4, it's not used.

Mark

Re: Configuring Exim for mail delivery

[Brian]

[Some snipping. Not too much, I hope].

On Sun 02 Oct 2016 at 01:05:20 +0100, Liam O'Toole wrote:

> On 2016-10-01, Brian  wrote:
> >
> > Exim's default behaviour, as has been mentioned a couple of times in
> > this thread, is to use DNS; nsswitch is not involved.
> 
> Doing an strace on the exim command shows that /etc/nsswitch is
> consulted first, then /etc/resolv.conf (followed by a DNS lookup of the
> smarthost).

This is what I cannot get round. I'm prepared to accept that my
understanding may be defective but when I see "driver = dnslookup" in
router/200_exim4-config_primary it fits what I observe. Which is why I
use a hubbed_hosts file to manually route mail to machines on the LAN.

> > This is a default
> > exim install; no files in conf.d altered. How about you?
> 
> No alterations I can remember, and 'dpkg --verify' reports no changes to
> exim4-related files. All customisations have been done via debconf. I am
> reluctant to divulge those customisations here, but I can tell you that
> the settings are not particularly exotic. One host on the local network
> is configured to use my ISP's SMTP server as its smarthost, while the
> other hosts in turn use the former as their smarthost.

I have the same setup and all customisations (apart from hubbed_hosts)
have been done via debconf. TBH, I cannot see why /etc/hosts should be
consulted because I thought there is first a check for an MX record and
then an attempt to resolve the host *using the DNS* if there was none.

Your instructions are clear so I can continue to try more customising
via debconf.

mo appears to have had no more success than I have. Don't know about
Mark.

-- 
Brian 

Re: Configuring Exim for mail delivery

[Liam O'Toole]

On 2016-10-02, Mark Fletcher  wrote:
> On Sat, Oct 01, 2016 at 11:22:06PM +0100, Brian wrote:
>> 
>> We all know a hubbed_hosts file works. Mark Fletcher has written
>> extensively about it and I have said a thing or too also. What I want to
>> know is why following the advice from Liam O'Toole doesn't work for me,
>> even though I have followed the instructions exactly.
>> 
>
> I think Liam is describing a situation where the only mail-capable 
> machine is the server, in your example gnome.monet. He configured it to 
> be the end-point for *.monet. But for mo's original use-case, gnome 
> should only be the end-point for gnome.monet and desktop should be the 
> end-point for desktop.monet. Then, if gnome.monet gets handed a mail for 
> desktop.monet, it doesn't try to deliver it, but instead tries to pass 
> it on, and that's when you need hubbed_hosts populated so it can find 
> desktop.monet to pass it on to.
>
> So Liam has consistently been describing a solution that, while 
> perfectly valid, is the solution to a slightly different problem than 
> the one mo originally asked about.
>
> Mark
>
>

My setup is more or less as you describe. The only difference is that
all machines are mail capable and use the local server as their
smarthost, while the server in turn uses an external smarthost.

Brian seems to be experiencing a more fundamental issue, where exim
refuses to resolve domain names in the expected manner. That one has me
stumped.

-- 

Liam

Re: Configuring Exim for mail delivery

[mo]

Am 02.10.2016 um 00:22 schrieb Brian:

On Sat 01 Oct 2016 at 22:47:27 +0200, mo wrote:


Am 01.10.2016 um 20:17 schrieb Brian:

On Sat 01 Oct 2016 at 17:25:46 +0100, Liam O'Toole wrote:


On 2016-10-01, mo  wrote:

First of all:
Thank you Liam for your help! :)
Thanks for the very nice and long explanation Mark! :)

I think i should elaborate a little more on my setup.. i guess i did not
make that very clear in the first place, sorry about that.

My network is consisting of the following systems:

Main PC - 192.168.23.11  (Running Debian Jessie)
Server  - 192.168.23.200 (Running Debian Jessie)

The server is always online, the PC is only half of the day on.

What i want to do now is the following:

Sending mail from my Main PC to my Server and also the other way around,

>from the Server to my Main PC.

The Server should also be able to send mail to the "outside" (Meaning to
other SMTP servers).
The second requirement is optional since i dont own a domain and all
this is sitting locally at my home. The most important thing for me is
to send and receive mail from both systems in my home network.
I hope this made my problem a little clearer :)

I'm a little ashamed to say that, but i could not totally follow your
explanations Mark... I'm quite a newbie when it comes to SMTP.. sorry :(

Thanks again for all your help ;)

Greets

mo




I should have been a little clearer myself. You don't need to register a
domain name. Just invent your own domain name for local purposes. Let's
say you choose the domain name "monet", and that you have already given
the hostnames "desktop" and "server" to your two machines. Then you
would edit the file /etc/hosts on both machines to contain the following
lines:

192.168.23.11 desktop.monet desktop
192.168.23.200 server.monet server


I did that on gnome and desktop with appropriate changes:

   192.168.7.20 desktop.monet desktop
   192.168.7.67 gnome.monet gnome


Now you only need to tell exim4 on the server that it is the final
destination for emails to *.monet, again using the debconf wizard. You
will then be able to send emails to local addresses, while emails to all
other domains will go through your ISP's smarthost.


I did that on gnome and desktop.


Incidently, you can also tell exim4 on the desktop to use the server as
its smarthost.

I realise that you're getting lots of (sometimes contradictory)
information from various sources. The barebones configuration I have
described above has served me well for several years.


All commands are issued from gnome.

 brian@gnome:~# ping -c3 desktop
 PING desktop.monet (192.168.7.20) 56(84) bytes of data.
 64 bytes from desktop.monet (192.168.7.20): icmp_seq=1 ttl=64 time=0.267 ms
 64 bytes from desktop.monet (192.168.7.20): icmp_seq=2 ttl=64 time=0.255 ms
 64 bytes from desktop.monet (192.168.7.20): icmp_seq=3 ttl=64 time=0.269 ms

 --- desktop.monet ping statistics ---
 3 packets transmitted, 3 received, 0% packet loss, time 2001ms
 rtt min/avg/max/mdev = 0.255/0.263/0.269/0.019 ms

 brian@gnome:~# ping -c3 desktop.monet
 PING desktop.monet (192.168.7.20) 56(84) bytes of data.
 64 bytes from desktop.monet (192.168.7.20): icmp_seq=1 ttl=64 time=0.264 ms
 64 bytes from desktop.monet (192.168.7.20): icmp_seq=2 ttl=64 time=0.255 ms
 64 bytes from desktop.monet (192.168.7.20): icmp_seq=3 ttl=64 time=0.255 ms

 --- desktop.monet ping statistics ---
 3 packets transmitted, 3 received, 0% packet loss, time 2002ms
 rtt min/avg/max/mdev = 0.255/0.258/0.264/0.004 ms

We expect that result because ping uses files in /etc/nsswitch.

 root@gnome:~# exim -bt brian@desktop
 R: dnslookup for brian@desktop
 brian@desktop is undeliverable: Unrouteable address

 root@gnome:~# exim -bt brian@desktop.monet
 R: dnslookup for brian@desktop.monet
 brian@desktop.monet is undeliverable: Unrouteable address

Am I the only one who gets this? No capability to deliver mail to
desktop. What am I doing wrong?



I think this is the problem with exim calling DNS on the given hostname...
which is doomed to fail. To get it working you need to create the
hubbed_hosts file and set your aliases in there, for example:
192.168.7.20: desktop

Then it should work fine, at least for me it did.

Hope this helps :)


Not really, I'm afraid.

We all know a hubbed_hosts file works. Mark Fletcher has written
extensively about it and I have said a thing or too also. What I want to
know is why following the advice from Liam O'Toole doesn't work for me,
even though I have followed the instructions exactly.

BTW: It would be 'desktop: 192.168.7.20' and 'desktop.monet:192.168.7.20'
in hubbed_hosts.


Ah yeah, right, i mixed the syntax up, sorry about that.

Re: Configuring Exim for mail delivery

[Mark Fletcher]

On Sat, Oct 01, 2016 at 11:22:06PM +0100, Brian wrote:
> 
> We all know a hubbed_hosts file works. Mark Fletcher has written
> extensively about it and I have said a thing or too also. What I want to
> know is why following the advice from Liam O'Toole doesn't work for me,
> even though I have followed the instructions exactly.
> 

I think Liam is describing a situation where the only mail-capable 
machine is the server, in your example gnome.monet. He configured it to 
be the end-point for *.monet. But for mo's original use-case, gnome 
should only be the end-point for gnome.monet and desktop should be the 
end-point for desktop.monet. Then, if gnome.monet gets handed a mail for 
desktop.monet, it doesn't try to deliver it, but instead tries to pass 
it on, and that's when you need hubbed_hosts populated so it can find 
desktop.monet to pass it on to.

So Liam has consistently been describing a solution that, while 
perfectly valid, is the solution to a slightly different problem than 
the one mo originally asked about.

Mark

Re: Configuring Exim for mail delivery

[Liam O'Toole]

On 2016-10-01, Brian  wrote:
> On Sat 01 Oct 2016 at 21:52:53 +0100, Liam O'Toole wrote:
>
>> On 2016-10-01, Brian  wrote:
>> > On Sat 01 Oct 2016 at 17:25:46 +0100, Liam O'Toole wrote:
>> >
>> >> On 2016-10-01, mo  wrote:
>> >> > First of all:
>> >> > Thank you Liam for your help! :)
>> >> > Thanks for the very nice and long explanation Mark! :)
>> >> >
>> >> > I think i should elaborate a little more on my setup.. i guess i did 
>> >> > not 
>> >> > make that very clear in the first place, sorry about that.
>> >> >
>> >> > My network is consisting of the following systems:
>> >> >
>> >> > Main PC - 192.168.23.11  (Running Debian Jessie)
>> >> > Server  - 192.168.23.200 (Running Debian Jessie)
>> >> >
>> >> > The server is always online, the PC is only half of the day on.
>> >> >
>> >> > What i want to do now is the following:
>> >> >
>> >> > Sending mail from my Main PC to my Server and also the other way 
>> >> > around, 
>> >> > from the Server to my Main PC.
>> >> > The Server should also be able to send mail to the "outside" (Meaning 
>> >> > to 
>> >> > other SMTP servers).
>> >> > The second requirement is optional since i dont own a domain and all 
>> >> > this is sitting locally at my home. The most important thing for me is 
>> >> > to send and receive mail from both systems in my home network.
>> >> > I hope this made my problem a little clearer :)
>> >> >
>> >> > I'm a little ashamed to say that, but i could not totally follow your 
>> >> > explanations Mark... I'm quite a newbie when it comes to SMTP.. sorry :(
>> >> >
>> >> > Thanks again for all your help ;)
>> >> >
>> >> > Greets
>> >> >
>> >> > mo
>> >> >
>> >> >
>> >> 
>> >> I should have been a little clearer myself. You don't need to register a
>> >> domain name. Just invent your own domain name for local purposes. Let's
>> >> say you choose the domain name "monet", and that you have already given
>> >> the hostnames "desktop" and "server" to your two machines. Then you
>> >> would edit the file /etc/hosts on both machines to contain the following
>> >> lines:
>> >> 
>> >>   192.168.23.11 desktop.monet desktop
>> >>   192.168.23.200 server.monet server
>> >
>> > I did that on gnome and desktop with appropriate changes:
>> >
>> > 192.168.7.20 desktop.monet desktop
>> > 192.168.7.67 gnome.monet gnome
>> >
>> >> Now you only need to tell exim4 on the server that it is the final
>> >> destination for emails to *.monet, again using the debconf wizard. You
>> >> will then be able to send emails to local addresses, while emails to all
>> >> other domains will go through your ISP's smarthost.
>> >
>> > I did that on gnome and desktop.
>> >
>> >> Incidently, you can also tell exim4 on the desktop to use the server as
>> >> its smarthost.
>> >> 
>> >> I realise that you're getting lots of (sometimes contradictory)
>> >> information from various sources. The barebones configuration I have
>> >> described above has served me well for several years.
>> >
>> > All commands are issued from gnome.
>> >
>> >   brian@gnome:~# ping -c3 desktop
>> >   PING desktop.monet (192.168.7.20) 56(84) bytes of data.
>> >   64 bytes from desktop.monet (192.168.7.20): icmp_seq=1 ttl=64 time=0.267 
>> > ms
>> >   64 bytes from desktop.monet (192.168.7.20): icmp_seq=2 ttl=64 time=0.255 
>> > ms
>> >   64 bytes from desktop.monet (192.168.7.20): icmp_seq=3 ttl=64 time=0.269 
>> > ms
>> >
>> >   --- desktop.monet ping statistics ---
>> >   3 packets transmitted, 3 received, 0% packet loss, time 2001ms
>> >   rtt min/avg/max/mdev = 0.255/0.263/0.269/0.019 ms
>> >
>> >   brian@gnome:~# ping -c3 desktop.monet
>> >   PING desktop.monet (192.168.7.20) 56(84) bytes of data.
>> >   64 bytes from desktop.monet (192.168.7.20): icmp_seq=1 ttl=64 time=0.264 
>> > ms
>> >   64 bytes from desktop.monet (192.168.7.20): icmp_seq=2 ttl=64 time=0.255 
>> > ms
>> >   64 bytes from desktop.monet (192.168.7.20): icmp_seq=3 ttl=64 time=0.255 
>> > ms
>> >
>> >   --- desktop.monet ping statistics ---
>> >   3 packets transmitted, 3 received, 0% packet loss, time 2002ms
>> >   rtt min/avg/max/mdev = 0.255/0.258/0.264/0.004 ms
>> >
>> > We expect that result because ping uses files in /etc/nsswitch.
>> >
>> >   root@gnome:~# exim -bt brian@desktop
>> >   R: dnslookup for brian@desktop
>> >   brian@desktop is undeliverable: Unrouteable address
>> >
>> >   root@gnome:~# exim -bt brian@desktop.monet
>> >   R: dnslookup for brian@desktop.monet
>> >   brian@desktop.monet is undeliverable: Unrouteable address
>> >
>> > Am I the only one who gets this? No capability to deliver mail to
>> > desktop. What am I doing wrong?
>> >
>> 
>> exim seems to be trying to resolve desktop.monet via DNS, thus ignoring
>> /etc/nsswitch. (I have no idea whether that is the default behaviour.) Do
>> you have a local DNS capable of resolving the address?
>
> Exim's default behaviour, as has been mentioned a couple of times in
> this thread, is to use DNS; nsswitch is not involved.

Doing an strace on the

Re: Configuring Exim for mail delivery

[Brian]

On Sat 01 Oct 2016 at 21:52:53 +0100, Liam O'Toole wrote:

> On 2016-10-01, Brian  wrote:
> > On Sat 01 Oct 2016 at 17:25:46 +0100, Liam O'Toole wrote:
> >
> >> On 2016-10-01, mo  wrote:
> >> > First of all:
> >> > Thank you Liam for your help! :)
> >> > Thanks for the very nice and long explanation Mark! :)
> >> >
> >> > I think i should elaborate a little more on my setup.. i guess i did not 
> >> > make that very clear in the first place, sorry about that.
> >> >
> >> > My network is consisting of the following systems:
> >> >
> >> > Main PC - 192.168.23.11  (Running Debian Jessie)
> >> > Server  - 192.168.23.200 (Running Debian Jessie)
> >> >
> >> > The server is always online, the PC is only half of the day on.
> >> >
> >> > What i want to do now is the following:
> >> >
> >> > Sending mail from my Main PC to my Server and also the other way around, 
> >> > from the Server to my Main PC.
> >> > The Server should also be able to send mail to the "outside" (Meaning to 
> >> > other SMTP servers).
> >> > The second requirement is optional since i dont own a domain and all 
> >> > this is sitting locally at my home. The most important thing for me is 
> >> > to send and receive mail from both systems in my home network.
> >> > I hope this made my problem a little clearer :)
> >> >
> >> > I'm a little ashamed to say that, but i could not totally follow your 
> >> > explanations Mark... I'm quite a newbie when it comes to SMTP.. sorry :(
> >> >
> >> > Thanks again for all your help ;)
> >> >
> >> > Greets
> >> >
> >> > mo
> >> >
> >> >
> >> 
> >> I should have been a little clearer myself. You don't need to register a
> >> domain name. Just invent your own domain name for local purposes. Let's
> >> say you choose the domain name "monet", and that you have already given
> >> the hostnames "desktop" and "server" to your two machines. Then you
> >> would edit the file /etc/hosts on both machines to contain the following
> >> lines:
> >> 
> >>192.168.23.11 desktop.monet desktop
> >>192.168.23.200 server.monet server
> >
> > I did that on gnome and desktop with appropriate changes:
> >
> > 192.168.7.20 desktop.monet desktop
> > 192.168.7.67 gnome.monet gnome
> >
> >> Now you only need to tell exim4 on the server that it is the final
> >> destination for emails to *.monet, again using the debconf wizard. You
> >> will then be able to send emails to local addresses, while emails to all
> >> other domains will go through your ISP's smarthost.
> >
> > I did that on gnome and desktop.
> >
> >> Incidently, you can also tell exim4 on the desktop to use the server as
> >> its smarthost.
> >> 
> >> I realise that you're getting lots of (sometimes contradictory)
> >> information from various sources. The barebones configuration I have
> >> described above has served me well for several years.
> >
> > All commands are issued from gnome.
> >
> >   brian@gnome:~# ping -c3 desktop
> >   PING desktop.monet (192.168.7.20) 56(84) bytes of data.
> >   64 bytes from desktop.monet (192.168.7.20): icmp_seq=1 ttl=64 time=0.267 
> > ms
> >   64 bytes from desktop.monet (192.168.7.20): icmp_seq=2 ttl=64 time=0.255 
> > ms
> >   64 bytes from desktop.monet (192.168.7.20): icmp_seq=3 ttl=64 time=0.269 
> > ms
> >
> >   --- desktop.monet ping statistics ---
> >   3 packets transmitted, 3 received, 0% packet loss, time 2001ms
> >   rtt min/avg/max/mdev = 0.255/0.263/0.269/0.019 ms
> >
> >   brian@gnome:~# ping -c3 desktop.monet
> >   PING desktop.monet (192.168.7.20) 56(84) bytes of data.
> >   64 bytes from desktop.monet (192.168.7.20): icmp_seq=1 ttl=64 time=0.264 
> > ms
> >   64 bytes from desktop.monet (192.168.7.20): icmp_seq=2 ttl=64 time=0.255 
> > ms
> >   64 bytes from desktop.monet (192.168.7.20): icmp_seq=3 ttl=64 time=0.255 
> > ms
> >
> >   --- desktop.monet ping statistics ---
> >   3 packets transmitted, 3 received, 0% packet loss, time 2002ms
> >   rtt min/avg/max/mdev = 0.255/0.258/0.264/0.004 ms
> >
> > We expect that result because ping uses files in /etc/nsswitch.
> >
> >   root@gnome:~# exim -bt brian@desktop
> >   R: dnslookup for brian@desktop
> >   brian@desktop is undeliverable: Unrouteable address
> >
> >   root@gnome:~# exim -bt brian@desktop.monet
> >   R: dnslookup for brian@desktop.monet
> >   brian@desktop.monet is undeliverable: Unrouteable address
> >
> > Am I the only one who gets this? No capability to deliver mail to
> > desktop. What am I doing wrong?
> >
> 
> exim seems to be trying to resolve desktop.monet via DNS, thus ignoring
> /etc/nsswitch. (I have no idea whether that is the default behaviour.) Do
> you have a local DNS capable of resolving the address?

Exim's default behaviour, as has been mentioned a couple of times in
this thread, is to use DNS; nsswitch is not involved. This is a default
exim install; no files in conf.d altered. How about you?

> You might try the mail command from the mailutils or bsd-mailx packages
> for comparison.

mail uses exim as the MTA. It 

Re: Configuring Exim for mail delivery

[Brian]

On Sat 01 Oct 2016 at 22:47:27 +0200, mo wrote:

> Am 01.10.2016 um 20:17 schrieb Brian:
> >On Sat 01 Oct 2016 at 17:25:46 +0100, Liam O'Toole wrote:
> >
> >>On 2016-10-01, mo  wrote:
> >>>First of all:
> >>>Thank you Liam for your help! :)
> >>>Thanks for the very nice and long explanation Mark! :)
> >>>
> >>>I think i should elaborate a little more on my setup.. i guess i did not
> >>>make that very clear in the first place, sorry about that.
> >>>
> >>>My network is consisting of the following systems:
> >>>
> >>>Main PC - 192.168.23.11  (Running Debian Jessie)
> >>>Server  - 192.168.23.200 (Running Debian Jessie)
> >>>
> >>>The server is always online, the PC is only half of the day on.
> >>>
> >>>What i want to do now is the following:
> >>>
> >>>Sending mail from my Main PC to my Server and also the other way around,
> >>>from the Server to my Main PC.
> >>>The Server should also be able to send mail to the "outside" (Meaning to
> >>>other SMTP servers).
> >>>The second requirement is optional since i dont own a domain and all
> >>>this is sitting locally at my home. The most important thing for me is
> >>>to send and receive mail from both systems in my home network.
> >>>I hope this made my problem a little clearer :)
> >>>
> >>>I'm a little ashamed to say that, but i could not totally follow your
> >>>explanations Mark... I'm quite a newbie when it comes to SMTP.. sorry :(
> >>>
> >>>Thanks again for all your help ;)
> >>>
> >>>Greets
> >>>
> >>>mo
> >>>
> >>>
> >>
> >>I should have been a little clearer myself. You don't need to register a
> >>domain name. Just invent your own domain name for local purposes. Let's
> >>say you choose the domain name "monet", and that you have already given
> >>the hostnames "desktop" and "server" to your two machines. Then you
> >>would edit the file /etc/hosts on both machines to contain the following
> >>lines:
> >>
> >>192.168.23.11 desktop.monet desktop
> >>192.168.23.200 server.monet server
> >
> >I did that on gnome and desktop with appropriate changes:
> >
> >192.168.7.20 desktop.monet desktop
> >192.168.7.67 gnome.monet gnome
> >
> >>Now you only need to tell exim4 on the server that it is the final
> >>destination for emails to *.monet, again using the debconf wizard. You
> >>will then be able to send emails to local addresses, while emails to all
> >>other domains will go through your ISP's smarthost.
> >
> >I did that on gnome and desktop.
> >
> >>Incidently, you can also tell exim4 on the desktop to use the server as
> >>its smarthost.
> >>
> >>I realise that you're getting lots of (sometimes contradictory)
> >>information from various sources. The barebones configuration I have
> >>described above has served me well for several years.
> >
> >All commands are issued from gnome.
> >
> >  brian@gnome:~# ping -c3 desktop
> >  PING desktop.monet (192.168.7.20) 56(84) bytes of data.
> >  64 bytes from desktop.monet (192.168.7.20): icmp_seq=1 ttl=64 time=0.267 ms
> >  64 bytes from desktop.monet (192.168.7.20): icmp_seq=2 ttl=64 time=0.255 ms
> >  64 bytes from desktop.monet (192.168.7.20): icmp_seq=3 ttl=64 time=0.269 ms
> >
> >  --- desktop.monet ping statistics ---
> >  3 packets transmitted, 3 received, 0% packet loss, time 2001ms
> >  rtt min/avg/max/mdev = 0.255/0.263/0.269/0.019 ms
> >
> >  brian@gnome:~# ping -c3 desktop.monet
> >  PING desktop.monet (192.168.7.20) 56(84) bytes of data.
> >  64 bytes from desktop.monet (192.168.7.20): icmp_seq=1 ttl=64 time=0.264 ms
> >  64 bytes from desktop.monet (192.168.7.20): icmp_seq=2 ttl=64 time=0.255 ms
> >  64 bytes from desktop.monet (192.168.7.20): icmp_seq=3 ttl=64 time=0.255 ms
> >
> >  --- desktop.monet ping statistics ---
> >  3 packets transmitted, 3 received, 0% packet loss, time 2002ms
> >  rtt min/avg/max/mdev = 0.255/0.258/0.264/0.004 ms
> >
> >We expect that result because ping uses files in /etc/nsswitch.
> >
> >  root@gnome:~# exim -bt brian@desktop
> >  R: dnslookup for brian@desktop
> >  brian@desktop is undeliverable: Unrouteable address
> >
> >  root@gnome:~# exim -bt brian@desktop.monet
> >  R: dnslookup for brian@desktop.monet
> >  brian@desktop.monet is undeliverable: Unrouteable address
> >
> >Am I the only one who gets this? No capability to deliver mail to
> >desktop. What am I doing wrong?
> >
> 
> I think this is the problem with exim calling DNS on the given hostname...
> which is doomed to fail. To get it working you need to create the
> hubbed_hosts file and set your aliases in there, for example:
> 192.168.7.20: desktop
> 
> Then it should work fine, at least for me it did.
> 
> Hope this helps :)

Not really, I'm afraid.

We all know a hubbed_hosts file works. Mark Fletcher has written
extensively about it and I have said a thing or too also. What I want to
know is why following the advice from Liam O'Toole doesn't work for me,
even though I have followed the instructions exactly.

BTW: It would be 'desktop: 192.168.7.20' and 'desktop.monet:192.168.7.20

Re: Configuring Exim for mail delivery

[Liam O'Toole]

On 2016-10-01, Brian  wrote:
> On Sat 01 Oct 2016 at 17:25:46 +0100, Liam O'Toole wrote:
>
>> On 2016-10-01, mo  wrote:
>> > First of all:
>> > Thank you Liam for your help! :)
>> > Thanks for the very nice and long explanation Mark! :)
>> >
>> > I think i should elaborate a little more on my setup.. i guess i did not 
>> > make that very clear in the first place, sorry about that.
>> >
>> > My network is consisting of the following systems:
>> >
>> > Main PC - 192.168.23.11  (Running Debian Jessie)
>> > Server  - 192.168.23.200 (Running Debian Jessie)
>> >
>> > The server is always online, the PC is only half of the day on.
>> >
>> > What i want to do now is the following:
>> >
>> > Sending mail from my Main PC to my Server and also the other way around, 
>> > from the Server to my Main PC.
>> > The Server should also be able to send mail to the "outside" (Meaning to 
>> > other SMTP servers).
>> > The second requirement is optional since i dont own a domain and all 
>> > this is sitting locally at my home. The most important thing for me is 
>> > to send and receive mail from both systems in my home network.
>> > I hope this made my problem a little clearer :)
>> >
>> > I'm a little ashamed to say that, but i could not totally follow your 
>> > explanations Mark... I'm quite a newbie when it comes to SMTP.. sorry :(
>> >
>> > Thanks again for all your help ;)
>> >
>> > Greets
>> >
>> > mo
>> >
>> >
>> 
>> I should have been a little clearer myself. You don't need to register a
>> domain name. Just invent your own domain name for local purposes. Let's
>> say you choose the domain name "monet", and that you have already given
>> the hostnames "desktop" and "server" to your two machines. Then you
>> would edit the file /etc/hosts on both machines to contain the following
>> lines:
>> 
>>  192.168.23.11 desktop.monet desktop
>>  192.168.23.200 server.monet server
>
> I did that on gnome and desktop with appropriate changes:
>
> 192.168.7.20 desktop.monet desktop
> 192.168.7.67 gnome.monet gnome
>
>> Now you only need to tell exim4 on the server that it is the final
>> destination for emails to *.monet, again using the debconf wizard. You
>> will then be able to send emails to local addresses, while emails to all
>> other domains will go through your ISP's smarthost.
>
> I did that on gnome and desktop.
>
>> Incidently, you can also tell exim4 on the desktop to use the server as
>> its smarthost.
>> 
>> I realise that you're getting lots of (sometimes contradictory)
>> information from various sources. The barebones configuration I have
>> described above has served me well for several years.
>
> All commands are issued from gnome.
>
>   brian@gnome:~# ping -c3 desktop
>   PING desktop.monet (192.168.7.20) 56(84) bytes of data.
>   64 bytes from desktop.monet (192.168.7.20): icmp_seq=1 ttl=64 time=0.267 ms
>   64 bytes from desktop.monet (192.168.7.20): icmp_seq=2 ttl=64 time=0.255 ms
>   64 bytes from desktop.monet (192.168.7.20): icmp_seq=3 ttl=64 time=0.269 ms
>
>   --- desktop.monet ping statistics ---
>   3 packets transmitted, 3 received, 0% packet loss, time 2001ms
>   rtt min/avg/max/mdev = 0.255/0.263/0.269/0.019 ms
>
>   brian@gnome:~# ping -c3 desktop.monet
>   PING desktop.monet (192.168.7.20) 56(84) bytes of data.
>   64 bytes from desktop.monet (192.168.7.20): icmp_seq=1 ttl=64 time=0.264 ms
>   64 bytes from desktop.monet (192.168.7.20): icmp_seq=2 ttl=64 time=0.255 ms
>   64 bytes from desktop.monet (192.168.7.20): icmp_seq=3 ttl=64 time=0.255 ms
>
>   --- desktop.monet ping statistics ---
>   3 packets transmitted, 3 received, 0% packet loss, time 2002ms
>   rtt min/avg/max/mdev = 0.255/0.258/0.264/0.004 ms
>
> We expect that result because ping uses files in /etc/nsswitch.
>
>   root@gnome:~# exim -bt brian@desktop
>   R: dnslookup for brian@desktop
>   brian@desktop is undeliverable: Unrouteable address
>
>   root@gnome:~# exim -bt brian@desktop.monet
>   R: dnslookup for brian@desktop.monet
>   brian@desktop.monet is undeliverable: Unrouteable address
>
> Am I the only one who gets this? No capability to deliver mail to
> desktop. What am I doing wrong?
>

exim seems to be trying to resolve desktop.monet via DNS, thus ignoring
/etc/nsswitch. (I have no idea whether that is the default behaviour.) Do
you have a local DNS capable of resolving the address?

You might try the mail command from the mailutils or bsd-mailx packages
for comparison.

-- 

Liam

Re: Configuring Exim for mail delivery

[mo]

Am 01.10.2016 um 20:17 schrieb Brian:

On Sat 01 Oct 2016 at 17:25:46 +0100, Liam O'Toole wrote:


On 2016-10-01, mo  wrote:

First of all:
Thank you Liam for your help! :)
Thanks for the very nice and long explanation Mark! :)

I think i should elaborate a little more on my setup.. i guess i did not
make that very clear in the first place, sorry about that.

My network is consisting of the following systems:

Main PC - 192.168.23.11  (Running Debian Jessie)
Server  - 192.168.23.200 (Running Debian Jessie)

The server is always online, the PC is only half of the day on.

What i want to do now is the following:

Sending mail from my Main PC to my Server and also the other way around,
from the Server to my Main PC.
The Server should also be able to send mail to the "outside" (Meaning to
other SMTP servers).
The second requirement is optional since i dont own a domain and all
this is sitting locally at my home. The most important thing for me is
to send and receive mail from both systems in my home network.
I hope this made my problem a little clearer :)

I'm a little ashamed to say that, but i could not totally follow your
explanations Mark... I'm quite a newbie when it comes to SMTP.. sorry :(

Thanks again for all your help ;)

Greets

mo




I should have been a little clearer myself. You don't need to register a
domain name. Just invent your own domain name for local purposes. Let's
say you choose the domain name "monet", and that you have already given
the hostnames "desktop" and "server" to your two machines. Then you
would edit the file /etc/hosts on both machines to contain the following
lines:

192.168.23.11 desktop.monet desktop
192.168.23.200 server.monet server


I did that on gnome and desktop with appropriate changes:

192.168.7.20 desktop.monet desktop
192.168.7.67 gnome.monet gnome


Now you only need to tell exim4 on the server that it is the final
destination for emails to *.monet, again using the debconf wizard. You
will then be able to send emails to local addresses, while emails to all
other domains will go through your ISP's smarthost.


I did that on gnome and desktop.


Incidently, you can also tell exim4 on the desktop to use the server as
its smarthost.

I realise that you're getting lots of (sometimes contradictory)
information from various sources. The barebones configuration I have
described above has served me well for several years.


All commands are issued from gnome.

  brian@gnome:~# ping -c3 desktop
  PING desktop.monet (192.168.7.20) 56(84) bytes of data.
  64 bytes from desktop.monet (192.168.7.20): icmp_seq=1 ttl=64 time=0.267 ms
  64 bytes from desktop.monet (192.168.7.20): icmp_seq=2 ttl=64 time=0.255 ms
  64 bytes from desktop.monet (192.168.7.20): icmp_seq=3 ttl=64 time=0.269 ms

  --- desktop.monet ping statistics ---
  3 packets transmitted, 3 received, 0% packet loss, time 2001ms
  rtt min/avg/max/mdev = 0.255/0.263/0.269/0.019 ms

  brian@gnome:~# ping -c3 desktop.monet
  PING desktop.monet (192.168.7.20) 56(84) bytes of data.
  64 bytes from desktop.monet (192.168.7.20): icmp_seq=1 ttl=64 time=0.264 ms
  64 bytes from desktop.monet (192.168.7.20): icmp_seq=2 ttl=64 time=0.255 ms
  64 bytes from desktop.monet (192.168.7.20): icmp_seq=3 ttl=64 time=0.255 ms

  --- desktop.monet ping statistics ---
  3 packets transmitted, 3 received, 0% packet loss, time 2002ms
  rtt min/avg/max/mdev = 0.255/0.258/0.264/0.004 ms

We expect that result because ping uses files in /etc/nsswitch.

  root@gnome:~# exim -bt brian@desktop
  R: dnslookup for brian@desktop
  brian@desktop is undeliverable: Unrouteable address

  root@gnome:~# exim -bt brian@desktop.monet
  R: dnslookup for brian@desktop.monet
  brian@desktop.monet is undeliverable: Unrouteable address

Am I the only one who gets this? No capability to deliver mail to
desktop. What am I doing wrong?



I think this is the problem with exim calling DNS on the given 
hostname... which is doomed to fail. To get it working you need to 
create the hubbed_hosts file and set your aliases in there, for example:

192.168.7.20: desktop

Then it should work fine, at least for me it did.

Hope this helps :)

Re: Configuring Exim for mail delivery

[mo]

Am 01.10.2016 um 18:25 schrieb Liam O'Toole:

On 2016-10-01, mo  wrote:

First of all:
Thank you Liam for your help! :)
Thanks for the very nice and long explanation Mark! :)

I think i should elaborate a little more on my setup.. i guess i did not
make that very clear in the first place, sorry about that.

My network is consisting of the following systems:

Main PC - 192.168.23.11  (Running Debian Jessie)
Server  - 192.168.23.200 (Running Debian Jessie)

The server is always online, the PC is only half of the day on.

What i want to do now is the following:

Sending mail from my Main PC to my Server and also the other way around,
from the Server to my Main PC.
The Server should also be able to send mail to the "outside" (Meaning to
other SMTP servers).
The second requirement is optional since i dont own a domain and all
this is sitting locally at my home. The most important thing for me is
to send and receive mail from both systems in my home network.
I hope this made my problem a little clearer :)

I'm a little ashamed to say that, but i could not totally follow your
explanations Mark... I'm quite a newbie when it comes to SMTP.. sorry :(

Thanks again for all your help ;)

Greets

mo




I should have been a little clearer myself. You don't need to register a
domain name. Just invent your own domain name for local purposes. Let's
say you choose the domain name "monet", and that you have already given
the hostnames "desktop" and "server" to your two machines. Then you
would edit the file /etc/hosts on both machines to contain the following
lines:

192.168.23.11 desktop.monet desktop
192.168.23.200 server.monet server

Now you only need to tell exim4 on the server that it is the final
destination for emails to *.monet, again using the debconf wizard. You
will then be able to send emails to local addresses, while emails to all
other domains will go through your ISP's smarthost.

Incidently, you can also tell exim4 on the desktop to use the server as
its smarthost.

I realise that you're getting lots of (sometimes contradictory)
information from various sources. The barebones configuration I have
described above has served me well for several years.


Thanks for the clarification Liam :)


If you add more machines to your network later on you should consider
setting up local DHCP and DNS instead of manually updating /etc/hosts
files. But we'll leave that for another day. :)


I think that day will soon come for me :) (I cant live without some 
playing and fuzzing around :^) )

Re: Configuring Exim for mail delivery

[Brian]

On Sat 01 Oct 2016 at 17:25:46 +0100, Liam O'Toole wrote:

> On 2016-10-01, mo  wrote:
> > First of all:
> > Thank you Liam for your help! :)
> > Thanks for the very nice and long explanation Mark! :)
> >
> > I think i should elaborate a little more on my setup.. i guess i did not 
> > make that very clear in the first place, sorry about that.
> >
> > My network is consisting of the following systems:
> >
> > Main PC - 192.168.23.11  (Running Debian Jessie)
> > Server  - 192.168.23.200 (Running Debian Jessie)
> >
> > The server is always online, the PC is only half of the day on.
> >
> > What i want to do now is the following:
> >
> > Sending mail from my Main PC to my Server and also the other way around, 
> > from the Server to my Main PC.
> > The Server should also be able to send mail to the "outside" (Meaning to 
> > other SMTP servers).
> > The second requirement is optional since i dont own a domain and all 
> > this is sitting locally at my home. The most important thing for me is 
> > to send and receive mail from both systems in my home network.
> > I hope this made my problem a little clearer :)
> >
> > I'm a little ashamed to say that, but i could not totally follow your 
> > explanations Mark... I'm quite a newbie when it comes to SMTP.. sorry :(
> >
> > Thanks again for all your help ;)
> >
> > Greets
> >
> > mo
> >
> >
> 
> I should have been a little clearer myself. You don't need to register a
> domain name. Just invent your own domain name for local purposes. Let's
> say you choose the domain name "monet", and that you have already given
> the hostnames "desktop" and "server" to your two machines. Then you
> would edit the file /etc/hosts on both machines to contain the following
> lines:
> 
>   192.168.23.11 desktop.monet desktop
>   192.168.23.200 server.monet server

I did that on gnome and desktop with appropriate changes:

192.168.7.20 desktop.monet desktop
192.168.7.67 gnome.monet gnome

> Now you only need to tell exim4 on the server that it is the final
> destination for emails to *.monet, again using the debconf wizard. You
> will then be able to send emails to local addresses, while emails to all
> other domains will go through your ISP's smarthost.

I did that on gnome and desktop.

> Incidently, you can also tell exim4 on the desktop to use the server as
> its smarthost.
> 
> I realise that you're getting lots of (sometimes contradictory)
> information from various sources. The barebones configuration I have
> described above has served me well for several years.

All commands are issued from gnome.

  brian@gnome:~# ping -c3 desktop
  PING desktop.monet (192.168.7.20) 56(84) bytes of data.
  64 bytes from desktop.monet (192.168.7.20): icmp_seq=1 ttl=64 time=0.267 ms
  64 bytes from desktop.monet (192.168.7.20): icmp_seq=2 ttl=64 time=0.255 ms
  64 bytes from desktop.monet (192.168.7.20): icmp_seq=3 ttl=64 time=0.269 ms

  --- desktop.monet ping statistics ---
  3 packets transmitted, 3 received, 0% packet loss, time 2001ms
  rtt min/avg/max/mdev = 0.255/0.263/0.269/0.019 ms

  brian@gnome:~# ping -c3 desktop.monet
  PING desktop.monet (192.168.7.20) 56(84) bytes of data.
  64 bytes from desktop.monet (192.168.7.20): icmp_seq=1 ttl=64 time=0.264 ms
  64 bytes from desktop.monet (192.168.7.20): icmp_seq=2 ttl=64 time=0.255 ms
  64 bytes from desktop.monet (192.168.7.20): icmp_seq=3 ttl=64 time=0.255 ms

  --- desktop.monet ping statistics ---
  3 packets transmitted, 3 received, 0% packet loss, time 2002ms
  rtt min/avg/max/mdev = 0.255/0.258/0.264/0.004 ms

We expect that result because ping uses files in /etc/nsswitch.

  root@gnome:~# exim -bt brian@desktop
  R: dnslookup for brian@desktop
  brian@desktop is undeliverable: Unrouteable address

  root@gnome:~# exim -bt brian@desktop.monet
  R: dnslookup for brian@desktop.monet
  brian@desktop.monet is undeliverable: Unrouteable address

Am I the only one who gets this? No capability to deliver mail to
desktop. What am I doing wrong?

-- 
Brian.

Re: Configuring Exim for mail delivery

[Liam O'Toole]

On 2016-10-01, mo  wrote:
> First of all:
> Thank you Liam for your help! :)
> Thanks for the very nice and long explanation Mark! :)
>
> I think i should elaborate a little more on my setup.. i guess i did not 
> make that very clear in the first place, sorry about that.
>
> My network is consisting of the following systems:
>
> Main PC - 192.168.23.11  (Running Debian Jessie)
> Server  - 192.168.23.200 (Running Debian Jessie)
>
> The server is always online, the PC is only half of the day on.
>
> What i want to do now is the following:
>
> Sending mail from my Main PC to my Server and also the other way around, 
> from the Server to my Main PC.
> The Server should also be able to send mail to the "outside" (Meaning to 
> other SMTP servers).
> The second requirement is optional since i dont own a domain and all 
> this is sitting locally at my home. The most important thing for me is 
> to send and receive mail from both systems in my home network.
> I hope this made my problem a little clearer :)
>
> I'm a little ashamed to say that, but i could not totally follow your 
> explanations Mark... I'm quite a newbie when it comes to SMTP.. sorry :(
>
> Thanks again for all your help ;)
>
> Greets
>
> mo
>
>

I should have been a little clearer myself. You don't need to register a
domain name. Just invent your own domain name for local purposes. Let's
say you choose the domain name "monet", and that you have already given
the hostnames "desktop" and "server" to your two machines. Then you
would edit the file /etc/hosts on both machines to contain the following
lines:

192.168.23.11 desktop.monet desktop
192.168.23.200 server.monet server

Now you only need to tell exim4 on the server that it is the final
destination for emails to *.monet, again using the debconf wizard. You
will then be able to send emails to local addresses, while emails to all
other domains will go through your ISP's smarthost.

Incidently, you can also tell exim4 on the desktop to use the server as
its smarthost.

I realise that you're getting lots of (sometimes contradictory)
information from various sources. The barebones configuration I have
described above has served me well for several years.

If you add more machines to your network later on you should consider
setting up local DHCP and DNS instead of manually updating /etc/hosts
files. But we'll leave that for another day. :)

-- 

Liam

Re: Configuring Exim for mail delivery

[Brian]

On Sat 01 Oct 2016 at 22:36:09 +0900, Mark Fletcher wrote:

> On Sat, Oct 01, 2016 at 01:56:40PM +0100, Brian wrote:
> 
> > The thing for Mo to grasp is that exim *always* does an MX lookup, often
> > using the ISP's DNS server. user@server will fail (as has been found
> > out) because the domain "server" is not in the DNS.
> > 
> > /etc/hosts is not consulted when the lookup is done. exim can be made to
> > look at /etc/hosts but for such a simple setup it is not worth the
> > effort and would likely lead to a world of pain.
> > 

I hope we are not talking at cross-purposes. I was explicitly addressing
the issue of why an entry in /etc/hosts for machines on the network will
not replace a hubbed_hosts file.

> With great respect I think that confuses the issue. A DNS lookup will 
> *not* explicitly get done by exim4 if the target domain is in 
> hubbed_hosts, or if exim4 has been told it is the local domain. The 

A hubbed_hosts file is for overriding or augmenting MX information from
the DNS (exim4-config_files). If you had

  lists.debian.org: 91.221.168.152

the DNS would not be used and any mail to debian-user@lists.debian.org
would go to 91.221.168.152. MX information would be overriden.

With

  server: 192.168.5.100 or server: server.local

MX information is augmented.

> point is one wishes to PREVENT a DNS lookup that is doomed to fail, and 

No. The point is you want to override or augment MX information. Ok, a
DNS lookup is prevented but it is not because it is one which is doomed
to fail. A lookup on lists.debian.org would succeed but for some reason
the user wants the mail to go to 91.221.168.152.

> one does so for machines that are not the machine-local domain by 
> putting them in hubbed_hosts, which will cause exim4 to throw out a 
> connection request for the local network infrastructure (starting with 
> the network infra on the local machine) to handle, without doing an 
> explicit DNS lookup. That is handled by /etc/hosts if it is populated, 
> and by Avahi if it is present and /etc/hosts is not populated, and no 
> doubt by a few other alternatives I am not familiar with as well. If 
> none of them succeed, the delivery will fail, because if I recall 
> correctly hubbed_hosts router config ends with no_more which prevents 
> other routers having a go.

exim does not use /etc/hosts; user@server will fail with '192.168.7.88
server' in it. user@server,local succeeds because server.local is in the
DNS.

-- 
Brian.

Re: Configuring Exim for mail delivery

[mo]

Am 01.10.2016 um 16:17 schrieb rhkra...@gmail.com:

On Saturday, October 01, 2016 08:23:10 AM mo wrote:

I use Icedove (Thunderbird) for all my personal mails and also to write
mail to the Debian users Mailing list ;)
I have never tried Kmail before, maybe i should, but Icedove fit's the
bill right :) (I'm normally a wm guy.. so i opt for lesser dependencies
when i install software... (Kmail pulls in a lot of KDE stuff that i
don't want) but atm i use Gnome.. well it works :D )
I will give Kmail a try on one of my vm's (Got Debian Jessie here in a
vm on which i have KDE installed)


AFAIK, Icedove is the same kind of email client as kmail, so there is no need
to try kmail.  (I happen to use (or, at least, used to use) a lot of other KDE
stuff, do using kmail was no burden for me.)  (I mean that Icedove uses (or at
least can use) pop3 to get emails and smtp to send emails--otoh, I have never
used Icedove, so I'm not absolutely sure.


Indeed, they are both MUA's with quite the same features (Of course the 
GUI is different - also another gui toolkit, qt - icedove uses gtk)

Yes, that is true, icedove can handle POP and IMAP


regards,
Randy Kramer



Greets

mo

Re: Configuring Exim for mail delivery

[mo]

Am 01.10.2016 um 15:57 schrieb Teemu Likonen:

mo [2016-10-01 12:36:10+02] wrote:


I'm not a friend of avahi to be honest, i much rather ignore it :D


Avahi is great. My ethernet-connected printer uses DHCP to get IP
address and network configuration. The printer announces itself to the
network with .local name so a print server can use that
name to connect to it. CUPS print server also announces its printers by
names. No static IP address configuration needed anywhere. I think the
underlying technique is called multicast DNS.



I guess i should be looking into avahi, never really did that, to be 
honest avahi so far did not really made much sense to me with my static 
network... But one can never learn enough ;)


Greets

mo

Re: Configuring Exim for mail delivery

[mo]

Am 01.10.2016 um 15:36 schrieb Mark Fletcher:

On Sat, Oct 01, 2016 at 01:56:40PM +0100, Brian wrote:


The thing for Mo to grasp is that exim *always* does an MX lookup, often
using the ISP's DNS server. user@server will fail (as has been found
out) because the domain "server" is not in the DNS.

/etc/hosts is not consulted when the lookup is done. exim can be made to
look at /etc/hosts but for such a simple setup it is not worth the
effort and would likely lead to a world of pain.



With great respect I think that confuses the issue. A DNS lookup will
*not* explicitly get done by exim4 if the target domain is in
hubbed_hosts, or if exim4 has been told it is the local domain. The
point is one wishes to PREVENT a DNS lookup that is doomed to fail, and
one does so for machines that are not the machine-local domain by
putting them in hubbed_hosts, which will cause exim4 to throw out a
connection request for the local network infrastructure (starting with
the network infra on the local machine) to handle, without doing an
explicit DNS lookup. That is handled by /etc/hosts if it is populated,
and by Avahi if it is present and /etc/hosts is not populated, and no
doubt by a few other alternatives I am not familiar with as well. If
none of them succeed, the delivery will fail, because if I recall
correctly hubbed_hosts router config ends with no_more which prevents
other routers having a go.

However, for domains NOT listed in hubbed_hosts, if not in smarthost
mode, yes exim4's next move will be an explicit DNS lookup on the
domain. It is trying to find out what *machine* it should contact to
make the delivery to that domain. If it is in smarthost mode, it throws
its hands in the air and passes the problem to the smarthost to solve.


Oh yes, i see. Indeed i can understand your point!
Thanks for the explanation ;)
My picture of exim is getting better and better :)


Mark



Greets

mo

Re: Configuring Exim for mail delivery

[Teemu Likonen]

mo [2016-10-01 12:36:10+02] wrote:

> I'm not a friend of avahi to be honest, i much rather ignore it :D

Avahi is great. My ethernet-connected printer uses DHCP to get IP
address and network configuration. The printer announces itself to the
network with .local name so a print server can use that
name to connect to it. CUPS print server also announces its printers by
names. No static IP address configuration needed anywhere. I think the
underlying technique is called multicast DNS.

-- 
/// Teemu Likonen   - .-..    //
// PGP: 4E10 55DC 84E9 DFF6 13D7 8557 719D 69D3 2453 9450 ///


signature.asc
Description: PGP signature

Re: Configuring Exim for mail delivery

[Mark Fletcher]

On Sat, Oct 01, 2016 at 01:56:40PM +0100, Brian wrote:

> The thing for Mo to grasp is that exim *always* does an MX lookup, often
> using the ISP's DNS server. user@server will fail (as has been found
> out) because the domain "server" is not in the DNS.
> 
> /etc/hosts is not consulted when the lookup is done. exim can be made to
> look at /etc/hosts but for such a simple setup it is not worth the
> effort and would likely lead to a world of pain.
> 

With great respect I think that confuses the issue. A DNS lookup will 
*not* explicitly get done by exim4 if the target domain is in 
hubbed_hosts, or if exim4 has been told it is the local domain. The 
point is one wishes to PREVENT a DNS lookup that is doomed to fail, and 
one does so for machines that are not the machine-local domain by 
putting them in hubbed_hosts, which will cause exim4 to throw out a 
connection request for the local network infrastructure (starting with 
the network infra on the local machine) to handle, without doing an 
explicit DNS lookup. That is handled by /etc/hosts if it is populated, 
and by Avahi if it is present and /etc/hosts is not populated, and no 
doubt by a few other alternatives I am not familiar with as well. If 
none of them succeed, the delivery will fail, because if I recall 
correctly hubbed_hosts router config ends with no_more which prevents 
other routers having a go.

However, for domains NOT listed in hubbed_hosts, if not in smarthost 
mode, yes exim4's next move will be an explicit DNS lookup on the 
domain. It is trying to find out what *machine* it should contact to 
make the delivery to that domain. If it is in smarthost mode, it throws 
its hands in the air and passes the problem to the smarthost to solve.

Mark

Re: Configuring Exim for mail delivery

[mo]

Am 01.10.2016 um 14:52 schrieb Mark Fletcher:

On Sat, Oct 01, 2016 at 02:24:16PM +0200, mo wrote:



Am 01.10.2016 um 14:20 schrieb Brian:

On Sat 01 Oct 2016 at 14:09:19 +0200, mo wrote:


Am 01.10.2016 um 14:02 schrieb Mark Fletcher:


No colons as separators in hubbed_hosts, to my knowledge. Use spaces or tabs.


I have colones in the hubbed_hosts file... seems to work.
I just tested it: It works with or without the colon. Maybe this is
interesting to know ;)


Please see exim4-config_files(5).



Just looked into the man page, indeed a colon is required there. ;)



No, it isn't. I don't use colons in my hubbed_hosts file.


Both works actually. I Just tried it. But the man pages uses colons.. 
seems like it works fine with or without ;)



Mark



Greets

mo

Re: Configuring Exim for mail delivery

[mo]

Am 01.10.2016 um 14:56 schrieb Brian:

On Sat 01 Oct 2016 at 21:23:33 +0900, Mark Fletcher wrote:


On Sat, Oct 01, 2016 at 12:36:10PM +0200, mo wrote:


I just did that and now mailing works flawlessly :D
Just one questions: Why do i need hubbed_host entries? Should it not be fine
alone to make a entry in /etc/hosts for the machines i want to send mail to
(I do not operate a dedicated DNS server).
This is something i dont really understand...


hubbed_host entries apply only to exim4. I also suspect, but am not
sure, that they are a Debian extension to exim4 in the sense that the
*DEBIAN* exim4 comes configured for them out of the box, while the
upstream exim4 does not. IIRC there is no reference to hubbed_hosts in
the upstream documentation, only in the Debian docs.


Correct. I'll add: the upstream documentation spec.txt.gz covers
hubbed_hosts in sections 20.3 to 20.7. It is not obligatory to read it.


They work because the debian config contains a router to handle hubbed
hosts. You can see what it is doing if you search
/var/lib/exim4/config.autogenerated for the text hubbed_hosts.


Fine.


If the file is not populated this router is skipped and then exim4
requires either that the address is the local machine, or that there is
a smarthost configured that it can delegate to, or that it can find an
official MX entry for the target domain by doing a DNS lookup. All of
which will fail for a local box that isn't registered to the world as a
mail server.


The thing for Mo to grasp is that exim *always* does an MX lookup, often
using the ISP's DNS server. user@server will fail (as has been found
out) because the domain "server" is not in the DNS.

/etc/hosts is not consulted when the lookup is done. exim can be made to
look at /etc/hosts but for such a simple setup it is not worth the
effort and would likely lead to a world of pain.


just out of curiosity:
What did i have to do to make exim honor the /etc/hosts file? :)
(I quite often find myself in the world of pain :D )

Greets

mo

Re: Configuring Exim for mail delivery

[mo]

Am 01.10.2016 um 14:51 schrieb Mark Fletcher:

On Sat, Oct 01, 2016 at 02:33:27PM +0200, mo wrote:




I sure appreciate to know the inner workings of it all :)
Good to know how avahi is involved here, this paints me a clearer picture :)



I just want to correct one thing I said here, having read your other
posts. In one of them you mentioned you have static routing mappings set
up for your network machines in /etc/hosts. That is a perfectly valid
setup, albeit it is not the default "Debian way" (by which I mean only
that it is not how Debian comes configured out of the box, or more
accurately out of the .iso) and not how I do it. What a pain if you buy
a new computer to add to your network! But absolutely nothing invalid
about it.


Well i'm using the static network config since quite some time, but i 
had planned to change over to DHCP... But for now it works ;)
(The work is not so hard, adding a machine to the network is done 
quickly with Debian ;) - My other machines use different Operating 
Systems, got FreeBSD and OpenBSD here to on the LAN, works like a charm :) )



In this case, Avahi is probably *not* involved because exim4 gets an
answer to the question of what IP the host name maps to, without having
to consult it. But it *would be* involved if you did not have static
mappings set up in /etc/hosts.


Good to know ;)


Mark



Thanks Mark ;)

Greets

mo

Re: Configuring Exim for mail delivery

[Brian]

On Sat 01 Oct 2016 at 21:23:33 +0900, Mark Fletcher wrote:

> On Sat, Oct 01, 2016 at 12:36:10PM +0200, mo wrote:
> > 
> > I just did that and now mailing works flawlessly :D
> > Just one questions: Why do i need hubbed_host entries? Should it not be fine
> > alone to make a entry in /etc/hosts for the machines i want to send mail to
> > (I do not operate a dedicated DNS server).
> > This is something i dont really understand...
> 
> hubbed_host entries apply only to exim4. I also suspect, but am not 
> sure, that they are a Debian extension to exim4 in the sense that the 
> *DEBIAN* exim4 comes configured for them out of the box, while the 
> upstream exim4 does not. IIRC there is no reference to hubbed_hosts in 
> the upstream documentation, only in the Debian docs.

Correct. I'll add: the upstream documentation spec.txt.gz covers
hubbed_hosts in sections 20.3 to 20.7. It is not obligatory to read it.

> They work because the debian config contains a router to handle hubbed 
> hosts. You can see what it is doing if you search 
> /var/lib/exim4/config.autogenerated for the text hubbed_hosts.

Fine.

> If the file is not populated this router is skipped and then exim4 
> requires either that the address is the local machine, or that there is 
> a smarthost configured that it can delegate to, or that it can find an 
> official MX entry for the target domain by doing a DNS lookup. All of 
> which will fail for a local box that isn't registered to the world as a 
> mail server.

The thing for Mo to grasp is that exim *always* does an MX lookup, often
using the ISP's DNS server. user@server will fail (as has been found
out) because the domain "server" is not in the DNS.

/etc/hosts is not consulted when the lookup is done. exim can be made to
look at /etc/hosts but for such a simple setup it is not worth the
effort and would likely lead to a world of pain.

-- 
Brian.

Re: Configuring Exim for mail delivery

[Mark Fletcher]

On Sat, Oct 01, 2016 at 02:24:16PM +0200, mo wrote:
> 
> 
> Am 01.10.2016 um 14:20 schrieb Brian:
> >On Sat 01 Oct 2016 at 14:09:19 +0200, mo wrote:
> >
> >>Am 01.10.2016 um 14:02 schrieb Mark Fletcher:
> >>>
> >>>No colons as separators in hubbed_hosts, to my knowledge. Use spaces or 
> >>>tabs.
> >>
> >>I have colones in the hubbed_hosts file... seems to work.
> >>I just tested it: It works with or without the colon. Maybe this is
> >>interesting to know ;)
> >
> >Please see exim4-config_files(5).
> >
> 
> Just looked into the man page, indeed a colon is required there. ;)
> 

No, it isn't. I don't use colons in my hubbed_hosts file.

Mark

Re: Configuring Exim for mail delivery

[Mark Fletcher]

On Sat, Oct 01, 2016 at 02:33:27PM +0200, mo wrote:
> 
> 
> 
> I sure appreciate to know the inner workings of it all :)
> Good to know how avahi is involved here, this paints me a clearer picture :)
> 

I just want to correct one thing I said here, having read your other 
posts. In one of them you mentioned you have static routing mappings set 
up for your network machines in /etc/hosts. That is a perfectly valid 
setup, albeit it is not the default "Debian way" (by which I mean only 
that it is not how Debian comes configured out of the box, or more 
accurately out of the .iso) and not how I do it. What a pain if you buy 
a new computer to add to your network! But absolutely nothing invalid 
about it.

In this case, Avahi is probably *not* involved because exim4 gets an 
answer to the question of what IP the host name maps to, without having 
to consult it. But it *would be* involved if you did not have static 
mappings set up in /etc/hosts.

Mark

Re: Configuring Exim for mail delivery

[mo]

Am 01.10.2016 um 14:23 schrieb Mark Fletcher:

On Sat, Oct 01, 2016 at 12:36:10PM +0200, mo wrote:


Did you follow a specific book or guide?


Google "debian exim4 configuration". And look at the upstream
documentation in package exim4-doc-html.



I will do so ;)




Exim configuration has the concept of "routers" and "transports".
Routers basically decide what to do with a message, and transports do
it. One of the routers configured by default in the Debian exim
configuration is for "hubbed hosts". What this means, is machines
capable of sending and receiving email ("hosts" in exim speak) that are
on the same LAN as this machine (connected by a "hub"). Note that this
"hub" could be your local home network router, and for these purposes
machines on WiFi and machines on a wired LAN would be considered on the
same hub, even though that isn't strictly true. The point is that
network packets can be addressed directly between the machines, they
don't require a router in between.



As far as i do understand this is that only machines which are defined as
hubbed hosts can be send mail in the local LAN? Or am i misunderstanding
something here? :)



In essence yes you are right, because a local configuration of exim4
would determine that the addresses are not local and not in
hubbed_hosts, and tell you to eff off, while a smarthost configuration
would attempt to use the smarthost to send to the local machine, which
is doomed to failure, and the internet configuration would attempt to
use DNS to find the local machine, which is also doomed to failure.
Being in hubbed_hosts prevents exim4 for going looking for an MX record
for the receiving host, which is guaranteed to fail for a machine that
isn't registered to the world at large as an email server.



Alright, i finally go it ;) Thanks for the explanation Mark! :)


In Debian, this is achieved with Avahi. This is what allows you, if you
have MachineA and MachineB on your network, to do for example "ping
MachineA.local" from MachineB and expect MachineA.local to be resolved
into an IP address.



I'm not a friend of avahi to be honest, i much rather ignore it :D


All I can do here is echo Brian. But also, even if you aren't its
friend, ignoring it is fine, because it comes already configured and
will just do its job whether it gets any love from you or not. I just
assumed you'd like to know what is going on under the hood.


I sure appreciate to know the inner workings of it all :)
Good to know how avahi is involved here, this paints me a clearer picture :)




In /etc/exim4, create a file owned by root called hubbed_hosts. In the
file, each line maps a "domain" (the part after the @ sign in an email
address) to a "host" (the name of a machine on your network, as it can
be reached from this machine). Put the domain first, then a tab
character (spaces may also be OK) and then the host. So for example I
have a machine on my network called affinity, and so in the hubbed_hosts
file on the machine I am sitting in front of now, I have two lines, one
saying "affinity.localaffinity.local", and the other saying
"affinityaffinity.local" (no quotes in the file). This tells the
local exim installation that any email address with @affinity.local as
the domain should be forwarded on to a machine called affinity.local,
and any mail with @affinity as the domain should be forwarded on to a
machine called affinity.local. Exim4 will then say "Connect to
affinity.local!" with no attempt to translate that into an IP address,
and Avahi daemon will answer "that is IP address WW.XX.YY.ZZ!" to which
exim will say "very well, connect to WW.XX.YY.ZZ!" and the exim4 on
affinity will wake up and co-operate to deliver the mail.


I just did that and now mailing works flawlessly :D
Just one questions: Why do i need hubbed_host entries? Should it not be fine
alone to make a entry in /etc/hosts for the machines i want to send mail to
(I do not operate a dedicated DNS server).
This is something i dont really understand...


hubbed_host entries apply only to exim4. I also suspect, but am not
sure, that they are a Debian extension to exim4 in the sense that the
*DEBIAN* exim4 comes configured for them out of the box, while the
upstream exim4 does not. IIRC there is no reference to hubbed_hosts in
the upstream documentation, only in the Debian docs.

They work because the debian config contains a router to handle hubbed
hosts. You can see what it is doing if you search
/var/lib/exim4/config.autogenerated for the text hubbed_hosts.


I will consult the Debian docs, currently reading over the wiki page of 
exim :)



If the file is not populated this router is skipped and then exim4
requires either that the address is the local machine, or that there is
a smarthost configured that it can delegate to, or that it can find an
official MX entry for the target domain by doing a DNS lookup. All of
which will fail for a local box that isn't registered to the world as a
mail server.


I see, thanks for t

Re: Configuring Exim for mail delivery

[Mark Fletcher]

On Sat, Oct 01, 2016 at 12:36:10PM +0200, mo wrote:
> 
> Did you follow a specific book or guide?

Google "debian exim4 configuration". And look at the upstream 
documentation in package exim4-doc-html.

> 
> >Exim configuration has the concept of "routers" and "transports".
> >Routers basically decide what to do with a message, and transports do
> >it. One of the routers configured by default in the Debian exim
> >configuration is for "hubbed hosts". What this means, is machines
> >capable of sending and receiving email ("hosts" in exim speak) that are
> >on the same LAN as this machine (connected by a "hub"). Note that this
> >"hub" could be your local home network router, and for these purposes
> >machines on WiFi and machines on a wired LAN would be considered on the
> >same hub, even though that isn't strictly true. The point is that
> >network packets can be addressed directly between the machines, they
> >don't require a router in between.
> >
> 
> As far as i do understand this is that only machines which are defined as
> hubbed hosts can be send mail in the local LAN? Or am i misunderstanding
> something here? :)
> 

In essence yes you are right, because a local configuration of exim4 
would determine that the addresses are not local and not in 
hubbed_hosts, and tell you to eff off, while a smarthost configuration 
would attempt to use the smarthost to send to the local machine, which 
is doomed to failure, and the internet configuration would attempt to 
use DNS to find the local machine, which is also doomed to failure. 
Being in hubbed_hosts prevents exim4 for going looking for an MX record 
for the receiving host, which is guaranteed to fail for a machine that 
isn't registered to the world at large as an email server.

> >In Debian, this is achieved with Avahi. This is what allows you, if you
> >have MachineA and MachineB on your network, to do for example "ping
> >MachineA.local" from MachineB and expect MachineA.local to be resolved
> >into an IP address.
> >
> 
> I'm not a friend of avahi to be honest, i much rather ignore it :D

All I can do here is echo Brian. But also, even if you aren't its 
friend, ignoring it is fine, because it comes already configured and 
will just do its job whether it gets any love from you or not. I just 
assumed you'd like to know what is going on under the hood.

> 
> >In /etc/exim4, create a file owned by root called hubbed_hosts. In the
> >file, each line maps a "domain" (the part after the @ sign in an email
> >address) to a "host" (the name of a machine on your network, as it can
> >be reached from this machine). Put the domain first, then a tab
> >character (spaces may also be OK) and then the host. So for example I
> >have a machine on my network called affinity, and so in the hubbed_hosts
> >file on the machine I am sitting in front of now, I have two lines, one
> >saying "affinity.localaffinity.local", and the other saying
> >"affinityaffinity.local" (no quotes in the file). This tells the
> >local exim installation that any email address with @affinity.local as
> >the domain should be forwarded on to a machine called affinity.local,
> >and any mail with @affinity as the domain should be forwarded on to a
> >machine called affinity.local. Exim4 will then say "Connect to
> >affinity.local!" with no attempt to translate that into an IP address,
> >and Avahi daemon will answer "that is IP address WW.XX.YY.ZZ!" to which
> >exim will say "very well, connect to WW.XX.YY.ZZ!" and the exim4 on
> >affinity will wake up and co-operate to deliver the mail.
> 
> I just did that and now mailing works flawlessly :D
> Just one questions: Why do i need hubbed_host entries? Should it not be fine
> alone to make a entry in /etc/hosts for the machines i want to send mail to
> (I do not operate a dedicated DNS server).
> This is something i dont really understand...

hubbed_host entries apply only to exim4. I also suspect, but am not 
sure, that they are a Debian extension to exim4 in the sense that the 
*DEBIAN* exim4 comes configured for them out of the box, while the 
upstream exim4 does not. IIRC there is no reference to hubbed_hosts in 
the upstream documentation, only in the Debian docs.

They work because the debian config contains a router to handle hubbed 
hosts. You can see what it is doing if you search 
/var/lib/exim4/config.autogenerated for the text hubbed_hosts.

If the file is not populated this router is skipped and then exim4 
requires either that the address is the local machine, or that there is 
a smarthost configured that it can delegate to, or that it can find an 
official MX entry for the target domain by doing a DNS lookup. All of 
which will fail for a local box that isn't registered to the world as a 
mail server.

Mark

Re: Configuring Exim for mail delivery

[mo]

Am 01.10.2016 um 14:20 schrieb Brian:

On Sat 01 Oct 2016 at 14:09:19 +0200, mo wrote:


Am 01.10.2016 um 14:02 schrieb Mark Fletcher:


No colons as separators in hubbed_hosts, to my knowledge. Use spaces or tabs.


I have colones in the hubbed_hosts file... seems to work.
I just tested it: It works with or without the colon. Maybe this is
interesting to know ;)


Please see exim4-config_files(5).



Just looked into the man page, indeed a colon is required there. ;)

Re: Configuring Exim for mail delivery

[Brian]

On Sat 01 Oct 2016 at 14:09:19 +0200, mo wrote:

> Am 01.10.2016 um 14:02 schrieb Mark Fletcher:
> >
> >No colons as separators in hubbed_hosts, to my knowledge. Use spaces or tabs.
> 
> I have colones in the hubbed_hosts file... seems to work.
> I just tested it: It works with or without the colon. Maybe this is
> interesting to know ;)

Please see exim4-config_files(5).

-- 
Brian.

Re: Configuring Exim for mail delivery

[rhkramer]

On Saturday, October 01, 2016 05:06:07 AM mo wrote:
> My network is consisting of the following systems:
> 
> Main PC - 192.168.23.11  (Running Debian Jessie)
> Server  - 192.168.23.200 (Running Debian Jessie)
> 
> The server is always online, the PC is only half of the day on.
> 
> What i want to do now is the following:
> 
> Sending mail from my Main PC to my Server and also the other way around,
> from the Server to my Main PC.
> The Server should also be able to send mail to the "outside" (Meaning to
> other SMTP servers).
> The second requirement is optional since i dont own a domain and all
> this is sitting locally at my home. The most important thing for me is
> to send and receive mail from both systems in my home network.
> I hope this made my problem a little clearer :)
> 
> I'm a little ashamed to say that, but i could not totally follow your
> explanations Mark... I'm quite a newbie when it comes to SMTP.. sorry :(
> 
> Thanks again for all your help ;)

Here is how I do something similar (I don't need to get all emails to both 
systems), and some other alternatives:

What I do now:

   * On my main desktop (which I normally use to send and receive emails), I 
use kmail, which I consider a "Windows style" email client (because I don't 
know what else to call it--it sends email via SMTP and receives email via 
POP3--it (the PC) doesn't use anything like an MTA (e.g., postfix)) and is set 
to delete emails from the server).  

My email provider / server is Google (which I don't really like because of the 
insecurity, but I started using it a long time ago and haven't bothered to 
switch)--for really confidential emails I use encryption).  

On the other PC, which I use only rarely to receive or send emails, I use a 
browser to access my google mail account.  Even though I set kmail on the 
other PC to delete emails from the server, google keeps them in the "all mail" 
file for something like 30 days.  (Aside: I forget how emails sent from the 
second PC get to the first--I'll have to test that--they do seem to get there.)

Other alternatives:

   * Use, for example, kmail on both PCs, but use something like rsync to keep 
the mail folders in sync on both PCs.

   * 

Re: Configuring Exim for mail delivery

[mo]

Am 01.10.2016 um 14:02 schrieb Mark Fletcher:

On Sat, Oct 01, 2016 at 11:01:17AM +0100, Brian wrote:

On Sat 01 Oct 2016 at 11:06:07 +0200, mo wrote:


First of all:
Thank you Liam for your help! :)
Thanks for the very nice and long explanation Mark! :)

I think i should elaborate a little more on my setup.. i guess i did not
make that very clear in the first place, sorry about that.

My network is consisting of the following systems:

Main PC - 192.168.23.11  (Running Debian Jessie)
Server  - 192.168.23.200 (Running Debian Jessie)

The server is always online, the PC is only half of the day on.

What i want to do now is the following:

Sending mail from my Main PC to my Server and also the other way around,
from the Server to my Main PC.
The Server should also be able to send mail to the "outside" (Meaning to
other SMTP servers).
The second requirement is optional since i dont own a domain and all this is
sitting locally at my home. The most important thing for me is to send and
receive mail from both systems in my home network.
I hope this made my problem a little clearer :)

I'm a little ashamed to say that, but i could not totally follow your
explanations Mark... I'm quite a newbie when it comes to SMTP.. sorry :(


Assuming the server hostname is "server".

1. On Main PC use your editor to create /etc/exim4/hubbed_hosts. In it
   put

   server: 192.168.23.200

   in it and restart exim4.

2. Send mail to user@server.

3. You can replace 'server: 192.168.23.200' with 'server: server.local'
   if avahi-daemon is running on both machines.



No colons as separators in hubbed_hosts, to my knowledge. Use spaces or tabs.


I have colones in the hubbed_hosts file... seems to work.
I just tested it: It works with or without the colon. Maybe this is 
interesting to know ;)



Mark

Re: Configuring Exim for mail delivery

[mo]

Am 01.10.2016 um 14:00 schrieb Mark Fletcher:

On Sat, Oct 01, 2016 at 01:39:47PM +0200, mo wrote:



Am 01.10.2016 um 13:22 schrieb Brian:

On Sat 01 Oct 2016 at 12:36:10 +0200, mo wrote:



I just did that and now mailing works flawlessly :D
Just one questions: Why do i need hubbed_host entries? Should it not be fine
alone to make a entry in /etc/hosts for the machines i want to send mail to
(I do not operate a dedicated DNS server).
This is something i dont really understand...


I'd suggest you try it and look at the logs.


Watch out, you may piss off your ISP if you repeatedly send emails it
can't deliver. They'll make their displeasure felt by not delivering
_any_ mails for you for a while. My suggestion is get local delivery
working first, then turn attention to mails outside.



Thanks for the hint Mark :)
So far i only tried it twice, i think i'm save for the moment. :D haha


Mark

Re: Configuring Exim for mail delivery

[mo]

Hi Mo


Hi Clive :)


I tried to send this with a .pdf yesterday d'oh! Anyway, we've just
reinstalled our servers with mail and automated backup and updated our
notes. They're not finalised and hence not on the web yet but you can
access them here:
https://dl.dropboxusercontent.com/u/63603283/InstallationNotes2016.9.24.pdf

Bit's of it may help.


It sure does! I quickly scanned over the pdf and the mail part is quite 
interesting for me, thanks a lot! ;)


Btw: Nice setup you got there! :)



Regards

Clive



Greets

mo

Re: Configuring Exim for mail delivery

[Mark Fletcher]

On Sat, Oct 01, 2016 at 11:01:17AM +0100, Brian wrote:
> On Sat 01 Oct 2016 at 11:06:07 +0200, mo wrote:
> 
> > First of all:
> > Thank you Liam for your help! :)
> > Thanks for the very nice and long explanation Mark! :)
> > 
> > I think i should elaborate a little more on my setup.. i guess i did not
> > make that very clear in the first place, sorry about that.
> > 
> > My network is consisting of the following systems:
> > 
> > Main PC - 192.168.23.11  (Running Debian Jessie)
> > Server  - 192.168.23.200 (Running Debian Jessie)
> > 
> > The server is always online, the PC is only half of the day on.
> > 
> > What i want to do now is the following:
> > 
> > Sending mail from my Main PC to my Server and also the other way around,
> > from the Server to my Main PC.
> > The Server should also be able to send mail to the "outside" (Meaning to
> > other SMTP servers).
> > The second requirement is optional since i dont own a domain and all this is
> > sitting locally at my home. The most important thing for me is to send and
> > receive mail from both systems in my home network.
> > I hope this made my problem a little clearer :)
> > 
> > I'm a little ashamed to say that, but i could not totally follow your
> > explanations Mark... I'm quite a newbie when it comes to SMTP.. sorry :(
> 
> Assuming the server hostname is "server".
> 
> 1. On Main PC use your editor to create /etc/exim4/hubbed_hosts. In it
>put
> 
>server: 192.168.23.200
> 
>in it and restart exim4.
> 
> 2. Send mail to user@server.
> 
> 3. You can replace 'server: 192.168.23.200' with 'server: server.local'
>if avahi-daemon is running on both machines.
> 

No colons as separators in hubbed_hosts, to my knowledge. Use spaces or tabs.

Mark

Re: Configuring Exim for mail delivery

[Mark Fletcher]

On Sat, Oct 01, 2016 at 01:39:47PM +0200, mo wrote:
> 
> 
> Am 01.10.2016 um 13:22 schrieb Brian:
> >On Sat 01 Oct 2016 at 12:36:10 +0200, mo wrote:
> >
> >>
> >>I just did that and now mailing works flawlessly :D
> >>Just one questions: Why do i need hubbed_host entries? Should it not be fine
> >>alone to make a entry in /etc/hosts for the machines i want to send mail to
> >>(I do not operate a dedicated DNS server).
> >>This is something i dont really understand...
> >
> >I'd suggest you try it and look at the logs.

Watch out, you may piss off your ISP if you repeatedly send emails it 
can't deliver. They'll make their displeasure felt by not delivering 
_any_ mails for you for a while. My suggestion is get local delivery 
working first, then turn attention to mails outside.

Mark

Re: Configuring Exim for mail delivery

[mo]

Am 01.10.2016 um 13:36 schrieb Mark Fletcher:

On Sat, Oct 01, 2016 at 11:06:07AM +0200, mo wrote:


I think i should elaborate a little more on my setup.. i guess i did not
make that very clear in the first place, sorry about that.

My network is consisting of the following systems:

Main PC - 192.168.23.11  (Running Debian Jessie)
Server  - 192.168.23.200 (Running Debian Jessie)

The server is always online, the PC is only half of the day on.

What i want to do now is the following:

Sending mail from my Main PC to my Server and also the other way around,
from the Server to my Main PC.
The Server should also be able to send mail to the "outside" (Meaning to
other SMTP servers).
The second requirement is optional since i dont own a domain and all this is
sitting locally at my home. The most important thing for me is to send and
receive mail from both systems in my home network.
I hope this made my problem a little clearer :)



Right. So you get mail going back and forth between your two machines,
server and PC, by creating and populating the hubbed_hosts file I
talked about in my previous mail, on both machines, pointing at each
other of course.


I created the hubbed_hosts file under /etc/exim4 and it now works fine, 
i can send mail from my server to my pc and vice versa :)



If you want to ping the server from the client, you should be able to do
"ping server.local" from your PC (obviously replace the actual name of
your server, which you didn't include in your mail, where I put server).
What is happening if you do that is your PC is saying "get me the
address of server.local!" and the Avahi daemon on your PC either already
knows that, or sends out a broadcast message to your network saying "is
there a server.local in the house???". The Avahi daemon running on the
server responds to that saying "yes, I'm here, and my IP address is
192.168.23.200!". The Avahi daemon on your PC responds to whatever did
the asking (ping in this case) with the required IP. Ping then requests
that packets be sent to IP address quoted. By this mechanism computers
on the same LAN can communicate with each other peer to peer without
fannying around with full-blown DNS, which is what Avahi is for. That is
installed by the Jessie installer by default as far as I can tell, so
both your machines should have it. It doesn't require any configuration,
so if you haven't touched it, it should work as I have described.
Although obviously, you have to substitute the real names for your
server and PC (but you *do* require the .local unless you have configured
Avahi to use something else)


I'm currently not using avahi as a matter of fact, but it works all fine 
without it ;)
(I have static entries in the /etc/hosts file for my server and for the 
pc - on each system of course)
I have never really worked with avahi... i kinda ask myself why do i 
need it if i can just use DNS or static entries in /etc/hosts. 
/etc/nsswitch.conf is also configured to lookup the /etc/hosts file first.
I know this question is OT, but since you mentioned avahi maybe i can 
ask you what kind of benefits avahi can offer me? :)

(I'm having a statically configured network with 4 machines)


If you used the default config of exim4 the hubbed_hosts router is set
up and waiting to be used. All you need to do to enable it is to
populate the hubbed_hosts file as I described. The other thing you need
to do is follow Liam's advice, except importantly what needs to be set
there is the "domain" of the local PC (on the local PC) or the server
(on the server) only. So the PC will accept mail for pc.local (or
whatever your pc is called) and the server for server.local (or whatever
the server is called). Then, you will be able to email yourself at the
server from the PC by sending a mail to mo@server.local, where I am
assuming your user name on the server is mo and the server's machine
name is server. Obviously you would substitute real names. And to go the
other way, from the server, you could send a mail to yourself on the PC
by mailing mo@pc.local.


I have asked that before i believe, sorry if this question shows up 
twice But why do i even need to set up hubbed_hosts?
I don't really understand why... Should exim not consider the /etc/hosts 
file to resolve the ip of my pc or server (Which i have entered there)
Also i have seen (before it worked) in the log that i get a "destination 
unreachable"... I just don't understand why exim needs to rely on the 
hubbed_hosts being set up?
(I hope you can understand what i mean, if not i will try my best to 
make it clearer :D )



Let's take a moment to go through what happens if you send a mail from
PC to server with everything set up as it should be.

On the PC you create a mail and address it to mo@server.local. Let's
imagine you use mutt to create it. And let's assume mutt is using its
default configuration to send the mail, which is to call sendmail. And,
since you have installed exim4, exim has overridden sendmail 

Re: Configuring Exim for mail delivery

[Clive Menzies]

On 01/10/16 12:39, mo wrote:



Am 01.10.2016 um 13:22 schrieb Brian:

On Sat 01 Oct 2016 at 12:36:10 +0200, mo wrote:

I just figured out how to get this working myself a week or two 
back, so

it's fresh in my mind. The key trick is the use of "hubbed hosts".


Did you follow a specific book or guide?


The manual for exim4-config_files is the first place to look.



I will look into the manual.
I also found a book about exim from O'Reilly, it's quite old (2001) 
but i guess i can get some info out of it.



Exim configuration has the concept of "routers" and "transports".
Routers basically decide what to do with a message, and transports do
it. One of the routers configured by default in the Debian exim
configuration is for "hubbed hosts". What this means, is machines
capable of sending and receiving email ("hosts" in exim speak) that 
are

on the same LAN as this machine (connected by a "hub"). Note that this
"hub" could be your local home network router, and for these purposes
machines on WiFi and machines on a wired LAN would be considered on 
the

same hub, even though that isn't strictly true. The point is that
network packets can be addressed directly between the machines, they
don't require a router in between.



As far as i do understand this is that only machines which are 
defined as
hubbed hosts can be send mail in the local LAN? Or am i 
misunderstanding

something here? :)


hubbed_hosts can send mail wherever you want. For example:

  example.com: smtp.example.com

would send mail to someone at example.com through smtp.example.com
(which could be a smarthost).



Got it, thanks ;)

In Debian, this is achieved with Avahi. This is what allows you, if 
you

have MachineA and MachineB on your network, to do for example "ping
MachineA.local" from MachineB and expect MachineA.local to be resolved
into an IP address.



I'm not a friend of avahi to be honest, i much rather ignore it :D


Let's hope your IP addresses do not change.



No changes here, static network configuration, so that should not pose 
problems. (My network only has 4 machines, so DHCP is not needed, at 
least atm i don't need it :) )



In /etc/exim4, create a file owned by root called hubbed_hosts. In the
file, each line maps a "domain" (the part after the @ sign in an email
address) to a "host" (the name of a machine on your network, as it can
be reached from this machine). Put the domain first, then a tab
character (spaces may also be OK) and then the host. So for example I
have a machine on my network called affinity, and so in the 
hubbed_hosts
file on the machine I am sitting in front of now, I have two lines, 
one

saying "affinity.localaffinity.local", and the other saying
"affinityaffinity.local" (no quotes in the file). This tells the
local exim installation that any email address with @affinity.local as
the domain should be forwarded on to a machine called affinity.local,
and any mail with @affinity as the domain should be forwarded on to a
machine called affinity.local. Exim4 will then say "Connect to
affinity.local!" with no attempt to translate that into an IP address,
and Avahi daemon will answer "that is IP address WW.XX.YY.ZZ!" to 
which

exim will say "very well, connect to WW.XX.YY.ZZ!" and the exim4 on
affinity will wake up and co-operate to deliver the mail.


I just did that and now mailing works flawlessly :D
Just one questions: Why do i need hubbed_host entries? Should it not 
be fine
alone to make a entry in /etc/hosts for the machines i want to send 
mail to

(I do not operate a dedicated DNS server).
This is something i dont really understand...


I'd suggest you try it and look at the logs.



I will try that out, exim has a pretty nice logging format i think ;)



Hi Mo

I tried to send this with a .pdf yesterday d'oh! Anyway, we've just 
reinstalled our servers with mail and automated backup and updated our 
notes. They're not finalised and hence not on the web yet but you can 
access them here:

https://dl.dropboxusercontent.com/u/63603283/InstallationNotes2016.9.24.pdf

Bit's of it may help.

Regards

Clive

--
Clive Menzies
http://freecriticalthinking.org

Re: Configuring Exim for mail delivery

[mo]

Am 01.10.2016 um 13:22 schrieb Brian:

On Sat 01 Oct 2016 at 12:36:10 +0200, mo wrote:


I just figured out how to get this working myself a week or two back, so
it's fresh in my mind. The key trick is the use of "hubbed hosts".


Did you follow a specific book or guide?


The manual for exim4-config_files is the first place to look.



I will look into the manual.
I also found a book about exim from O'Reilly, it's quite old (2001) but 
i guess i can get some info out of it.



Exim configuration has the concept of "routers" and "transports".
Routers basically decide what to do with a message, and transports do
it. One of the routers configured by default in the Debian exim
configuration is for "hubbed hosts". What this means, is machines
capable of sending and receiving email ("hosts" in exim speak) that are
on the same LAN as this machine (connected by a "hub"). Note that this
"hub" could be your local home network router, and for these purposes
machines on WiFi and machines on a wired LAN would be considered on the
same hub, even though that isn't strictly true. The point is that
network packets can be addressed directly between the machines, they
don't require a router in between.



As far as i do understand this is that only machines which are defined as
hubbed hosts can be send mail in the local LAN? Or am i misunderstanding
something here? :)


hubbed_hosts can send mail wherever you want. For example:

  example.com: smtp.example.com

would send mail to someone at example.com through smtp.example.com
(which could be a smarthost).



Got it, thanks ;)


In Debian, this is achieved with Avahi. This is what allows you, if you
have MachineA and MachineB on your network, to do for example "ping
MachineA.local" from MachineB and expect MachineA.local to be resolved
into an IP address.



I'm not a friend of avahi to be honest, i much rather ignore it :D


Let's hope your IP addresses do not change.



No changes here, static network configuration, so that should not pose 
problems. (My network only has 4 machines, so DHCP is not needed, at 
least atm i don't need it :) )



In /etc/exim4, create a file owned by root called hubbed_hosts. In the
file, each line maps a "domain" (the part after the @ sign in an email
address) to a "host" (the name of a machine on your network, as it can
be reached from this machine). Put the domain first, then a tab
character (spaces may also be OK) and then the host. So for example I
have a machine on my network called affinity, and so in the hubbed_hosts
file on the machine I am sitting in front of now, I have two lines, one
saying "affinity.localaffinity.local", and the other saying
"affinityaffinity.local" (no quotes in the file). This tells the
local exim installation that any email address with @affinity.local as
the domain should be forwarded on to a machine called affinity.local,
and any mail with @affinity as the domain should be forwarded on to a
machine called affinity.local. Exim4 will then say "Connect to
affinity.local!" with no attempt to translate that into an IP address,
and Avahi daemon will answer "that is IP address WW.XX.YY.ZZ!" to which
exim will say "very well, connect to WW.XX.YY.ZZ!" and the exim4 on
affinity will wake up and co-operate to deliver the mail.


I just did that and now mailing works flawlessly :D
Just one questions: Why do i need hubbed_host entries? Should it not be fine
alone to make a entry in /etc/hosts for the machines i want to send mail to
(I do not operate a dedicated DNS server).
This is something i dont really understand...


I'd suggest you try it and look at the logs.



I will try that out, exim has a pretty nice logging format i think ;)

Greets

mo

Re: Configuring Exim for mail delivery

[Mark Fletcher]

On Sat, Oct 01, 2016 at 11:06:07AM +0200, mo wrote:
> 
> I think i should elaborate a little more on my setup.. i guess i did not
> make that very clear in the first place, sorry about that.
> 
> My network is consisting of the following systems:
> 
> Main PC - 192.168.23.11  (Running Debian Jessie)
> Server  - 192.168.23.200 (Running Debian Jessie)
> 
> The server is always online, the PC is only half of the day on.
> 
> What i want to do now is the following:
> 
> Sending mail from my Main PC to my Server and also the other way around,
> from the Server to my Main PC.
> The Server should also be able to send mail to the "outside" (Meaning to
> other SMTP servers).
> The second requirement is optional since i dont own a domain and all this is
> sitting locally at my home. The most important thing for me is to send and
> receive mail from both systems in my home network.
> I hope this made my problem a little clearer :)
> 

Right. So you get mail going back and forth between your two machines, 
server and PC, by creating and populating the hubbed_hosts file I 
talked about in my previous mail, on both machines, pointing at each 
other of course.

If you want to ping the server from the client, you should be able to do 
"ping server.local" from your PC (obviously replace the actual name of 
your server, which you didn't include in your mail, where I put server). 
What is happening if you do that is your PC is saying "get me the 
address of server.local!" and the Avahi daemon on your PC either already 
knows that, or sends out a broadcast message to your network saying "is 
there a server.local in the house???". The Avahi daemon running on the 
server responds to that saying "yes, I'm here, and my IP address is 
192.168.23.200!". The Avahi daemon on your PC responds to whatever did 
the asking (ping in this case) with the required IP. Ping then requests 
that packets be sent to IP address quoted. By this mechanism computers 
on the same LAN can communicate with each other peer to peer without 
fannying around with full-blown DNS, which is what Avahi is for. That is 
installed by the Jessie installer by default as far as I can tell, so 
both your machines should have it. It doesn't require any configuration, 
so if you haven't touched it, it should work as I have described. 
Although obviously, you have to substitute the real names for your 
server and PC (but you *do* require the .local unless you have configured 
Avahi to use something else)

If you used the default config of exim4 the hubbed_hosts router is set 
up and waiting to be used. All you need to do to enable it is to 
populate the hubbed_hosts file as I described. The other thing you need 
to do is follow Liam's advice, except importantly what needs to be set 
there is the "domain" of the local PC (on the local PC) or the server 
(on the server) only. So the PC will accept mail for pc.local (or 
whatever your pc is called) and the server for server.local (or whatever 
the server is called). Then, you will be able to email yourself at the 
server from the PC by sending a mail to mo@server.local, where I am 
assuming your user name on the server is mo and the server's machine 
name is server. Obviously you would substitute real names. And to go the 
other way, from the server, you could send a mail to yourself on the PC 
by mailing mo@pc.local.

Let's take a moment to go through what happens if you send a mail from 
PC to server with everything set up as it should be.

On the PC you create a mail and address it to mo@server.local. Let's 
imagine you use mutt to create it. And let's assume mutt is using its 
default configuration to send the mail, which is to call sendmail. And, 
since you have installed exim4, exim has overridden sendmail to actually 
be calling exim4. So, when mutt sends a mail, exim4 running on your PC 
gets handed the mail.

The first thing it does, is say is this mail for this domain. Hmmm. I am 
pc.local. This mail is going to server.local. That ain't me. So not 
local delivery. OK, next I will try hubbed hosts. Do I have any 
hubbed_hosts? Let's look in the hubbed_hosts file. Yep, I do. Can i find 
the @server.local domain in the hubbed_hosts file? Yes, I can. Right, 
where do I send it then? Ah, I send it to a machine called server.local. 
OK... Oi! Network! Gimme the address for server.local... (this is 
where Avahi does its thing)...Thanks! Right, Connect to 192.168.23.200 
port 25!

At this point the exim4 running on your server gets a dig in the ribs, 
wakes up, and responds to the connection. The two exim4s talk to each 
other and the net result is the mail gets transferred from the exim4 
running on the PC to the exim4 running on the server.

Then the exim4 running on the server goes through the same rigmarole, 
except it finds that the mail IS addressed to a local address, so it 
goes into delivery mode and the mail finds its way into the right 
mailbox on that machine.

Now let's consider what would happen if you 

Re: Configuring Exim for mail delivery

[Brian]

On Sat 01 Oct 2016 at 12:36:10 +0200, mo wrote:

> >I just figured out how to get this working myself a week or two back, so
> >it's fresh in my mind. The key trick is the use of "hubbed hosts".
> 
> Did you follow a specific book or guide?

The manual for exim4-config_files is the first place to look.

> >Exim configuration has the concept of "routers" and "transports".
> >Routers basically decide what to do with a message, and transports do
> >it. One of the routers configured by default in the Debian exim
> >configuration is for "hubbed hosts". What this means, is machines
> >capable of sending and receiving email ("hosts" in exim speak) that are
> >on the same LAN as this machine (connected by a "hub"). Note that this
> >"hub" could be your local home network router, and for these purposes
> >machines on WiFi and machines on a wired LAN would be considered on the
> >same hub, even though that isn't strictly true. The point is that
> >network packets can be addressed directly between the machines, they
> >don't require a router in between.
> >
> 
> As far as i do understand this is that only machines which are defined as
> hubbed hosts can be send mail in the local LAN? Or am i misunderstanding
> something here? :)

hubbed_hosts can send mail wherever you want. For example:

  example.com: smtp.example.com

would send mail to someone at example.com through smtp.example.com
(which could be a smarthost).

> >In Debian, this is achieved with Avahi. This is what allows you, if you
> >have MachineA and MachineB on your network, to do for example "ping
> >MachineA.local" from MachineB and expect MachineA.local to be resolved
> >into an IP address.
> >
> 
> I'm not a friend of avahi to be honest, i much rather ignore it :D

Let's hope your IP addresses do not change.

> >In /etc/exim4, create a file owned by root called hubbed_hosts. In the
> >file, each line maps a "domain" (the part after the @ sign in an email
> >address) to a "host" (the name of a machine on your network, as it can
> >be reached from this machine). Put the domain first, then a tab
> >character (spaces may also be OK) and then the host. So for example I
> >have a machine on my network called affinity, and so in the hubbed_hosts
> >file on the machine I am sitting in front of now, I have two lines, one
> >saying "affinity.localaffinity.local", and the other saying
> >"affinityaffinity.local" (no quotes in the file). This tells the
> >local exim installation that any email address with @affinity.local as
> >the domain should be forwarded on to a machine called affinity.local,
> >and any mail with @affinity as the domain should be forwarded on to a
> >machine called affinity.local. Exim4 will then say "Connect to
> >affinity.local!" with no attempt to translate that into an IP address,
> >and Avahi daemon will answer "that is IP address WW.XX.YY.ZZ!" to which
> >exim will say "very well, connect to WW.XX.YY.ZZ!" and the exim4 on
> >affinity will wake up and co-operate to deliver the mail.
> 
> I just did that and now mailing works flawlessly :D
> Just one questions: Why do i need hubbed_host entries? Should it not be fine
> alone to make a entry in /etc/hosts for the machines i want to send mail to
> (I do not operate a dedicated DNS server).
> This is something i dont really understand...

I'd suggest you try it and look at the logs.

-- 
Brian.

Re: Configuring Exim for mail delivery

[mo]

I'll assume you have a home network and are trying to connect to send
mails between machines on that network, and additionally be able to send
email to domains outside your network.


That is right ;)


I'm also assuming that you don't have specific domains for your own
machines, so that when you send mail outside you want to use an email
provider such as gmail, or hover, etc.


Also true ;)



I just figured out how to get this working myself a week or two back, so
it's fresh in my mind. The key trick is the use of "hubbed hosts".


Did you follow a specific book or guide?


Exim configuration has the concept of "routers" and "transports".
Routers basically decide what to do with a message, and transports do
it. One of the routers configured by default in the Debian exim
configuration is for "hubbed hosts". What this means, is machines
capable of sending and receiving email ("hosts" in exim speak) that are
on the same LAN as this machine (connected by a "hub"). Note that this
"hub" could be your local home network router, and for these purposes
machines on WiFi and machines on a wired LAN would be considered on the
same hub, even though that isn't strictly true. The point is that
network packets can be addressed directly between the machines, they
don't require a router in between.



As far as i do understand this is that only machines which are defined 
as hubbed hosts can be send mail in the local LAN? Or am i 
misunderstanding something here? :)



In Debian, this is achieved with Avahi. This is what allows you, if you
have MachineA and MachineB on your network, to do for example "ping
MachineA.local" from MachineB and expect MachineA.local to be resolved
into an IP address.



I'm not a friend of avahi to be honest, i much rather ignore it :D


In /etc/exim4, create a file owned by root called hubbed_hosts. In the
file, each line maps a "domain" (the part after the @ sign in an email
address) to a "host" (the name of a machine on your network, as it can
be reached from this machine). Put the domain first, then a tab
character (spaces may also be OK) and then the host. So for example I
have a machine on my network called affinity, and so in the hubbed_hosts
file on the machine I am sitting in front of now, I have two lines, one
saying "affinity.localaffinity.local", and the other saying
"affinityaffinity.local" (no quotes in the file). This tells the
local exim installation that any email address with @affinity.local as
the domain should be forwarded on to a machine called affinity.local,
and any mail with @affinity as the domain should be forwarded on to a
machine called affinity.local. Exim4 will then say "Connect to
affinity.local!" with no attempt to translate that into an IP address,
and Avahi daemon will answer "that is IP address WW.XX.YY.ZZ!" to which
exim will say "very well, connect to WW.XX.YY.ZZ!" and the exim4 on
affinity will wake up and co-operate to deliver the mail.


I just did that and now mailing works flawlessly :D
Just one questions: Why do i need hubbed_host entries? Should it not be 
fine alone to make a entry in /etc/hosts for the machines i want to send 
mail to (I do not operate a dedicated DNS server).

This is something i dont really understand...


If the target email domain is not present in hubbed_hosts, then a
default "smarthost" configuration will fall through the hubbed hosts
router and arrive at the smarthost router, which in my case then tries
to use my mail provider to send a mail to a local machine, which is
doomed to failure because the outside provider cannot see my individual
machines on my local network.

If you really should be using the "internet" configuration, you still
need hubbed_hosts for local mails because whereas the hubbed_hosts
option just leaves it to the local network to figure out what it is
talking about, an internet-configured exim will attempt to find and send
to the target machine. To do so, it will send out a DNS request to
resolve the ip address of the target host. Avahi won't catch this, and
unless you are running a DNS server locally on your network (most people
don't, and many home network routers don't include one) that request
will go out of your network to the DNS server provided by your ISP. That
DNS server, being outside your network, won't be able to resolve your
local machine names and so won't be able to give you back an IP address
to use, unless your target machines are publicly individually visible on
the Internet, which is unlikely if this is a home configuration we are
talking about here.

So the configuration you are after is local domains specified in
hubbed_hosts, and everything else falls through to either a smarthost or
a dns-based attempt to send outside your network.

Hope that helps, let us know if you need more help.


Your explanation helped a lot ;)


Mark




Greets

mo

Re: Configuring Exim for mail delivery

[mo]

Hi Brian :)



Assuming the server hostname is "server".

1. On Main PC use your editor to create /etc/exim4/hubbed_hosts. In it
   put

   server: 192.168.23.200

   in it and restart exim4.

2. Send mail to user@server.

3. You can replace 'server: 192.168.23.200' with 'server: server.local'
   if avahi-daemon is running on both machines.



It worked perfectly
...I just found out that "mail" does not support Maildir format, but 
mutt does fine
I can now send and receive mail from and to my server. Thank you very 
much for your help! (...And for the easy step by step guide )


Thanks again

Greets
mo

Re: Configuring Exim for mail delivery

[Brian]

On Sat 01 Oct 2016 at 11:06:07 +0200, mo wrote:

> First of all:
> Thank you Liam for your help! :)
> Thanks for the very nice and long explanation Mark! :)
> 
> I think i should elaborate a little more on my setup.. i guess i did not
> make that very clear in the first place, sorry about that.
> 
> My network is consisting of the following systems:
> 
> Main PC - 192.168.23.11  (Running Debian Jessie)
> Server  - 192.168.23.200 (Running Debian Jessie)
> 
> The server is always online, the PC is only half of the day on.
> 
> What i want to do now is the following:
> 
> Sending mail from my Main PC to my Server and also the other way around,
> from the Server to my Main PC.
> The Server should also be able to send mail to the "outside" (Meaning to
> other SMTP servers).
> The second requirement is optional since i dont own a domain and all this is
> sitting locally at my home. The most important thing for me is to send and
> receive mail from both systems in my home network.
> I hope this made my problem a little clearer :)
> 
> I'm a little ashamed to say that, but i could not totally follow your
> explanations Mark... I'm quite a newbie when it comes to SMTP.. sorry :(

Assuming the server hostname is "server".

1. On Main PC use your editor to create /etc/exim4/hubbed_hosts. In it
   put

   server: 192.168.23.200

   in it and restart exim4.

2. Send mail to user@server.

3. You can replace 'server: 192.168.23.200' with 'server: server.local'
   if avahi-daemon is running on both machines.

-- 
Brian.

Re: Configuring Exim for mail delivery

[mo]

First of all:
Thank you Liam for your help! :)
Thanks for the very nice and long explanation Mark! :)

I think i should elaborate a little more on my setup.. i guess i did not 
make that very clear in the first place, sorry about that.


My network is consisting of the following systems:

Main PC - 192.168.23.11  (Running Debian Jessie)
Server  - 192.168.23.200 (Running Debian Jessie)

The server is always online, the PC is only half of the day on.

What i want to do now is the following:

Sending mail from my Main PC to my Server and also the other way around, 
from the Server to my Main PC.
The Server should also be able to send mail to the "outside" (Meaning to 
other SMTP servers).
The second requirement is optional since i dont own a domain and all 
this is sitting locally at my home. The most important thing for me is 
to send and receive mail from both systems in my home network.

I hope this made my problem a little clearer :)

I'm a little ashamed to say that, but i could not totally follow your 
explanations Mark... I'm quite a newbie when it comes to SMTP.. sorry :(


Thanks again for all your help ;)

Greets

mo

Re: Configuring Exim for mail delivery

[Mark Fletcher]

On Fri, Sep 30, 2016 at 10:22:10PM +0200, mo wrote:
> Hi fellow Debian users ;)
> I want to do the following configuration:
> Send and deliver local mails between my systems. Currently exim is
> configured as a Internet Server (dpkg-reconfigure exim4-config).
> In general i kinda ask myself how i would go about doing that?
> I want to send mail from my server to my pc and vice versa, also i want to
> be able to send mail "out" to other smtp servers.
> 

Depending on your local setup, having Exim set as an Internet server may 
not be the right answer, as Liam has already said.

I'm going to make some assumptions here and you can correct them if they 
are wrong.

I'll assume you have a home network and are trying to connect to send 
mails between machines on that network, and additionally be able to send 
email to domains outside your network.

I'm also assuming that you don't have specific domains for your own 
machines, so that when you send mail outside you want to use an email 
provider such as gmail, or hover, etc.

For most home network situations, ISPs don't like you trying to send 
email directly from your home network. They want you to use their (or at 
least SOMEONE's) smarthost. That makes it less likely they will find 
themselves accessories to spamming. Also, many mainstream destination 
email addresses will not accept mail from just any old place; if you try 
to send mail directly to them from behind your home network router, even 
if your ISP allows you to do so, the other end may reject the mail 
because they can't tell what machine it is coming from.

If my assumptions above are right, you want to use "smarthost" as the 
configuration. If I am wrong and you have your own domain and the right 
to set up mail servers in it, then you do want the "internet" setting, 
but you still want to pay attention to the rest of this message as it 
addresses local network delivery.

I just figured out how to get this working myself a week or two back, so 
it's fresh in my mind. The key trick is the use of "hubbed hosts".

Exim configuration has the concept of "routers" and "transports". 
Routers basically decide what to do with a message, and transports do 
it. One of the routers configured by default in the Debian exim 
configuration is for "hubbed hosts". What this means, is machines 
capable of sending and receiving email ("hosts" in exim speak) that are 
on the same LAN as this machine (connected by a "hub"). Note that this 
"hub" could be your local home network router, and for these purposes 
machines on WiFi and machines on a wired LAN would be considered on the 
same hub, even though that isn't strictly true. The point is that 
network packets can be addressed directly between the machines, they 
don't require a router in between.

In Debian, this is achieved with Avahi. This is what allows you, if you 
have MachineA and MachineB on your network, to do for example "ping 
MachineA.local" from MachineB and expect MachineA.local to be resolved 
into an IP address.

As far as I can tell, Avahi is installed by default when you install a 
new Debian installation. I don't know how long that has been true, but 
my experience is that it is now.

In /etc/exim4, create a file owned by root called hubbed_hosts. In the 
file, each line maps a "domain" (the part after the @ sign in an email 
address) to a "host" (the name of a machine on your network, as it can 
be reached from this machine). Put the domain first, then a tab 
character (spaces may also be OK) and then the host. So for example I 
have a machine on my network called affinity, and so in the hubbed_hosts 
file on the machine I am sitting in front of now, I have two lines, one 
saying "affinity.localaffinity.local", and the other saying 
"affinityaffinity.local" (no quotes in the file). This tells the 
local exim installation that any email address with @affinity.local as 
the domain should be forwarded on to a machine called affinity.local, 
and any mail with @affinity as the domain should be forwarded on to a 
machine called affinity.local. Exim4 will then say "Connect to 
affinity.local!" with no attempt to translate that into an IP address, 
and Avahi daemon will answer "that is IP address WW.XX.YY.ZZ!" to which 
exim will say "very well, connect to WW.XX.YY.ZZ!" and the exim4 on 
affinity will wake up and co-operate to deliver the mail.

If the target email domain is not present in hubbed_hosts, then a 
default "smarthost" configuration will fall through the hubbed hosts 
router and arrive at the smarthost router, which in my case then tries 
to use my mail provider to send a mail to a local machine, which is 
doomed to failure because the outside provider cannot see my individual 
machines on my local network.

If you really should be using the "internet" configuration, you still 
need hubbed_hosts for local mails because whereas the hubbed_hosts 
option just leaves it to the local network to figure out what it is 
talking about, an internet-con

Re: Configuring Exim for mail delivery

[Liam O'Toole]

On 2016-09-30, mo  wrote:
> Hi fellow Debian users ;)
>
> First off some information. (both, the pc and the server run Debian Jessie):
>
> Distributor ID:   Debian
> Description:  Debian GNU/Linux 8.6 (jessie)
> Release:  8.6
> Codename: jessie
>
> Exim:
> ii  exim44.84.2-2+deb8u1 
>   all  metapackage to ease Exim MTA (v4) installation
> ii  exim4-base   4.84.2-2+deb8u1 
>   amd64support files for all Exim MTA (v4) packages
> ii  exim4-config 4.84.2-2+deb8u1 
>   all  configuration for the Exim MTA (v4)
> ii  exim4-daemon-light   4.84.2-2+deb8u1 
>   amd64lightweight Exim MTA (v4) daemon
>
>
> I'm currently playing around with exim4... and to be honest i'm a little 
> lost here.
> I want to do the following configuration:
> Send and deliver local mails between my systems. Currently exim is 
> configured as a Internet Server (dpkg-reconfigure exim4-config).
> In general i kinda ask myself how i would go about doing that?
> I want to send mail from my server to my pc and vice versa, also i want 
> to be able to send mail "out" to other smtp servers.
>
> Is Exim here the right choice? (I do think so at least)
>
> To be honest i never played with a smtp server before... so my knowledge 
> is a bit foggy :P (Don't worry, i know what a MTA, MUA etc is)
>
> Thank you all in advance for your help ;)
>
> Btw: I will of course provide more information if needed ;)
>
> Greets
>
> mo
>
>

If you run 'dpkg-reconfigure exim4-config' again, you will see a
question about "Other destinations for which mail is accepted". Here you
would enter something like '*.yourdomain.com', where your PC and
server belong to that domain. In that way exim4 will deliver email
directly to those hosts rather than relaying outside your network.

Regarding your second requirement, you probably want to choose the
second option on the first screen, ie, "mail sent by smarthost; received
via SMTP or fetchmail". You would then enter the name of your ISP's SMTP
when prompted later for the name of the smarthost.

-- 

Liam

Configuring Exim for mail delivery

[mo]

Hi fellow Debian users ;)

First off some information. (both, the pc and the server run Debian Jessie):

Distributor ID: Debian
Description:Debian GNU/Linux 8.6 (jessie)
Release:8.6
Codename:   jessie

Exim:
ii  exim44.84.2-2+deb8u1 
 all  metapackage to ease Exim MTA (v4) installation
ii  exim4-base   4.84.2-2+deb8u1 
 amd64support files for all Exim MTA (v4) packages
ii  exim4-config 4.84.2-2+deb8u1 
 all  configuration for the Exim MTA (v4)
ii  exim4-daemon-light   4.84.2-2+deb8u1 
 amd64lightweight Exim MTA (v4) daemon



I'm currently playing around with exim4... and to be honest i'm a little 
lost here.

I want to do the following configuration:
Send and deliver local mails between my systems. Currently exim is 
configured as a Internet Server (dpkg-reconfigure exim4-config).

In general i kinda ask myself how i would go about doing that?
I want to send mail from my server to my pc and vice versa, also i want 
to be able to send mail "out" to other smtp servers.


Is Exim here the right choice? (I do think so at least)

To be honest i never played with a smtp server before... so my knowledge 
is a bit foggy :P (Don't worry, i know what a MTA, MUA etc is)


Thank you all in advance for your help ;)

Btw: I will of course provide more information if needed ;)

Greets

mo

Re: SMTP-Error 451 while using smarthost for mail delivery

[deloptes]

b1 wrote:

> On Thu, 2010-04-22 at 17:28 +, Camaleón wrote:
>> On Thu, 22 Apr 2010 16:20:01 +0200, b1 wrote:
>> 
>> > Currently I am trying to set up a Debian Lenny Server, but I am stuck
>> > at mail delivery. The server I am trying to set up, has no FQDN, so I
>> > used my ISP-Mailserver as a smarthost (I enabled the proper SMTP
>> > authentication in exim4).
>> > This setup worked a few days, before I suddenly received 451 errors. At
>> > first I thought it to be a problem with Exim4, so I switched to
>> > postfix. But postfix also gives me the 451 error:
>> > 
>> > Apr 22 15:53:31 openshoolproxy postfix/smtp[24368]: 413CF26EF9:
>> > to=, orig_to=,
>> > relay=smtp.strato.com[81.169.145.132]:25, delay=2137,
>> > delays=2136/0.05/0.33/0.12, dsn=4.0.0, status=deferred (host
>> > smtp.strato.com[81.169.145.132] said: 451 Local Error (in reply to end
>> > of DATA command))
>> 
>> Mmm, the remote server (81.169.145.132) has encountered some kind of
>> error while sending "data" command.
>> 
>> But, are you in control of Strato's server? If no, then you can only
>> contact them and request more info about this error. If the problem is on
>> their side, you can only "guess".
>>  
>> (...)
>> 
>> > telnet smtp.strato.de 25
>> > Trying 81.169.145.133...
>> > Connected to smtp.strato.de.
>> > Escape character is '^]'.
>> > 220 smtp.passthru
>>   ^
>> 
>> (...)
>> 
>> > 451 Local Error
>> 
>> Look that "smtp.passthru" string, it seems some kind of proxy/redirector
>> service.
>> 
>> > Very odd. After this fail I tried the same procedure from my arch linux
>> > box at home. It succeeded:
>> > 
>> > 
>> > 
>> > 
>> > telnet smtp.strato.com 25
>> > Trying 81.169.145.132...
>> > Connected to smtp.strato.com.
>> > Escape character is '^]'.
>> > 220 post.strato.de [fruni mo3] ESMTP RZmta 23.0 ready; Thu, 22 Apr 2010
>> > 15:55:55 +0200 (MEST)
>> 
>> (...)
>> 
>> > 250 queued as g0718am3MD7AJw
>> 
>> That server response looks more "normal". No proxy between you and smtp
>> server.
>> 
>> (...)
>> 
>> If available, try to send an e-mail using a secure channel (SSL/TLS
>> 465/587 port) and check if that works. The idea behind this is to bypass
>> the proxy server on their side altough I'm not sure this will work :-/
>> 
>> Greetings,
>> 
>> --
>> Camaleón
>> 
>> 
> 
> 
> Hey thanks camaleon
> 
> You pointed me at the right direction with your passthru hint. We had a
> proxy on our net, through which the smtp-messages were going. This proxy
> had a virus scanner, which caused the problem. After disabling the
> scanner everything works fine.
> 
> Thank you
> 
> Benedikt
> 
> 
> 

if you have been using amavis or am,amavis+clamav be aware that support for
older clamav was thrown away, so it's not working very well. It was
blocking my email for some time.

regards


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/hqubp3$u6...@dough.gmane.org

Re: SMTP-Error 451 while using smarthost for mail delivery

[b1]

On Thu, 2010-04-22 at 17:28 +, Camaleón wrote:
> On Thu, 22 Apr 2010 16:20:01 +0200, b1 wrote:
> 
> > Currently I am trying to set up a Debian Lenny Server, but I am stuck at
> > mail delivery. The server I am trying to set up, has no FQDN, so I used
> > my ISP-Mailserver as a smarthost (I enabled the proper SMTP
> > authentication in exim4).
> > This setup worked a few days, before I suddenly received 451 errors. At
> > first I thought it to be a problem with Exim4, so I switched to postfix.
> > But postfix also gives me the 451 error:
> > 
> > Apr 22 15:53:31 openshoolproxy postfix/smtp[24368]: 413CF26EF9:
> > to=, orig_to=,
> > relay=smtp.strato.com[81.169.145.132]:25, delay=2137,
> > delays=2136/0.05/0.33/0.12, dsn=4.0.0, status=deferred (host
> > smtp.strato.com[81.169.145.132] said: 451 Local Error (in reply to end
> > of DATA command))
> 
> Mmm, the remote server (81.169.145.132) has encountered some kind of 
> error while sending "data" command.
> 
> But, are you in control of Strato's server? If no, then you can only 
> contact them and request more info about this error. If the problem is on 
> their side, you can only "guess".
>  
> (...)
> 
> > telnet smtp.strato.de 25
> > Trying 81.169.145.133...
> > Connected to smtp.strato.de.
> > Escape character is '^]'.
> > 220 smtp.passthru
>   ^
> 
> (...)
> 
> > 451 Local Error
> 
> Look that "smtp.passthru" string, it seems some kind of proxy/redirector 
> service.
> 
> > Very odd. After this fail I tried the same procedure from my arch linux
> > box at home. It succeeded:
> > 
> > 
> > 
> > 
> > telnet smtp.strato.com 25
> > Trying 81.169.145.132...
> > Connected to smtp.strato.com.
> > Escape character is '^]'.
> > 220 post.strato.de [fruni mo3] ESMTP RZmta 23.0 ready; Thu, 22 Apr 2010
> > 15:55:55 +0200 (MEST)
> 
> (...)
> 
> > 250 queued as g0718am3MD7AJw
> 
> That server response looks more "normal". No proxy between you and smtp 
> server.
> 
> (...)
> 
> If available, try to send an e-mail using a secure channel (SSL/TLS 
> 465/587 port) and check if that works. The idea behind this is to bypass 
> the proxy server on their side altough I'm not sure this will work :-/
> 
> Greetings,
> 
> -- 
> Camaleón
> 
> 


Hey thanks camaleon

You pointed me at the right direction with your passthru hint. We had a
proxy on our net, through which the smtp-messages were going. This proxy
had a virus scanner, which caused the problem. After disabling the
scanner everything works fine.

Thank you

Benedikt



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1272052688.3395.1.ca...@localhost.localdomain

Re: SMTP-Error 451 while using smarthost for mail delivery

[Camaleón]

On Thu, 22 Apr 2010 16:20:01 +0200, b1 wrote:

> Currently I am trying to set up a Debian Lenny Server, but I am stuck at
> mail delivery. The server I am trying to set up, has no FQDN, so I used
> my ISP-Mailserver as a smarthost (I enabled the proper SMTP
> authentication in exim4).
> This setup worked a few days, before I suddenly received 451 errors. At
> first I thought it to be a problem with Exim4, so I switched to postfix.
> But postfix also gives me the 451 error:
> 
> Apr 22 15:53:31 openshoolproxy postfix/smtp[24368]: 413CF26EF9:
> to=, orig_to=,
> relay=smtp.strato.com[81.169.145.132]:25, delay=2137,
> delays=2136/0.05/0.33/0.12, dsn=4.0.0, status=deferred (host
> smtp.strato.com[81.169.145.132] said: 451 Local Error (in reply to end
> of DATA command))

Mmm, the remote server (81.169.145.132) has encountered some kind of 
error while sending "data" command.

But, are you in control of Strato's server? If no, then you can only 
contact them and request more info about this error. If the problem is on 
their side, you can only "guess".
 
(...)

> telnet smtp.strato.de 25
> Trying 81.169.145.133...
> Connected to smtp.strato.de.
> Escape character is '^]'.
> 220 smtp.passthru
  ^

(...)

> 451 Local Error

Look that "smtp.passthru" string, it seems some kind of proxy/redirector 
service.

> Very odd. After this fail I tried the same procedure from my arch linux
> box at home. It succeeded:
> 
> 
> 
> 
> telnet smtp.strato.com 25
> Trying 81.169.145.132...
> Connected to smtp.strato.com.
> Escape character is '^]'.
> 220 post.strato.de [fruni mo3] ESMTP RZmta 23.0 ready; Thu, 22 Apr 2010
> 15:55:55 +0200 (MEST)

(...)

> 250 queued as g0718am3MD7AJw

That server response looks more "normal". No proxy between you and smtp 
server.

(...)

If available, try to send an e-mail using a secure channel (SSL/TLS 
465/587 port) and check if that works. The idea behind this is to bypass 
the proxy server on their side altough I'm not sure this will work :-/

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2010.04.22.17.28...@gmail.com

Re: SMTP-Error 451 while using smarthost for mail delivery

[b1]

Hi Sjoerd

Thank you for your answer.
I just logged onto the Debian machine (per ssh) and tried it again.
Unfortunately it failed again. As before it gave the 451 Local Error.


On Thu, 2010-04-22 at 16:24 +0200, Sjoerd Hardeman wrote:
> b1 schreef:
> > This looks very strange to me. Independently from my mailserver the
> > telnet command should have succeeded on both machines. But it failed on
> > my debian box. What could be wrong? Is this a problem of my setup, or is
> > my ISP blocking something?
> Did you try your Debian machine again? It might be a temporary problem 
> which was solved during your trip home to try it on the other computer.
> 
> Sjoerd
> 



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1271950330.11753.22.ca...@localhost.localdomain

Re: SMTP-Error 451 while using smarthost for mail delivery

[Sjoerd Hardeman]

b1 schreef:

This looks very strange to me. Independently from my mailserver the
telnet command should have succeeded on both machines. But it failed on
my debian box. What could be wrong? Is this a problem of my setup, or is
my ISP blocking something?
Did you try your Debian machine again? It might be a temporary problem 
which was solved during your trip home to try it on the other computer.


Sjoerd



signature.asc
Description: OpenPGP digital signature

SMTP-Error 451 while using smarthost for mail delivery

[b1]

Hello alltogether

Currently I am trying to set up a Debian Lenny Server, but I am stuck at
mail delivery. The server I am trying to set up, has no FQDN, so I used
my ISP-Mailserver as a smarthost (I enabled the proper SMTP
authentication in exim4).
This setup worked a few days, before I suddenly received 451 errors.
At first I thought it to be a problem with Exim4, so I switched to
postfix. But postfix also gives me the 451 error:

Apr 22 15:53:31 openshoolproxy postfix/smtp[24368]: 413CF26EF9:
to=, orig_to=,
relay=smtp.strato.com[81.169.145.132]:25, delay=2137,
delays=2136/0.05/0.33/0.12, dsn=4.0.0, status=deferred (host
smtp.strato.com[81.169.145.132] said: 451 Local Error (in reply to end
of DATA command))

To further troubleshoot my problem I used telnet to connect to
smtp.strato.com and to send a mail manually.

This is what I did:

telnet smtp.strato.de 25
Trying 81.169.145.133...
Connected to smtp.strato.de.
Escape character is '^]'.
220 smtp.passthru
EHLO openshoolproxy
250-smtp.passthru
250-ENHANCEDSTATUSCODES
250-8BITMIME
250-DELIVERBY
250-SIZE 104857600
250-AUTH PLAIN LOGIN CRAM-MD5
250 HELP
AUTH LOGIN
334 VXNlcm5hbWU6
d2Vic2VydmljZUBiMW9ubGluZS5kZQ==
334 UGFzc3dvcmQ6
MYPASSWORD_IN_BASE64
235 2.0.0 OK Authenticated
mail from: webserv...@b1online.de
250 2.1.0  Sender ok
rcpt to: bened...@b1online.de
250 2.1.5  Recipient ok
DATA
354 Start mail input; end with .
test
.
451 Local Error




Very odd. After this fail I tried the same procedure from my arch linux
box at home. It succeeded:




telnet smtp.strato.com 25
Trying 81.169.145.132...
Connected to smtp.strato.com.
Escape character is '^]'.
220 post.strato.de [fruni mo3] ESMTP RZmta 23.0 ready; Thu, 22 Apr 2010
15:55:55 +0200 (MEST)
EHLO openshoolproxy
250-post.strato.de [fruni mo3] greets 79.230.91.82
250-ENHANCEDSTATUSCODES
250-8BITMIME
250-PIPELINING
250-DELIVERBY
250-SIZE 104857600
250-AUTH PLAIN LOGIN CRAM-MD5
250-STARTTLS
250 HELP
AUTH LOGIN
334 VXNlcm5hbWU6
d2Vic2VydmljZUBiMW9ubGluZS5kZQ==
334 UGFzc3dvcmQ6
MYPASSWORD_IN_BASE64
235 2.0.0 OK Authenticated
mail from: webserv...@b1online.de
250 2.1.0  Sender ok
rcpt to: bened...@b1online.de
250 2.1.5  Recipient ok
DATA
354 Enter data for mail with id g0718am3MD7AJw
test mich
.
250 queued as g0718am3MD7AJw


This looks very strange to me. Independently from my mailserver the
telnet command should have succeeded on both machines. But it failed on
my debian box. What could be wrong? Is this a problem of my setup, or is
my ISP blocking something?

Thanks in advance

Benedikt




-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1271946001.11753.18.ca...@localhost.localdomain

Re: Mail Delivery (failure [EMAIL PROTECTED])

[info]

From: [EMAIL PROTECTED]
Subject: Autoresponder

Sehr geehrter Absender,

vielen Dank für Ihre Mail an [EMAIL PROTECTED] Wir werden sie schnellstmöglich 
an den zuständigen Kollegen weiterleiten.

Sollten Sie jedoch zu einem unserer Produkte technische oder inhaltliche Fragen 
haben, wenden Sie sich bitte an unsere kompetente Support-Hotline:

Tel. 0900 1 / 40 00 43  (0,99 € / Minute aus dem deutschen Festnetz)

Wir haben uns zu dieser Lösung entschlossen, um Ihnen eine schnelle und 
qualifizierte Hilfe bei Problemen mit unseren Produkten anzubieten. Leider ist 
in 99 Prozent aller Fälle das PC-System des Kunden als Ursache des Problems zu 
nennen und nicht das Produkt an sich. Bitte haben Sie daher Verständnis, dass 
wir uns zu dieser Lösung entschlossen haben. 

Mit freundlichen Grüßen

Ihr rondomedia-Team




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: mail delivery

[Csanyi Pal]

On Mon, May 29, 2006 at 12:17:42PM -0400, Roberto C. Sanchez wrote:
> Csanyi Pal wrote:
> > 
> >>What are the contents of /etc/mailname?  Does exim use it?
> > 
> > The contents of /etc/mailname is: 
> > 
> > csanyipal.info 
> > 
> > How can I know does exim use it?
> > 
> Obviously, Exim is not using it.  On my system, /etc/mailname contains
> my fully qualified domain name.  However, I also use the myhostname
> option in Postfix's main.cf.  I am not sure which is having th edesired
> effect.  I don't use Exim so I don't know how it works, but the
> following article may have some helpful info:
> 
> http://www.trekweb.com/~jasonb/articles/exim4_courier/exim4.html

I asked on pkg-exim4-users list about this and get a link that help me 
to solve this problem. The link is:
http://wiki.debian.org/PkgExim4UserFAQ#head-48c5470f61731b8daae30fa0d7ef8dc175d92f07

In my case, when I installed Debian Sarge, then I give the hostname 
"debian-csp" to my system.

After a year I register the domain csanyipal.info and start to use public 
IP address but don't change my hostname from debian-csp to csanyipal.info. 

Exim4 use hostname of the system, so when I changed it to my registered 
FQDN, mail delivery become successful. (I restarted the system because I 
don't know other way how to change the uname -a out.)

-- 
Regards, Csányi Paul
http://www.ektf.hu/~Csanyi.Pal (Up to now, it is in Hungarian only.)
http://csanyipal.info/moodle  <<<---  Moodle - Course Management System
http://csanyipal.info:81  <<<---  sTeam - Cooperative Learning


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: mail delivery

[Felix C. Stegerman]

* Csanyi Pal <[EMAIL PROTECTED]> [2006-05-29 18:01]:
> I try to send a mail to Roberto but get the following error message:
>
> This message was created automatically by mail delivery software.
> A message that you sent could not be delivered to one or more of its
> recipients. This is a permanent error. The following address(es)
> failed:
>
>   [EMAIL PROTECTED] SMTP error from remote mailer after
>   RCPT TO:<[EMAIL PROTECTED]>: host
>   santiago.familiasanchez.net [66.93.22.254]: 504 : Helo
>   command rejected: need fully-qualified hostname
>
> I use exim4 on my Debian system with exim4-daemon-heavy.

I use exim4-deamon-light, but I had a similar problem a while ago. I
solved it by adding
  primary_hostname = my.host.name
to /etc/exim4/exim4.conf.template.


- Felix

-- 
Felix C. Stegerman <[EMAIL PROTECTED]>  http://obfusk.net
~ "Any sufficiently advanced bug is indistinguishable from a feature."
~   -- R. Kulawiec
~ vim: set ft=mail tw=70 sw=2 sts=2 et:


pgpkRtVydX81W.pgp
Description: PGP signature

Re: mail delivery

[Roberto C. Sanchez]

Csanyi Pal wrote:
> 
>>What are the contents of /etc/mailname?  Does exim use it?
> 
> 
> The contents of /etc/mailname is: 
> 
> csanyipal.info 
> 
> 
> How can I know does exim use it?
> 
Obviously, Exim is not using it.  On my system, /etc/mailname contains
my fully qualified domain name.  However, I also use the myhostname
option in Postfix's main.cf.  I am not sure which is having th edesired
effect.  I don't use Exim so I don't know how it works, but the
following article may have some helpful info:

http://www.trekweb.com/~jasonb/articles/exim4_courier/exim4.html

-Roberto

-- 
Roberto C. Sanchez
http://familiasanchez.net/~roberto


signature.asc
Description: OpenPGP digital signature

Re: mail delivery

[Csanyi Pal]

On Mon, May 29, 2006 at 06:11:15PM +0200, Csanyi Pal wrote:
> On Mon, May 29, 2006 at 12:05:12PM -0400, Roberto C. Sanchez wrote:
> > Csanyi Pal wrote:
> > > 
> > > I try to send a mail to Roberto but get the following error message:
> > > 
> > > This message was created automatically by mail delivery software.
> > > 
> > > A message that you sent could not be delivered to one or more of its
> > > recipients. This is a permanent error. The following address(es) 
> > > failed:
> > > 
> > >   [EMAIL PROTECTED]
> > > SMTP error from remote mailer after RCPT 
> > > TO:<[EMAIL PROTECTED]>:
> > > host santiago.familiasanchez.net [66.93.22.254]:
> > > 504 : Helo command rejected: need fully-qualified hostname
> > > 
> > > I use exim4 on my Debian system with exim4-daemon-heavy.
> > > 
> > > How can I solve this problem?
> 
> > What are the contents of /etc/mailname?  Does exim use it?
> 
> The contents of /etc/mailname is: 
> 
> csanyipal.info 

csanyipal.info is my domain name:

host csanyipal.info
csanyipal.info has address 85.222.164.136

> How can I know does exim use it?

-- 
Regards, Csányi Paul
http://www.ektf.hu/~Csanyi.Pal (Up to now, it is in Hungarian only.)
http://csanyipal.info/moodle  <<<---  Moodle - Course Management System
http://csanyipal.info:81  <<<---  sTeam - Cooperative Learning


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: mail delivery

[Csanyi Pal]

On Mon, May 29, 2006 at 12:05:12PM -0400, Roberto C. Sanchez wrote:
> Csanyi Pal wrote:
> > 
> > I try to send a mail to Roberto but get the following error message:
> > 
> > This message was created automatically by mail delivery software.
> > 
> > A message that you sent could not be delivered to one or more of its
> > recipients. This is a permanent error. The following address(es) 
> > failed:
> > 
> >   [EMAIL PROTECTED]
> > SMTP error from remote mailer after RCPT 
> > TO:<[EMAIL PROTECTED]>:
> > host santiago.familiasanchez.net [66.93.22.254]:
> > 504 : Helo command rejected: need fully-qualified hostname
> > 
> > I use exim4 on my Debian system with exim4-daemon-heavy.
> > 
> > How can I solve this problem?

> What are the contents of /etc/mailname?  Does exim use it?

The contents of /etc/mailname is: 

csanyipal.info 


How can I know does exim use it?

-- 
Regards, Csányi Paul
http://www.ektf.hu/~Csanyi.Pal (Up to now, it is in Hungarian only.)
http://csanyipal.info/moodle  <<<---  Moodle - Course Management System
http://csanyipal.info:81  <<<---  sTeam - Cooperative Learning


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: mail delivery

[Roberto C. Sanchez]

Csanyi Pal wrote:
> Hello!
> 
> I try to send a mail to Roberto but get the following error message:
> 
> This message was created automatically by mail delivery software.
> 
> A message that you sent could not be delivered to one or more of its
> recipients. This is a permanent error. The following address(es) 
> failed:
> 
>   [EMAIL PROTECTED]
> SMTP error from remote mailer after RCPT 
> TO:<[EMAIL PROTECTED]>:
> host santiago.familiasanchez.net [66.93.22.254]:
> 504 : Helo command rejected: need fully-qualified hostname
> 
> I use exim4 on my Debian system with exim4-daemon-heavy.
> 
> How can I solve this problem?
> 
> Thanks for any advice!
> 

What are the contents of /etc/mailname?  Does exim use it?

-Roberto

-- 
Roberto C. Sanchez
http://familiasanchez.net/~roberto


signature.asc
Description: OpenPGP digital signature

mail delivery

[Csanyi Pal]

Hello!

I try to send a mail to Roberto but get the following error message:

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) 
failed:

  [EMAIL PROTECTED]
SMTP error from remote mailer after RCPT 
TO:<[EMAIL PROTECTED]>:
host santiago.familiasanchez.net [66.93.22.254]:
504 : Helo command rejected: need fully-qualified hostname

I use exim4 on my Debian system with exim4-daemon-heavy.

How can I solve this problem?

Thanks for any advice!

-- 
Regards, Csányi Paul
http://www.ektf.hu/~Csanyi.Pal (Up to now, it is in Hungarian only.)
http://csanyipal.info/moodle  <<<---  Moodle - Course Management System
http://csanyipal.info:81  <<<---  sTeam - Cooperative Learning


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Mail Delivery (failure [EMAIL PROTECTED])

[feedback]

Thank you for contacting Action on Gilbert's Syndrome.  

I run the organisation in my spare time and so I may not be able to respond to 
you immediately, and beg your patience. I'll be in touch when I can, and in the 
mean time, take care, 
best wishes,
Adina, 
Director.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Qmail redundant mail delivery

[Jay Zach]

Jay Zach wrote:
> Jay Zach wrote:
> 
>>For some reason I keep getting multiple messages of the same message to my
>>inbox.  Qmail redelivers all messages multiple times, like it thinks that it
>>doesn't deliver them, even though it does.  I play around with it and change
>>permissions, and restart qmail, and it seems to start working, then the next 
>>day
>>it starts all over again.  I have dovecot mucking around in the same Maildir
>>directory, so that's a possible source of a conflict I suppose.   Any ideas
>>would be greatly appreciated, as this is starting to drive me nuts! (yes I
>>created the Maildir with the maildirmake command) Thanks
>>
> 
> 
> 
> Never mind, I just did an apt-get upgrade and it seems to be working now.
> Not sure which of the following packages might have helped, maybe gcc ??
> 
> 
>  apt apt-move apt-utils cpp-4.0 debconf debconf-i18n dhcp-client discover1
> findutils gcc-4.0 gcc-4.0-base libdiscover1 libgcc1 libhtml-parser-perl
>   libkrb53 libsmbclient libstdc++6 libsysfs1 libxslt1.1 make net-tools
> python2.3-apt samba-doc setserial ucf whois zsh
> 
> 


Actually it started happening again.  That's why it's driving me crazy  :)   I
keep thinking it is fixed when I do something, then it starts all over.  Here is
the error from mail.info again:



Dec  9 06:38:43 BBM qmail: 1134128323.103503 starting delivery 435: msg 304103
to local [EMAIL PROTECTED]
Dec  9 06:38:43 BBM qmail: 1134128323.104656 status: local 1/10 remote 0/20
Dec  9 06:38:43 BBM qmail: 1134128323.218914 delivery 435: deferral:
Temporary_error_on_maildir_delivery._(#4.
3.0)/
Dec  9 06:38:43 BBM qmail: 1134128323.219133 status: local 0/10 remote 0/20
Dec  9 06:40:44 BBM qmail: 1134128444.201486 starting delivery 436: msg 304103
to local [EMAIL PROTECTED]
Dec  9 06:40:44 BBM qmail: 1134128444.201750 status: local 1/10 remote 0/20
Dec  9 06:40:44 BBM qmail: 1134128444.321242 delivery 436: deferral:
Temporary_error_on_maildir_delivery._(#4.
3.0)/
Dec  9 06:40:44 BBM qmail: 1134128444.321456 status: local 0/10 remote 0/20




Any help would be GREATLLY appreciated  :)


-- 


"The way of the world is to praise dead saints and prosecute live ones."
 -- Nathaniel Howe

Friday Dec 09, 2005




begin:vcard
fn:Jay Zach
n:Zach;Jay
org:CBI;IS
adr;dom:;;1500 N. Ritter;Indianapolis;IN
email;internet:[EMAIL PROTECTED]
title:NT Administrator
tel;work:(317) 355
tel;cell:(317) 339-3525
x-mozilla-html:FALSE
url:http://www.ecommunity.com
version:2.1
end:vcard

Re: Qmail redundant mail delivery

[Jay Zach]

Jay Zach wrote:
> For some reason I keep getting multiple messages of the same message to my
> inbox.  Qmail redelivers all messages multiple times, like it thinks that it
> doesn't deliver them, even though it does.  I play around with it and change
> permissions, and restart qmail, and it seems to start working, then the next 
> day
> it starts all over again.  I have dovecot mucking around in the same Maildir
> directory, so that's a possible source of a conflict I suppose.   Any ideas
> would be greatly appreciated, as this is starting to drive me nuts! (yes I
> created the Maildir with the maildirmake command) Thanks
> 


Never mind, I just did an apt-get upgrade and it seems to be working now.
Not sure which of the following packages might have helped, maybe gcc ??


 apt apt-move apt-utils cpp-4.0 debconf debconf-i18n dhcp-client discover1
findutils gcc-4.0 gcc-4.0-base libdiscover1 libgcc1 libhtml-parser-perl
  libkrb53 libsmbclient libstdc++6 libsysfs1 libxslt1.1 make net-tools
python2.3-apt samba-doc setserial ucf whois zsh


-- 


BOFH excuse #346:

Your/our computer(s) had suffered a memory leak, and we are waiting for them to
be topped up.

Wednesday Dec 07, 2005




begin:vcard
fn:Jay Zach
n:Zach;Jay
org:CBI;IS
adr;dom:;;1500 N. Ritter;Indianapolis;IN
email;internet:[EMAIL PROTECTED]
title:NT Administrator
tel;work:(317) 355
tel;cell:(317) 339-3525
x-mozilla-html:FALSE
url:http://www.ecommunity.com
version:2.1
end:vcard

Qmail redundant mail delivery

[Jay Zach]

For some reason I keep getting multiple messages of the same message to my
inbox.  Qmail redelivers all messages multiple times, like it thinks that it
doesn't deliver them, even though it does.  I play around with it and change
permissions, and restart qmail, and it seems to start working, then the next day
it starts all over again.  I have dovecot mucking around in the same Maildir
directory, so that's a possible source of a conflict I suppose.   Any ideas
would be greatly appreciated, as this is starting to drive me nuts! (yes I
created the Maildir with the maildirmake command) Thanks

This is what fills up my mail.info file when it is occuring:

Dec  7 13:21:53 BBM qmail: 1133979713.981459 starting delivery 289: msg 304103
to local [EMAIL PROTECTED]
Dec  7 13:21:53 BBM qmail: 1133979713.981716 status: local 1/10 remote 0/20
Dec  7 13:21:54 BBM qmail: 1133979714.095174 delivery 289: deferral:
Temporary_error_on_maildir_delivery._(#4.3.0)/
Dec  7 13:21:54 BBM qmail: 1133979714.095392 status: local 0/10 remote 0/20


I've changed all permissions on my Maildir so they seem to match all other users
permissions (who don't seem to be having the problem)


BBM:/home/user1/Maildir# ls -lah
total 228K
drwx--   26 user1 users  4.0K Dec  7 14:16 .
drwx--  102 user1 users  8.0K Nov 29 15:53 ..
drwx--5 user1 users  4.0K Dec  1 22:38 .INBOX.FWC
drwx--5 user1 users  4.0K Dec  7 09:08 .INBOX.Family
drwx--5 user1 users  4.0K Dec  2 14:52 .INBOX.Friends
drwx--5 user1 users  4.0K Nov  9 16:27 .INBOX.Games
drwx--5 user1 users  4.0K Dec  1 22:38 .INBOX.Games.Chess
drwx--5 user1 users  4.0K Nov  9 16:21 .INBOX.Games.Earth
drwx--5 user1 users  4.0K Dec  1 22:38 .INBOX.Games.Earth.MKR
drwx--5 user1 users  4.0K Dec  1 22:38 .INBOX.Genealogy
drwx--5 user1 users  4.0K Dec  1 22:38 .INBOX.Jokes
drwx--5 user1 users  4.0K Dec  3 16:58 .INBOX.KeeperStuff
drwx--5 user1 users  4.0K Nov  9 16:21 .INBOX.Masons
drwx--5 user1 users  4.0K Dec  7 14:00 .INBOX.System Messages
drwx--5 user1 users  4.0K Dec  7 13:19 .INBOX.Tips&-Tricks
drwx--5 user1 users  4.0K Nov  9 16:21 .INBOX.Work
drwx--5 user1 users  4.0K Dec  6 11:46 .Junk
drwx--5 user1 users  4.0K Dec  6 11:44 .Sent
drwx--5 user1 users  4.0K Dec  7 14:16 .Trash
-rwx--1 user1 users 0 Oct 24 11:24 .qmail-default
drwx--5 user1 users  4.0K Oct 24 13:26 OUT
drwx--2 user1 users  8.0K Dec  7 14:16 cur
-rw---1 user1 users17 Dec  5 21:24 dovecot-keywords
-rw---1 user1 admins 2.5K Dec  7 14:02 dovecot-uidlist
-rw---1 user1 users  1.4K Dec  7 14:02 dovecot.index
-rw---1 user1 users   50K Dec  7 14:16 dovecot.index.cache
-rw---1 user1 users   42K Dec  7 14:16 dovecot.index.log
drwx--2 user1 users  4.0K Oct 24 20:33 friends
drwx--2 user1 users  4.0K Dec  7 14:02 new
-rwx--1 user1 users   240 Nov 25 10:45 subscriptions
drwx--2 user1 users  4.0K Dec  7 14:02 tmp


-- 


BOFH excuse #346:

Your/our computer(s) had suffered a memory leak, and we are waiting for them to
be topped up.

Wednesday Dec 07, 2005




begin:vcard
fn:Jay Zach
n:Zach;Jay
org:CBI;IS
adr;dom:;;1500 N. Ritter;Indianapolis;IN
email;internet:[EMAIL PROTECTED]
title:NT Administrator
tel;work:(317) 355
tel;cell:(317) 339-3525
x-mozilla-html:FALSE
url:http://www.ecommunity.com
version:2.1
end:vcard

FW: Mail delivery failed: returning message to sender

[[EMAIL PROTECTED]]

Hi guys and gals,

I just updated all updatable packages on my system (Sid, 2.6.7 kernel)
using aptitude. After doing so, aptitude now shows the following entry
for *all* packages:

WARNING: This version of 'xyz' is from an untrusted source! Installing
this package could allow a malicious individual to damage or take
control of your system.

At the moment I only have one line in /etc/apt/sources.lst:

deb ftp://ftp2.de.debian.org/debian sid main contrib non-free


What is going on? Forgive me if this is an obvious question, I have yet
to amster apt and found nothing really similar in Google.

Thankx, Peter



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

[EMAIL PROTECTED]: Mail delivery failed: returning message to sender]

[Lorenzo Taylor]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

kamaraju kusumanchi's comments on Re: failing to upgrade udev were as follows:

# In such a case, you should use stable distribution. Unstable is not for 
# everyone. It is useless to complain about instability of unstable. 
# Unstable is meant just to be that.

But later in my message I referred to the same type of instability in stable.
Stable includes a package called udf-tools, which requires a kernel patch that
is not available at all in Debian until kernel 2.6.10.  But stable only ships
with 2.6.8.  This is an instability in stable.  Therefore, this type of
instability is not only limited to unstable and testing.

Lorenzo
- -- 
- -BEGIN GEEK CODE BLOCK-
Version: 3.12
GCS d- s:+ a- C+++ UL P+ L+++ E- W++ N o K- w---
O M V- PS+++ PE Y+ PGP++ t++ 5+ X+ R tv-- b++ DI-- D+
G e* h r+++ y+++
- --END GEEK CODE BLOCK--
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFC2BeKG9IpekrhBfIRArvfAJ41yOdYrFnMtabKuiM4Q5n+JKxCZwCdF9ow
CyVm90TsRxdbGMCmLuZi0t4=
=AcI9
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

R: Mail Delivery (failure support@tomtom.com)

[TomTom Support]

 
 

Dear Customer,Thank you for your email.  Due to extensive changes in our support systems, we are no longer monitoring this email box, and are therefore unable to respond to this message.Please go to our website http://www.tomtom.com : we have redesigned this site to make it easier for you to find answers to your questions about our products.  If you cannot find what you are looking for, you will also be able to contact us with a request for information or for support.With best regards,TomTom BV.--Geachte klant,Bedankt voor uw e-mail. Als gevolg van de omvangrijke veranderingen in ons ondersteuningssysteem gebruiken wij deze e-mail box niet meer. Wij zijn daardoor niet in staat uw e-mail te beantwoorden.  Gaat u daarom naar onze website op http://www.tomtom.com. Wij hebben deze site geheel vernieuwd zodat u de antwoorden op uw vragen omtrent onze producten makkelijker kunt vinden. Indien u niet kunt vinden wat u zoekt, kunt u dan ook contact met ons opnemen voor informatie of ondersteuning.Met vriendelijke groetTomTom  BV Cher Client,Merci pour votre courrier électronique. En raison d'importants changements de nos systèmes de support, nous n'utilisons plus actuellement  cette boîte de réception d'email, nous sommes donc dans l'impossibilité de répondre à ce courrier.Veuillez, s'il-vous-plait, visiter notre nouveau site de support sur  internet à l'adresse suivante: http://www.tomtom.com/.  Nous avons conçu ce site afin de vous faciliter la recherche de réponses à toutes vos questions sur nos produits. Si vous ne pouvez pas trouver ce que vous recherchez, vous aurez aussi la possibilité de nous contacter pour toutes vos demandes d'informations.Très cordialement,TomTom  BV ---Sehr geehrter Kunde,Vielen Dank für Ihre Email. Auf Grund größerer Änderungen unseres Support-Systems werden Emails, welche an diese Adresse gesendet werden nicht mehr von uns bearbeitet.Bitte besuchen Sie in Zukunft unsere Webseite http://www.tomtom.com. Um Ihnen die Suche nach Antworten   bezüglich unserer Produkte zu erleichtern, haben wir diese Seite weiter umgestaltet. Sollten Sie unter "Support" keine Antwort auf Ihre Frage finden, haben Sie die Möglichkeit uns über eine Informations- bzw. Support-Anfrage kontaktieren.Mit freundlichen Grüßen,TomTom B.V.

 

Re: Mail Delivery (failure store@mini-itx.com)

[store]

---
Reduced email service between 21st April - 2nd May 2005
All orders placed online will continue to be despatched
---

Thank you for your email.

Mini-ITX.com is on holiday! We are running a reduced email service between 21st 
April and 1st May. We will not be able to answer all email queries during this 
time, and email response times will be slower than normal.

The Warehouse is FULLY operational, and orders placed online will continue to 
be despatched daily each evening. Stock levels are real time - if an item shows 
as in stock, then it is in stock. If an item is out of stock, then it will be 
automatically ordered for you.

Please direct any after-sales support issues to [EMAIL PROTECTED], after first 
looking for your answer on the site, or using google. We will try to help you 
as soon as possible.

If you have a tracking query, you may contact Parceline on 0845 9 300 100 (UK), 
or +44 845 9 300 350 (International) and quote your tracking number. This does 
not apply to Hush or Tranquil machines. Your tracking number (and printable 
invoice) are sent to you automatically after despatch.

This is an automated message.

Kind Regards,
Mini-ITX.com online store

-- 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

[eunet.co.yu #12245] Automatski odgovor na: Mail Delivery (failure info@eunet.co.yu)

[Hosting informacije via RT]

Hvala vam na poruci koju ste poslali EUnetovoj sluzbi prodaje.
Ovo je automatizovan odgovor naseg Sistema za pracenje zahteva, na vasu
poruku s temom:

 "Mail Delivery (failure [EMAIL PROTECTED])",

koja je i citirana na kraju poruke.

Nema potrebe da saljete odgovor na ovaj e-mail. Vasoj poruci dodeljen je
evidencioni broj: [eunet.co.yu #12245].

Molimo vas da u polje "Subject:" svih buducih poruka koje budete slali
na ovu temu ukljucite i vas evidencioni broj

 [eunet.co.yu #12245]

To ce nam omoguciti da pratimo kompletnu komunikaciju na zapocetu temu i
da brze i lakse servisiramo vas zahtev i pruzimo trazenu podrsku.

Za ovo je dovoljno i da odgovorite na ovaj e-mail koristeci funkciju
"Reply".


Srdacan pozdrav, 

EUnet d.o.o. Beograd - http://hosting.eunet.yu
Dubrovacka 35/III, 11000 Beograd, Serbia & Montenegro
Tel: +381 (0)11 3305-605, Fax: +381 (0)11 3305-606 



Tekst Vase originalne poruke:
-
  
This transaction appears to have no content


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: {Virus?} Mail Delivery (failure sales@cyclades.com)

[Sales Department]

Dear Customer:

This automatic response is to acknowledge that your message
has been received by Cyclades.

A sales representative will be contacting you shortly. If 
you don't receive a response in 48 hours, please let us know.

Cyclades Sales


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Mail Delivery (failure support@taloha.com)

[support]

Malo ni!

Ea mai koe?

***

IF YOU HAVE ANY COMMENTS ON THE NEWLY TRANSLATED DOT TK WEBSITE
PLEASE SEND AN EMAIL TO [EMAIL PROTECTED] PLEASE ALWAYS INCLUDE
IN YOUR COMMENT THE LANGUAGE YOU ARE COMMENTING ON AND THE
HTML OR SCRIPT PAGE LOCATED IN THE ADDRESS BAR OF YOUR BROWSER.

***

We thank you for your support question. So that we are able to provide 
You immediate assistance, we developed this automated email response.  
It contains several useful tips and answers to typical support questions.  
We hope it will help solve your issue!

Although this email is usually helpful for standard support issues, if you 
were unable to locate the answer to your problem, please email 
[EMAIL PROTECTED]  We will provide further assistance within 48 hours.

PROBLEM 1
-
Problem: Internal server error
or
Explicit server error

We thank you for reporting this error.  Dot TK is growing very rapidly and 
as a result, our systems are expanding dramatically, as well.  Because of this
growth, we do see occasional errors, such as the one you have received.  We 
are working hard to minimize such errors and are hopeful that it will not 
effect 
you beyond this incident.

PROBLEM 2
-
Problem: I stopped in the middle of the registration process and now
my domain is taken.

Don't worry. If you were in the registration process and did not complete 
the last step (Step 5), then your domain is probably just .on hold. for 30 
minutes. After 30 minutes the domain name should automatically be 
released.  To secure the domain, you will have to complete the entire 
registration process again at that time.

PROBLEM 3
-
Problem: I did not get a confirmation email.

There are a number of reasons that this may have occurred.  You can request
a copy of your confirmation email by going to:
http://my.dot.tk/cgi-bin/login01.taloha
Please enter your email address and click 'Resend the new registration email'.

However, if you provided an incorrect email address or did not get the 
confirmation email for some other reason your registration of the 
domain will not be accepted.  The domain is on hold, 
but will be released by our system within 72 hours (3 days).  At that time, 
the domain will be available for re-registration.  If you wish to secure the 
domain, you will be required to complete the registration process again.  
We apologize for any inconvenience this may cause you.

PROBLEM 4
-
Problem: My address did not pass the verification system.

Dot TK uses an Address Verification System to insure that our 
registrants provide valid information and that the information is correct. 
Due to the complexity of International Address Verification, the system 
occasionally identifies correct, valid data as invalid.

If you are experiencing this problem, please be sure you are completing 
all the fields. All fields are mandatory, except the fax number.  If you do not 
have a phone line or area code, please be sure you enter a '0' in the area 
code field and '00' in the phone number field. This usually solves the 
problem.

PROBLEM 5
-
Problem: I have problems with uploading content to my website.

Dot TK is NOT an Internet Service Provider or hosting facility.
We just forward your Dot TK domain name to another existing
webpage or website, located somewhere on the Internet. Please
consult your existing Internet Service provider or hosting
facility how you can upload HTML, images and more with programs
like FTP, WSFTP or SCP.

PROBLEM 6
-
Problem: I forgot my password!

Dot TK can send your password to your email address. Just go to
http://my.dot.tk/cgi-bin/login01.taloha
and fill out your email address. Click then on the text
'Email me my password' and within seconds you will receive
an email with your password.

Please note that both email address and password are case
sensitive.

PROBLEM 7
-
Problem: my domain has been suspended, now what?

For all FREEDOMAIN.TK domain names there is an important
rule: you should have at least 30 hits every 90 days.
If you have less then 30 hits, your domain name will
be suspended for 10 following days. During these days
you are able to buy your domain name. Please visit
My Dot TK, login, and go to 'Pay for domain'.

Please note that this usage rule is ONLY applicable
for FREEDOMAIN.TK domain names and NOT for PAIDDOMAIN.TK,
SPECIALDOMAIN.TK and TRADEMARK.TK domain names.

If your support issue has not been answered, please send an email to 
[EMAIL PROTECTED] for personal assistance.

Faka fetai (thank you)

Dot TK Support team



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Mail Delivery (failure mailback@photoways.com)

[mailback]

--- Begin Message ---



Cher(e) Photowaysien(ne),
 
Vous avez envoyé un message à l'adresse à notre attention, maiscelle-ci 
n'est pas active en réception et votre message ne pourra être lu.
 
Afin de répondre rapidement à toute demande, nous avons instauré un 
systèmede formulaire que nous vous demandons de remplir. Cela permettra 
ainsi unclassement et un suivi très efficace de vos demandes.
 
Ce formulaire se trouve à l'adresse : www.photoways.com/help/
 
En vous remerciant de votre compréhension et de votre confiance.
 
Très cordialement,
 
Service Clientèle PhotowaysEnergy Park bat.6134 Bld de 
Verdun92413 Courbevoie Cedex
 
Pour toute question, notre service clientèle se tient à votre 
dispositiondu lundi au vendredi de 09h00 à 18H00 au 0826 30 22 20 (0,15 
Euros / min)
 
 
 
--- End Message ---

Re: RE: Mail Delivery (failure jobs@1stsearch.com) [Qurb #362224]

[EriknSF]

Hi!

Re: Mail Delivery (failure greigstad@reigstad.com) "123323"

[Gordon H. Reigstad]

Thank you for sending me your email. I really want to receive it.

In an effort to eliminate junk email, I am using Mail Wiper.  Mail Wiper has placed 
your message safely on hold.

Please reply to this email and send it to me so I can add you to my eMail address book 
and we will be able to communicate freely from now on.


Thank you for your assistance.


For 100% Junk free eMail please visit http://www.mailwiper.com

Re: *** VIRUS ALERT *** Mail Delivery (failure contact@guitariff.net)

[contact]

From: [EMAIL PROTECTED]
Subject: Répondeur automatique [EMAIL PROTECTED]

Ceci est un répondeur automatique.


L'email que vous venez d'envoyer à [EMAIL PROTECTED] n'a pas pu arriver à destination 
et ne sera donc pas traité.

Merci de le faire transmettre à [EMAIL PROTECTED]


Salutations.





-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Mail delivery error / Fehler bei Mailauslieferung

[idf]

Der Empfaenger dieser Email ist an Bord unbekannt.
Nachstehend finden Sie die fehlerhafte Mailadresse
und die vollstaendigen Kopfdaten der nicht ausgelieferten
Email. Bitte beachten Sie, dass es technisch nicht moeglich
ist, Blindkopien (Bcc:) zu empfangen.
-
The recipient of this email is unknown on board.
Below you'll find the failed address and the complete
headers of the undelivered mail. Please note that it
is not possible to receive blind carbon copys (Bcc:).


[EMAIL PROTECTED]

= ORIGINAL HEADERS =

Return-Path: <[EMAIL PROTECTED]>
Received: from hlsmail.hls-cruises.com (localhost [127.0.0.1])
: by kommrouter.ms-europa.com (8.12.3/8.12.3/Debian-6.6) with ESMTP id i7PG5Pn8012783
: for <[EMAIL PROTECTED]>; Wed, 25 Aug 2004 16:12:18 GMT
Received: from vip.ms-europa.com (pD9515309.dip.t-dialin.net [217.81.83.9])
: by hls-cruises.com (8.11.6/8.11.6) with ESMTP id i7P9TNX06694
: for <[EMAIL PROTECTED]>; Wed, 25 Aug 2004 11:29:24 +0200
Message-Id: <[EMAIL PROTECTED]>
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: Request
Date: Wed, 25 Aug 2004 11:35:35 +0200
X-Priority: 3
X-MSMail-Priority: Normal
X-UIDL: TQo!!pIJ"![Ol"!aBe!!
Status:  O


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Mail Delivery (failure jobs.singapore@sap.com)

[jobs . singapore]

Dear Applicant 

Thank you for your interest in SAP.  We have received your resume online.
We will be reviewing it and will notify you within the next
3 weeks if you are shortlisted for a position in SAP.

Yours sincerely 

SAP Asia Pte Ltd - Human Resource Dept 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Mail Delivery (failure anne-lise@fjellogfjord-konferanser.no)

[anne-lise]

Hei

Jeg er på ferie, tilbake mandag 02.08.04. Ring Renate, hun kan hjelpe deg så lenge. 

Vi snakkes

Vennlig hilsen
Anne - Lise Amundsen


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Mail Delivery (failure info@torrelignyviaggi.com)

[info]

From: [EMAIL PROTECTED]
Subject: Casella di posta elettronica non configurata

Contattare il web master per l'assistenza
 Original Message 




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Mail Delivery (failure sag@castnet.com)

[SAG Enrollment Criteria]

Thank you for your Castnet.com renewal or membership request. Currently, SAG 
members-in-good-standing are eligible to receive a free Castnet membership or renewal.

For a free membership, you will need to:

1) Mail or email your headshot to us. Pictures must be in .jpg format and true 
size—8”x10”, 300dpi preferred.
2) Include your name, address, tel/fax numbers, email, and your valid 8-digit SAG ID 
number.
3) Include a photocopy of your SAG card. If you are emailing your information, please 
scan and attach your SAG card .
4) Include your agency/management information: address, tel/fax numbers, and email.
5) Mail to: Castnet Services; 127 West Church Street Suite 300; Orlando, FL  32801.
6) or Email to: [EMAIL PROTECTED]

Once the above is received, we will contact you with your username and password.
Please note that we must receive your headshot and a copy of your SAG card in order to 
activate your account.

For a free renewal, you will need to:

1) Mail, fax, or email a copy of your current SAG card along with your renewal request.
2) Mail to: Castnet Services; 127 West Church Street Suite 300; Orlando, FL  32801.
3) or Fax to: 323-964-4940.
4) or Email to: [EMAIL PROTECTED]

Once the above is received, we will update your account with a complementary renewal.

Your free SAG membership/renewal is courtesy of Fashion Rock LLC, Castnet's parent 
company.

Best regards,

Castnet Client Services
127 West Church Street Suite 300
Orlando, FL  32801
866-582-4201  Ext. 3603
www.castnet.com


This is an automatic response.

RE: Mail Delivery (failure info@infinitiwireless.com [Qurb #251420]

[Tom Freeland]

This is an automated message.

I apologize for the inconvenience, but I need your help in fighting
spam. I'm using a program called Qurb which automatically maintains
a list of approved senders for me. Messages from approved senders go
directly to my Inbox. Messages from addresses that Qurb hasn't seen
before are quarantined until the address of the sender can be
confirmed.

TO CONFIRM YOUR ADDRESS PLEASE REPLY TO THIS MESSAGE WITHOUT
MODIFYING THE SUBJECT.

There is no need to include any additional information in your
reply. I will be notified of your original message immediately and
you should not receive a confirmation message like this from me in
the future.

Thanks!


Free download at http://www.qurb.com/

RE: Mail Delivery (failure customer_service@musicmatch.com)

[custsupp]

Hello,

Thank you for contacting the Musicmatch Customer Support Department.  Emails are 
answered Monday through Friday during regular business hours (8AM to 5PM PST.)  We 
respond to all email in the order in which they are received. For this reason, please 
do not resubmit your customer support request. 

The average response time is currently under 12 hours. 

You may be able to find the answers to your questions much faster at any of the 
various locations:

For FAQ's, interactive tutorials and usage instructions starting with the basics all 
the way through advanced topics, point your Internet browser to the following web page:

http://www.musicmatch.com/info/user_guide/

The Musicmatch searchable Knowledge Base:
http://www.musicmatch.com/form/support/

Another good source of information about Musicmatch Jukebox features and functionality 
is Musicmatch Jukebox Help.  You can view the help documentation by clicking the 
"Help" menu within the Jukebox and selecting "Musicmatch Jukebox Help" from the popup 
menu. 


To change or cancel a Musicmatch MX subscription trial or renewal, use the following 
URL to login to your account management web page:

http://www.musicmatch.com/acctmgmt/

We look forward to assisting you!  Thank you for your patience and support!

Best Regards,
Musicmatch
Customer Support

RE: Mail Delivery (failure jobs@1stsearch.com) [Qurb #362224]

[Betsy Reinking]

This is an automated message.

I apologize for the inconvenience, but I need your help in fighting
spam. I'm using a program called Qurb which automatically maintains
a list of approved senders for me. Messages from approved senders go
directly to my Inbox. Messages from addresses that Qurb hasn't seen
before are quarantined until the address of the sender can be
confirmed.

TO CONFIRM YOUR ADDRESS PLEASE REPLY TO THIS MESSAGE WITHOUT
MODIFYING THE SUBJECT.

There is no need to include any additional information in your
reply. I will be notified of your original message immediately and
you should not receive a confirmation message like this from me in
the future.

Thanks!


Free download at http://www.qurb.com/

Re: Re: Mail Delivery (failure customerservice@clubmosaico.com) [#3355304]

[TM7023]

tengo una orden de libros con ustede y no me allegao , megustaria saber que debo de ahacer para recibir mis libros, la orden ya fue pagada de mi cuenta, espero su respuesta, gracias

Re: Re: Mail Delivery (failure customerservice@clubmosaico.com) [#3355304]

[TM7023]

hola ! yo tengo una compra de libros con ustedes y no he recibido mi paquete, no se que hacer para saber que pasa la orden ya fue pagada, ustede tomas su dinero de mi cuenta y ahora no se que hacer para recibir mis libros, mi orden indica que los recibiria el dia 8 de junio.    mi nombre esl Griselda F. Montes . Espero una respuesta lo mas pronto posible, gracias.

Re: Mail Delivery (failure inquirie@rishashay.com)

[inquirie]

This is an autoresponder. I'll never see your message.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Mail Delivery (failure elcamino@jesucristo.net)

[recibido]

 www.JESUCRISTO.net 

Respuesta automática a su e-mail. No responda a este e-mail. Reponderemos 
personalmente a su mensaje a la mayor brevedad posible. Dios le bendiga muy 
grandemente. 

Webmaster 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Mail Delivery (failure customerservice@clubmosaico.com) [#3355304]

[customer . service]

Servicio  al Cliente recibió su correspondencia.  Tenga la seguridad de que su mensaje 
es importante y que uno de nuestros especialistas en correspondencia le contestará  
cuanto antes sea posible, si así fuera necesario. Nuestro horario de trabajo es de 6 
de la mañana a 11 de la noche, hora del Este, de Lunes a Viernes.

Si  nos escribió por problemas técnicos, permítanos un poco más de tiempo para 
responder pues pudiéramos tener que consultar a nuestro equipo técnico a los efectos 
de la solución.

* La dirección de respuesta de esta correspondencia es de una cuenta automatizada. 
Este mensaje es solamente una notificación y no debe responderse.
Gracias



-  Wrote -
 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Mail Delivery (failure customerservice@clubmosaico.com) [#3295091]

[customer . service]

Servicio  al Cliente recibió su correspondencia.  Tenga la seguridad de que su mensaje 
es importante y que uno de nuestros especialistas en correspondencia le contestará  
cuanto antes sea posible, si así fuera necesario. Nuestro horario de trabajo es de 6 
de la mañana a 11 de la noche, hora del Este, de Lunes a Viernes.

Si  nos escribió por problemas técnicos, permítanos un poco más de tiempo para 
responder pues pudiéramos tener que consultar a nuestro equipo técnico a los efectos 
de la solución.

* La dirección de respuesta de esta correspondencia es de una cuenta automatizada. 
Este mensaje es solamente una notificación y no debe responderse.
Gracias



-  Wrote -
 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

[Auto-Reply] Mail Delivery (failure leekenn@sh163.net)

[leekenn]

My Email address has been changed to [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Mail Delivery (failure info@wgs.com)

[lm]

This is an autoresponder. I'll never see your message.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Mail Delivery (failure jaliag@aet-es.org)

[jaliag]

El servidor de correo de la AET le informa:

Hay un problema con su mensaje, ha sido rechazado por el servidor.

Fuentes de errores más comunes:

1. la dirección no es correcta 
   a)error tipográfico
   b)dominio .com .org .net incorrecto

2. Ha enviado un mensaje a una lista de correo en lo cual no está inscrito.

para inscribirse en la lista AETforo:
http://www.aet-es.org/info/lista.html

para inscribirse en cualquier otra lista de la AET pongase en contacto con el [EMAIL 
PROTECTED]

Para cualquier duda sobre este mensaje envie un mensaje a:
[EMAIL PROTECTED]

Un cordial saludo
Asociación Española de teletrabajo


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Mail Delivery (failure webmaster@mathforum.org)

[Math Forum Webmaster]

Hello --

Thanks for writing in to the Math Forum! This automatic response
confirms that we've received your message.

At the bottom of this note, please find a few questions that people 
commonly send to the Forum, along with our standard responses.  
We sincerely hope that you find the answer to your question among 
those we've listed.

If you have a question or concern that this list does not address
sufficiently, a Forum staff member will respond to your message
within the next couple of days.

Thank you,

The Math Forum Staff
http://mathforum.org/

__
Q: WHERE CAN I GET HELP WITH A MATH QUESTION?

A:   Have you heard about Ask Dr. Math, the Forum's question and
 answer service for math students and their teachers? We have
 a searchable archive of questions and answers, plus a form
 for submitting questions, at:

   http://mathforum.org/dr.math/

 If you submit a question to the doctors, give as much information
 as possible about the trouble you're having: show the work you've
 already done, and ask specific questions about whatever it is you
 don't understand.


__
Q: WHERE CAN I FIND A MATH FORMULA OR DEFINITION?

A:   Try the Dr. Math FAQ for formulas:

   http://mathforum.org/dr.math/faq/faq.formulas.html

 ... or Eric Weisstein's World of Mathematics, formerly Eric's 
 Treasure Trove of Mathematics:

   http://mathworld.wolfram.com/

__
Q: WHERE CAN I GET ADVICE ON   ?

A:   Have you heard about the Forum's Teacher2Teacher service? Our
 panel of teaching professionals is available to answer your
 questions about teaching mathematics or how your children are
 learning math:

   http://mathforum.org/t2t/

 To reach a broad audience, post a message to a relevant mailing
 list or newsgroup. Here's a list of discussions hosted and/or
 recommended by the Forum:

   http://mathforum.org/discussions/


__
Q: WHERE CAN I FIND WEB PAGES ON   ?

A:   Visit the Internet Math Library, an annotated catalog of
 mathematics and mathematics education web sites. The Library
 features a description of each entry, hierarchical categories
 for browsing, a searcher on each browse page, and selected sites
 for each category's starting points:

   http://mathforum.org/library/

 Alternately, conducting a search remains a good way to find
 specific resources on the Internet. We encourage you to go to
 our main search engine and enter keywords pertaining to the
 topic you want to find:

   http://mathforum.org/grepform.html


__
Q: WILL YOU LIST MY URL ON YOUR SITE?

A:  You're quite welcome to suggest URLs for inclusion in our Math
Library, as long as they relate to math or math education. Please
fill out this online form:

   http://mathforum.org/library/add.html


__
Q: MAY I LINK TO YOUR SITE?

A:  Sure - go right ahead! Please give us proper attribution and
state clearly that this is a Forum resource, and not something
of your own creation. If you'd like to have us make a reciprocal
link, fill out the web form mentioned above.


__
Q: MAY I HAVE PERMISSION TO REPRODUCE YOUR CONTENT?

A:  You may reproduce a Math Forum web page for private or classroom
use. Please give us proper attribution and state clearly that this
is a Math Forum resource, and not something of your own creation.
You may not publish the reproduction on a public website or for
commercial purposes without our explicit permission.

For commercial reproductions, please complete and submit our
permission form:

   http://mathforum.org/help/permission.html

To learn more about our terms of use, please read

   http://mathforum.org/announce/terms.html








-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]