No delay warnings although delay_warning_time is set?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
14 messages Options
Reply | Threaded
Open this post in threaded view
|

No delay warnings although delay_warning_time is set?

Ralph Seichter-10
I'm trying to get Postfix to send warnings for delayed mail in a setup
which includes two Postfix services on one LAN server (one for inbound
mail, one for outbound mail) and two external relayhosts through which
all outbound mail is routed. The LAN machine listens on two IP addresses
and is known to DNS as 'mailhub' [192.168.101.7] and 'mailhub-out'
[192.168.101.8], respectively.

When outbound mail is sent to an email address with an invalid domain
(i.e. [hidden email]), the relayhosts both respond with

  450 4.1.2 <[hidden email]>: Recipient address rejected: Domain not found

and "mailq -C /etc/postfix-out" shows that the mail is still queued,
just es expected with a temporary error 450. Postfix keeps on trying to
deliver the mail, which is fine, but the sender of the queued mail is
never notified that there has been a delay. I thought that setting the
parameter delay_warning_time was enough the have delay notifications
sent. Is there anything else I need to do?

Here are the configurations for the two LAN Postfix services. If you
need logs or master.cf aswell, please let me know.

  # postconf -c /etc/postfix -n
  alias_database = hash:/etc/aliases
  alias_maps = hash:/etc/aliases
  alternate_config_directories = /etc/postfix-out
  authorized_flush_users = hash:/etc/postfix/admins
  authorized_mailq_users = $authorized_flush_users
  command_directory = /usr/sbin
  config_directory = /etc/postfix
  content_filter = amavisd:127.0.0.1:10024
  daemon_directory = /usr/lib/postfix
  data_directory = /var/lib/postfix
  debug_peer_level = 2
  delay_warning_time = 10m
  disable_vrfy_command = yes
  home_mailbox = .maildir/
  html_directory = /usr/share/doc/packages/postfix/html
  inet_interfaces = $myhostname, localhost
  local_recipient_maps = proxy:unix:passwd.byname $alias_maps
  mail_owner = postfix
  mailq_path = /usr/bin/mailq
  manpage_directory = /usr/share/man
  masquerade_domains = $mydomain
  message_size_limit = 43000000
  mydestination = $myhostname, localhost.$mydomain, [192.168.101.7], [more domain names]
  myhostname = mailhub.domain.tld
  mynetworks = 127.0.0.0/8, 192.168.100.0/24, 192.168.101.0/24
  myorigin = $mydomain
  newaliases_path = /usr/bin/newaliases
  queue_directory = /var/spool/postfix
  readme_directory = /usr/share/doc/packages/postfix/readme
  sendmail_path = /usr/sbin/sendmail
  setgid_group = postdrop
  smtp_fallback_relay = [fallback-relay.domain.tld]
  smtp_sasl_auth_enable = yes
  smtp_sasl_password_maps = hash:/etc/postfix/saslpw
  smtp_sasl_security_options = noanonymous
  smtp_tls_CAfile = /etc/horus-ca.pem
  smtp_tls_loglevel = 1
  smtp_tls_note_starttls_offer = yes
  smtp_use_tls = yes
  smtpd_banner = $myhostname ESMTP
  transport_maps = hash:/etc/postfix/transport
  unknown_local_recipient_reject_code = 550

  root@mailhub (19) /etc/postfix-out # postconf -c /etc/postfix-out -n
  alias_database = hash:/etc/aliases
  alias_maps = hash:/etc/aliases
  authorized_flush_users = hash:/etc/postfix/admins
  authorized_mailq_users = $authorized_flush_users
  command_directory = /usr/sbin
  config_directory = /etc/postfix-out
  content_filter = amavisd:127.0.0.1:11024
  daemon_directory = /usr/lib/postfix
  data_directory = /var/lib/postfix-out
  debug_peer_level = 2
  delay_warning_time = 10m
  disable_vrfy_command = yes
  home_mailbox = .maildir/
  html_directory = /usr/share/doc/packages/postfix/html
  inet_interfaces = $myhostname
  local_recipient_maps = proxy:unix:passwd.byname $alias_maps
  mail_owner = postfix
  mailq_path = /usr/bin/mailq
  manpage_directory = /usr/share/man
  masquerade_domains = $mydomain
  message_size_limit = 43000000
  mydestination = $myhostname, localhost.$mydomain, [192.168.101.8], [more domain names]
  myhostname = mailhub-out.domain.tld
  mynetworks = 127.0.0.0/8, 192.168.100.0/24, 192.168.101.0/24
  myorigin = $mydomain
  newaliases_path = /usr/bin/newaliases
  queue_directory = /var/spool/postfix-out
  readme_directory = /usr/share/doc/packages/postfix/readme
  sendmail_path = /usr/sbin/sendmail
  setgid_group = postdrop
  smtp_fallback_relay = [fallback-relay.domain.tld]
  smtp_sasl_auth_enable = yes
  smtp_sasl_password_maps = hash:/etc/postfix/saslpw
  smtp_sasl_security_options = noanonymous
  smtp_tls_CAfile = /etc/horus-ca.pem
  smtp_tls_loglevel = 1
  smtp_tls_note_starttls_offer = yes
  smtp_use_tls = yes
  smtpd_banner = $myhostname ESMTP
  syslog_name = postfix-out
  transport_maps = hash:/etc/postfix/transport
  unknown_local_recipient_reject_code = 550

  # cat /etc/postfix/transport
  * :[relay.domain.tld]

