Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • 3 Votes
    3 Posts
    982 Views
    H
    Yeah, that makes sense. having a warning pop up before deleting an address that’s part of a mailing list would save a lot of confusion. even just a simple check and confirmation message would do the trick.
  • 0 Votes
    15 Posts
    4k Views
    avatar1024A
    @girish said: @avatar1024 said: Does that means one cannot use an external relay to replace the built in SMTP server if we use mailing lists (or the mailbox + forward implementation in Cloudron 10) - given most likely senders and mailing lists members with use random email providers? Yes, with a typical smart host / relay you cannot keep the original sender on list/forward delivery to Gmail/Posteo/etc. I want to mention that this is for the forwarding feature. Forwarding requires From address to be preserved. A mailing list behaves differently. It rewrites From/Reply-To etc and makes itself the originator of the email. This feature was never implemented in Cloudron. The forwarding feature was incorrectly labeled as mailing list and this misnaming is fixed in Cloudron 10. I guess we have to look into Distribution lists/mailing lists for the next releases, if you are interested in this. But the From address will change, not sure if it will work for your use case. It's usually meant for group@example.com or list@example.com style workflows. Thanks Girish, and yes a mailing list feature will be useful for some of my use case. I guess the point here is that it's a shame there isn't a way to use an external relay as a blanket replacement (i.e. covering all email features including forwarding) to the built-in SMTP server cause those services have added features to ensure reliable delivery (say when the server has a bad IP rep and gets regularly blocked notably by Microsoft stupid IP range blacklist approach).
  • 1 Votes
    30 Posts
    6k Views
    girishG
    With Cloudron 10, the forwarding logic is based on sieve. So, it's identical to roundcube.
  • SYMPA, or similar...

    Solved Support mailing-lists
    6
    2 Votes
    6 Posts
    3k Views
    girishG
    I think https://forum.cloudron.io/topic/1660/sympa-mailing-list and https://forum.cloudron.io/topic/6776/mailing-list-feature-basic-moderation are the relevant threads. @andrewwri maybe you can leave a note in the sympa thread as to how you installed sympa and how you are maintaining it. Maybe some notes on your current set up will also help (what is the email server? how is it interfacing with the email server etc). thanks!
  • Mailing List - answer to list not sender

    Moved Feature Requests mail mailing-lists
    6
    2 Votes
    6 Posts
    3k Views
    girishG
    Worthwhile reads - ``Reply-To'' Munging Considered Harmful and Reply-to-List, or Reply-to-All?
  • Mailing list using Sendgrid

    Support sendgrid mail mailing-lists
    5
    1 Votes
    5 Posts
    3k Views
    girishG
    Usually in email providers, there are two kinds of setups - identity based setup (to set up relaying a single email address) or a domain based setup ( to set up relaying for the entier domain). You have to set up domain based setup. This is because each app on Cloudron sends email with potentially a different email address (in the username portion).
  • Mailing Lists not really working

    Solved Support mail mailing-lists
    6
    0 Votes
    6 Posts
    3k Views
    chetbakerC
    @girish Thanks about that. That was the fix. Fastmail already whitelist it the domain and we are ready to go. Thanks!
  • 3 Votes
    10 Posts
    5k Views
    d19dotcaD
    @girish - this is not possible to do unfortunately in Cloudron it seems, but kindly tell me if I'm doing something wrong here. The redirect works for filtering out spam, in other words only non-spam messages get through to the endpoint email using a filter like this: # rule:[Forward non-spam messages] if allof (not header :contains "x-spam-status" "Yes,") { redirect "<externalEmailAddress>"; } However, all messages marked as spam still save in the mailbox regardless of any filters I set to discard them. In my case, I want the spam messages to be discarded/deleted automatically as there's no sense in them remaining in the "forwarding only" mailbox. It seems maybe there's a priority filter going on elsewhere in Cloudron that's overriding my sieve filter? Using a filter like this: # rule:[Discard spam messages on arrival] if allof (header :contains "x-spam-status" "Yes,") { discard; stop; } ... will still save the email in the Spam folder. I've tried variations of it too but no-dice. Basically I can't get any filters to work when it's an identified spam message, only filters when it's NOT spam. Here's a way to reproduce it: Set this filter in Roundcube: # rule:[Discard spam messages on arrival] if allof (header :contains "x-spam-status" "Yes,") { discard; stop; } Send a message to the email account using the GTUBE string which SpamAssassin automatically marks with 1000 points, it's basically a test for spam filters: XJS*C4JDBQADN1.NSBN3*2IDNEN*GTUBE-STANDARD-ANTI-UBE-TEST-EMAIL*C.34X See if the message is really discarded per the sieve filter or if it's still arriving in the Spam folder. In my cases, they still arrive in the Spam folder which seems to be incorrect behaviour. Edit: I wrote a dedicated bug for this instead: https://forum.cloudron.io/topic/5189/can-t-discard-spam-messages-on-arrival-using-sieve-filters/1
  • 1 Votes
    2 Posts
    1k Views
    girishG
    You can set flags on the email with sieve filters. I think this is only available in roundcube UI though. [image: bf4f52b4-5648-41a9-aca2-f799daadb640-image.png] Then, in thunderbird, you can highlight them accordingly - https://support.mozilla.org/en-US/kb/message-tags