Le 12-06-2023, à 21:25:40 +0200, Michel Verdier a écrit :
On 2023-06-11, steve wrote:
After a few days with this configuration, same errors are still present.
I guess I'll have either to reinstall or go the postfix way.
Just to be sure before you reinstall can you provide
exim -bP | grep sy
On 2023-06-11, steve wrote:
>>> After a few days with this configuration, same errors are still present.
>>>
>>> I guess I'll have either to reinstall or go the postfix way.
>>
>>Just to be sure before you reinstall can you provide
>>exim -bP | grep syslog
>
> syslog_duplication
Docs indicate it
Hi Michel,
Le 10-06-2023, à 11:19:25 +0200, Michel Verdier a écrit :
On 2023-06-10, steve wrote:
Hi Michel and al,
After a few days with this configuration, same errors are still present.
I guess I'll have either to reinstall or go the postfix way.
Just to be sure before you reinstall can
On 2023-06-10, steve wrote:
> Hi Michel and al,
>
> After a few days with this configuration, same errors are still present.
>
> I guess I'll have either to reinstall or go the postfix way.
Just to be sure before you reinstall can you provide
exim -bP | grep syslog
Hi Michel and al,
After a few days with this configuration, same errors are still present.
I guess I'll have either to reinstall or go the postfix way.
Have a nice day,
steve
Le 05-06-2023, à 10:50:00 +0200, Michel Verdier a écrit :
Le 5 juin 2023 Steve a écrit :
if one succeed without me
Le 05-06-2023, à 10:50:00 +0200, Michel Verdier a écrit :
Le 5 juin 2023 Steve a écrit :
if one succeed without message and with code 0, add in
/etc/logrotate.d/exim4-base and /etc/logrotate.d/exim4-paniclog
postrotate
systemctl exim4-base
endscript
if you add reload but still get
Le 5 juin 2023 Steve a écrit :
>>if one succeed without message and with code 0, add in
>>/etc/logrotate.d/exim4-base and /etc/logrotate.d/exim4-paniclog
>>
>>postrotate
>>systemctl exim4-base
>>endscript
>>
>>if you add reload but still get the error try restart, I don't know if
>>th
Le 05-06-2023, à 10:21:52 +0200, Michel Verdier a écrit :
Le 5 juin 2023 Steve a écrit :
Merci pour ton aide Michel.
De rien :) Let's continue in english for the list
Sure.
log_file_path = /var/log/exim4/%slog
log_selector = +smtp_protocol_error +smtp_syntax_error
+tls_certificate_verif
Le 5 juin 2023 Steve a écrit :
> Merci pour ton aide Michel.
De rien :) Let's continue in english for the list
> log_file_path = /var/log/exim4/%slog
> log_selector = +smtp_protocol_error +smtp_syntax_error
> +tls_certificate_verified +tls_peerdn
exim writes directly to the logfiles. If you ge
Le 05-06-2023, à 09:09:05 +0200, Michel Verdier a écrit :
Le 5 juin 2023 Steve a écrit :
Yes, nothing is done after rotation. But I don't remember the default
exim logging mechanism. Can you provide
grep -r log_file_path /etc/exim*
This gives nothing.
Then can you provide
exim -bP
(snip i
Le 5 juin 2023 Steve a écrit :
>>Yes, nothing is done after rotation. But I don't remember the default
>>exim logging mechanism. Can you provide
>>
>>grep -r log_file_path /etc/exim*
>
> This gives nothing.
Then can you provide
exim -bP
(snip ip adresses if you want)
Le 04-06-2023, à 19:11:57 +0200, Michel Verdier a écrit :
Le 4 juin 2023 Steve a écrit :
Does this help?
Yes, nothing is done after rotation. But I don't remember the default
exim logging mechanism. Can you provide
grep -r log_file_path /etc/exim*
This gives nothing.
Le 4 juin 2023 Steve a écrit :
> Does this help?
Yes, nothing is done after rotation. But I don't remember the default
exim logging mechanism. Can you provide
grep -r log_file_path /etc/exim*
Le 04-06-2023, à 14:30:08 +0200, Michel Verdier a écrit :
Le 4 juin 2023 Steve a écrit :
2023-06-04T06:30:54.117016+02:00 box exim[24894]: 2023-06-04 06:30:54
1q5fOD-0006TT-2C failed to write to main log: length=91 result=-1 errno=9 (Bad
file descriptor)
2023-06-04T06:30:54.150516+02:00 box
Le 4 juin 2023 Steve a écrit :
> 2023-06-04T06:30:54.117016+02:00 box exim[24894]: 2023-06-04 06:30:54
> 1q5fOD-0006TT-2C failed to write to main log: length=91 result=-1 errno=9
> (Bad file descriptor)
> 2023-06-04T06:30:54.150516+02:00 box exim[24894]: write failed on panic log:
> length=116
On Sun 26 Mar 2023 at 12:47:45 (-0700), pe...@easthope.ca wrote:
>
> (4) "TLS on connect is not natively supported." OK but the test
> confirmed that it can work. Documentation could tell how to
> configure. Otherwise link to instructions at least.
>
> (5)
> https://www.exim.org/exim-html-curr
In-reply-to:
References:
<5319ac62b1294b2290d3d14a6cd8b...@easthope.ca>
From: David Wright
Date: Sat, 25 Mar 2023 23:34:54 -0500
In the first instance, just try sending a test message using the
commands I gave, except starting off with:
$ openssl s_client -crlf -connect mail.east
On Sat 25 Mar 2023 at 19:47:35 (-0700), pe...@easthope.ca wrote:
> > That looks fine, and shows that you're going to send through their
> > port 465, which will require TLS and authentication. So first you need
> > to encode your username and password with:
> >
> > $ echo -e -n '\0username\0passw
In-reply-to:
References: <9ef536feee6ec3ae2e3032d22e06d...@easthope.ca>
From: David Wright
Date: Fri, 24 Mar 2023 23:18:47 -0500
That looks fine, and shows that you're going to send through their
port 465, which will require TLS and authentication. So first you need
to encode your u
On Thu 23 Mar 2023 at 11:27:17 (-0700), pe...@easthope.ca wrote:
>
> # /etc/exim4/update-exim4.conf.conf
> #
> # Most of the heading comments removed.
> #
> # This is a Debian specific file
>
> dc_eximconfig_configtype='smarthost'
> dc_other_hostnames=''
> dc_local_interfaces='127.0.0.1'
> dc_rea
Header lines not handled by Web interface.
In-reply-to:
References: <5674e986a67af53a04b27f08cd161...@easthope.ca>
From: David Wright
Date: Wed, 22 Mar 2023 17:06:20 -0500
What are the contents of /etc/exim4/update-exim4.conf.conf, the
configuration file?
# /etc/exim4/update-exim4
On Wed 22 Mar 2023 at 13:52:00 (-0700), pe...@easthope.ca wrote:
>
> After configuring exim for a new smarthost, message sending fails.
What are the contents of /etc/exim4/update-exim4.conf.conf, the
configuration file?
> This might help to identify the problem.
>
> root@dalton:/home/root# exim
Am 07.05.21 um 02:12 schrieb Michael Biebl:
exim4 is unfortunately still SysV-only and doesn't ship a native systemd
.service file. So the correct command is
"update-rc.d exim4 disable"
For the curious: you can run "systemctl disable exim4" as well.
This will just run the above command though
exim4 is unfortunately still SysV-only and doesn't ship a native systemd
.service file. So the correct command is
"update-rc.d exim4 disable"
"update-rc.d exim4 remove" will remove the symlinks in /etc/rc?.d/ but on
the next package update, they will be recreated.
So if you want to make this a p
On Wed, May 05, 2021 at 05:27:13PM +0300, Andrei POPESCU wrote:
> On Mi, 05 mai 21, 07:46:03, Greg Wooledge wrote:
> >
> > You're using a package that has not yet been converted to systemd. It's
> > still using an old init.d script, and systemd is performing a conversion
> > on the fly.
> >
> >
On Mi, 05 mai 21, 07:46:03, Greg Wooledge wrote:
>
> You're using a package that has not yet been converted to systemd. It's
> still using an old init.d script, and systemd is performing a conversion
> on the fly.
>
> The basic start and stop subcommands will work fine, but disable may
> not wor
On Wed, May 05, 2021 at 12:07:29PM +0100, Joe wrote:
> On Tue, 4 May 2021 18:44:12 -0400
> Greg Wooledge wrote:
> >
> > Could you kindly tell us what "systemctl status exim4.service" says
> > on this buster machine of yours? Perhaps your command is turning up
> > one of the automatically convert
On Tue, 4 May 2021 18:44:12 -0400
Greg Wooledge wrote:
> On Tue, May 04, 2021 at 10:14:45PM +0100, Joe wrote:
> > ...and buster. It's exim4.service as stated by:
> > systemctl --type=service | grep exim
>
> According to packages.debian.org[1] there is no such file in any
> package.
>
> Of co
On Tue, May 04, 2021 at 10:14:45PM +0100, Joe wrote:
> ...and buster. It's exim4.service as stated by:
> systemctl --type=service | grep exim
According to packages.debian.org[1] there is no such file in any
package.
Of course, that's not proof of the nonexistence of such a file, because
it might
On Tue, 4 May 2021 18:27:57 +0100
Joe wrote:
> On Tue, 4 May 2021 13:15:51 -0400
> Greg Wooledge wrote:
>
> > On Tue, May 04, 2021 at 10:03:43AM -0700, John Conover wrote:
> > > That was the question, Greg:
> > >
> > > "Searching for exim in
> > > /etc/systemd/system/multi-user.targe
On Tue, May 04, 2021 at 01:46:29PM -0700, John Conover wrote:
>
> Try:
>
> man update-rc.d
> man 8 update-rc.d
>
Please stop top-posting, and please reply to the list.
> Greg Wooledge writes:
> > On Tue, May 04, 2021 at 01:27:56PM -0700, John Conover wrote:
> > > As per the man page f
On Tue, May 04, 2021 at 01:27:56PM -0700, John Conover wrote:
> As per the man page for System V init, to disable launching of exim:
>
> update-rc.d -f exim remove
What man page is this allegedly from, exactly?
For the archives, this issue was created by looking for penetration
vulnerabilities during the boot of a Debian Buster machine using
tcpdump(1) on a machine between Buster, and the it's Internet facing
router.
There was exim traffic when exim boots, but exim was SUPPOSED to be
disabled during bo
On 5/4/2021 7:28 PM, Erwan David wrote:
Le 04/05/2021 à 19:26, Joe a écrit :
On Tue, 4 May 2021 10:03:43 -0700
cono...@rahul.net (John Conover) wrote:
Greg Wooledge writes:
On Tue, May 04, 2021 at 09:17:38AM -0700, John Conover wrote:
Searching for exim in
/etc/systemd/system/multi-user.targ
On Tue, May 04, 2021 at 10:27:17AM -0700, John Conover wrote:
>
> Thanks, Greg. "update-rc.d -f exim remove" is the command for
> /etc/init.d. But its broken.
You forgot to reply to the list.
Nobody with any sense uses update-rc.d for system admin work. It's
there for Debian packages to use, a
Le 04/05/2021 à 19:26, Joe a écrit :
> On Tue, 4 May 2021 10:03:43 -0700
> cono...@rahul.net (John Conover) wrote:
>
>> Greg Wooledge writes:
>>> On Tue, May 04, 2021 at 09:17:38AM -0700, John Conover wrote:
Searching for exim in
/etc/systemd/system/multi-user.target.wants/* and
/l
On Tue, 4 May 2021 13:15:51 -0400
Greg Wooledge wrote:
> On Tue, May 04, 2021 at 10:03:43AM -0700, John Conover wrote:
> > That was the question, Greg:
> >
> > "Searching for exim in
> > /etc/systemd/system/multi-user.target.wants/* and
> > /lib/systemd/system/* yields nothing."
> >
On Tue, 4 May 2021 10:03:43 -0700
cono...@rahul.net (John Conover) wrote:
> Greg Wooledge writes:
> > On Tue, May 04, 2021 at 09:17:38AM -0700, John Conover wrote:
> > > Searching for exim in
> > > /etc/systemd/system/multi-user.target.wants/* and
> > > /lib/systemd/system/* yields nothing.
> >
On Tue, May 04, 2021 at 10:03:43AM -0700, John Conover wrote:
> That was the question, Greg:
>
> "Searching for exim in
> /etc/systemd/system/multi-user.target.wants/* and
> /lib/systemd/system/* yields nothing."
>
> so, it wasn't there. Which service?, (or how to find out?)
So... I
Greg Wooledge writes:
> On Tue, May 04, 2021 at 09:17:38AM -0700, John Conover wrote:
> > Searching for exim in /etc/systemd/system/multi-user.target.wants/*
> > and /lib/systemd/system/* yields nothing.
> >
> > How do I stop exim from launching across boots?
>
> Presumably there is a systemd ser
On Tue, May 04, 2021 at 09:17:38AM -0700, John Conover wrote:
> Searching for exim in /etc/systemd/system/multi-user.target.wants/*
> and /lib/systemd/system/* yields nothing.
>
> How do I stop exim from launching across boots?
Presumably there is a systemd service, which is enabled. You will wa
Hello,
On Thu, Jun 20, 2019 at 08:45:13PM +0100, Brian wrote:
> At least 2000,000, hosts on the internet. You reckon you will be in
> the first tranche of targets?
I don't know about "amongst the first" but there are multiple
services scanning every port of the entire IPv4 space now and
selli
On Fri 21 Jun 2019 at 21:14:42 +1000, Andrew McGlashan wrote:
> On 21/6/19 4:08 pm, Reco wrote:
> > What I'm most interested is here is the time distribution. I.e. has
> > the number of exploitation attempts lowered after the Exim banner
> > change? Stayed the same?
>
> Not a single one since, so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 21/6/19 4:08 pm, Reco wrote:
> What I'm most interested is here is the time distribution. I.e. has
> the number of exploitation attempts lowered after the Exim banner
> change? Stayed the same?
Not a single one since, so far.
Although I di
Hi.
On Fri, Jun 21, 2019 at 06:36:20AM +1000, Andrew McGlashan wrote:
> On 21/6/19 5:52 am, Reco wrote:
> > Plain old grep is more than enough here. This one:
> >
> > grep 'run{' /var/log/exim4/reject*
> >
> > finds things like these:
> >
> > 2019-06-19 18:54:43 H=(service.com) [107.182
On Thu, Jun 20, 2019 at 10:50:08PM +0100, Brian wrote:
So? Looks like a normal day. Announcing exim as version 4.92 (or any
other value) is most unlikely to reduce the number of these attempts.
I'm seeing the same attempts on postfix servers...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
On 21/6/19 4:49 am, Reco wrote:
>> Thank you, I've changed the banner for now let's hope that
>> lessens the problem.
>
> Please share the results if possible.
>
> On this particular MTA I've counted whopping 4 attempts to exploit
> CVE-2
On Fri 21 Jun 2019 at 04:15:35 +1000, Andrew McGlashan wrote:
> On 20/6/19 11:57 pm, Brian wrote:
> > On Thu 20 Jun 2019 at 23:26:08 +1000, Andrew McGlashan wrote:
> >
> >> # dpkg-query -l|grep \ exim|awk '{print $2,$3}'|column -t exim4
> >> 4.89-2+deb9u4 exim4-base 4.89-2+deb9u4 exim4-c
Hi.
On Fri, Jun 21, 2019 at 04:40:11AM +1000, Andrew McGlashan wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
>
>
> On 20/6/19 11:45 pm, Reco wrote:
> > Hi.
> >
> > On Thu, Jun 20, 2019 at 11:26:08PM +1000, Andrew McGlashan wrote:
> >> Is there a way to provide version of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 20/6/19 11:45 pm, Reco wrote:
> Hi.
>
> On Thu, Jun 20, 2019 at 11:26:08PM +1000, Andrew McGlashan wrote:
>> Is there a way to provide version of "4.92" easily or some other
>> text to stop the likelihood of outsiders trying to pound on and
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 20/6/19 11:57 pm, Brian wrote:
> On Thu 20 Jun 2019 at 23:26:08 +1000, Andrew McGlashan wrote:
>
>> # dpkg-query -l|grep \ exim|awk '{print $2,$3}'|column -t exim4
>> 4.89-2+deb9u4 exim4-base 4.89-2+deb9u4 exim4-config
>> 4.89-2+deb9u4
On Thu 20 Jun 2019 at 23:26:08 +1000, Andrew McGlashan wrote:
> # dpkg-query -l|grep \ exim|awk '{print $2,$3}'|column -t
> exim4 4.89-2+deb9u4
> exim4-base 4.89-2+deb9u4
> exim4-config4.89-2+deb9u4
> exim4-daemon-heavy 4.89-2+deb9u4
> exim4-doc-html 4.89-1
>
On Thu, Jun 20, 2019 at 11:26:08PM +1000, Andrew McGlashan wrote:
> Shodan [1] reports loads of vulnerable [2] servers running pre 4.92
> versions of Exim, those include Debian Exim variants reporting 4.89
> even for fully patched servers.
General answer:
https://www.debian.org/security/faq
Hi.
On Thu, Jun 20, 2019 at 11:26:08PM +1000, Andrew McGlashan wrote:
> Is there a way to provide version of "4.92" easily or some other text
> to stop the likelihood of outsiders trying to pound on and exploit the
> server? Even though they won't be able to do successfully due to up to
>
On Tue 17 May 2016 at 12:32:33 -0500, David Wright wrote:
> On Thu 12 May 2016 at 20:38:41 (+0100), Brian wrote:
>
> > For Exim and minimaldns the question is
> >
> > Does the hostname resolve to a fqdn (something with a dot in it)?
> >
> > 127.0.1.1 alum.anything_you_want
On Thu 12 May 2016 at 20:38:41 (+0100), Brian wrote:
> On Thu 12 May 2016 at 10:08:49 -0500, David Wright wrote:
> > On Thu 12 May 2016 at 11:33:10 (+0100), Brian wrote:
> > > On Wed 11 May 2016 at 14:51:31 -0500, David Wright wrote:
> > > > BTW when will dpkg-reconfigure exim4-config either st
On Thu 12 May 2016 at 10:08:49 -0500, David Wright wrote:
> On Thu 12 May 2016 at 11:33:10 (+0100), Brian wrote:
> > On Wed 11 May 2016 at 14:51:31 -0500, David Wright wrote:
> > >
> > > BTW when will dpkg-reconfigure exim4-config either stop saying
> > > "hostname --fqdn did not return a ful
Hi Don,
Only just seen this!
On 27/10/14 15:31, Don Armstrong wrote:
On Mon, 27 Oct 2014, Paul Duncan wrote:
Thanks very much for that. Purging exim4-config and then doing a complete
apt-get install of exim4 did the trick :-)
For the record, you don't need to purge and reinstall to get back
c
On Mon, 27 Oct 2014, Paul Duncan wrote:
> Thanks very much for that. Purging exim4-config and then doing a complete
> apt-get install of exim4 did the trick :-)
For the record, you don't need to purge and reinstall to get back
configuration files you may have accidentally deleted.
Just use:
UCF
On Mon, 27 Oct 2014 11:32:29 +
Paul Duncan wrote:
Hello Paul,
>Thanks very much for that. Purging exim4-config and then doing a
>complete apt-get install of exim4 did the trick :-)
You're welcome.
Although I was far from sure that it would work, I had my fingers
crossed. :-)
--
Regar
Hi Brad,
Thanks very much for that. Purging exim4-config and then doing a
complete apt-get install of exim4 did the trick :-)
Cheers,
Paul.
On 27/10/14 11:12, Brad Rogers wrote:
On Mon, 27 Oct 2014 10:54:38 +
Paul Duncan wrote:
Hello Paul,
Currently, if I try to do a purge of exim4,
On Mon, 27 Oct 2014 11:12:34 +
Brad Rogers wrote:
Hello,
>is in exim4-config. Try re-installing that.
Should have said "...just that."
--
Regards _
/ ) "The blindingly obvious is
/ _)radnever immediately apparent"
I ain't got no time for intellectual
On Mon, 27 Oct 2014 10:54:38 +
Paul Duncan wrote:
Hello Paul,
>Currently, if I try to do a purge of exim4, this is what happens:
exim4 is a meta-package that pulls in various others. It does not
contain the file you deleted.
A search at https://packages.debian.org/ shows that exim4.conf.t
Frank Van Damme wrote, On 2013-02-19 3:17 AM:
Hi,
most of my Debian serves have an Exim daemon running as satellite to
another server. I'm experiencing delays at the moment and trying to
send mail using the "sendmail" command from the command line, it
appears that the entire process of routing a
On Tue, 19 Feb 2013 12:17:59 +0100
Frank Van Damme wrote:
> Hi,
>
> most of my Debian serves have an Exim daemon running as satellite to
> another server. I'm experiencing delays at the moment and trying to
> send mail using the "sendmail" command from the command line, it
> appears that the ent
On Sat, Sep 22, 2012 at 02:48:38PM -0700, Ross Boylan wrote:
> Third, I'm a bit puzzled by Jon's remarks quoted above. Martin
> recommends using a single, aka monolothic configuration file. Jon says
> "I disagree" but then suggests doing away with the debian framework.
Martin was replying to me.
Joe writes:
> I have to admit to using the single file, as I haven't yet had the
> enthusiasm to go through my old (sarge?) and heavily-customised one to
> break it into the bite-sized conf.d chunks.
Just stay with your own configuration file. Split configurations are evil.
--
Debian testing
On Sat, 22 Sep 2012 14:48:38 -0700
Ross Boylan wrote:
>
> Anyway, you can choose any of 3 approaches to configuration:
> 1. Use the split config in conjunction with the package management
> tools (debconf) to configure exim.
>
> 2. Like 1, but use the monolithic config file. It's not clear to
On Fri, 2012-09-21 at 17:58 +0100, Jon Dowland wrote:
> On Thu, Sep 20, 2012 at 07:10:18PM +0200, Martin Steigerwald wrote:
> > I think its better to configure exim4 for single configuration file by
> > whatever means is described in the wiki page Camaleón linked to, likely an
> >
> > dpkg-reconf
On Thu, Sep 20, 2012 at 07:10:18PM +0200, Martin Steigerwald wrote:
> I think its better to configure exim4 for single configuration file by
> whatever means is described in the wiki page Camaleón linked to, likely an
>
> dpkg-reconfigure exim4something
We differ in our opinion.
In my opinion,
No, I am not, but it is principal.
On Sep 20, 2012 8:48 AM, "Jon Dowland" wrote:
> Do you need split configuration? Are you wedded to it? My advice would be
> to
> copy /var/lib/exim4/config.autogenerated to /etc/exim4.conf, at which
> point the
> Debian exim configuration is overridden, and just
Am Donnerstag, 20. September 2012 schrieb Jon Dowland:
> Do you need split configuration? Are you wedded to it? My advice would
> be to copy /var/lib/exim4/config.autogenerated to /etc/exim4.conf, at
> which point the Debian exim configuration is overridden, and just edit
> that one file instead.
Do you need split configuration? Are you wedded to it? My advice would be to
copy /var/lib/exim4/config.autogenerated to /etc/exim4.conf, at which point the
Debian exim configuration is overridden, and just edit that one file instead.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.
On Tue, 18 Sep 2012 20:46:55 -0400, Mark Robinson wrote:
(please, no html posts, thanks...)
> I know it might not be in the right group but is related mostly with
> Debian.
Nah, this group is perfect but you may also be interested in:
http://lists.alioth.debian.org/mailman/listinfo/pkg-exim4-u
On Tue, Sep 18, 2012 at 08:46:55PM -0400, Mark Robinson wrote:
>I know it might not be in the right group but is related mostly with
>Debian.
>There is Exim 4.72 under Debian with split configuration files.
>I need to remove header and I know how to do in Exim. In section
>remot
Frank Van Damme writes:
> Hello list,
>
> I'm into a slight struggle with my mail servers. They are satellite
> systems (no local mail, everything goes to a smarthost). I figured out
> that by changing the mailname to generaldomain.com instead of
> themachineshostname.generaldomain.com, all users
On Thu, 13 Sep 2012 16:02:22 +0200, Frank Van Damme wrote:
> I'm into a slight struggle with my mail servers. They are satellite
> systems (no local mail, everything goes to a smarthost). I figured out
> that by changing the mailname to generaldomain.com instead of
> themachineshostname.generaldom
On Thu, 03 May 2012 21:53:26 +0100, Tony van der Hoff wrote:
> On 03/05/12 20:55, Camaleón wrote:
>> Does bind9 have any problem with ipv6? I didn't notice, at least in my
>> Lenny servers :-?
>>
> Yes, I think it was discussed on this list. Maybe not bind9, but my
> router can't handle ipv6:
No
On 03/05/12 20:55, Camaleón wrote:
On Thu, 03 May 2012 18:07:05 +0100, Tony van der Hoff wrote:
On 03/05/12 16:52, Camaleón wrote:
(...)
Check you "/etc/hosts" file. You should have this line which enables
the ipv6 loopback interface:
***
::1 localhost ip6-localhost ip6-loopback ***
On Thu, 03 May 2012 18:07:05 +0100, Tony van der Hoff wrote:
> On 03/05/12 16:52, Camaleón wrote:
(...)
>> Check you "/etc/hosts" file. You should have this line which enables
>> the ipv6 loopback interface:
>>
>> ***
>> ::1 localhost ip6-localhost ip6-loopback ***
>
> Yeah, it's commented
On 03/05/12 16:52, Camaleón wrote:
On Wed, 02 May 2012 18:05:56 +0100, Tony van der Hoff wrote:
tony@tony-lx:~$ sudo ifconfig lo
[sudo] password for tony:
loLink encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1 RX p
On Wed, 02 May 2012 18:05:56 +0100, Tony van der Hoff wrote:
> On 02/05/12 17:40, Camaleón wrote:
>>
>> I guess you could configure Exim ("dpkg-reconfigure exim4-config") so
>> that listens only at the desired interfaces (i.e., only to localhost
>> ipv4 -127.0.0.1- instead adding localhost ipv6 -:
On 02/05/12 17:40, Camaleón wrote:
I guess you could configure Exim ("dpkg-reconfigure exim4-config") so
that listens only at the desired interfaces (i.e., only to localhost ipv4
-127.0.0.1- instead adding localhost ipv6 -::1- addresses).
Thanks, everybody, for your answers. Especially this one
On Wed, 02 May 2012 10:17:59 +0100, Tony van der Hoff wrote:
> On my Squeeze box, I am getting occasional panics from Exim, due to port
> 25 being in use. I imagine it's occasionally clashing with Thunderbird:
With Thunderbird? :-?
> exim paniclog /var/log/exim4/paniclog on tony-lx.magpieway.net
On Wed, May 02, 2012 at 11:29:19AM +0200, Jochen Spieker wrote:
> You need to find out the source of the problem. Do you regularly restart
> Exim?
In my experience, with the Debian packaging, this is usually caused by exim
conflicting with itself. I've never figured the problem out entirely, but
On Wed 02 May 2012 at 10:17:59 +0100, Tony van der Hoff wrote:
> What would be the preferred way of overcoming this problem?
Sorting out what the problem is, I suppose. But on the odd occasion it
happens here I just delete paniclog.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.
Tony van der Hoff:
>
> On my Squeeze box, I am getting occasional panics from Exim, due to
> port 25 being in use. I imagine it's occasionally clashing with
> Thunderbird:
Thunderbird / Icedove will never bind to port 25. And even if it wanted
to, listening on ports < 1024 is only allowed for proc
On Mon, 27 Feb 2012 10:43:32 +, Shaun wrote:
> On 26/02/2012 16:13, Camaleón wrote:
>> On Sat, 25 Feb 2012 10:38:41 +, Shaun wrote: So you basically want
>> to change the SMTP greeting?
>
> Yes, but I wanted to give the reason why also. Just in case it changes
> the solution or recommenda
On 26/02/2012 16:13, Camaleón wrote:
> On Sat, 25 Feb 2012 10:38:41 +, Shaun wrote:
> So you basically want to change the SMTP greeting?
Yes, but I wanted to give the reason why also. Just in case it changes
the solution or recommendation.
>> MAIN_HARDCODE_PRIMARY_HOSTNAME='mail.mydomain.com'
On Sat, 25 Feb 2012 10:38:41 +, Shaun wrote:
> I ran my domain through a DNS health checker type site, just to make
> sure I fix any issues. The only 'problem' was that it said the SMTP
> greeting on my MXs doesn't match that listed as the FQDN for the domain.
> That's because I tend to run ma
On Sun, 05 Dec 2010 07:45:28 -1000, Joel Roth wrote:
> On Sun, Dec 05, 2010 at 12:46:08PM +, Camale??n wrote:
>> > Any ideas where to poke around?
>>
>> What makes you think Exim4 is adding a carriage return in the subject
>> line? :-? Does it happen for _all_ the e-mails passing through you
On Sun, Dec 05, 2010 at 12:46:08PM +, Camale??n wrote:
> On Sun, 05 Dec 2010 01:09:58 -1000, Joel Roth wrote:
>
> > The subject line says it all.
> >
> > I think having ^M show up in my mutt display looks dorky, and would like
> > to configure my way out of this, if possible.
> >
> > Any idea
On Sun, 05 Dec 2010 01:09:58 -1000, Joel Roth wrote:
> The subject line says it all.
>
> I think having ^M show up in my mutt display looks dorky, and would like
> to configure my way out of this, if possible.
>
> Any ideas where to poke around?
What makes you think Exim4 is adding a carriage re
On 5/3/10, Camaleón wrote:
> As per "/usr/share/doc/exim4-base/README.Debian.gz" (lenny):
> If you need to support these, set SMTPLISTENEROPTIONS='-oX 465:25 -oP
> var/run/exim4/exim.pid' in /etc/default/exim4
That was it; I needed the -oP option. Thanks.
--
No no no, my fish's name is Eric, E
On Mon, 03 May 2010 10:41:51 -0400, Eric d'Alibut wrote:
> Can exim be made to listen to two ports (587 and 25) on one ip?
>
> I put this in /etc/default/exim4:
>
> SMTPLISTENEROPTIONS='-oX 587:25'
>
> Exim responded by generating a /var/log/exim4/paniclog file containing:
>
> "socket bind() to
On Wed December 9 2009, Tzafrir Cohen wrote:
> > Is how the program works. And one who install it have to know before hand
> > what kind of warning provides.
>
> Right. The fact that the OP asked this question (twice, even) clearly
> demonstrates he did not read the FAQ. In the FAQ you have in ques
On Wed, 09 Dec 2009 13:17:17 -0800, Kevin Ross wrote:
>> > Is this outdated?
>>
>>
>> Well, yes.
>>
>> As per Exim's site, the current verion is 4.71. And "4.69" is "minor"
>> than "4.71" :-)
>
> The version in Lenny is not 4.69, it's 4.69-9, which is different.
I suppose the last digit "-9
On Wed December 9 2009, Tzafrir Cohen wrote:
> Right. The fact that the OP asked this question (twice, even) clearly
> demonstrates he did not read the FAQ. In the FAQ you have in question
> 3.2 (right after question 3.1 with some very frightening text about
> things you should do before considerin
On Wed December 9 2009, Camaleón wrote:
> I don't know how Rkhunter works, but it should be configurable so the
> user can select what kind of warning wants to receive.
there is an rkhunter.conf file, but after looking at "man rkhunter" I didn't
see anything about turning off the messages for cer
On Wed December 9 2009, Camaleón wrote:
> - Rkhunter is just doing its job: it advices you there is a newer version
> available for those packages and that's right. Is up to you upgrading
> them or not.
>
> I, personally, would not take any step :-)
>
>
> No one's fail.
>
> Juts remember that upgr
1 - 100 of 1780 matches
Mail list logo
