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


Skip to content
  • Email group forwarding

    Unsolved Support mail forwarding
    13
    2 Votes
    13 Posts
    85 Views
    jamesJ
    Hello @da5nsy @da5nsy said: but moved away from it because they couldn't get it to send emails reliably. Just as a cautious note. Freescout sends mails on a cron based task scheduler. Same with getting mails from the configured mailbox. This can be noticed as a failure to send or receive mails, but also enabled the feature of unsend mail because if you'd send right away there is no unsend mail in the mail protocol. If you find such errors with applications provided by Cloudron, please always report them in the forum so just in case if there is something wrong with the application, we can have a look and find a solution. Or at least, we can explain why it is behaving in a certain way.
  • 0 Votes
    4 Posts
    190 Views
    jamesJ
    Hello @estudios507 Thank you for the detailed report. I will try to assist you to my best capabilities. @estudios507 said in Cloudron rejects iCloud forwarding only when “Delete after forwarding” is enabled (SMTP 550 on MAIL FROM): Identify which Cloudron restriction/policy is triggering “Mail from domain ‘X’ is not allowed from your host” in this scenario. Regarding why this is happening. When iCloud forwards messages in delete mode, iCloud uses the original sender’s MAIL FROM (envelope-from) unchanged instead of rewriting it. If that original sender domain is hosted on the same Cloudron server, Cloudron sees an external connection (from iCloud’s outbound IP) claiming to send mail from its own domain. Cloudron treats that as spoofing and rejects it. @estudios507 said in Cloudron rejects iCloud forwarding only when “Delete after forwarding” is enabled (SMTP 550 on MAIL FROM): Confirm whether there is a supported and safe way in Cloudron to allow this specific flow (forwarding from iCloud with delete enabled) without broadly weakening anti-spoofing protections. There is also another topic regarding this issue with iCloud, see: https://forum.cloudron.io/topic/1998/mail-error-after-sending-message-mail-from-domain-example-com-is-not-allowed-from-your-host A fix is to add the iCloud servers to the domain A's SPF record. Your current SPF record is: dig TXT estudios507.com +short "v=spf1 a:mail.estudios507.com include:_spf.safewebservices.com ~all" You can edit that to include apple: "v=spf1 a:mail.estudios507.com include:_spf.safewebservices.com include:_spf.apple.com ~all" after that edit it can take some time to propagate, but this should resolve your issue.
  • Emails Failing DMARC Validation on Forwarding via Cloudron

    Solved Support email forwarding
    11
    1 Votes
    11 Posts
    3k Views
    jamesJ
    I suspect this is a similar issue to https://forum.cloudron.io/topic/14928 Marking as solved for now.
  • 1 Votes
    8 Posts
    3k Views
    fbartelsF
    @dsp76 said in Easy way to handle mail forwarding without setting up accounts for each?: individual "mailing list" for each receiver Yes, exactly.
  • 0 Votes
    6 Posts
    2k Views
    B
    @girish Wow that worked perfectly, thank you so much!
  • 3 Votes
    10 Posts
    3k 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
  • not working email forward when email relay ?

    Solved Support email relay forwarding
    20
    0 Votes
    20 Posts
    5k Views
    girishG
    @msbt thanks! I will try to see if I can make this just "work" in the next release.
  • Forward All Emails

    Solved Support mail forwarding sieve
    14
    0 Votes
    14 Posts
    5k Views
    W
    @marcusquinn Thanks for the info!
  • 0 Votes
    7 Posts
    4k Views
    d19dotcaD
    @girish Just wanted to say that this resolved the issue. Thank you! So to clarify, this was not a Cloudron issue but a simple DNS issue for the SPF records.