Wallace not intercepting resource invitations

[Cornelius Hald]

Hi,

so it looks like wallaced is listening on port 10026 and I got log
messages like that one:

Feb 28 12:44:29 mail postfix/smtp[21690]: 75B58120211:
to=<resource-car-porsche at kodira.de>, relay=127.0.0.1[127.0.0.1]:10026,
delay=0.08, delays=0.05/0.02/0/0, dsn=2.0.0, status=sent (250 Ok)

So it looks like mail is correctly piped through wallace.

But shouldn't wallace consume those resource invitations completely? It
is not clear to me, why postfix tries to deliver that mail to a mailbox
that doesn't exist anyway...

Cheers,
Conny

On Sat, 2015-02-28 at 15:34 +0100, Cornelius Hald wrote:
> Hi Daniel,
> 
> thanks for asking.
> 
> Doing "grep -i wallace /var/log/maillog" doesn't give any hits, but in
> pykolab.log (loglevel 'debug') I see messages like the following, so I
> think mails are routed through wallace:
> 
> 2015-02-28 15:16:07,933 pykolab.wallace INFO Message is not an iTip
> message or does not contain any (valid) iTip.
> 2015-02-28 15:16:08,131 pykolab.wallace INFO Message is not an iTip
> message or does not contain any (valid) iTip events.
> 2015-02-28 15:16:08,134 pykolab.wallace INFO Accepting message
> in /var/spool/pykolab/wallace/footer/incoming/tmpLVPfIi (by module
> footer)
> 
> Those entries are not necessarily a result of sending a resource
> invitation. They might have a different origin.
> 
> What should I look for in /var/log/maillog to see whether or not mail is
> routed through wallace?
> 
> 
> In /etc/postfix/master.cf I have the following entries pointing to
> wallace:
> 
> [...]
> # Listener to re-inject email from Amavisd into Postfix
> 127.0.0.1:10025     inet        n       -       n       -       100
> smtpd
>     -o cleanup_service_name=cleanup_internal
>     -o content_filter=smtp-wallace:[127.0.0.1]:10026
>     -o local_recipient_maps=
>     -o relay_recipient_maps=
>     -o smtpd_restriction_classes=
>     -o smtpd_client_restrictions=
>     -o smtpd_helo_restrictions=
>     -o smtpd_sender_restrictions=
>     -o smtpd_recipient_restrictions=permit_mynetworks,reject
>     -o mynetworks=127.0.0.0/8
>     -o smtpd_authorized_xforward_hosts=127.0.0.0/8
> 
> # Filter email through Wallace
> smtp-wallace        unix        -       -       n       -       3
> smtp
>     -o smtp_data_done_timeout=1800
>     -o disable_dns_lookups=yes
>     -o smtp_send_xforward_command=yes
>     -o max_use=20
> 
> # Listener to re-inject email from Wallace into Postfix
> 127.0.0.1:10027     inet        n       -       n       -       100
> smtpd
>     -o cleanup_service_name=cleanup_internal
>     -o content_filter=
>     -o local_recipient_maps=
>     -o relay_recipient_maps=
>     -o smtpd_restriction_classes=
>     -o smtpd_client_restrictions=
>     -o smtpd_helo_restrictions=
>     -o smtpd_sender_restrictions=
>     -o smtpd_recipient_restrictions=permit_mynetworks,reject
>     -o mynetworks=127.0.0.0/8
>     -o smtpd_authorized_xforward_hosts=127.0.0.0/8
> [...]
> 
> 
> What do you think? Does any of this give a hint what's going wrong?
> 
> Thanks!
> Conny
> 
> 
> 
> On Sat, 2015-02-28 at 14:07 +0100, Daniel Hoffend wrote:
> > Hello Conny
> > 
> > Can you confirm that the message has been routed through wallace according to your mail.log? Every mail has to go through wallace. That's similar to amavisd.
> > 
> > Otherwise there are 2 possibilities:
> > 
> > 1) your mail flow in postfix is wrongly configured. (virtual-alias-maps, etc)
> > 
> > 2) your postfix isn't configured to route mails through wallace.
> > 
> > --
> > Regards
> > Daniel
> > 
> 
> _______________________________________________
> users mailing list
> users at lists.kolab.org
> https://lists.kolab.org/mailman/listinfo/users