Yahoo Groups archive

Milter-greylist

Index last updated: 2026-04-28 23:32 UTC

Thread

RCPT information in X-Greylist: inspected by header is empty

RCPT information in X-Greylist: inspected by header is empty

2015-08-18 by Marcus Schopen

Hi,

RCPT information in "X-Greylist: inspected by ..." header is empty:

Aug 18 13:38:47 mail sm-mta[2685]: t7IBcj35001685: Milter add: header:
X-Greylist: inspected by milter-greylist-4.5.11 (mx.server.com [x.x.x.x]);
Tue, 18 Aug 2015 13:38:47 +0200 (CEST) for IP:'x.x.x.x'
DOMAIN:'smtp.server.com' HELO:'smtp.senderserver.com'
FROM:'sender@...' RCPT:''

Setup is running milter-greylist-4.5.11 with 8.14.4-4.1ubuntu1 on Ubuntu
14.04 LTS. Milter-greylist is running via TCP socket on an internal
machine.

sendmail.mc:
INPUT_MAIL_FILTER(`greylist',`S=inet:12345@scanner, F=, T=S:1m;R:1m')dnl

greylist.conf:
racl continue from /.*/ addheader "X-Greylist: inspected by %V for IP:'%i'
DOMAIN:'%d' HELO:'%h' FROM:'%f' RCPT:'%r'"

Ciao
Marcus

Re: [milter-greylist] RCPT information in X-Greylist: inspected by header is empty

2015-08-19 by Marcus Schopen

Hi,

On Tue, 18 Aug 2015 14:41:25 +0000, "Emmanuel Dreyfus manu@...
[milter-greylist]" <milter-greylist@yahoogroups.com> wrote:
> On Tue, Aug 18, 2015 at 01:50:15PM +0200, Marcus Schopen
> lists-yahoogroups@... [milter-greylist] wrote:
>> RCPT information in "X-Greylist: inspected by ..." header is empty:
> 
> Recipient was <> ?

No, the recipient is not <>. I'm using mimedefang's
md_check_against_smtp_server feature to check if an recipient exists on the
internal Server. But mimedefang is called after milter-greylist and
md_check_against_smtp_server does the check with an empty sender and not
with an empty recipient.

INPUT_MAIL_FILTER(`greylist',`S=inet:12345@internal, F=, T=S:1m;R:1m')dnl
INPUT_MAIL_FILTER(`mimedefang', `S=inet:123457@internal, F=T,
T=S:5m;R:5m;E:10m')dnl
INPUT_MAIL_FILTER(`opendkim',`S=inet:123458@internal, F=, T=S:1m;R:1m')dnl

Ciao!

Re: [milter-greylist] RCPT information in X-Greylist: inspected by header is empty

2016-09-08 by Marcus Schopen

Hi,

On 2015-08-18 13:50, Marcus Schopen lists-yahoogroups@... 
[milter-greylist] wrote:
> Hi,
> 
> RCPT information in "X-Greylist: inspected by ..." header is empty:
> 
> Aug 18 13:38:47 mail sm-mta[2685]: t7IBcj35001685: Milter add: header:
> X-Greylist: inspected by milter-greylist-4.5.11 (mx.server.com
> [x.x.x.x]);
> Tue, 18 Aug 2015 13:38:47 +0200 (CEST) for IP:'x.x.x.x'
> DOMAIN:'smtp.server.com' HELO:'smtp.senderserver.com'
> FROM:'sender@...' RCPT:''
> 
> Setup is running milter-greylist-4.5.11 with 8.14.4-4.1ubuntu1 on
> Ubuntu
> 14.04 LTS. Milter-greylist is running via TCP socket on an internal
> machine.
> 
> sendmail.mc:
> INPUT_MAIL_FILTER(`greylist',`S=inet:12345@scanner, F=,
> T=S:1m;R:1m')dnl
> 
> greylist.conf:
> racl continue from /.*/ addheader "X-Greylist: inspected by %V for
> IP:'%i'
> DOMAIN:'%d' HELO:'%h' FROM:'%f' RCPT:'%r'"


Checking some logs this morning I'd like to come back to above problem 
one year ago. I checked all hosts, where milter-greylist is running. 
After upgrading to version 4.6.1 on some hosts the problem is still 
there and I have an empty rcpt %r value:

mail.log:
---------------------
Sep  8 08:04:14 vorlage1204 milter-greylist: u8863xiF006342: skipping 
greylist because this is the default action, (from=<info@...>, 
rcpt=<ich@...>, addr=[192.168.100.100][192.168.100.100]) ACL 186
Sep  8 08:04:14 vorlage1204 sm-mta[6342]: u8863xiF006342: 
milter=greylist, action=rcpt, continue
Sep  8 08:04:14 vorlage1204 sm-mta[6342]: u8863xiF006342: Milter 
(greylist): time command (R), 0
Sep  8 08:04:16 vorlage1204 sm-mta[6342]: u8863xiF006342: 
milter=greylist, action=data, continue
Sep  8 08:04:16 vorlage1204 sm-mta[6342]: u8863xiF006342: Milter 
(greylist): time command (T), 0
Sep  8 08:04:19 vorlage1204 sm-mta[6342]: u8863xiF006342: 
from=<info@...>, size=6, class=0, nrcpts=1, 
msgid=<201609080604.u8863xiF006342@...>, proto=ESMTP, 
daemon=MTA-v4, relay=[192.168.100.100]
Sep  8 08:04:19 vorlage1204 sm-mta[6342]: u8863xiF006342: Milter 
(greylist): headers, send
Sep  8 08:04:19 vorlage1204 sm-mta[6342]: u8863xiF006342: Milter 
(greylist): headers, sent
Sep  8 08:04:19 vorlage1204 sm-mta[6342]: u8863xiF006342: 
milter=greylist, action=eoh, continue
Sep  8 08:04:19 vorlage1204 sm-mta[6342]: u8863xiF006342: Milter 
(greylist): body, send
Sep  8 08:04:19 vorlage1204 sm-mta[6342]: u8863xiF006342: 
milter=greylist, action=body, continue
Sep  8 08:04:19 vorlage1204 sm-mta[6342]: u8863xiF006342: Milter 
(greylist): body, sent
Sep  8 08:04:19 vorlage1204 sm-mta[6342]: u8863xiF006342: Milter add: 
header: X-Greylist: Default is to whitelist mail, not delayed by 
milter-greylist-4.6.1 (vorlage1204.testdom.de [192.168.100.21]); Thu, 08 
Sep 2016 08:04:19 +0200 (CEST)
Sep  8 08:04:19 vorlage1204 sm-mta[6342]: u8863xiF006342: Milter add: 
header: X-Greylist: inspected by milter-greylist-4.6.1 
(vorlage1204.testdom.de [192.168.100.21]); Thu, 08 Sep 2016 08:04:19 
+0200 (CEST) for IP:'192.168.100.100' DOMAIN:'[192.168.100.100]' 
HELO:'me' FROM:'info@...' RCPT:''
Sep  8 08:04:19 vorlage1204 sm-mta[6342]: u8863xiF006342: Milter accept: 
message
Sep  8 08:04:19 vorlage1204 sm-mta[6343]: u8863xiF006342: 
to=<ich@...>, delay=00:00:05, xdelay=00:00:00, mailer=local, 
pri=30687, dsn=2.0.0, stat=Sent
---------------------

sendmail.mc:
---------------------
define(`confMILTER_LOG_LEVEL', `99')dnl
INPUT_MAIL_FILTER(`greylist',`S=local:/var/run/milter-greylist/milter-greylist.sock, 
F=, T=S:1m;R:1m')dnl
---------------------

This might be the reason why I can't combine a from and rcpt list in a 
ACL (see yesterdays mail "combining from and rcpt lists in one ACL").

Any ideas?

Ciao
Marcus

Re: [milter-greylist] RCPT information in X-Greylist: inspected by header is empty

2016-09-14 by Marcus Schopen

Hi Emmanuel,

On 2016-09-14 05:26, manu@... [milter-greylist] wrote:
> Marcus Schopen lists-yahoogroups@... [milter-greylist]
> <milter-greylist@yahoogroups.com> wrote:
> 
>> Any ideas?
> 
> Do you have {rcpt_addr} in sendmail.cf O Milter.macros.envrcpt?


Thanks for your feedback. Yes, I think I do have set {rcpt_addr}:


grep Milter.macros sendmail.cf:
--------
sendmail.cf:O Milter.macros.connect=j, _, {daemon_name}, {if_name}, 
{if_addr}
sendmail.cf:O Milter.macros.helo={tls_version}, {cipher}, {cipher_bits}, 
{cert_subject}, {cert_issuer}
sendmail.cf:O Milter.macros.envfrom=i, {auth_type}, {auth_authen}, 
{auth_ssf}, {auth_author}, {mail_mailer}, {mail_host}, {mail_addr}
sendmail.cf:O Milter.macros.envrcpt={rcpt_mailer}, {rcpt_host}, 
{rcpt_addr}
sendmail.cf:O Milter.macros.eom={msg_id}
--------


greylist.conf:
--------
[...]
racl continue from /.*/ addheader "X-Greylist: inspected by %V for 
IP:'%i' DOMAIN:'%d' HELO:'%h' FROM:'%f' RCPT:'%r'"
racl whitelist default
--------


Logfile, with milter-greylist 4.6.1, sendmail 8.14.4-2ubuntu2.1:
--------
Sep 14 13:23:00 vorlage1204 sm-mta[2723]: u8EBN0HL002723: Milter 
(greylist): init success to negotiate
Sep 14 13:23:00 vorlage1204 sm-mta[2723]: u8EBN0HL002723: Milter: 
connect to filters
Sep 14 13:23:00 vorlage1204 milter-greylist: GeoIP is not available
Sep 14 13:23:00 vorlage1204 sm-mta[2723]: u8EBN0HL002723: 
milter=greylist, action=connect, continue
Sep 14 13:23:00 vorlage1204 sm-mta[2723]: u8EBN0HL002723: Milter 
(greylist): time command (C), 0
Sep 14 13:23:04 vorlage1204 sm-mta[2723]: u8EBN0HL002723: 
milter=greylist, action=helo, continue
Sep 14 13:23:04 vorlage1204 sm-mta[2723]: u8EBN0HL002723: Milter 
(greylist): time command (H), 0
Sep 14 13:23:10 vorlage1204 sm-mta[2723]: u8EBN0HL002723: Milter: 
sender: <test@...>
Sep 14 13:23:10 vorlage1204 sm-mta[2723]: u8EBN0HL002723: 
milter=greylist, action=mail, continue
Sep 14 13:23:10 vorlage1204 sm-mta[2723]: u8EBN0HL002723: Milter 
(greylist): time command (M), 0
Sep 14 13:23:19 vorlage1204 sm-mta[2723]: u8EBN0HL002723: Milter: rcpts: 
<test@...>
Sep 14 13:23:19 vorlage1204 milter-greylist: u8EBN0HL002723: skipping 
greylist because this is the default action, (from=<test@...>, 
rcpt=<test@...>, addr=[192.168.100.100][192.168.100.100]) ACL 176
Sep 14 13:23:19 vorlage1204 sm-mta[2723]: u8EBN0HL002723: 
milter=greylist, action=rcpt, continue
Sep 14 13:23:19 vorlage1204 sm-mta[2723]: u8EBN0HL002723: Milter 
(greylist): time command (R), 0
Sep 14 13:23:21 vorlage1204 sm-mta[2723]: u8EBN0HL002723: 
milter=greylist, action=data, continue
Sep 14 13:23:21 vorlage1204 sm-mta[2723]: u8EBN0HL002723: Milter 
(greylist): time command (T), 0
Sep 14 13:23:27 vorlage1204 sm-mta[2723]: u8EBN0HL002723: 
from=<test@...>, size=5, class=0, nrcpts=1, 
msgid=<201609141123.u8EBN0HL002723@...>, proto=ESMTP, 
daemon=MTA-v4, relay=[192.168.100.100]
Sep 14 13:23:27 vorlage1204 sm-mta[2723]: u8EBN0HL002723: Milter 
(greylist): headers, send
Sep 14 13:23:27 vorlage1204 sm-mta[2723]: u8EBN0HL002723: Milter 
(greylist): headers, sent
Sep 14 13:23:27 vorlage1204 sm-mta[2723]: u8EBN0HL002723: 
milter=greylist, action=eoh, continue
Sep 14 13:23:27 vorlage1204 sm-mta[2723]: u8EBN0HL002723: Milter 
(greylist): body, send
Sep 14 13:23:27 vorlage1204 sm-mta[2723]: u8EBN0HL002723: 
milter=greylist, action=body, continue
Sep 14 13:23:27 vorlage1204 sm-mta[2723]: u8EBN0HL002723: Milter 
(greylist): body, sent
Sep 14 13:23:27 vorlage1204 sm-mta[2723]: u8EBN0HL002723: Milter add: 
header: X-Greylist: Default is to whitelist mail, not delayed by 
milter-greylist-4.6.1 (vorlage1204.test.de [192.168.100.21]); Wed, 14 
Sep 2016 13:23:27 +0200 (CEST)
Sep 14 13:23:27 vorlage1204 sm-mta[2723]: u8EBN0HL002723: Milter add: 
header: X-Greylist: inspected by milter-greylist-4.6.1 
(vorlage1204.test.de [192.168.100.21]); Wed, 14 Sep 2016 13:23:27 +0200 
(CEST) for IP:'192.168.100.100' DOMAIN:'[192.168.100.100]' HELO:'me' 
FROM:'test@...' RCPT:''
Sep 14 13:23:27 vorlage1204 sm-mta[2723]: u8EBN0HL002723: Milter accept: 
message
Sep 14 13:23:27 vorlage1204 sm-mta[2724]: u8EBN0HL002723: 
to=<test@...>, delay=00:00:08, xdelay=00:00:00, mailer=local, 
pri=30695, dsn=2.0.0, stat=Sent
--------

Don't understand why %r value is missing at the point of inserting the 
X-Greylist header.

Ciao!

Re: [milter-greylist] RCPT information in X-Greylist: inspected by header is empty

2016-09-17 by manu@...

Marcus Schopen lists-yahoogroups@... [milter-greylist]
<milter-greylist@yahoogroups.com> wrote:

> Don't understand why %r value is missing at the point of inserting the
> X-Greylist header.

I looked at the sources. The header addition happens at the DATA stage,
when there is no defined recipient because there may be multiple
recipients.

%r is only valid at RCPT-stage. I see no way of easily fixing this:
should we add multiple headers when we have multiple recipients?

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@...

Re: [milter-greylist] RCPT information in X-Greylist: inspected by header is empty

2016-09-17 by Marcus Schopen

Hi,

On 2016-09-17 09:31, manu@... [milter-greylist] wrote:
> Marcus Schopen lists-yahoogroups@... [milter-greylist]
> <milter-greylist@yahoogroups.com> wrote:
> 
>> Don't understand why %r value is missing at the point of inserting the
>> X-Greylist header.
> 
> I looked at the sources. The header addition happens at the DATA stage,
> when there is no defined recipient because there may be multiple
> recipients.

Hmmm, in the tests I just had one single rcpt.

> %r is only valid at RCPT-stage. I see no way of easily fixing this:
> should we add multiple headers when we have multiple recipients?


Good question, might be helpful ...

Ciao
Marcus

Re: [milter-greylist] RCPT information in X-Greylist: inspected by header is empty

2016-09-17 by manu@...

Marcus Schopen lists-yahoogroups@... [milter-greylist]
<milter-greylist@yahoogroups.com> wrote:

> > I looked at the sources. The header addition happens at the DATA stage,
> > when there is no defined recipient because there may be multiple
> > recipients.
> 
> Hmmm, in the tests I just had one single rcpt.

Sure, but this is a general problem: at DATA-stage, there is no such
concept as "the unique recipent".

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@...

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.