This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
Cc: in <auto-dbm> replies
- Previous message (by thread): Cc: in <auto-dbm> replies
- Next message (by thread): whois output and the "changed" line.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
kissg at sztaki.hu
kissg at sztaki.hu
Fri Sep 11 11:43:31 CEST 1998
> > I think the database should send any outgoing mails > > with sender address <nobody at no.where.ripe.net> or similar Dear Carsten, > come on, you're kidding, aren't you? This would mean to expand > Usenet's bad habits to RIPE email answers. That doesn't seem to > be a really good idea... I just say that *automatic* aswers should be blocked. However I don't think to hide the real sender as spammers do. Any human intelligence can find out easily where the mail came from if the RFC822 header contains a Sender: or X-This-Mail-Really-Came-From: ;-) line. So this header looks absolute correct for me: To: <as required> Cc: <as proposed> From: bit-bucket at ripe.net (Do not reply this address) Sender: ripe-db at ripe.net (RIPE database engine) X-Comment: This is an acknowledgement, not intended to be replied. Regards Gabor
- Previous message (by thread): Cc: in <auto-dbm> replies
- Next message (by thread): whois output and the "changed" line.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]