Re: something similar to always_bcc in postfix?
Sent from my iPhone > On Jul 25, 2016, at 2:18 PM, Edgar Pettijohnwrote: > > > > Sent from my iPhone > > On Jul 25, 2016, at 11:33 AM, Denis Fondras wrote: > >>> I'd like to bcc all incoming mail to a specified address, but could not >>> figure out how. Anyone has any pointers? >>> My current setup is opensmtpd + dovecot with virtual domains. >> >> I don't know if it is possible with OpenSMTPd. >> Alternatively and probably not as efficient but if you use pigeonhole you can >> add a global sieve script to copy email to another recipient. >> >> Denis >> >> -- >> You received this mail because you are subscribed to misc@opensmtpd.org >> To unsubscribe, send a mail to: misc+unsubscr...@opensmtpd.org > > I know it's possible with postfix, so I'm sure opensmtpd can do it too. Not > sure how unfortunately. > > -- > You received this mail because you are subscribed to misc@opensmtpd.org > To unsubscribe, send a mail to: misc+unsubscr...@opensmtpd.org > This is an excerpt from table(5) In a virtual domain context, the key is either a user part, a full email address or a catch all, following selection rules described in smtpd.conf(5), and the value is one or many recipients as described in aliases(5): @example.com catch...@example.com
Re: something similar to always_bcc in postfix?
Sent from my iPhone On Jul 25, 2016, at 11:33 AM, Denis Fondraswrote: >> I'd like to bcc all incoming mail to a specified address, but could not >> figure out how. Anyone has any pointers? >> My current setup is opensmtpd + dovecot with virtual domains. > > I don't know if it is possible with OpenSMTPd. > Alternatively and probably not as efficient but if you use pigeonhole you can > add a global sieve script to copy email to another recipient. > > Denis > > -- > You received this mail because you are subscribed to misc@opensmtpd.org > To unsubscribe, send a mail to: misc+unsubscr...@opensmtpd.org > I know it's possible with postfix, so I'm sure opensmtpd can do it too. Not sure how unfortunately. -- You received this mail because you are subscribed to misc@opensmtpd.org To unsubscribe, send a mail to: misc+unsubscr...@opensmtpd.org
Re: Opensmtpd crash because of loop (version: 5.9.1)
This was fixed in 5.9.3 release, try upgrading and report if you still experience a crash. Gilles Le 25 juil. 2016 8:35 PM, Mik Ja écrit :version: 5.9.1Hello,I'm configuring Opensmtpd with dkimproxy and of course I did many tests but one email is stuck somewhere and makes the daemon to crash.smtpd.conflisten on 127.0.0.1listen on 127.0.0.1 port 10028 tag DKIM_OUT # Emails from dkimproxylisten on 10.x.x.x # Emails from clients# Mails tagged received from dkimproxy_out are sent outsideaccept tagged DKIM_OUT for any relay# Mails received from local or authorised networks are sent to dkimproxyaccept from local for any relay via smtp://127.0.0.1:10027accept from source for any relay via smtp://127.0.0.1:10027dkimproxy_out.conf# specify what address/port DKIMproxy should listen onlisten   127.0.0.1:10027# specify what address/port DKIMproxy forwards mail torelay    127.0.0.1:10028# specify what domains DKIMproxy can sign for (comma-separated, no spaces)domain   mydomain.com# specify what signatures to addsignature dkim(c=relaxed)signature domainkeys(c=nofws)# specify location of the private keykeyfile  /var/dkimproxy_private.key# specify the selector (i.e. the name of the key record put in DNS)selector selector1I'm not saying my configuration is good or that I didn't do anything wrong, but to me the opensmtpd shouldn't crash. It should do another action but not crashing. Regards# smtpd -vddebug: mta: waiting for 1s before next transactiondebug: mta: flush for d52ef88fdf8981ad (-> root@mymx.mydomain.com)debug: mta: received evp:8b6db1a643cfeb5d for debug: mta: draining [relay:mymx.mydomain.com] refcount=3, ntask=3, nconnector=1, nconn=1debug: mta: [relay:mymx.mydomain.com] waiting for connectormta: timeout for session hangondebug: mta: 0xe4560120670: handling next task for relay [relay:mymx.mydomain.com]mta: timeout for session hangondebug: mta: 0xe45c8c20670: handling next task for relay [relay:127.0.0.1,port=10027,mx]smtp: 0xe4600176000: fd 11 from queuesmtp: 0xe4600176000: fd 13 from filtersmtp: 0xe45ee852000: fd 15 from queuesmtp: 0xe45ee852000: fd 17 from filterwarn: loop detected: Undefined error: 0debug: smtp: 0xe4600176000: data io done (133750 bytes)smtp-in: Failed command on session 1e3ede1e65cff40a: "DATA" => 500 5.4.6 Routing loop detected: Loop detectedrelay: PermFail for 4477466d6c1e0f40: session=1e3ede1dbb8fd8f2, from= , to= , rcpt=<->, source=10.1.1.2, relay=10.1.1.2 (mymx.mydomain.com), delay=3s, stat=500 5.4.6 Routing loop detected: Loop detecteddebug: mta: waiting for 1s before next transactionfilter: eom not received yetdebug: mta: flush for 4477466d6c1e0f40 (-> root@mymx.mydomain.com)debug: queue: bouncing evp:4477466d6c1e0f40 as evp:4477466df0027753debug: scheduler: evp:4477466df0027753 scheduled (bounce)debug: bounce: new message 4477466ddebug: bounce: adding report 4477466df0027753: root@mymx.mydomain.com: 500 5.4.6 Routing loop detected: Loop detecteddebug: bounce: drain: nmessage=1 running=0debug: bounce: next message not ready yetdebug: bounce: setting timerdebug: smtp: 0xe45ee852000: data io done (272204 bytes)filter: deferring eom query...filter: running eom query...debug: 0xe45ee852000: end of message, msgflags=0xsmtp-in: Accepted message 536b9882 on session 1e3ee0b37b2eb128: from=<>, to= , size=272204, ndest=1, proto=ESMTPdebug: scheduler: evp:536b98820ca287a8 scheduled (mta)debug: mta: received evp:536b98820ca287a8 for debug: mta: draining [relay:mymx.mydomain.com] refcount=3, ntask=3, nconnector=1, nconn=1debug: mta: [relay:mymx.mydomain.com] waiting for connectorrelay: Ok for a781d87f733b347e: session=1e3ee0b24957ff6b, from=<>, to= , rcpt=<->, source=127.0.0.1, relay=127.0.0.1 (localhost), delay=1s, stat=250 2.0.0: 536b9882 Message accepted for deliverydebug: mta: waiting for 1s before next transactiondebug: mta: flush for a781d87f733b347e (-> user@mymx.mydomain.com)mta: timeout for session hangondebug: bounce: timeoutdebug: bounce: drain: nmessage=1 running=0debug: bounce: requesting new enqueue socket...debug: bounce: enough sessions runningdebug: mta: 0xe4560120670: handling next task for relay [relay:mymx.mydomain.com]mta: timeout for session hangondebug: mta: 0xe45c8c20670: no task for relay [relay:127.0.0.1,port=10027,mx]mta: debug: last connection: hanging on for 9sdebug: smtp: new client on listener: 0xe45a62ca000smtp-in: New session 1e3ee0f6c4669080 from host mymx.mydomain.com [local]smtp-in: Failed command on session 1e3ede1e65cff40a: "MAIL FROM:<>" => 503 5.5.1 Invalid command: Command not allowed at this point.debug: bounce: got enqueue socket 5debug: bounce: new session 0xe458e0e2200relay: PermFail for a0a53973398497c8: session=1e3ede1dbb8fd8f2, from=<>, to= , rcpt=<->, source=10.1.1.2, relay=10.1.1.2 (mymx.mydomain.com), delay=3s, stat=503 5.5.1
Opensmtpd crash because of loop (version: 5.9.1)
version: 5.9.1 Hello,I'm configuring Opensmtpd with dkimproxy and of course I did many tests but one email is stuck somewhere and makes the daemon to crash. smtpd.conf listen on 127.0.0.1 listen on 127.0.0.1 port 10028 tag DKIM_OUT # Emails from dkimproxy listen on 10.x.x.x # Emails from clients# Mails tagged received from dkimproxy_out are sent outside accept tagged DKIM_OUT for any relay# Mails received from local or authorised networks are sent to dkimproxy accept from local for any relay via smtp://127.0.0.1:10027 accept from source for any relay via smtp://127.0.0.1:10027 dkimproxy_out.conf # specify what address/port DKIMproxy should listen on listen 127.0.0.1:10027 # specify what address/port DKIMproxy forwards mail to relay 127.0.0.1:10028 # specify what domains DKIMproxy can sign for (comma-separated, no spaces) domain mydomain.com # specify what signatures to add signature dkim(c=relaxed) signature domainkeys(c=nofws) # specify location of the private key keyfile /var/dkimproxy_private.key # specify the selector (i.e. the name of the key record put in DNS) selector selector1 I'm not saying my configuration is good or that I didn't do anything wrong, but to me the opensmtpd shouldn't crash. It should do another action but not crashing. Regards # smtpd -vd debug: mta: waiting for 1s before next transaction debug: mta: flush for d52ef88fdf8981ad (-> r...@mymx.mydomain.com) debug: mta: received evp:8b6db1a643cfeb5d fordebug: mta: draining [relay:mymx.mydomain.com] refcount=3, ntask=3, nconnector=1, nconn=1 debug: mta: [relay:mymx.mydomain.com] waiting for connector mta: timeout for session hangon debug: mta: 0xe4560120670: handling next task for relay [relay:mymx.mydomain.com] mta: timeout for session hangon debug: mta: 0xe45c8c20670: handling next task for relay [relay:127.0.0.1,port=10027,mx] smtp: 0xe4600176000: fd 11 from queue smtp: 0xe4600176000: fd 13 from filter smtp: 0xe45ee852000: fd 15 from queue smtp: 0xe45ee852000: fd 17 from filter warn: loop detected: Undefined error: 0 debug: smtp: 0xe4600176000: data io done (133750 bytes) smtp-in: Failed command on session 1e3ede1e65cff40a: "DATA" => 500 5.4.6 Routing loop detected: Loop detected relay: PermFail for 4477466d6c1e0f40: session=1e3ede1dbb8fd8f2, from= , to= , rcpt=<->, source=10.1.1.2, relay=10.1.1.2 (mymx.mydomain.com), delay=3s, stat=500 5.4.6 Routing loop detected: Loop detected debug: mta: waiting for 1s before next transaction filter: eom not received yet debug: mta: flush for 4477466d6c1e0f40 (-> r...@mymx.mydomain.com) debug: queue: bouncing evp:4477466d6c1e0f40 as evp:4477466df0027753 debug: scheduler: evp:4477466df0027753 scheduled (bounce) debug: bounce: new message 4477466d debug: bounce: adding report 4477466df0027753: r...@mymx.mydomain.com: 500 5.4.6 Routing loop detected: Loop detected debug: bounce: drain: nmessage=1 running=0 debug: bounce: next message not ready yet debug: bounce: setting timer debug: smtp: 0xe45ee852000: data io done (272204 bytes) filter: deferring eom query... filter: running eom query... debug: 0xe45ee852000: end of message, msgflags=0x smtp-in: Accepted message 536b9882 on session 1e3ee0b37b2eb128: from=<>, to= , size=272204, ndest=1, proto=ESMTP debug: scheduler: evp:536b98820ca287a8 scheduled (mta) debug: mta: received evp:536b98820ca287a8 for debug: mta: draining [relay:mymx.mydomain.com] refcount=3, ntask=3, nconnector=1, nconn=1 debug: mta: [relay:mymx.mydomain.com] waiting for connector relay: Ok for a781d87f733b347e: session=1e3ee0b24957ff6b, from=<>, to= , rcpt=<->, source=127.0.0.1, relay=127.0.0.1 (localhost), delay=1s, stat=250 2.0.0: 536b9882 Message accepted for delivery debug: mta: waiting for 1s before next transaction debug: mta: flush for a781d87f733b347e (-> u...@mymx.mydomain.com) mta: timeout for session hangon debug: bounce: timeout debug: bounce: drain: nmessage=1 running=0 debug: bounce: requesting new enqueue socket... debug: bounce: enough sessions running debug: mta: 0xe4560120670: handling next task for relay [relay:mymx.mydomain.com] mta: timeout for session hangon debug: mta: 0xe45c8c20670: no task for relay [relay:127.0.0.1,port=10027,mx] mta: debug: last connection: hanging on for 9s debug: smtp: new client on listener: 0xe45a62ca000 smtp-in: New session 1e3ee0f6c4669080 from host mymx.mydomain.com [local] smtp-in: Failed command on session 1e3ede1e65cff40a: "MAIL FROM:<>" => 503 5.5.1 Invalid command: Command not allowed at this point. debug: bounce: got enqueue socket 5 debug: bounce: new session 0xe458e0e2200 relay: PermFail for a0a53973398497c8: session=1e3ede1dbb8fd8f2, from=<>, to= , rcpt=<->, source=10.1.1.2, relay=10.1.1.2 (mymx.mydomain.com), delay=3s, stat=503 5.5.1 Invalid command: Command not allowed at this point. debug: mta: flush for
Re: something similar to always_bcc in postfix?
> I'd like to bcc all incoming mail to a specified address, but could not > figure out how. Anyone has any pointers? > My current setup is opensmtpd + dovecot with virtual domains. I don't know if it is possible with OpenSMTPd. Alternatively and probably not as efficient but if you use pigeonhole you can add a global sieve script to copy email to another recipient. Denis -- You received this mail because you are subscribed to misc@opensmtpd.org To unsubscribe, send a mail to: misc+unsubscr...@opensmtpd.org