BTW, I know that a delay_warning_time of 10 minutes is way too short, I
use it only for testing. I tried different values up to 4 hours, but the
results where the same.

Thanks for your help!

-R
Reply | Threaded
Open this post in threaded view
|

Re: No delay warnings although delay_warning_time is set?

Wolfgang Zeikat
Hi,

On 22.05.2008 13:25, Ralph Seichter wrote:

> and "mailq -C /etc/postfix-out" shows that the mail is still queued,

>   # postconf -c /etc/postfix -n

could it be that you have two main.cf files, one in /etc/postfix-out/
and a different one in /etc/postfix/ - and you showed the postconf
output for the latter?

In other words: could it be you need to configure the delay_warning_time
in /etc/postfix-out/main.cf?

Regards,

wolfgang



Reply | Threaded
Open this post in threaded view
|

Re: No delay warnings although delay_warning_time is set?

Ralph Seichter-10
* Wolfgang Zeikat:

> could it be that you have two main.cf files, one in /etc/postfix-out/
> and a different one in /etc/postfix/ - and you showed the postconf
> output for the latter?

Please have a look at my previous message again. You will find that I
included configuration information from both /etc/postfix-out and
/etc/postfix. Each of the main.cf files in these directories contains
the line "delay_warning_time = 10m".

-R
Reply | Threaded
Open this post in threaded view
|

Re: No delay warnings although delay_warning_time is set?

Wietse Venema
In reply to this post by Ralph Seichter-10
Ralph Seichter:
> I'm trying to get Postfix to send warnings for delayed mail in a setup
> which includes two Postfix services on one LAN server (one for inbound
> mail, one for outbound mail) and two external relayhosts through which
> all outbound mail is routed. The LAN machine listens on two IP addresses
> and is known to DNS as 'mailhub' [192.168.101.7] and 'mailhub-out'
> [192.168.101.8], respectively.
..
>   delay_warning_time = 10m
>   delay_warning_time = 10m

These changes take effect only for new mail. They have  no effect on
mali that is already in the queue.

        Wietse
Reply | Threaded
Open this post in threaded view
|

Re: No delay warnings although delay_warning_time is set?

Ralph Seichter-10
* Wietse Venema:

> These changes take effect only for new mail. They have no effect on
> mali that is already in the queue.

Sorry, I should have described what I did during testing more detailed:
I set delay_warning_time to a couple of different values, used "postfix
reload" to have the changes activated, cleared the mail queue of old
messages and then sent new email to [hidden email]. So far, I have not
received any delayed mail notifications.

-R
Reply | Threaded
Open this post in threaded view
|

Re: No delay warnings although delay_warning_time is set?

Victor Duchovni
On Thu, May 22, 2008 at 09:37:17PM +0200, Ralph Seichter wrote:

