-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Trying to build opensmtpd 7.7 on  a sparc64 running OpenBSD 7.3 I get the 
following:

./../usr.sbin/smtpd/queue_proc.o: In function `queue_proc_message_fd_r':
./../usr.sbin/smtpd/queue_proc.c:182: undefined reference to `imsg_get_fd'
./../usr.sbin/smtpd/scheduler_proc.o: In function `scheduler_proc_call':
./../usr.sbin/smtpd/scheduler_proc.c:43: undefined reference to `imsgbuf_flush'
./../usr.sbin/smtpd/scheduler_proc.c:64: undefined reference to `imsgbuf_read'
./../usr.sbin/smtpd/scheduler_proc.o: In function `scheduler_proc_init':
./../usr.sbin/smtpd/scheduler_proc.c:115: undefined reference to `imsgbuf_init'
./../usr.sbin/smtpd/scheduler_proc.c:117: undefined reference to 
`imsgbuf_allow_fdpass'
collect2: ld returned 1 exit status
*** Error 1 in mk/smtpd (Makefile:1286 'smtpd')
*** Error 1 in mk (Makefile:398 'all-recursive': @fail=;  if (target_option=k; 
case ${target_option-} in  ?) ;;  *) echo "am__make_running_w...)
*** Error 1 in . (Makefile:451 'all-recursive': @fail=;  if (target_option=k; 
case ${target_option-} in  ?) ;;  *) echo "am__make_running_wi...)
*** Error 2 in /usr/local/stars/opensmtpd-7.7.0p0 (Makefile:358 'all')

On OpenBSD 7.4 on an AMD64 I get 


>>> referenced by smtpd.c:933 (../../usr.sbin/smtpd/smtpd.c:933)
>>>               ../../usr.sbin/smtpd/smtpd.o:(setup_peers)
>>> referenced 5 more times
cc: error: linker command failed with exit code 1 (use -v to see invocation)
*** Error 1 in mk/smtpd (Makefile:1286 'smtpd')
*** Error 1 in mk (Makefile:398 'all-recursive': @fail=;  if (target_option=k; 
case ${target_option-} in  ?) ;;  *) echo "am__make_running_w...)
*** Error 1 in . (Makefile:451 'all-recursive': @fail=;  if (target_option=k; 
case ${target_option-} in  ?) ;;  *) echo "am__make_running_wi...)
*** Error 2 in /usr/local/stars/opensmtpd-7.7.0p0 (Makefile:358 'all')

Is this to be expected?  

RSVP Thanks,

Duncan (Dhu) Campbell

On Thu, 19 Jun 2025 20:35:11 +0300
Uolys <uo...@vivaldi.net> wrote:

> I am completely confused… Maybe I just don't understand the syntax of 
> aliases and virtusertable (a.k.a. virtual)? Sendmail treated both tables 
> as intended in the following format:
> 
> > root: uolys
> > postmaster: uolys
> > cron: uolys
> > info: uolys
> > …
> > vladas: uolys
> > uolys: vla...@on.lt
> 
> Where uolys is an internal user ID, and vladas — my real public name in 
> /etc/mail/aliases
> 
> /etc/mail/virtusertable was mainly for domains aliases in the same 
> localhost:
> 
> > @sala.online.lt  %1...@on.lt
> > @online.lt  %1...@on.lt
> 
> OpenSMTPd does not seem to support this method of name transfer, no such 
> example in table <https://man.openbsd.org/table.5> manual:
> 
> > user1                       otheruser
> > us...@example.org   otheruser1,otheruser2
> > @example.org                otheru...@example.com
> > @                   catch...@example.com
> 
> Could you give me please an example of the format in which I can correct 
> my alias or virtual tables for OpenSMTPd?
> 
> 
> On 6/19/25 18:55, BetaRays wrote:
> > On 2025-06-19 17:46, Uolys wrote:
> >> action "cyrus" lmtp "/var/cyrus/socket/lmtp rcpt-to <virtual>
> >> action "cyrus" lmtp "/var/cyrus/socket/lmtp rcpt-to <aliases>
> > You’re missing virtual <virtual> or alias <aliases>, rcpt-to is an 
> > optional argument for lmtp.
> >
> > Here is the option’s documentation from man smtpd.conf:
> >
> > lmtp destination [rcpt-to] Deliver the message to an LMTP server at 
> > destination.  The location may be expressed as host:port or as a UNIX 
> > socket. Optionally, rcpt-to might be specified to use the recipient 
> > email address (after expansion) instead of the local user in the LMTP 
> > session as RCPT TO.


  -- 
Je suis Canadien:
  Ce n'est pas Francais ou Anglais,
  C'est une esp`ece de sauvage. 
  Ne obliviscaris: vix ea nostra voco!

 *A mari ad mari ad mari*

  Duncan Patton a Campbell

-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQTKdleqECmr94McXWPR6f/NOjb3lQUCaFmhewAKCRDR6f/NOjb3
lZ8sAQCkjy6+8VagmZRfm9Ld2B+9DXJ7118XXfYkKfdZWlyZuwD+PeN3A2osR27S
daCzMEMh2Q2etW7xCdcvApHJm5W+kA8=
=2H9V
-----END PGP SIGNATURE-----

Reply via email to