Loading ...
Sorry, an error occurred while loading the content.

Re: Microsoft Outlook Meeting Schedule Converted To Plain Text

Expand Messages
  • Ralf Hildebrandt
    ... Neither Postfix nor amavisd do any conversion. -- Ralf Hildebrandt (Ralf.Hildebrandt@charite.de) plonk@charite.de Postfix - Einrichtung,
    Message 1 of 5 , Nov 1, 2006
    • 0 Attachment
      * mynullvoid <mynullvoid@...>:
      > Hi,
      >
      > I had setup my postfix and everything working fine, but my problem is that if any of my user send a meeting schedule invitation, the 'email' will be converted to plain text instead of an alert for the receipent to accept the invitation.

      Neither Postfix nor amavisd do any conversion.

      --
      Ralf Hildebrandt (Ralf.Hildebrandt@...) plonk@...
      Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155
      http://www.postfix-buch.com
      To rephrase, spam is not the answer. Spam is the question. Death is
      not the answer, but pretty close to it.
    • Victor Duchovni
      ... When message headers are malformed (don t start with Header-Name: , Postfix will insert a blank line between the valid headers and first invalid header,
      Message 2 of 5 , Nov 1, 2006
      • 0 Attachment
        On Wed, Nov 01, 2006 at 01:47:15PM +0100, Ralf Hildebrandt wrote:

        > * mynullvoid <mynullvoid@...>:
        > > Hi,
        > >
        > > I had setup my postfix and everything working fine, but my problem is that if any of my user send a meeting schedule invitation, the 'email' will be converted to plain text instead of an alert for the receipent to accept the invitation.
        >
        > Neither Postfix nor amavisd do any conversion.

        When message headers are malformed (don't start with "Header-Name:",
        Postfix will insert a blank line between the valid headers and first
        invalid header, which becomes part of the message body together with
        any subsequent possibly valid headers.

        Don't send broken messages, and they will be forwarded intact.

        --
        Viktor.

        Disclaimer: off-list followups get on-list replies or get ignored.
        Please do not ignore the "Reply-To" header.

        To unsubscribe from the postfix-users list, visit
        http://www.postfix.org/lists.html or click the link below:
        <mailto:majordomo@...?body=unsubscribe%20postfix-users>

        If my response solves your problem, the best way to thank me is to not
        send an "it worked, thanks" follow-up. If you must respond, please put
        "It worked, thanks" in the "Subject" so I can delete these quickly.
      • Dan Horne
        ... We have Outlook meeting requests going through postfix without issue. What I have seen in the past is that software that adds information to the body of
        Message 3 of 5 , Nov 1, 2006
        • 0 Attachment
          > >
          > > Neither Postfix nor amavisd do any conversion.
          >
          > When message headers are malformed (don't start with
          > "Header-Name:", Postfix will insert a blank line between the
          > valid headers and first invalid header, which becomes part of
          > the message body together with any subsequent possibly valid headers.
          >
          > Don't send broken messages, and they will be forwarded intact.
          >

          We have Outlook meeting requests going through postfix without issue.
          What I have seen in the past is that software that adds information to
          the body of emails (such as footers or signatures or disclaimers) will
          'break' these meeting requests and cause them to be displayed as plain
          text messages rather than being handled invisibly by Outlook. This
          won't be signatures or disclaimers added by Outlook, but rather by
          third-party software somewhere in the mail path.

          --DH

          CONFIDENTIALITY NOTICE:
          This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.

          SPAM-FREE 1.0(2476)
        • mynullvoid
          What I have in my mail setup are: [courier-imap]+[postfix]+[amavis-new]+[procmail] as of for amavis-new it have [clamav]+[spamassassin]. Spamassassin will
          Message 4 of 5 , Nov 1, 2006
          • 0 Attachment
            What I have in my mail setup are: [courier-imap]+[postfix]+[amavis-new]+[procmail] as of for amavis-new it have [clamav]+[spamassassin]. Spamassassin will interact with [pyzor]+[razor]+[dcc]. How do check which point it went wrong and how do I make the email intact without broken?
             
            Please advice.
             
            Thank you
             
            ================This is my main.cf=====================
            smtpd_banner = $myhostname ESMTP $mail_name (foobar)
            biff = no
            broken_sasl_auth_clients = yes
            command_directory = /usr/sbin
            config_directory = /etc/postfix
            content_filter = smtp-amavis:[127.0.0.1]:10024
            receive_override_options = no_address_mappings
            daemon_directory = /usr/lib/postfix
            default_process_limit = 512
            home_mailbox = Maildir/
            local_destination_recipient_limit = 300
            append_dot_mydomain = no
            delay_warning_time = 4h
            myhostname = mail.foobar.com.my
            alias_maps = hash:/etc/aliases
            alias_database = hash:/etc/aliases
            myorigin = /etc/mailname
            mydestination = foobar.com.my, localhost.localdomain, localhost.localdomain, localhost, foobar.com.my
            mydomain = foobar.com.my
            mynetworks = 127.0.0.0/8, 192.168.0.0/24, 192.168.2.0/24
            program_directory = /usr/lib/postfix
            mailbox_command = /usr/bin/procmail -a "$EXTENSION"
            mailbox_size_limit = 0
            message_size_limit = 0
            recipient_delimiter = +
            setgid_group = postdrop
            inet_interfaces = all
            smtpd_helo_required = yes
            disable_vrfy_command = yes
            smtpd_sender_restrictions =
                        permit_sasl_authenticated,
                        permit_mynetworks,
                        check_sender_access hash:/etc/postfix/maps/sender_access,
                        reject_unknown_sender_domain,
                        reject_unknown_address,
                        reject_rbl_client bl.spamcop.net,
                        reject_rbl_client sbl-xbl.spamhaus.org,
                        reject_rbl_client dul.dnsbl.sorbs.net,
                        reject_rbl_client web.dnsbl.sorbs.net,
                        reject_rbl_client zombie.dnsbl.sorbs.net,
                        reject_rbl_client cbl.abuseat.org,
                        reject_rbl_client dnsbl.njabl.org,
                        reject_rbl_client relays.ordb.org,
                        reject_rbl_client dnsbl-1.uceprotect.net,
                        reject_rbl_client dnsbl-2.uceprotect.net,
                        reject_rbl_client cn.rbl.cluecentral.net,
                        reject_rbl_client nigeria.blackholes.us,
                        reject_rbl_client brazil.blackholes.us,
            smtpd_recipient_restrictions =
                        permit_sasl_authenticated,
                        permit_mynetworks,
                        reject_non_fqdn_sender,
                        reject_non_fqdn_recipient,
                        reject_unknown_recipient_domain,
                        reject_unauth_destination,
                        reject_unverified_recipient,
                        reject_unauth_pipelining,
                        check_sender_access hash:/etc/postfix/maps/whitelist,
                        reject_rbl_client bl.spamcop.net,
                        reject_rbl_client dul.dnsbl.sorbs.net,
                        reject_rbl_client web.dnsbl.sorbs.net,
                        reject_rbl_client cbl.abuseat.org,
                        reject_rbl_client dnsbl.njabl.org,
                        reject_rbl_client sbl-xbl.spamhaus.org,
                        reject_rbl_client list.dsbl.org,
                        reject_rbl_client zombie.dnsbl.sorbs.net,
                        reject_rbl_client relays.ordb.org,
                        reject_rbl_client dnsbl-1.uceprotect.net,
                        reject_rbl_client dnsbl-2.uceprotect.net,
                        reject_rbl_client cn.rbl.cluecentral.net,
                        reject_rbl_client nigeria.blackholes.us,
                        reject_rbl_client brazil.blackholes.us,
                        check_policy_service inet:127.0.0.1:60000,
                        permit
            smtpd_data_restrictions =
                        reject_unauth_pipelining,
                        permit
            smtpd_sasl_auth_enable = yes
            smtpd_sasl_security_options = noanonymous
            smtpd_sasl_local_domain =
            broken_sasl_auth_clients = yes
            smtpd_tls_CAfile = /etc/postfix/ssl/cacert.pem
            smtpd_tls_cert_file = /etc/postfix/ssl/newcert.pem
            smtpd_tls_key_file = /etc/postfix/ssl/newreq.pem
            smtpd_tls_loglevel = 3
            smtpd_tls_received_header = yes
            smtpd_tls_session_cache_timeout = 3600s
            smtpd_use_tls = yes
            tls_random_source = dev:/dev/urandom
            transport_maps = hash:/etc/postfix/maps/transport
            ===========end==============

            Dan Horne <dan@...> wrote:
            > >
            > > Neither Postfix nor amavisd do any conversion.
            >
            > When message headers are malformed (don't start with
            > "Header-Name:", Postfix will insert a blank line between the
            > valid headers and first invalid header, which becomes part of
            > the message body together with any subsequent possibly valid headers.
            >
            > Don't send broken messages, and they will be forwarded intact.
            >

            We have Outlook meeting requests going through postfix without issue.
            What I have seen in the past is that software that adds information to
            the body of emails (such as footers or signatures or disclaimers) will
            'break' these meeting requests and cause them to be displayed as plain
            text messages rather than being handled invisibly by Outlook. This
            won't be signatures or disclaimers added by Outlook, but rather by
            third-party software somewhere in the mail path.

            --D
             


            Low, Low, Low Rates! Check out Yahoo! Messenger's cheap PC-to-Phone call rates.

          Your message has been successfully submitted and would be delivered to recipients shortly.