> * Wietse Venema:
>
> > These changes take effect only for new mail. They have no effect on
> > mali that is already in the queue.
>
> Sorry, I should have described what I did during testing more detailed:
> I set delay_warning_time to a couple of different values, used "postfix
> reload" to have the changes activated, cleared the mail queue of old
> messages and then sent new email to [hidden email]. So far, I have not
> received any delayed mail notifications.

Then either no mail was delayed, or your tests are flawed. Delay warnings
work as documented.

    2008-05-22T13:19:23-0400 amnesiac postfix/smtpd[3179]: AD6F448011:
    client=unknown[192.0.2.1]
    ...
    2008-05-22T14:36:06-0400 amnesiac postfix/smtp[20575]: AD6F448011:
    to=<[hidden email]>, relay=none, delay=4603, delays=4573/0/30/0,
        dsn=4.4.1, status=deferred (connect to mx.example.com[192.0.2.2]:25:
        Connection timed out)
    2008-05-22T15:46:06-0400 amnesiac postfix/smtp[11787]: AD6F448011:
    to=<[hidden email]>, relay=none, delay=8802, delays=8772/0/30/0,
        dsn=4.4.1, status=deferred (connect to mx.example.com[192.0.2.2]:25:
        Connection timed out)
    2008-05-22T15:46:06-0400 amnesiac postfix/bounce[14516]: AD6F448011:
    sender delay notification: 2617A4847E

I have a delay warning of 2 hours, this fired off a notice after the first
failure that was 2 hours after the message was queued.

--
        Viktor.

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.

To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
<mailto:[hidden email]?body=unsubscribe%20postfix-users>

If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.
Reply | Threaded
Open this post in threaded view
|

Re: No delay warnings although delay_warning_time is set?

Ralph Seichter-10
* Victor Duchovni:

> Then either no mail was delayed, or your tests are flawed.
> Delay warnings work as documented.

There are definitely delayed messages, as logs and mailq show.

I maintain a number of Postfix servers, and delay warnings usually work
fine. I don't suspect an error in Postfix, but rather some mistake in
the way I configured things (one physical machine with two instances of
postfix). Do you have any suggestions on how to better test/debug this
setup?

-R
Reply | Threaded
Open this post in threaded view
|

Re: No delay warnings although delay_warning_time is set?

Victor Duchovni
On Fri, May 23, 2008 at 12:58:14PM +0200, Ralph Seichter wrote:

> * Victor Duchovni:
>
> > Then either no mail was delayed, or your tests are flawed.
> > Delay warnings work as documented.
>
> There are definitely delayed messages, as logs and mailq show.
>
> I maintain a number of Postfix servers, and delay warnings usually work
> fine. I don't suspect an error in Postfix, but rather some mistake in
> the way I configured things (one physical machine with two instances of
> postfix). Do you have any suggestions on how to better test/debug this
> setup?

Look at queued files with "postcat". In the envelope section of a message
that is not yet too old:

    ...
    named_attribute: client_address_type=2
    warning_message_time: Fri May 23 11:48:58 2008
    ...

and one that is:

    ...
    named_attribute: client_address_type=2
    warning_message_time: Wed Dec 31 19:00:00 1969
    ...

if the record is always missing or present and 12 AM GMT Jan 1 1970 you
are not configuring delay warnings correctly. The record is added by
the cleanup daemon.

--
        Viktor.

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.

To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
<mailto:[hidden email]?body=unsubscribe%20postfix-users>

If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.
Reply | Threaded
Open this post in threaded view
|

Re: No delay warnings although delay_warning_time is set?

Wietse Venema
In reply to this post by Ralph Seichter-10
Ralph Seichter:

> * Wietse Venema:
>
> > These changes take effect only for new mail. They have no effect on
> > mali that is already in the queue.
>
> Sorry, I should have described what I did during testing more detailed:
> I set delay_warning_time to a couple of different values, used "postfix
> reload" to have the changes activated, cleared the mail queue of old
> messages and then sent new email to [hidden email]. So far, I have not
> received any delayed mail notifications.

Obviously, things are not configured in the way you describe,
so instead of an eyewitness report, actual concrete logging,
postconf -n, and master.cf would be more suitable.

        Wietse
Reply | Threaded
Open this post in threaded view
|

