Re: [ris-int] Reply-To forwarded to /dev/null in myASn messages
Shouldn't there be follow up by a risopsy when a notification fails to be delivered? (for permanent failures, either try
Quite unlikely, if I know that alarm notifications were successfully sent to my inbox.
Sorry, I don't understand your reply. If a mail from the myASn system bounces, someone should in my opinion take action. Either the user made a mistake, typo, entering the e-mail address in the myASn system, or he has left the ISP owning the ASn. risops could try to get in touch with the ASn owner, to get the email address corrrected (remember, we are running a _service_ ) or when that fails remove the address from the alarm system (no point polluting internal an external systems with e-mails you know will bounce back) Also, when the human recipients behind a remote e-mail change, they might reply, querying what the message was about; it's not polite to silently ignore such one-off replies. -- Rene
We need to add risops to the trusted users class in sendmail.cf on weesp. Something like So myASn can use reply-to address forwarded to /dev/null
Once Matthew Williams wrote:
Hi Alexis,
Working on this?
Cheers, Matthew
----- Forwarded message from Mail Delivery System <MAILER-DAEMON@ripe.net> -----
X-Recipient: <risops@ripe.net> Date: Tue, 13 Jul 2004 23:43:50 +0200 (CEST) From: MAILER-DAEMON@ripe.net (Mail Delivery System) Subject: Undelivered Mail Returned to Sender To: risops@ripe.net
Shouldn't there be follow up by a risopsy when a notification fails to be delivered? (for permanent failures, either try
Quite unlikely, if I know that alarm notifications were successfully sent to my inbox.
Sorry, I don't understand your reply.
If a mail from the myASn system bounces, someone should in my opinion take action. Either the user made a mistake, typo, entering the e-mail address in the myASn system, or he has left the ISP owning the ASn. risops could try to get in touch with the ASn owner, to get the email address corrrected (remember, we are running a _service_ ) or when that fails remove the address from the alarm system (no point polluting internal an external systems with e-mails you know will bounce back)
I think you are a few months ahead in planning. Now, if reply-to was set to the destination email addr, then we could incorporate a function that would disable the alarm nots after a few bounces. Until then, we need a quick fix. Cheers, Matthew
Also, when the human recipients behind a remote e-mail change, they might reply, querying what the message was about; it's not polite to silently ignore such one-off replies.
-- Rene
We need to add risops to the trusted users class in sendmail.cf on weesp. Something like So myASn can use reply-to address forwarded to /dev/null
Once Matthew Williams wrote:
Hi Alexis,
Working on this?
Cheers, Matthew
----- Forwarded message from Mail Delivery System <MAILER-DAEMON@ripe.net> -----
X-Recipient: <risops@ripe.net> Date: Tue, 13 Jul 2004 23:43:50 +0200 (CEST) From: MAILER-DAEMON@ripe.net (Mail Delivery System) Subject: Undelivered Mail Returned to Sender To: risops@ripe.net
Now, if
reply-to was set to the destination email addr,
Error... this should of course be something related to the account itself, not the dest addr. Anyway, I have added disable-after-n-bounces to the requested features page. Cheers, Matthew
-----Original Message----- From: ris-int-admin@ripe.net [mailto:ris-int-admin@ripe.net] On Behalf Of Matthew Williams Sent: 14 July 2004 15:16 To: 'Rene Wilhelm' Cc: ris-int@ripe.net; 'Arife Vural' Subject: RE: [ris-int] Reply-To forwarded to /dev/null in myASn messages
Shouldn't there be follow up by a risopsy when a notification fails to be delivered? (for permanent failures, either try
Quite unlikely, if I know that alarm notifications were successfully sent to my inbox.
Sorry, I don't understand your reply.
If a mail from the myASn system bounces, someone should in my opinion take action. Either the user made a mistake, typo, entering the e-mail address in the myASn system, or he has left the ISP owning the ASn. risops could try to get in touch with the ASn owner, to get the email address corrrected (remember, we are running a _service_ ) or when that fails remove the address from the alarm system (no point polluting internal an external systems with e-mails you know will bounce back)
I think you are a few months ahead in planning. Now, if reply-to was set to the destination email addr, then we could incorporate a function that would disable the alarm nots after a few bounces. Until then, we need a quick fix.
Cheers, Matthew
Also, when the human recipients behind a remote e-mail change, they might reply, querying what the message was about; it's not polite to silently ignore such one-off replies.
-- Rene
We need to add risops to the trusted users class in
sendmail.cf on
weesp. Something like So myASn can use reply-to address forwarded to /dev/null
Once Matthew Williams wrote:
Hi Alexis,
Working on this?
Cheers, Matthew
----- Forwarded message from Mail Delivery System <MAILER-DAEMON@ripe.net> -----
X-Recipient: <risops@ripe.net> Date: Tue, 13 Jul 2004 23:43:50 +0200 (CEST) From: MAILER-DAEMON@ripe.net (Mail Delivery System) Subject: Undelivered Mail Returned to Sender To: risops@ripe.net
participants (2)
-
Matthew Williams -
Rene Wilhelm