Re: smtpd.conf new grammar
Final update. I've been working with Edgar who has helped no end and I now have a working config. For me the working line is actually: action "lmtp-local" mda "/usr/libexec/mail.lmtp -d unix:/var/dovecot/lmtp -f %{sender} %{dest}" virtual and the corresponding match is: match tag "SPAM_IN" from any for domain action "lmtp-local" Hopefully this might help someone in the future. Regards - Nick On 28/05/2018 16:48, Nick Ryan wrote: Hi Mark, viq, did either of you get it to work with the virtual table? Mine mostly works with: action "lmtp-local" mda "/usr/libexec/mail.lmtp -d unix:/var/dovecot/lmtp -f %{sender} %{rcpt}" virtual but it ignores the virtual table completely. If I miss out the ${rcpt}, I get a no recipient specified and if I have the {user.username} it gives a similar error. Did your virtual work or am I doing something daft? Regards - Nick On 27/05/2018 08:51, viq wrote: On 18-05-27 09:34:10, Mark Patruck wrote: For me it works with %{user.username} as mail.lmtp(8) user. See "FORMAT SPECIFIERS" in smtpd.conf(5) for details. Shows how well I read the man page With this it works, thank you! On Sun, May 27, 2018 at 09:04:56AM +0200, viq wrote: > On 18-05-26 19:18:56, Edgar Pettijohn III wrote: > > > > > Sorry, I've read the announcements, looked at man pages and examples, > > > but still didn't manage to figure out how to translate "deliver via dovecot > > > lmtp" > > > (to have sieve working) into the new syntax. So far my config was: > > > > > > table vusers ldap:/etc/mail/ldap.conf > > > table vdomains ldap:/etc/mail/ldap.conf > > > table passwd ldap:/etc/mail/ldap.conf > > > > > > accept from local for local virtual deliver to lmtp > > > "/var/dovecot/lmtp" > > > accept from any for domain virtual deliver to lmtp > > > "/var/dovecot/lmtp" > > > > > > > > > I tried changing those into: > > > > > > action "lmtp-local" mda "/usr/libexec/mail.lmtp -d /var/dovecot/lmtp" > > > > try: > > action "lmtp-local" mda "/usr/libexec/mail.lmtp -d unix:/var/dovecot/lmtp -f > > %{sender}" > > Well, this time I'm getting > result=TempFail stat=Error ("mail.lmtp: no recipient was specified") > so there's difference. So I tried > action "lmtp-local" mda "/usr/libexec/mail.lmtp -d unix:/var/dovecot/lmtp -f %{sender} %{recipient}" virtual > but that resulted in > result=TempFail stat=Error ("smtpd: mda command line could not be expanded: Interrupted system call") > same with %{rcpt-to} > > Where did you get the %{} syntax? I haven't seen it anywhere when > reading about this. > > > However, this does feel odd. I need to switch over as well, but still trying > > to wrap my brain around the new config. > > > virtual > > > action "relay" relay > > > match from local for local action "lmtp-local" > > > match from any for domain action "lmtp-local" > > > match from local for any action "relay" > > > > > > > > > but delivery attempts fail with Error ("mail.lmtp: sender must be specified > > > with -f") > > > > > > What would be the proper config for this? > > > -- > > > viq > > > -- Mark Patruck ( mark at wrapped.cx ) GPG key 0xF2865E51 / 187F F6D3 EE04 1DCE 1C74 F644 0D3C F66F F286 5E51 http://www.wrapped.cx
protection fault trap with OpenBSD 6.3
Hi List, i am having issues with OpenBSD 6.3, latest patches as of today applied. We are using gif-tunnels between our datacenters, transport encryption and OpenBGPD to announce the prefixes between the datacenters. The boxes also have isakmpd tunnels on a carp interface to AWS and GCP. The setup is working fine with existing 6.1 boxes and there's no problem in pushing/receiving several 100MBit/s (according to observium snmpd data, which gets constantly collected). Switching the traffic to the 6.3 hosts, we get a freeze on one of the boxes after about 45 minutes of transferring traffic (all IPv4 traffic in our case for now): login: kernel: protection fault trap, code=0 Stopped at export_sa+0x5c: movl0(%rcx),%ecx ddb{0}> show panic the kernel did not panic ddb{0}> bt export_sa(10,80002240c0b0) at export_sa+0x5c pfkeyv2_expire(8095c400,8095c400) at pfkeyv2_expire+0x14e tdb_timeout(80002240c260) at tdb_timeout+0x39 softclock_thread(0) at softclock_thread+0xc6 end trace frame: 0x0, count: -4 ddb{0}> ps PID TID PPIDUID S FLAGS WAIT COMMAND 72451 269194 73777 0 30x100083 ttyin ksh 73777 173781 1 0 30x100080 kqreadtmux 75976 220444 64078 0 30x100083 kqreadtmux 64078 416346 52315 0 30x10008b pause ksh 52315 192412 90927 0 30x92 selectsshd 98917 236376 1 0 30x100083 ttyin getty 88517 86024 1 0 30x100083 ttyin getty 39458 242138 1 0 30x100083 ttyin getty 16509 160463 1 0 30x100083 ttyin getty 5741 397042 1 0 30x100083 ttyin getty 39044 336292 1 0 30x100083 ttyin getty 12648 371611 1 0 30x100098 poll cron 64944 488151 1 0 30x90 selectbacula-fd 64944 93309 1 0 3 0x490 fsleepbacula-fd 90927 275325 1 0 30x80 selectsshd 30069 438532 1556 30x90 selectnrpe 61921 464479 1 99 30x100090 poll sndiod 19307 265996 1110 30x100090 poll sndiod 67642 23609 35037 95 30x100092 kqreadsmtpd 30995 503192 35037103 30x100092 kqreadsmtpd 30135 432207 35037 95 30x100092 kqreadsmtpd 48369 40239 35037 95 30x100092 kqreadsmtpd 15265 58238 35037 95 30x100092 kqreadsmtpd 88554 334766 35037 95 30x100092 kqreadsmtpd 35037 186739 1 0 30x100080 kqreadsmtpd 96223 160438 58191 75 70x100052bgpd 90387 61271 58191 75 30x100092 poll bgpd 58191 101172 1 0 30x80 poll bgpd 42084 456307 1 0 30x100080 kqreadsnmpd 18317 107917 1 91 30x100092 kqreadsnmpd 44555 140946 1 91 30x92 kqreadsnmpd 24182 166156 1 0 30x80 selectsshd 52767 308392 14070 68 70x50isakmpd 14070 24576 1 0 30x80 netio isakmpd 57007 139418 35428 83 30x100092 poll ntpd 35428 91196 92310 83 30x100092 poll ntpd 92310 242928 1 0 30x100080 poll ntpd 77320 412385 65645 74 30x100092 bpf pflogd 65645 394793 1 0 30x80 netio pflogd 30559 279846 77380 73 30x100090 kqreadsyslogd 77380 496624 1 0 30x100082 netio syslogd 98706 10022 77669115 30x100092 kqreadslaacd 11631 15638 77669115 30x100092 kqreadslaacd 77669 211051 1 0 30x80 kqreadslaacd 75393 324227 0 0 3 0x14200 pgzerozerothread 9 431378 0 0 3 0x14200 aiodoned aiodoned 39050 216833 0 0 3 0x14200 syncerupdate 97565 501358 0 0 3 0x14200 cleaner cleaner 96696 450450 0 0 3 0x14200 reaperreaper 39575 483587 0 0 3 0x14200 pgdaemon pagedaemon 67857 79140 0 0 3 0x14200 bored crynlk 64493 339992 0 0 7 0x14200crypto 40655 184052 0 0 3 0x14200 usbtskusbtask 35598 495188 0 0 3 0x14200 usbatsk usbatsk 61415 132786 0 0 3 0x40014200 acpi0 acpi0 43475 414851 0 0 7 0x40014200idle11 94572 515090 0 0 7 0x40014200idle10 45748
Re: smtpd.conf new grammar
Hi Edgar, this is the format: postmas...@nr.ie n...@nr.ie webmas...@nr.ien...@nr.ie n...@nr.ie vmail Is this where it's pulling the %{user.username} being vmail from? Dovecot is expecting u...@domain.tld Regards - Nick On 28/05/2018 18:28, Edgar Pettijohn III wrote: On 05/28/18 10:48, Nick Ryan wrote: Hi Mark, viq, did either of you get it to work with the virtual table? Mine mostly works with: action "lmtp-local" mda "/usr/libexec/mail.lmtp -d unix:/var/dovecot/lmtp -f %{sender} %{rcpt}" virtual but it ignores the virtual table completely. If I miss out the ${rcpt}, I get a no recipient specified and if I have the {user.username} it gives a similar error. Did your virtual work or am I doing something daft? Regards - Nick It really depends on how your dovecot is set up. Is it expecting a `u...@domain.tld' for the username or just the user part? How is your set up? Personally, I think its easier in the long run to either use a passwd-file from extras or an sql table of some sort. That way smtpd and dovecot can share more easily. Edgar On 27/05/2018 08:51, viq wrote: On 18-05-27 09:34:10, Mark Patruck wrote: For me it works with %{user.username} as mail.lmtp(8) user. See "FORMAT SPECIFIERS" in smtpd.conf(5) for details. Shows how well I read the man page With this it works, thank you! On Sun, May 27, 2018 at 09:04:56AM +0200, viq wrote: > On 18-05-26 19:18:56, Edgar Pettijohn III wrote: > > > > > Sorry, I've read the announcements, looked at man pages and examples, > > > but still didn't manage to figure out how to translate "deliver via dovecot > > > lmtp" > > > (to have sieve working) into the new syntax. So far my config was: > > > > > > table vusers ldap:/etc/mail/ldap.conf > > > table vdomains ldap:/etc/mail/ldap.conf > > > table passwd ldap:/etc/mail/ldap.conf > > > > > > accept from local for local virtual deliver to lmtp > > > "/var/dovecot/lmtp" > > > accept from any for domain virtual deliver to lmtp > > > "/var/dovecot/lmtp" > > > > > > > > > I tried changing those into: > > > > > > action "lmtp-local" mda "/usr/libexec/mail.lmtp -d /var/dovecot/lmtp" > > > > try: > > action "lmtp-local" mda "/usr/libexec/mail.lmtp -d unix:/var/dovecot/lmtp -f > > %{sender}" > > Well, this time I'm getting > result=TempFail stat=Error ("mail.lmtp: no recipient was specified") > so there's difference. So I tried > action "lmtp-local" mda "/usr/libexec/mail.lmtp -d unix:/var/dovecot/lmtp -f %{sender} %{recipient}" virtual > but that resulted in > result=TempFail stat=Error ("smtpd: mda command line could not be expanded: Interrupted system call") > same with %{rcpt-to} > > Where did you get the %{} syntax? I haven't seen it anywhere when > reading about this. > > > However, this does feel odd. I need to switch over as well, but still trying > > to wrap my brain around the new config. > > > virtual > > > action "relay" relay > > > match from local for local action "lmtp-local" > > > match from any for domain action "lmtp-local" > > > match from local for any action "relay" > > > > > > > > > but delivery attempts fail with Error ("mail.lmtp: sender must be specified > > > with -f") > > > > > > What would be the proper config for this? > > > -- > > > viq > > > -- Mark Patruck ( mark at wrapped.cx ) GPG key 0xF2865E51 / 187F F6D3 EE04 1DCE 1C74 F644 0D3C F66F F286 5E51 http://www.wrapped.cx
Re: Autocompletion with pass in ksh
On 18/05/28 16:53, justina colmena wrote: On Sun, 6 May 2018 06:33:13 +0200 Niels Kobschaetzki wrote: pass (www.password-store.org) is a password manager Did you mean https://www.passwordstore.org/ (no hyphen)? "the standard unix password manager" It depends on GnuPG, https://www.gnupg.org/ which is a GNU project. If this is part of an actual Unix standard, please do tell. "UNIX(R)" is a registered trademark of "The Open Group" No, it is not a standard. That is probably just an exaggeration. But it is very useful. GPG is usually installed on unix-oid systems and it is itself only a shell-script. In addition it needs git for its history and sync. Cheers, Niels
Re: smtpd.conf new grammar
On 05/28/18 10:48, Nick Ryan wrote: Hi Mark, viq, did either of you get it to work with the virtual table? Mine mostly works with: action "lmtp-local" mda "/usr/libexec/mail.lmtp -d unix:/var/dovecot/lmtp -f %{sender} %{rcpt}" virtual but it ignores the virtual table completely. If I miss out the ${rcpt}, I get a no recipient specified and if I have the {user.username} it gives a similar error. Did your virtual work or am I doing something daft? Regards - Nick It really depends on how your dovecot is set up. Is it expecting a `u...@domain.tld' for the username or just the user part? How is your set up? Personally, I think its easier in the long run to either use a passwd-file from extras or an sql table of some sort. That way smtpd and dovecot can share more easily. Edgar On 27/05/2018 08:51, viq wrote: On 18-05-27 09:34:10, Mark Patruck wrote: For me it works with %{user.username} as mail.lmtp(8) user. See "FORMAT SPECIFIERS" in smtpd.conf(5) for details. Shows how well I read the man page With this it works, thank you! On Sun, May 27, 2018 at 09:04:56AM +0200, viq wrote: > On 18-05-26 19:18:56, Edgar Pettijohn III wrote: > > > > > Sorry, I've read the announcements, looked at man pages and examples, > > > but still didn't manage to figure out how to translate "deliver via dovecot > > > lmtp" > > > (to have sieve working) into the new syntax. So far my config was: > > > > > > table vusers ldap:/etc/mail/ldap.conf > > > table vdomains ldap:/etc/mail/ldap.conf > > > table passwd ldap:/etc/mail/ldap.conf > > > > > > accept from local for local virtual deliver to lmtp > > > "/var/dovecot/lmtp" > > > accept from any for domain virtual deliver to lmtp > > > "/var/dovecot/lmtp" > > > > > > > > > I tried changing those into: > > > > > > action "lmtp-local" mda "/usr/libexec/mail.lmtp -d /var/dovecot/lmtp" > > > > try: > > action "lmtp-local" mda "/usr/libexec/mail.lmtp -d unix:/var/dovecot/lmtp -f > > %{sender}" > > Well, this time I'm getting > result=TempFail stat=Error ("mail.lmtp: no recipient was specified") > so there's difference. So I tried > action "lmtp-local" mda "/usr/libexec/mail.lmtp -d unix:/var/dovecot/lmtp -f %{sender} %{recipient}" virtual > but that resulted in > result=TempFail stat=Error ("smtpd: mda command line could not be expanded: Interrupted system call") > same with %{rcpt-to} > > Where did you get the %{} syntax? I haven't seen it anywhere when > reading about this. > > > However, this does feel odd. I need to switch over as well, but still trying > > to wrap my brain around the new config. > > > virtual > > > action "relay" relay > > > match from local for local action "lmtp-local" > > > match from any for domain action "lmtp-local" > > > match from local for any action "relay" > > > > > > > > > but delivery attempts fail with Error ("mail.lmtp: sender must be specified > > > with -f") > > > > > > What would be the proper config for this? > > > -- > > > viq > > > -- Mark Patruck ( mark at wrapped.cx ) GPG key 0xF2865E51 / 187F F6D3 EE04 1DCE 1C74 F644 0D3C F66F F286 5E51 http://www.wrapped.cx
Re: Autocompletion with pass in ksh
On Sun, 6 May 2018 06:33:13 +0200 Niels Kobschaetzki wrote: > pass (www.password-store.org) is a password manager Did you mean https://www.passwordstore.org/ (no hyphen)? "the standard unix password manager" It depends on GnuPG, https://www.gnupg.org/ which is a GNU project. If this is part of an actual Unix standard, please do tell. "UNIX(R)" is a registered trademark of "The Open Group" http://www.opengroup.org/unix "The Open Group" is a very strange consortium of large tech corporations, none of which have anything to do with GnuPG or with this little utility "pass," however useful it might be.
Re: smtpd.conf new grammar
Hi Mark, viq, did either of you get it to work with the virtual table? Mine mostly works with: action "lmtp-local" mda "/usr/libexec/mail.lmtp -d unix:/var/dovecot/lmtp -f %{sender} %{rcpt}" virtual but it ignores the virtual table completely. If I miss out the ${rcpt}, I get a no recipient specified and if I have the {user.username} it gives a similar error. Did your virtual work or am I doing something daft? Regards - Nick On 27/05/2018 08:51, viq wrote: On 18-05-27 09:34:10, Mark Patruck wrote: For me it works with %{user.username} as mail.lmtp(8) user. See "FORMAT SPECIFIERS" in smtpd.conf(5) for details. Shows how well I read the man page With this it works, thank you! On Sun, May 27, 2018 at 09:04:56AM +0200, viq wrote: > On 18-05-26 19:18:56, Edgar Pettijohn III wrote: > > > > > Sorry, I've read the announcements, looked at man pages and examples, > > > but still didn't manage to figure out how to translate "deliver via dovecot > > > lmtp" > > > (to have sieve working) into the new syntax. So far my config was: > > > > > > table vusers ldap:/etc/mail/ldap.conf > > > table vdomains ldap:/etc/mail/ldap.conf > > > table passwd ldap:/etc/mail/ldap.conf > > > > > > accept from local for local virtual deliver to lmtp > > > "/var/dovecot/lmtp" > > > accept from any for domain virtual deliver to lmtp > > > "/var/dovecot/lmtp" > > > > > > > > > I tried changing those into: > > > > > > action "lmtp-local" mda "/usr/libexec/mail.lmtp -d /var/dovecot/lmtp" > > > > try: > > action "lmtp-local" mda "/usr/libexec/mail.lmtp -d unix:/var/dovecot/lmtp -f > > %{sender}" > > Well, this time I'm getting > result=TempFail stat=Error ("mail.lmtp: no recipient was specified") > so there's difference. So I tried > action "lmtp-local" mda "/usr/libexec/mail.lmtp -d unix:/var/dovecot/lmtp -f %{sender} %{recipient}" virtual > but that resulted in > result=TempFail stat=Error ("smtpd: mda command line could not be expanded: Interrupted system call") > same with %{rcpt-to} > > Where did you get the %{} syntax? I haven't seen it anywhere when > reading about this. > > > However, this does feel odd. I need to switch over as well, but still trying > > to wrap my brain around the new config. > > > virtual > > > action "relay" relay > > > match from local for local action "lmtp-local" > > > match from any for domain action "lmtp-local" > > > match from local for any action "relay" > > > > > > > > > but delivery attempts fail with Error ("mail.lmtp: sender must be specified > > > with -f") > > > > > > What would be the proper config for this? > > > -- > > > viq > > > -- Mark Patruck ( mark at wrapped.cx ) GPG key 0xF2865E51 / 187F F6D3 EE04 1DCE 1C74 F644 0D3C F66F F286 5E51 http://www.wrapped.cx
Re: smtpd.conf new grammar
On 05/28/18 03:50, Gilles Chehade wrote: On Sun, May 27, 2018 at 08:05:05AM -0500, ed...@pettijohn-web.com wrote: On May 27, 2018 2:10 AM, viqwrote: On 18-05-26 20:30:32, Amelia A Lewis wrote: On Sun, 27 May 2018 00:43:02 +0200, viq wrote: Sorry, I've read the announcements, looked at man pages and examples, but still didn't manage to figure out how to translate "deliver via dovecot lmtp" (to have sieve working) into the new syntax. So far my config was: table vusers ldap:/etc/mail/ldap.conf table vdomains ldap:/etc/mail/ldap.conf table passwd ldap:/etc/mail/ldap.conf accept from local for local virtual deliver to lmtp "/var/dovecot/lmtp" accept from any for domain virtual deliver to lmtp "/var/dovecot/lmtp" I tried changing those into: action "lmtp-local" mda "/usr/libexec/mail.lmtp -d /var/dovecot/lmtp" virtual action "relay" relay match from local for local action "lmtp-local" match from any for domain action "lmtp-local" match from local for any action "relay" but delivery attempts fail with Error ("mail.lmtp: sender must be specified with -f") What would be the proper config for this? Good point (and I'm going to need it, too, when I get to that point, for dovecot lmtp on one machine and dspam lmtp on another). Gilles, shouldn't there be a keyword 'lmtp' to go along with mbox/maildir/mda/relay/forward-only/expand-only? Comparing old (6.2) smtp.conf(5) with the updated one linked from your article, it seems to be the only missing method of delivery. Or perhaps it just got skipped in the man page? viq, have you tried action "lmtp-local" lmtp "/var/dovecot/lmtp" ? No, FAQ is very explict about it being removed: http://www.openbsd.org/faq/current.html#r20180524 That makes me sad :(. That is a really ugly line in the config. ok, let me explain the issue and if you gals and guys come up with some solution that isn't hackish, I won't oppose it :-) mbox is easy, no parameters need to be exposed to config, we can easily provide a syntaxic sugar: action foobar mbox = action foobar mda "/usr/libexec/mail.local ..." maildir is easy, no parameters needs to be exposed to config ... except for a single path that can be expressed as a STRING, we can easily give syntax sugar too. action foobar maildir = action foobar mda "/usr/libexec/mail.maildir ..." action foobar maildir path = action foobar mda "/usr/libexec/mail.maildir path ..." lmtp is not easy, it requires multiple parameters and people have a lot of different use-cases with it. I can't easily provide a syntaxic sugar and we must expose -d, -f, rcpt-to, etc... this isn't acceptable for me so if you manage to make all options fit in one STRING I will be ok but if I have to add keywords specific I won't. Something like: action "lmtp-local" lmtp "/var/dovecot/lmtp" would be fine by me, but people are using other parameters than just the lmtp socket, or maybe we can provide a syntaxic sugar for this case, and people using any other option must use the longer option ? Overall. I'm not too worried about it. After reading the new table(5). I can really see the power of the new config syntax. I was kind of thinking a new mailertable similar to sendmail might be nice. It would clean up the config, but I don't think its really worth spending time on. Its not like anyone prints out their smtpd.conf and frames it on the wall to look at daily. Haven't tried it, but the "/path/to/mail.lmtp -args" could probably go into a variable so it looks cleaner also: action "lmtp-local" mda $lmtp Edgar
ProLiant DL380 gen10
Hi, anyone running OpenBSD on ProLiant DL380 gen10? I need a box to replace my dying firewall. My employer strongly prefers HP for (networking) servers due to their presence here in Serbia. How good is their support is best described by the fact they don't have demo centre to try it out, while non-faulty hardware can not be returned. Other vendors are either non-present, or have even worse support. So I have to buy a few thousand worth "cat in a bag" and cross my fingers it will work. If there are people running OpenBSD on ProLiant DL380 gen 10 or some other current ProLiant please tell me about your experiences. Thank you in advance, -- Before enlightenment - chop wood, draw water. After enlightenment - chop wood, draw water. Marko Cupać https://www.mimar.rs/
Re: programs crash on Dell Latitude E7470
viq, Thanks so far for your suggestions. On 27 May 09:18 viq wrote: > On 18-05-25 14:15:08, Marco van Hulten wrote: > > Hello— > > > > I have a Dell Latitude E7470 with the latest OpenBSD snapshot. > > > > $ uname -a > > OpenBSD ultron.hulten.org 6.3 GENERIC.MP#45 amd64 > > > > dmesg is attached. > > > > Applications crash. For instance for Claws Mail: > > > > Segmentation fault (core dumped) claws-mail > > > > For Firefox there might be more useful output: > > > > ... > > runSafeSyncWithoutClone@resource://gre/modules/ExtensionUtils.jsm:73:129 > > runSafeWithoutClone@resource://gre/modules/ExtensionCommon.jsm:133:38 > > wrapPromise/<@resource://gre/modules/ExtensionCommon.jsm:312:13 > > ]] > > runSafe failure: cloning into [object Sandbox]: out of memory > > Sounds like ether you're running out of system memory, or running into > ulimit limits. `ulimit` == unlimited Memory consumption stays far below available real memory, never seen swapping (but I have 8 GB of swap). > Probably running memtest wouldn't go amiss either. I did one pass, which took 1h30 or so. No errors. I used stress(1) from packages. This stress --cpu 4 --io 4 --vm 2 --vm-bytes 700M --timeout 60s did not appear to cause issues except for the screen (connected to a docking station) two or three times about 1 second going black and coming back up again. Firefox, for instance, did not crash during this test. Bottom of dmesg (this time attached) says "CPU pipe B FIFO underrun". Marco OpenBSD 6.3-current (GENERIC.MP) #45: Thu May 24 19:22:57 MDT 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 16811323392 (16032MB) avail mem = 16293687296 (15538MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xeb460 (106 entries) bios0: vendor Dell Inc. version "1.12.3" date 12/11/2016 bios0: Dell Inc. Latitude E7470 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT FIDT MCFG HPET SSDT LPIT SSDT SSDT SSDT DBGP DBG2 SSDT UEFI SSDT SSDT MSDM SLIC TCPA DMAR ASF! acpi0: wakeup devices PEGP(S4) PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4) PXSX(S4) RP09(S4) PXSX(S4) RP10(S4) PXSX(S4) RP11(S4) PXSX(S4) RP12(S4) PXSX(S4) RP13(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz, 2095.92 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 24MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz, 2095.13 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz, 2095.13 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 1, core 0, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz, 2095.13 MHz cpu3:
Re: smtpd.conf new grammar
On Sun, May 27, 2018 at 08:05:05AM -0500, ed...@pettijohn-web.com wrote: > > On May 27, 2018 2:10 AM, viqwrote: > > > > On 18-05-26 20:30:32, Amelia A Lewis wrote: > > > On Sun, 27 May 2018 00:43:02 +0200, viq wrote: > > > > Sorry, I've read the announcements, looked at man pages and examples, > > > > but still didn't manage to figure out how to translate "deliver via > > > > dovecot > > > > lmtp" > > > > (to have sieve working) into the new syntax. So far my config was: > > > > > > > > table vusers ldap:/etc/mail/ldap.conf > > > > table vdomains ldap:/etc/mail/ldap.conf > > > > table passwd ldap:/etc/mail/ldap.conf > > > > > > > > accept from local for local virtual deliver to lmtp > > > > "/var/dovecot/lmtp" > > > > accept from any for domain virtual deliver to lmtp > > > > "/var/dovecot/lmtp" > > > > > > > > > > > > I tried changing those into: > > > > > > > > action "lmtp-local" mda "/usr/libexec/mail.lmtp -d /var/dovecot/lmtp" > > > > virtual > > > > action "relay" relay > > > > match from local for local action "lmtp-local" > > > > match from any for domain action "lmtp-local" > > > > match from local for any action "relay" > > > > > > > > > > > > but delivery attempts fail with Error ("mail.lmtp: sender must be > > > > specified > > > > with -f") > > > > > > > > What would be the proper config for this? > > > > > > Good point (and I'm going to need it, too, when I get to that point, > > > for dovecot lmtp on one machine and dspam lmtp on another). > > > > > > Gilles, shouldn't there be a keyword 'lmtp' to go along with > > > mbox/maildir/mda/relay/forward-only/expand-only? Comparing old (6.2) > > > smtp.conf(5) with the updated one linked from your article, it seems to > > > be the only missing method of delivery. > > > > > > Or perhaps it just got skipped in the man page? viq, have you tried > > > > > > action "lmtp-local" lmtp "/var/dovecot/lmtp" > > > > > > ? > > > > No, FAQ is very explict about it being removed: > > http://www.openbsd.org/faq/current.html#r20180524 > > > > That makes me sad :(. That is a really ugly line in the config. > ok, let me explain the issue and if you gals and guys come up with some solution that isn't hackish, I won't oppose it :-) mbox is easy, no parameters need to be exposed to config, we can easily provide a syntaxic sugar: action foobar mbox = action foobar mda "/usr/libexec/mail.local ..." maildir is easy, no parameters needs to be exposed to config ... except for a single path that can be expressed as a STRING, we can easily give syntax sugar too. action foobar maildir = action foobar mda "/usr/libexec/mail.maildir ..." action foobar maildir path = action foobar mda "/usr/libexec/mail.maildir path ..." lmtp is not easy, it requires multiple parameters and people have a lot of different use-cases with it. I can't easily provide a syntaxic sugar and we must expose -d, -f, rcpt-to, etc... this isn't acceptable for me so if you manage to make all options fit in one STRING I will be ok but if I have to add keywords specific I won't. Something like: > > > action "lmtp-local" lmtp "/var/dovecot/lmtp" would be fine by me, but people are using other parameters than just the lmtp socket, or maybe we can provide a syntaxic sugar for this case, and people using any other option must use the longer option ? -- Gilles Chehade https://www.poolp.org @poolpOrg