Hi all,

Ubuntu 14.04, SOGo nightlies (3.0.2.20160409-1 at time of writing). Live server with working email. SOGo otherwise fully working.

I have SOGoEnableEMailAlarms set to yes in sogo.conf, OCSEMailAlarmsFolderURL correctly configured and a cron entry for the sogo user to run sogo-ealarms-notify.

Events with email reminders set correctly appear in sogo_sogo_alarms_folder in the database, and disappear at the right time. However, no emails.

Performing strace on sogo-ealarms-notify when it's called by cron reveals that the process is indeed reading the alarms folder in the database and reading the associated event from the database.

sogo-ealarms-notify then opens a connection to the SMTP server, and I see the following in strace:

connect(7, {sa_family=AF_INET, sin_port=htons(25), sin_addr=inet_addr("127.0.0.1")}, 16) = 0

fcntl(7, F_GETFL)                       = 0x2 (flags O_RDWR)

fcntl(7, F_SETFL, O_RDWR|O_NONBLOCK)    = 0

fcntl(7, F_GETFL)                       = 0x802 (flags O_RDWR|O_NONBLOCK)

getsockname(7, {sa_family=AF_INET, sin_port=htons(57822), sin_addr=inet_addr("127.0.0.1")}, [16]) = 0

recvfrom(7, 0x299f910, 512, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable)

poll([{fd=7, events=POLLRDNORM}], 1, 3600000) = 1 ([{fd=7, revents=POLLRDNORM}])

recvfrom(7, "220 my.host.com ESMTP Postfix (Ubuntu)\r\n", 512, 0, NULL, NULL) = 43

stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=250, ...}) = 0

open("/etc/hosts", O_RDONLY|O_CLOEXEC)  = 8

fstat(8, {st_mode=S_IFREG|0644, st_size=176, ...}) = 0

mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f5069b16000

read(8, "127.0.0.1 localhost.localdomain localhost\n99.99.99.99 my.host.com host1\n99.99.99.99 my.alias.com s18501073\n99.99.99.99 my.alias2.com\n", 4096) = 176

close(8)                                = 0

munmap(0x7f5069b16000, 4096)            = 0

sendto(7, "EHLO localhost.localdomain", 26, MSG_NOSIGNAL, NULL, 0) = 26

sendto(7, "\r\n", 2, MSG_NOSIGNAL, NULL, 0) = 2

recvfrom(7, 0x299f910, 512, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable)

poll([{fd=7, events=POLLRDNORM}], 1, 3600000) = 1 ([{fd=7, revents=POLLRDNORM}])

recvfrom(7, "250-my.host.com\r\n250-STARTTLS\r\n250-SIZE 10240000\r\n250-VRFY\r\n250-AUTH PLAIN LOGIN\r\n250-AUTH=PLAIN LOGIN\r\n250-ENHANCEDSTATUSCODES\r\n250-8BITMIME\r\n250 DSN\r\n", 512, 0, NULL, NULL) = 155

brk(0x29cc000)                          = 0x29cc000

sendto(7, "QUIT\r\n", 6, MSG_NOSIGNAL, NULL, 0) = 6

recvfrom(7, 0x299f910, 512, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable)

poll([{fd=7, events=POLLRDNORM}], 1, 3600000) = 1 ([{fd=7, revents=POLLRDNORM}])

recvfrom(7, "221 2.0.0 Bye\r\n", 512, 0, NULL, NULL) = 15

recvfrom(7, 0x299f910, 512, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable)

poll([{fd=7, events=POLLRDNORM}], 1, 3600000) = 1 ([{fd=7, revents=POLLRDNORM}])

recvfrom(7, "", 512, 0, NULL, NULL)     = 0

shutdown(7, SHUT_RDWR)                  = 0

close(7)                                = 0

(hostnames and IPs changed to protect a live server)

As you can see, sogo-ealarms-notify is connecting, sending EHLO, then QUITting without attempting to send any email. The postfix log (with debug) confirms this.

sogo-ealarms-notify appears to do this (connect/ehlo/quit) for every invitee in the event. An event with a single invitee (or none, so just the organiser) has one connection in strace. An event with multiple invitees causes sogo-ealarms-notify to make the same number of connections as there are invitees. However, as no data is ever sent I can't associate connections to invitee addresses - I'm making assumptions therefore.

Anyone any suggestions? Anyone got it working on 3.0.2 or 3.0.2 nightlies?

Peter.
--
users@sogo.nu
https://inverse.ca/sogo/lists

Reply via email to