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
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
can you provide
exim -bP | grep syslog
syslog_duplication
syslog_facility =
syslog_pid
syslog_processname = exim
syslog_timestamp
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
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
+tls_certificate_verified +tls_peerdn
exim writes directly to the logfiles. If you get the error almost every
day it can be because of the rotation.
This error appears everyday. I boot my machine every morning at 6 am.
I don't know it exim provide a reload command, so try
systemctl reload exim4-base
systemctl
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 logf
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
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:
Hi,
Running Debian bookworm fully updated.
Since a couple of weeks, i see strange lines in the logs:
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
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)
>
onnect mail.easthope.ca:465
After the certificate stuff, you should then see lines like:
...
And you carry on from there with:
AUTH PLAIN encodedstring
The test message was transmitted. Good!
(1) Section 1. in
https://www.exim.org/exim-html-current/doc/html/spec_h
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
usly broken here?
Before trying the interactive process, checked a bunch of details
including instructions in https://wiki.debian.org/Exim. Generated
fresh /etc/exim4/exim.crt and /etc/exim4/exim.key.
Requested delivery of the last message in the queue.
$ exim -M 1pgCEl-00010a
ing is the output from running the echo…base64
command. Note that it's sent encrypted.
Unlike the test of exim that you conducted with:
> root@dalton:/home/root# exim -bh 142.103.107.137.465
this one will send a real email, which you should get back as
recipient. This will be testing your new
← that's a blank line
Hand written test 01
.← that's nothing but a fullstop
Return
quit
root@dalton:/home/root# exim -bh 142.103.107.137.465
SMTP testing session as if from host 142.103.107.137
but without any ident (RF
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@da
Hi,
In case this message is duplicated, apology in advance.
After configuring exim for a new smarthost, message sending fails.
This might help to identify the problem.
root@dalton:/home/root# exim -bh 142.103.1m.1n
SMTP testing session as if from host 142.103.1m.1n
but without any
Hoi Geert en anderen,
Op 28-08-2022 om 12:51 schreef Geert Stappers:
On Sun, Aug 28, 2022 at 09:44:09AM +0200, Gijs Hillenius wrote:
Ik zit nu naar Unbound te kijken. Dat lijkt minder complex? Is dit
*echt* alles ?
Ha Geert
Ik, tien dagen terug:
>> >> Mijn exim4.conf.templat bevat
>> >> .ifndef CHECK_RCPT_IP_DNSBLS
>> >> CHECK_RCPT_IP_DNSBLS = \
>> >> cbl.abuseat.org : \
>> >> virbl.dnsbl.bit.nl : \
>> >> zen.spamhaus.org
>> >> .endif
mijn posts op de lijst (hieronder)
.255.254: Error: open resolver;
>>>> https://www.spamhaus.org/returnc/pub/2400:cb00:71:1024::a29e:52ca)
>>>
>>> Je gebruikt wellicht de verkeerde DNS, let op dat "open resolver":
>>>
>>> https://www.spamhaus.com/resource-center/if-you-query
://www.spamhaus.org/returnc/pub/2400:cb00:71:1024::a29e:52ca)
Je gebruikt wellicht de verkeerde DNS, let op dat "open resolver":
https://www.spamhaus.com/resource-center/if-you-query-spamhaus-projects-dnsbls-via-cloudflares-dns-move-to-the-free-data-query-service/
Jij gebruikt blijkbaar Exim, dat ken
/pub/2400:cb00:71:1024::a29e:52ca)
> >
> > Je gebruikt wellicht de verkeerde DNS, let op dat "open resolver":
> >
> > https://www.spamhaus.com/resource-center/if-you-query-spamhaus-projects-dnsbls-via-cloudflares-dns-move-to-the-free-data-query-service/
> >
PT
>> : 209.51.188.17 is listed at cbl.abuseat.org
>> (127.255.255.254: Error: open resolver;
>> https://www.spamhaus.org/returnc/pub/2400:cb00:71:1024::a29e:52ca)
>
> Je gebruikt wellicht de verkeerde DNS, let op dat "open resolver":
>
> https://www.spamhaus.com/resou
dat "open resolver":
https://www.spamhaus.com/resource-center/if-you-query-spamhaus-projects-dnsbls-via-cloudflares-dns-move-to-the-free-data-query-service/
Jij gebruikt blijkbaar Exim, dat ken ik niet zo goed. Ik gebruik
Postfix, belangrijk daarbij is dat je na wijzigen DNS Postfix echt
On Fri, Aug 26, 2022 at 12:51:52PM +0200, Gijs Hillenius wrote:
> >>
> >> Via het fediverse wees iemand me op:
> >> https://github.com/spamhaus/spamassassin-dqs
> >
> > Uit de README.md van die URL:
> >
> > | What is DQS?
> > |
> > | Data Query Service (DQS) is a set of DNSBLs, updated in
[...] grote knip
>>
>> Via het fediverse wees iemand me op:
>> https://github.com/spamhaus/spamassassin-dqs
>
> Uit de README.md van die URL:
>
> | What is DQS?
> |
> | Data Query Service (DQS) is a set of DNSBLs, updated in real-time,
> | operated by Spamhaus Technology
>
>> Heeft
gt; Ik heb het hele block maar even uitgezet.
>
> Via het fediverse wees iemand me op:
> https://github.com/spamhaus/spamassassin-dqs
Uit de README.md van die URL:
| What is DQS?
|
| Data Query Service (DQS) is a set of DNSBLs, updated in real-time,
| operated by Spamhaus Techno
aring met die plugin?
Mijn vraag: maakt deze plugin het overbodig om in Exim te wijzen naar
Spamhaus?
Ik dee wat tests, en die gaan "fout" waarbij Spamhaus met vertelt:
This email was delivered, but should have been rejected during the
SMTP session. Your MX is not configured to use SMP
On Thu, 18 Aug 2022 12:20:23 +0200
Gijs Hillenius wrote:
> Mijn exim4.conf.templat bevat
>
> .ifndef CHECK_RCPT_IP_DNSBLS
> CHECK_RCPT_IP_DNSBLS = \
> cbl.abuseat.org : \
> virbl.dnsbl.bit.nl : \
> zen.spamhaus.org
> .endif
Volgens mij is virbl.dnsbl.bit.nl al jaren
Mijn exim4.conf.templat bevat
.ifndef CHECK_RCPT_IP_DNSBLS
CHECK_RCPT_IP_DNSBLS = \
cbl.abuseat.org : \
virbl.dnsbl.bit.nl : \
zen.spamhaus.org
.endif
maar .. ik krijg het idee dat deze regels achterhaald zijn.
die eerste (cbl) is blijkbaar al een paar jaar terug
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
-rc.d is the correct tool and it should even take care of
> synchronizing state between systemd and sysv-rc.
Hmm. Well, I suppose it's possible, especially if the OP kept using the
wrong filename (exim vs. exim4).
I still wouldn't care to try it, personally. Knowing that it's a native
init
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
ng up
> > one of the automatically converted init.d scripts. If so, this will
> > be made clear in the systemctl status report.
>
> ● exim4.service - LSB: exim Mail Transport Agent
>Loaded: loaded (/etc/init.d/exim4; generated)
>Active: active (running) since Wed 2021-0
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
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, b
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
:
> > > 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?
unicorn:~$ man update-rc.d | grep exim
unicorn:~$ man 8 update-rc.d | grep exim
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
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
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 Deb
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
>>>
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
> >
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
> > >
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?,
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?
>
&
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 e
I use either exim or another MTA. When I want to use the other MTA,
"update-rc.d -f exim remove" does not remove exim from "ps eax" after
today's exim update.
Searching for exim in /etc/systemd/system/multi-user.target.wants/*
and /lib/systemd/system/* yields nothing.
How
Dat volgt, wellicht.
condition = ${run{/usr/bin/spfquery -v 1 --ip \"$sender_host_address\" -s
\"$sender_address\" --helo-id \"$sender_helo_name\"}\
{no}{${if eq {$runrc}{1}{yes}{no
On 17 June 2020 09:57 Gijs Hillenius, wrote:
> Goedenmor
Goedenmorgen
Is er hier iemand die Debian's Exim macro's kan spellen?
Al jaren terug stelde ik de standaard regeltjes voor SPF in, maar het
val me nu pas op dat de check altijd "none" oplevert.
Kan iemand die regel met me meelezen? Is het omdat de query meer
teruggeeft dan 1 woord
# Générer un certificat :
sudo bash /usr/share/doc/exim4-base/examples/exim-gencert
[*] Creating a self signed SSL certificate for Exim!
This may be sufficient to establish encrypted connections but for
secure identification you need to buy a real certificate!
Please enter
Bonjour,
Je cherche à loguer les mails que j'envoie depuis le terminal, avec la
commande mail.
J'utilise Exim et Rsyslog.
Mon fichier de log mail.log reste vide.
Je suppose que les droits propriétaires sont les bons sur mon fichier
mail.log ( root:adm ).
Si quelqu'un a une configuration
Rainer Dorsch wrote:
> Am Montag, 18. Mai 2020, 19:58:06 CEST schrieb Dan Ritter:
> > Rainer Dorsch wrote:
> > I think you're overcomplicating it.
> >
> > Your domain can and should have two or more MX records, with
> > different priority levels. The MX records don't even have to
> > point to
On Tue, May 19, 2020 at 05:10:33PM +0200, Rainer Dorsch wrote:
> Just curious, if I have multiple MX records, how would you sync the incoming
> emails (*) ? I can see with an NFS mounted home directory with Maildir
> mailboxes that could work and dovecot could probably run on multiple hosts
>
Am Montag, 18. Mai 2020, 19:58:06 CEST schrieb Dan Ritter:
> Rainer Dorsch wrote:
> > Hi,
> >
> > I am just wondering how a efficient setup for TLS/DNS for exim looks like:
> >
> > Right now I have an A entry in the DNS server for smtp. and a
> > letsenc
oose the very simplest systems, they can be
> > > configured to look up the MX record and use that. (Postfix has a
> > > fallback_relay option, Exim can accept multiple hosts in a
> > > route_list statement, and so forth.)
> >
> > Thanks again for your reply.
> >
; > understand that they can make use of the MX record).
> >
> > It depends on the MTA you choose for your email clients, but
> > unless you choose the very simplest systems, they can be
> > configured to look up the MX record and use that. (Postfix has
concerned about the outgoing server configured in the email
> > clients and used to send main from my domain (at least so far I did not
> > understand that they can make use of the MX record).
>
> It depends on the MTA you choose for your email clients, but
> unless you c
they can make use of the MX record).
It depends on the MTA you choose for your email clients, but
unless you choose the very simplest systems, they can be
configured to look up the MX record and use that. (Postfix has a
fallback_relay option, Exim can accept multiple hosts in a
route_list state
Am Montag, 18. Mai 2020, 19:58:06 CEST schrieb Dan Ritter:
> Rainer Dorsch wrote:
> > Hi,
> >
> > I am just wondering how a efficient setup for TLS/DNS for exim looks like:
> >
> > Right now I have an A entry in the DNS server for smtp. and a
> > letsenc
Rainer Dorsch wrote:
> Hi,
>
> I am just wondering how a efficient setup for TLS/DNS for exim looks like:
>
> Right now I have an A entry in the DNS server for smtp. and a
> letsencrypt certificate as well.
>
> If I setup a new server and call it SMTP2, I need to
Hi,
I am just wondering how a efficient setup for TLS/DNS for exim looks like:
Right now I have an A entry in the DNS server for smtp. and a
letsencrypt certificate as well.
If I setup a new server and call it SMTP2, I need to reconfigure this in all my
email clients. If I install the SMTP
On Sat 17 Aug 2019 at 07:20:45 (-), Curt wrote:
> On 2019-08-16, Greg Wooledge wrote:
> > On Fri, Aug 16, 2019 at 02:20:09PM -0500, David Wright wrote:
> >> AIUI exim should be able to deliver emails into a user's mbox, but
> >> I'm confused about how exim is meant
On 2019-08-16, Greg Wooledge wrote:
> On Fri, Aug 16, 2019 at 02:20:09PM -0500, David Wright wrote:
>> AIUI exim should be able to deliver emails into a user's mbox, but
>> I'm confused about how exim is meant to do that, because it runs as
>> user Debian-exim, bu
On Fri, Aug 16, 2019 at 02:20:09PM -0500, David Wright wrote:
> AIUI exim should be able to deliver emails into a user's mbox, but
> I'm confused about how exim is meant to do that, because it runs as
> user Debian-exim, but mailbox permissions are normally group:mail.
I don't know m
AIUI exim should be able to deliver emails into a user's mbox, but
I'm confused about how exim is meant to do that, because it runs as
user Debian-exim, but mailbox permissions are normally group:mail.
For example, with exim4 on hostR set up as …
internet site; mail is sent and received
ho wants to scan for this vulnerability is
just going to buy access to a list of every host on the Internet
that has an open port 25, maybe an open port 25 running the
vulnerable versions of Exim if that is offered. That will be a very
manageable list of IPs. They won't have to do the scanning
themselves.
This is o
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?
>
-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.
A
15.227.108108-227-15-51.rev.cloud.scaleway.com.
> 1051.77.148.55 55.ip-51-77-148.eu.
> 1185.58.114.228228.pool85-58-114.dynamic.orange.es.
> 1289.248.171.57scanner20.openportstats.com.
> 1398.158.184.125 206.217.215.125.static.midphase.com.
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?
Reco
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
>
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-
>
> > # rgrep banner /etc/exim4/
> > /etc/exim4/conf.d/main/02_exim4-config_options:# smtp_banner =
> > $smtp_active_hostname ESMTP Exim $version_number $tod_full
> > /etc/exim4/exim4.conf.template:# smtp_banner =
> > $smtp_active_hostname ESMTP Exim $version_numb
od of outsiders trying to pound on and
>> exploit the server? Even though they won't be able to do
>> successfully due to up to date patch status.
>
> # rgrep banner /etc/exim4/
> /etc/exim4/conf.d/main/02_exim4-config_options:# smtp_banner =
> $smtp_active_hostname ESMTP Exim $ver
-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 exim
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-do
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/sec
cessfully due to up to
> date patch status.
# rgrep banner /etc/exim4/
/etc/exim4/conf.d/main/02_exim4-config_options:# smtp_banner =
$smtp_active_hostname ESMTP Exim $version_number $tod_full
/etc/exim4/exim4.conf.template:# smtp_banner = $smtp_active_hostname ESMTP Exim
$version_numbe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
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.
$ telnet mail.example.org 25
Trying ip_add_re_ss...
Connected
On 2019-06-10, Greg Wooledge wrote:
> On Sat, Jun 08, 2019 at 04:50:06PM -, Curt wrote:
>> https://lwn.net/Articles/790553/
>>
>> I was actually going to point to another article on the subject, but as
>> it revealed the exact modus operandi for the (local) exploit (which is
>> trivial to an
On Sat, Jun 08, 2019 at 04:50:06PM -, Curt wrote:
> https://lwn.net/Articles/790553/
>
> I was actually going to point to another article on the subject, but as
> it revealed the exact modus operandi for the (local) exploit (which is
> trivial to an extreme) I thought better of it.
https://lwn.net/Articles/790553/
I was actually going to point to another article on the subject, but as
it revealed the exact modus operandi for the (local) exploit (which is
trivial to an extreme) I thought better of it.
--
“Decisions are never really made – at best they manage to emerge,
ted-linux-server
Хоча там питання поставлене більш широко.
> Я якось після сендмейла з разу на постфікс перескочив. Нічим не можу допомогти
Насправді питання не стільки про exim, скільки про те як назначити
hostname. Але не як це робиться, а який варіант обрати. Я перед цим
пробував ставити бі
Доброго дня.
Я так зрозумів, що чомусь вважається, що FQDN хоста має бути обов'язково
прописаний в /etc/hosts, звідки exim його і візьме.
Але не рекомендується то не значить заборонено.
P.S.: Ти диви... А я вважав що тут взагалі нікого не буває :)
З повагою,
Якимчук Сергій
03.04.2019
Я якось після сендмейла з разу на постфікс перескочив. Нічим не можу
допомогти
Many thanks,
Serge
On Wed, Apr 3, 2019 at 10:34 AM Nazar Zhuk wrote:
> Привіт,
>
> On 4/1/19 10:30 AM, Yuri Kanivetsky wrote:
> > Усім привіт.
> >
> > То лист undead чи half-life? :)
> >
Привіт,
On 4/1/19 10:30 AM, Yuri Kanivetsky wrote:
Усім привіт.
То лист undead чи half-life? :)
https://lists.debian.org/debian-user-ukrainian/2006/11/msg1.html
Тепер нас тут двоє.
Краще спробую поставити питання...
Нажаль не знаю відповіді. Якщо потрібно, можу перекласти на
, що вони мають на увазі що міняючи домен
з якого відправляється пошта (From), треба буде не забути поміняти
primary_hostname. Але це начебто може максимум вплинути на те, чи
листи будуть роспізнані як спам (SpamAssassin score). І то не факт. Чи
є якісь додаткові міркування?
Далі, припустимо що я
ned
> >
> > No estoy usando ipv6
> >
> >
> > El dom., 24 mar. 2019 a las 10:59, Gerardo Diez (<
> >
> > gerardo.diez.gar...@gmail.com>) escribió:
> > > El dom., 24 mar. 2019 14:53, Fernando Romero
> > >
> > > escribió
9 a las 10:59, Gerardo Diez (<
>
> gerardo.diez.gar...@gmail.com>) escribió:
> > El dom., 24 mar. 2019 14:53, Fernando Romero
> >
> > escribió:
> >> Hola como están.
> >> Estoy corriendo debian 9 como servidor de correo con exim, funcionaba
> >> perfecto has
Fernando Romero
> escribió:
>
>> Hola como están.
>> Estoy corriendo debian 9 como servidor de correo con exim, funcionaba
>> perfecto hasta que quise habilitar ssl.
>> Ahí ya me dejo de autentificar, tanto por smtp como por ssl, este es el
>> error que me ap
1 - 100 of 8098 matches
Mail list logo