Re: No delay warnings although delay_warning_time is set?

Ralph Seichter-10
* Wietse Venema:

> Obviously, things are not configured in the way you describe,
> so instead of an eyewitness report, actual concrete logging,
> postconf -n, and master.cf would be more suitable.

I included two "postconf -f" outputs in my original message; please see
<http://archives.neohapsis.com/archives/postfix/2008-05/1146.html>. Here
are the contents of the corresponding master.cf files:

  # grep -v '^#' /etc/postfix/master.cf
  smtp      inet  n       -       n       -       -       smtpd
  pickup    fifo  n       -       n       60      1       pickup
  cleanup   unix  n       -       n       -       0       cleanup
  qmgr      fifo  n       -       n       300     1       qmgr
  tlsmgr    unix  -       -       n       1000?   1       tlsmgr
  rewrite   unix  -       -       n       -       -       trivial-rewrite
  bounce    unix  -       -       n       -       0       bounce
  defer     unix  -       -       n       -       0       bounce
  trace     unix  -       -       n       -       0       bounce
  verify    unix  -       -       n       -       1       verify
  flush     unix  n       -       n       1000?   0       flush
  proxymap  unix  -       -       n       -       -       proxymap
  smtp      unix  -       -       n       -       -       smtp
  relay     unix  -       -       n       -       -       smtp
   -o fallback_relay=
  showq     unix  n       -       n       -       -       showq
  error     unix  -       -       n       -       -       error
  retry     unix  -       -       n       -       -       error
  discard   unix  -       -       n       -       -       discard
  local     unix  -       n       n       -       -       local
  virtual   unix  -       n       n       -       -       virtual
  lmtp      unix  -       -       n       -       -       lmtp
  anvil     unix  -       -       n       -       1       anvil
  scache    unix  -       -       n       -       1       scache
  proxywrite unix -       -       n       -       1       proxymap
  amavisd   unix   -      -       n       -       2       smtp
   -o smtp_data_done_timeout=1200
   -o disable_dns_lookups=yes
  127.0.0.1:10025 inet  n -       n       -       -       smtpd
   -o content_filter=
   -o local_recipient_maps=
   -o smtpd_helo_restrictions=
   -o smtpd_client_restrictions=
   -o smtpd_sender_restrictions=
   -o smtpd_recipient_restrictions=permit_mynetworks,reject
   -o mynetworks=127.0.0.0/8

  # grep -v '^#' /etc/postfix-out/master.cf
  smtp      inet  n       -       n       -       -       smtpd
  pickup    fifo  n       -       n       60      1       pickup
  cleanup   unix  n       -       n       -       0       cleanup
  qmgr      fifo  n       -       n       300     1       qmgr
  tlsmgr    unix  -       -       n       1000?   1       tlsmgr
  rewrite   unix  -       -       n       -       -       trivial-rewrite
  bounce    unix  -       -       n       -       0       bounce
  defer     unix  -       -       n       -       0       bounce
  trace     unix  -       -       n       -       0       bounce
  verify    unix  -       -       n       -       1       verify
  flush     unix  n       -       n       1000?   0       flush
  proxymap  unix  -       -       n       -       -       proxymap
  smtp      unix  -       -       n       -       -       smtp
  relay     unix  -       -       n       -       -       smtp
   -o fallback_relay=
  showq     unix  n       -       n       -       -       showq
  error     unix  -       -       n       -       -       error
  retry     unix  -       -       n       -       -       error
  discard   unix  -       -       n       -       -       discard
  local     unix  -       n       n       -       -       local
  virtual   unix  -       n       n       -       -       virtual
  lmtp      unix  -       -       n       -       -       lmtp
  anvil     unix  -       -       n       -       1       anvil
  scache    unix  -       -       n       -       1       scache
  proxywrite unix -       -       n       -       1       proxymap
  amavisd   unix   -      -       n       -       2       smtp
   -o smtp_data_done_timeout=1200
   -o disable_dns_lookups=yes
  127.0.0.1:11025 inet  n -       n       -       -       smtpd
   -o content_filter=
   -o local_recipient_maps=
   -o smtpd_helo_restrictions=
   -o smtpd_client_restrictions=
   -o smtpd_sender_restrictions=
   -o smtpd_recipient_restrictions=permit_mynetworks,reject
   -o mynetworks=127.0.0.0/8

