Stefan Bauer:
> Jan 25 15:31:14 mx2 postfix/smtpd[10117]: NOQUEUE: reject: RCPT from
> opsmail.colo.comodo.com[91.209.196.133]: 550 5.1.1
> <webmas...@domain.tld: Recipient address rejected: undeliverable
> address: host IP[IP] said: 550 5.1.1 <webmas...@domain.tld: Recipient
> address rejected: User unknown in virtual mailbox table (in reply to
> RCPT TO command); from=<no_reply_supp...@trust-provider.com>
> to=<webmas...@domain.tld proto=ESMTP
> helo=<mcmail3.mcr.colo.comodo.net>
> Jan 25 15:31:14 mx2 postfix/smtp[10124]: 2CFE27E3A2:
> to=<webmas...@domain.tld, relay=IP[IP]:25, delay=0.25,
> delays=0/0.01/0.21/0.03, dsn=2.1.5, status=deliverable (250 2.1.5 Ok)
The second logfile record shows that a new probe was sent with queue
ID 2CFE27E3A2 (the old result had expired, or it was older than
half the expiration time), and the probe result was 'deliverable'.
If the old result was expired, then it would be a surprise that the
expired result was returned to smtpd. Normally, an expired result
is supposed to be ignored, as if the result did not exist.
If the result was older than half the expiration time but not
expired, then it would be OK to return the old probe result to
smtpd.
> I dont see a veify request at 15:31 at the remote site. why is postfix
> still caching verify results but report instead after client was
> rejected, that the address is deliverable?
The probe had queue ID 2CFE27E3A2. Look in your mail logfile.
Wietse
