spacedriveapp / spacedriveapp/spacebot
the email is not working
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.4k
- Forks
- 367
- PR merge metrics
- No merged PRs in 30d
Description
Im trying to connect the email channel using imap and smtp, already got the app password and tested it on another script, after i configured i ask the agent to fetch the last email but it failed
and when sent email from another email, i dont see email channel created
this is my config
[messaging.email]
enabled = true
imap_host = "imap.gmail.com"
imap_port = 993
imap_username = "myemail@gmail.com"
imap_password = "app_password"
imap_use_tls = true
smtp_host = "smtp.gmail.com"
smtp_port = 587
smtp_username = "myemail@gmail.com"
smtp_password = "app_password"
smtp_use_starttls = true
from_address = "myemail@gmail.com"
from_name = "Fiqi Gading"
poll_interval_secs = 30
folders = ["INBOX"]
[[bindings]]
agent_id = "main"
channel = "email"
what is it that im missing?
btw i deploy it with docker compose
services:
spacebot:
image: ghcr.io/spacedriveapp/spacebot:latest
container_name: spacebot
restart: unless-stopped
ports:
- "19898:19898"
volumes:
- spacebot-data:/data
environment:
- ANTHROPIC_API_KEY=${ANTHROPIC_API_KEY}
# Optional:
# - DISCORD_BOT_TOKEN=${DISCORD_BOT_TOKEN}
volumes:
spacebot-data:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the spacebot Docker Compose service and its [messaging.email] configuration, then check the container output while requesting a fetch and sending a test message. Done means identifying the missing configuration or error and confirming that the email channel is created and can fetch mail.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, rust
- Domain
- backend, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100