I send my test emails using

  $ date | mutt -s "Test mail $(date) - Please ignore" [hidden email]

And the log shows lines like these:

  May 23 19:02:04 mailhub postfix/pickup[31739]: DD1987F7E3: uid=1001 from=<seichter>
  May 23 19:02:04 mailhub postfix/cleanup[31826]: DD1987F7E3: message-id=<[hidden email]>
  May 23 19:02:04 mailhub postfix/qmgr[12551]: DD1987F7E3: from=<[hidden email]>, size=527, nrcpt=1 (queue active)
  May 23 19:02:09 mailhub postfix/smtpd[31834]: connect from localhost[127.0.0.1]
  May 23 19:02:09 mailhub postfix/smtpd[31834]: 9DA957F7E4: client=localhost[127.0.0.1]
  May 23 19:02:09 mailhub postfix/cleanup[31826]: 9DA957F7E4: message-id=<[hidden email]>
  May 23 19:02:09 mailhub postfix/qmgr[12551]: 9DA957F7E4: from=<[hidden email]>, size=970, nrcpt=1 (queue active)
  May 23 19:02:09 mailhub postfix/smtpd[31834]: disconnect from localhost[127.0.0.1]
  May 23 19:02:09 mailhub postfix/smtp[31828]: DD1987F7E3: to=<[hidden email]>, relay=127.0.0.1[127.0.0.1]:10024, delay=4.8, delays=0.06/0.02/0.01/4.8, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 9DA957F7E4)
  May 23 19:02:09 mailhub postfix/qmgr[12551]: DD1987F7E3: removed
  May 23 19:02:09 mailhub postfix/smtp[31835]: setting up TLS connection to relay.domain.tld[123.123.123.123]:25
  May 23 19:02:09 mailhub postfix/smtp[31835]: Untrusted TLS connection established to relay.domain.tld[123.123.123.123]:25: TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)
  May 23 19:02:10 mailhub postfix/smtp[31835]: 9DA957F7E4: host relay.domain.tld[123.123.123.123] said: 450 4.1.2 <[hidden email]>: Recipient address rejected: Domain not found (in reply to RCPT TO command)
  May 23 19:02:10 mailhub postfix/smtp[31835]: setting up TLS connection to fallback-relay.domain.tld[234.234.234.234]:25
  May 23 19:02:10 mailhub postfix/smtp[31835]: Untrusted TLS connection established to fallback-relay.domain.tld[234.234.234.234]:25: TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)
  May 23 19:02:10 mailhub postfix/smtp[31835]: 9DA957F7E4: to=<[hidden email]>, relay=fallback-relay.domain.tld[234.234.234.234]:25, delay=1.3, delays=0.03/0.04/0.77/0.49, dsn=4.1.2, status=deferred (host fallback-relay.domain.tld[234.234.234.234] said: 450 4.1.2 <[hidden email]>: Recipient address rejected: Domain not found (in reply to RCPT TO command))

  # mailq
  -Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient-------
  9DA957F7E4      970 Fri May 23 19:02:09  [hidden email]
  (host fallback-relay.domain.tld[234.234.234.234] said: 450 4.1.2 <[hidden email]>: Recipient address rejected: Domain not found (in reply to RCPT TO command))
                                           [hidden email]

  -- 1 Kbytes in 1 Request.

  # postcat -q 9DA957F7E4
  *** ENVELOPE RECORDS deferred/9/9DA957F7E4 ***
  message_size:             970             592               1               0             970
  message_arrival_time: Fri May 23 19:02:09 2008
  create_time: Fri May 23 19:02:09 2008
  named_attribute: rewrite_context=local
  sender: [hidden email]
  named_attribute: encoding=7bit
  named_attribute: log_client_name=localhost
  named_attribute: log_client_address=127.0.0.1
  named_attribute: log_client_port=60585
  named_attribute: log_message_origin=localhost[127.0.0.1]
  named_attribute: log_helo_name=localhost
  named_attribute: log_protocol_name=ESMTP
  named_attribute: client_name=localhost
  named_attribute: reverse_client_name=localhost
  named_attribute: client_address=127.0.0.1
  named_attribute: client_port=60585
  named_attribute: helo_name=localhost
  named_attribute: client_address_type=2
  warning_message_time: Fri May 23 19:12:09 2008
  named_attribute: dsn_orig_rcpt=rfc822;[hidden email]
  original_recipient: [hidden email]
  recipient: [hidden email]
  *** MESSAGE CONTENTS deferred/9/9DA957F7E4 ***
  Received: from localhost (localhost [127.0.0.1])
          by mailhub.domain.tld (Postfix) with ESMTP id 9DA957F7E4
          for <[hidden email]>; Fri, 23 May 2008 19:02:09 +0200 (CEST)
  X-Virus-Scanned: at ElektroPhysik
  Received: from mailhub.domain.tld ([127.0.0.1])
          by localhost (mailhub.domain.tld [127.0.0.1]) (amavisd-new, port 10024)
          with ESMTP id FJJklrZfPPsR for <[hidden email]>;
          Fri, 23 May 2008 19:02:04 +0200 (CEST)
  Received: by mailhub.domain.tld (Postfix, from userid 1001)
          id DD1987F7E3; Fri, 23 May 2008 19:02:04 +0200 (CEST)
  Date: Fri, 23 May 2008 19:02:04 +0200
  From: Ralph Seichter <[hidden email]>
  To: [hidden email]
  Subject: Test mail Fri May 23 19:02:04 CEST 2008 - Please ignore
  Message-ID: <[hidden email]>
  MIME-Version: 1.0
  Content-Type: text/plain; charset=us-ascii
  Content-Disposition: inline
  User-Agent: Mutt/1.5.16 (2007-06-09)

  Fri May 23 19:02:04 CEST 2008
  *** HEADER EXTRACTED deferred/9/9DA957F7E4 ***
  named_attribute: encoding=7bit
  *** MESSAGE FILE END deferred/9/9DA957F7E4 ***

