Hello Edgar, I just found that the path is related to the home directory of the virtual user that is specified in /etc/passwd If you have a configuration that uses virtual users and that relies on a unix user _vmail then this unix user has an entry in /etc/passwd So the smtpd deamon uses the home directory path specified in /etc/passwd although it's might not be specified in the smtpd.confIs it normal that the home directory of that user should be used ?
Le samedi 6 janvier 2018 à 00:52:15 UTC+1, Edgar Pettijohn <ed...@pettijohn-web.com> a écrit : On Fri, Jan 05, 2018 at 11:09:13PM +0000, Mik J wrote: > Hello all, > What do you think about my initial question.When I receive an email, I have > the following messagewarn: smtpd: parent_forward_open: /var/mail/_vmail: No > such file or directory > With /var/mail... not /var/rep... like I wrote in my first message > I don't store my mails in /var/mail/_vmail. I mounted a NFS share to another > server and the mount point is not /var/mail > This message comes from smtpd.c > if (stat(directory, &sb) < 0) { > log_warn("warn: smtpd: parent_forward_open: %s", directory); > return -1; > } > > > or if (errno == ELOOP) > ... > else > log_warn("warn: smtpd: parent_forward_open: %s", > pathname); > return -1; > > > Regards > > > Le mercredi 3 janvier 2018 à 15:25:25 UTC+1, Scott Court <z...@z5t1.com> a >écrit : > You should include your entire smtpd.conf. > > That's ok; it's all good. > > > One thing though: I noticed that there have been several API version bumps > between 6.0.2 and the current git version in smtpd/smtpd-api.h (namely > PROC_*_API_VERSION has been bumped from 1 to 2). When I was working with the > git version the other day I realized that this change in the API version > breaks backwards compatibility with any extras that have been installed (from > OpenSMTPD-extras). > > This makes me wonder if this 6.0.3 release might actually warrant a larger > version number bump (maybe to 6.1.0 or even 7.0.0) to signify this backwards > incompatible change. > > On Tue, Jan 02, 2018 at 09:43:52AM -0500, Scott Court wrote: > > On 01/01/2018 07:19 PM, Mik J wrote: > > # smtpd -h > version: OpenSMTPD 6.0.0 > > Also, if anyone knows why 6.0.2 is not the version shipped in the > latest 6.2 openbsd. > > Thanks > > I have been wondering about this myself. After taking a look at the code > in the OpenBSD CVS tree though, it looks like the "6.0.0" version of > OpenSMTPD shipped with OpenBSD 6.2 is actually not the 6.0.0 version > available on opensmtpd.org. It appears that it is actually closer to a > recent fork of the CVS version of OpenSMTPD. > > Additionally, the OpenSMTPD version in OpenBSD has been upgraded with > the release of OpenBSD 6.1 and 6.2; however, the version number seems to > stay at "6.0.0" for some reason. I tried building OpenSMTPD 6.0.2 from > source the other day, just to find out it was actually older than the > "6.0.0" version in my stock OpenBSD 6.2. > > This seems very strange to me. > > > You are absolutely right. > > We used to have a release process specifically for OpenSMTPD when it was > using git as a main repository and synchronized to OpenBSD but since the > switch we never discussed our versionning despite the fact that there is > a different workflow and we often have many minor commits that we do not > think warrant a version update... but causes OpenSMTPD to have different > code for identical versions. > > In the meantime, I have bumped the version in OpenBSD -current to 6.0.3, > this will make it obvious that the code is more ahead than on github. > > This weekend, I will update the code on github and prepare a 6.0.3 minor > release so everyone gets the same code for that version, then we'll have > a discussion on how we will prevent this from happening in the future. > > This was entirely my fault so... apologies > > > >