On 12 Nov 2013, at 22:06, Gregory Nowak g...@gregn.net wrote:
This name won't appear on From: lines of outgoing messages if
rewriting
is enabled.
It does leak out in message-Id strings however.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of
On Thu, 14 Nov 2013, Jonathan Dowland wrote:
On 12 Nov 2013, at 22:06, Gregory Nowak g...@gregn.net wrote:
This name won't appear on From: lines of outgoing messages if
rewriting
is enabled.
It does leak out in message-Id strings however.
Newbie's question: is it a problem? Is there a
On Thu, Nov 14, 2013 at 10:45:56AM +0200, Itay wrote:
Newbie's question: is it a problem? Is there a risk?
Not really, but some people may prefer that their internal host names
and suchlike are not exposed to the outside world. I first noticed it
when trying to configure my MUA to recognise my
On Thu, 14 Nov 2013, Jonathan Dowland wrote:
On Thu, Nov 14, 2013 at 10:45:56AM +0200, Itay wrote:
Newbie's question: is it a problem? Is there a risk?
Not really, but some people may prefer that their internal host names
and suchlike are not exposed to the outside world. I first noticed it
Hi,
I want to conclude this thread with a summary. I hope some may
benefit from this.
First many thanks to Gregory Nowak, Jonathan Dowland, Chris Davies,
and Curt, who helped me along the way.
My purpose:
I wanted that the system mail notifications (cron failed jobs, etc.)
to end up in
On Tue, Nov 12, 2013 at 09:39:55AM +0200, Itay wrote:
I don't remember editing /etc/mailname by hand; 'dpkg -S' says it's
not owned by any debian package.
So how this file gets its content?
It was created when you installed exim, and would be changed when
running dpkg-reconfigure exim4-config.
On Mon, 11 Nov 2013, Jonathan Dowland wrote:
On Mon, Nov 11, 2013 at 09:20:18AM +0200, Itay wrote:
3) The last command I isssued:
# echo This is a test message. | exim -v -i root
is still hanging.
This was the behavior I was seeing yesterday as well.
Try killing it and re-issuing it since
On Mon, Nov 11, 2013 at 12:33:46PM +0200, Itay wrote:
I tried several times, including re-issuing 'exim4 -qff'.
It hangs and I have to kill it.
The output is appended below.
OK I wouldn't worry about the hanging from this output. I suspect it's
just the SMTP client and/or server keeping the
On Mon, Nov 11, 2013 at 08:28:31AM +0200, Itay wrote:
I don't understand why ':25' is appended, and what is the meaning of
that.
There are a number of things I want to reply to in this thread. So,
I'm going to do this in each relevant message, since that will be
easier for me. Apologies if the
On Mon, Nov 11, 2013 at 08:50:33AM +0200, Itay wrote:
I was using 465 because that's how my email client (alpine) uses the
provider's SMTP. It was configured some years ago, and I was not
aware that a change is required.
Yes, mail.messagingengine.com still seems to accept connections on tcp
On Mon, Nov 11, 2013 at 12:33:46PM +0200, Itay wrote:
On Mon, 11 Nov 2013, Jonathan Dowland wrote:
It looks like your mail configuration is now fixed.
I agree, for the most part anyway.
Finally -- I don't know if it is significant -- but I note in the
output below, for example 3 lines from
On Mon, 11 Nov 2013, Gregory Nowak wrote:
On Mon, Nov 11, 2013 at 08:28:31AM +0200, Itay wrote:
I don't understand why ':25' is appended, and what is the meaning of
that.
There are a number of things I want to reply to in this thread. So,
I'm going to do this in each relevant message, since
Thanks to Jonathan and Greg, and others, it seems that the cause for
the problem was found.
See below.
On Mon, 11 Nov 2013, Jonathan Dowland wrote:
Date: Mon, 11 Nov 2013 11:33:22 +
From: Jonathan Dowland j...@debian.org
To: debian-user@lists.debian.org
Subject: Re: [OT?] What's wrong
On Mon, 11 Nov 2013, Gregory Nowak wrote:
On Mon, Nov 11, 2013 at 12:33:46PM +0200, Itay wrote:
On Mon, 11 Nov 2013, Jonathan Dowland wrote:
It looks like your mail configuration is now fixed.
I agree, for the most part anyway.
Finally -- I don't know if it is significant -- but I note in
On Mon, 11 Nov 2013, Gregory Nowak wrote:
On Mon, Nov 11, 2013 at 08:50:33AM +0200, Itay wrote:
I was using 465 because that's how my email client (alpine) uses the
provider's SMTP. It was configured some years ago, and I was not
aware that a change is required.
Yes,
Hi,
I apologize for the long post.
I thought it's best to put as much information including stuff inserted into
configuration files and relevant parts of log file.
I am struggling to configure exim4 on my home desktop to send system
notifications to my public email address. So far with no
On 2013-11-10, Itay deb...@itayf.fastmail.fm wrote:
4. Insert in /etc/exim4/passwd.client the following line:
smtp.mail.provider:myem...@fastmail.fm:ClearTextPassWord
This part I don't understand. I thought you were supposed to put fastmail.fm's
smtp server in the first field?
Itay deb...@itayf.fastmail.fm wrote:
I am struggling to configure exim4 on my home desktop to send system
notifications to my public email address [...]
[I replaced smtp's port with NNN. Also, assume 'machine' is output of
command 'hostname', while 'machine.homenetwork' is output of 'hostname
On Sun, 10 Nov 2013, Chris Davies wrote:
Chris: thanks for helping me out.
Itay deb...@itayf.fastmail.fm wrote:
I am struggling to configure exim4 on my home desktop to send system
notifications to my public email address [...]
[I replaced smtp's port with NNN. Also, assume 'machine' is
On Sun, 10 Nov 2013, Curt wrote:
On 2013-11-10, Itay deb...@itayf.fastmail.fm wrote:
4. Insert in /etc/exim4/passwd.client the following line:
smtp.mail.provider:myem...@fastmail.fm:ClearTextPassWord
This part I don't understand. I thought you were supposed to put fastmail.fm's
smtp server
On 2013-11-10, Itay deb...@itayf.fastmail.fm wrote:
R: smarthost for r...@fastmail.fm
T: remote_smtp_smarthost for r...@fastmail.fm
Connecting to mail.messagingengine.com [66.111.4.52]:25 ... failed:
**?
Connection refused
On Sun, 10 Nov 2013, Roger B.A. Klorese wrote:
On Nov 10, 2013, at 10:07 AM, Itay deb...@itayf.fastmail.fm wrote:
On Sun, 10 Nov 2013, Chris Davies wrote:
Itay deb...@itayf.fastmail.fm wrote:
IP address or host name of the outgoing smarthost
= mail.messagingengine.com::NNN.
Should be a
On Sun, Nov 10, 2013 at 01:15:26PM +, Chris Davies wrote:
IP address or host name of the outgoing smarthost
= mail.messagingengine.com::NNN.
Should be a single colon, not double. For example, mail.example.net:587
No, this is incorrect. When you run dpkg-reconfigure exim4-config, it
On Sun, 10 Nov 2013, Curt wrote:
On 2013-11-10, Itay deb...@itayf.fastmail.fm wrote:
R: smarthost for r...@fastmail.fm
T: remote_smtp_smarthost for r...@fastmail.fm
Connecting to mail.messagingengine.com [66.111.4.52]:25 ... failed:
**?
On Sun, 10 Nov 2013, Gregory Nowak wrote:
By mistake I sent my reply directly to the responder (sorry Greg) and
not to the list. Here is a copy:
On Sun, Nov 10, 2013 at 01:15:26PM +, Chris Davies wrote:
IP address or host name of the outgoing smarthost
=
On Mon, 11 Nov 2013, Itay wrote:
On Sun, 10 Nov 2013, Gregory Nowak wrote:
On Sun, Nov 10, 2013 at 01:15:26PM +, Chris Davies wrote:
IP address or host name of the outgoing smarthost
= mail.messagingengine.com::NNN.
Should be a single colon, not double. For example,
On Mon, Nov 11, 2013 at 09:20:18AM +0200, Itay wrote:
3) The last command I isssued:
# echo This is a test message. | exim -v -i root
is still hanging.
This was the behavior I was seeing yesterday as well.
Try killing it and re-issuing it since you've made the other changes.
It looks like
27 matches
Mail list logo