If read "warning_message_time: Fri May 23 19:12:09 2008" correctly, a
delayed mail notification should have been sent at 19:12:09, but it is
now approximately 19:27 and I can't see any notification so far. I
checked the mail log again, but

  # grep 9DA957F7E4 /var/log/mail

returns no log entries after the following line:

  May 23 19:02:10 mailhub postfix/smtp[31835]: 9DA957F7E4: to=<[hidden email]>, relay=fallback-relay.domain.tld[234.234.234.234]:25, delay=1.3, delays=0.03/0.04/0.77/0.49, dsn=4.1.2, status=deferred (host fallback-relay.domain.tld[234.234.234.234] said: 450 4.1.2 <[hidden email]>: Recipient address rejected: Domain not found (in reply to RCPT TO command))

That seems rather strange to me.

-R
Reply | Threaded
Open this post in threaded view
|

Re: No delay warnings although delay_warning_time is set?

Victor Duchovni
On Fri, May 23, 2008 at 07:27:54PM +0200, Ralph Seichter wrote:

>   May 23 19:02:10 mailhub postfix/smtp[31835]: 9DA957F7E4: to=<[hidden email]>, relay=fallback-relay.domain.tld[234.234.234.234]:25, delay=1.3, delays=0.03/0.04/0.77/0.49, dsn=4.1.2, status=deferred (host fallback-relay.domain.tld[234.234.234.234] said: 450 4.1.2 <[hidden email]>: Recipient address rejected: Domain not found (in reply to RCPT TO command))
>
>   # mailq
>   -Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient-------
>   9DA957F7E4      970 Fri May 23 19:02:09  [hidden email]
>   (host fallback-relay.domain.tld[234.234.234.234] said: 450 4.1.2 <[hidden email]>: Recipient address rejected: Domain not found (in reply to RCPT TO command))
>                                            [hidden email]
>
>   warning_message_time: Fri May 23 19:12:09 2008
>
> If read "warning_message_time: Fri May 23 19:12:09 2008" correctly, a
> delayed mail notification should have been sent at 19:12:09, but it is
> now approximately 19:27 and I can't see any notification so far. I
> checked the mail log again, but

