Re: how could a safety mechanism be configured?
On Thu, May 02, 2019 at 02:17:27AM +0200, Thomas Bohl wrote: > Hello, > > > So what happened to me was that I activated a crontab accidentally that > > fetchmails POP3 mail. It connects to localhost and delivers to me > > (pjp@localhost). In my case the lmtp delivery caused a no such mailbox > > error, and opensmtpd then sent a bounce to the originators of the mail as > > MAILER-DAEMON via the relay. How can I in future prevent this through the > > config? > > Let fetchmail directly deliver to /var/imap/socket/lmtp should do the trick, > because no bouncing smtpd is involved. Thank you for the hint! I finally have it working with directly delivering to lmtp. No more accidental bounces I hope! Best Regards, -peter -- You received this mail because you are subscribed to misc@opensmtpd.org To unsubscribe, send a mail to: misc+unsubscr...@opensmtpd.org
Re: how could a safety mechanism be configured?
Hello, So what happened to me was that I activated a crontab accidentally that fetchmails POP3 mail. It connects to localhost and delivers to me (pjp@localhost). In my case the lmtp delivery caused a no such mailbox error, and opensmtpd then sent a bounce to the originators of the mail as MAILER-DAEMON via the relay. How can I in future prevent this through the config? Let fetchmail directly deliver to /var/imap/socket/lmtp should do the trick, because no bouncing smtpd is involved. -- You received this mail because you are subscribed to misc@opensmtpd.org To unsubscribe, send a mail to: misc+unsubscr...@opensmtpd.org
how could a safety mechanism be configured?
Hi, This is sorta a feature request, but may be solveable by a better config: https://marc.info/?l=openbsd-misc&m=155670259203430&w=2 What I did was explained there. Here is my config for the mail system in question: ---> ... some keys cut ... listen on lo0 listen on ix1 tls auth table aliases file:/etc/mail/aliases table secrets file:/etc/mail/secrets action "local" lmtp "/var/imap/socket/lmtp" user _cyrus alias action "relay" relay tls no-verify host smtps://la...@mail.solarscale.de \ auth match for local action "local" match for any action "relay" match auth from any for any action "relay" <--- So what happened to me was that I activated a crontab accidentally that fetchmails POP3 mail. It connects to localhost and delivers to me (pjp@localhost). In my case the lmtp delivery caused a no such mailbox error, and opensmtpd then sent a bounce to the originators of the mail as MAILER-DAEMON via the relay. How can I in future prevent this through the config? If not possible, is it simple to somehow work out a workaround for such situations? I'm just lucky OpenBSD mailing lists seem to have a catch for such bounces, but I still had to say sorry. Regards, -peter -- You received this mail because you are subscribed to misc@opensmtpd.org To unsubscribe, send a mail to: misc+unsubscr...@opensmtpd.org