Not *at* 19:12, *after* 19:12, when the next delivery attempt fails.

>   # grep 9DA957F7E4 /var/log/mail
>
> returns no log entries after the following line:
>
>   May 23 19:02:10 mailhub postfix/smtp[31835]: 9DA957F7E4: to=<[hidden email]>, relay=fallback-relay.domain.tld[234.234.234.234]:25, delay=1.3, delays=0.03/0.04/0.77/0.49, dsn=4.1.2, status=deferred (host fallback-relay.domain.tld[234.234.234.234] said: 450 4.1.2 <[hidden email]>: Recipient address rejected: Domain not found (in reply to RCPT TO command))
>
> That seems rather strange to me.

Well, what are your queue_run_delay, minimal_backoff_time and
maximal_backoff_time?

--
        Viktor.

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.

To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
<mailto:[hidden email]?body=unsubscribe%20postfix-users>

If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.
Reply | Threaded
Open this post in threaded view
|

Re: No delay warnings although delay_warning_time is set?

Noel Jones-2
In reply to this post by Ralph Seichter-10
Ralph Seichter wrote:

>
> If read "warning_message_time: Fri May 23 19:12:09 2008" correctly, a
> delayed mail notification should have been sent at 19:12:09, but it is
> now approximately 19:27 and I can't see any notification so far. I
> checked the mail log again, but
>
>   # grep 9DA957F7E4 /var/log/mail
>
> returns no log entries after the following line:
>
>   May 23 19:02:10 mailhub postfix/smtp[31835]: 9DA957F7E4: to=<[hidden email]>, relay=fallback-relay.domain.tld[234.234.234.234]:25, delay=1.3, delays=0.03/0.04/0.77/0.49, dsn=4.1.2, status=deferred (host fallback-relay.domain.tld[234.234.234.234] said: 450 4.1.2 <[hidden email]>: Recipient address rejected: Domain not found (in reply to RCPT TO command))
>
> That seems rather strange to me.
>
> -R

Warnings are not sent until postfix attempts delivery and the
warning time has passed.  No warning is expected if postfix
hasn't touched the mail since the initial attempt failed.

In your postconf -n output it doesn't look as if you've
changed the various backoff and queue parameters, so next
check to see if your active queue is clogged with other
undeliverable mail or if something is preventing the queue
manager from running.

Note that it's reasonable to add transport entries for a few
of the more frequently fat-fingered domain names that don't
deliver, that way the user gets quick feedback that they
misspelled the name.
# transports
hotmal.com    error:5.1.2 hotmail.com, not hotmal.com
hotmial.com   error:5.1.2 hotmail.com not hotmial.com
hotamil.com   error:5.1.2 hotmail.com not hotamil.com
wanado.fr     error:5.1.2 wanadoo.fr not wanado.fr
... I'm sure there's lots more

--
Noel Jones
Reply | Threaded
Open this post in threaded view
|

Re: No delay warnings although delay_warning_time is set?

Ralph Seichter-10
In reply to this post by Victor Duchovni
* Victor Duchovni:

> Not *at* 19:12, *after* 19:12, when the next delivery attempt fails.

I see, that makes more sense.

> Well, what are your queue_run_delay, minimal_backoff_time and
> maximal_backoff_time?

I did not change the default values.

-R
Reply | Threaded
Open this post in threaded view
|

Re: No delay warnings although delay_warning_time is set?

Ralph Seichter-10
In reply to this post by Noel Jones-2
* Noel Jones:

> In your postconf -n output it doesn't look as if you've changed the
> various backoff and queue parameters, so next check to see if your
> active queue is clogged with other undeliverable mail or if something
> is preventing the queue manager from running.

The mail queue does not contain other undelivered mail except from the
test messages I sent, and the system is generally under little load.
There are seldom more than 5 messages queued, and these mostly because
the outbound DSL network connection is down for a couple of minutes.

What could prevent the queue manager from running, and how would I check
for this kind of trouble?

> Note that it's reasonable to add transport entries for a few of the more
> frequently fat-fingered domain names that don't deliver, that way the
> user gets quick feedback that they misspelled the name.

A good suggestion, I'll keep that in mind.

-R